Vodia provisioning for Grandstream desktop phones involves several key steps to ensure seamless integration with our PBX. Administrators must first map the MAC address of each phone to a PBX extension, set the necessary provisioning parameters and enable MAC-based provisioning for added security. Grandstream phones require specific configuration within their web interface, where the provisioning server address must be set to the PBX's URL. For phones located on the same local area network (LAN), Vodia offers a simplified provisioning process that allows for automatic detection and setup with minimal user input.
When provisioning a Grandstream phone, you should first set the required settings on the PBX as shown in the provisioning document Steps Before Provisioning.
It is important to note in the document "Steps Before Provisioning" how to map the MAC address of the phone to the PBX extension under the registration tab as shown below.
It is also important to note in the document "Steps Before Provisioning" under Domain > Advanced > General Settings > Provisioning Parameters(as shown again below).
The Authentication user, Authentication password and Authentication PIN settings allow administrators to provision phones and log in to a phone’s web interface remotely. These settings enable administrators to use identical usernames and passwords for all devices in a domain, simplifying the authentication process from the GUI of the phone. The password will bypass users’ passwords (the web interface passwords), so they won't be able to use their passwords; hence, this setting can be used to keep users out of the phone’s web interface and prevent them from inadvertently changing anything.
For provisioning buttons, the setting up of buttons is described in buttons. There you will see how to prepare a new buttons profile, how to set up the individual buttons (like BLF) and how to map that profile to a specific extension. The numbers for the buttons correspond to the buttons on the phone. If a number isn't added in the profile, that button will not be set on the phone.
Open MAC Provisioning
For security reasons, navigate to the extension level and activate "Open account for MAC based provisioning", as shown, to allow the phone to provision to that specific account.
Grandstream Phone Settings for Auto Provisioning
Log into the web interface of the phone and, according to the model, navigate to the page where you can enter the provisioning server address. In model GXP2200, the setting is called Config Server Path - it's found on page "Maintenance" -> "Upgrade" as shown below. In other models it could be on "Upgrade" and "Advanced" page or something else that needs to be found in the documentation of the respective model.
In "Config Server Path" setting, add this URL PBXIP/prov where the PBXIP is the IP or resolvable domain of the pbx server.
Make sure that "Upgrade Via" (if present) is set to "HTTP".
Press Save. Now you can reboot the phone for provisioning.
Setup Devices in LAN
If your phone is in the same LAN as the PBX, then you don't have to do many of the above things, and you can simply provision almost any phone with a single press of a button by using this feature of the PBX. Make sure the phone is factory reset (or at least has the default username and password). You still have to do the Steps Before Provisioning but, after that, just go to the PBX page Setup Devices in LAN where the PBX will show you all the phones it has automatically detected in the LAN. You simply choose the phones you want to provision, assign each one a domain and extension and press "Setup" - that's it. The phones will be provisioned. For details on this feature, please go to: Setup Devices in LAN.
GRP2612/13/14
Vodia PBX 63.1 and higher supports Grandstream GRP2612/13/14 models. The provisioning is the same as it is with the other models, with the following differences:
LAN provisioning: Because Grandstream phones now use a device-dependent password for the web interface - the zero-touch no longer works. To have this working, you now need to log in to the web interface of the phone and use the password printed on the back of the phone to set the config server path to the path to the PBX. Cloud provisioning using Grandstream RPS should still work the same. For the LAN provisioning follow these steps:
Add the phone MAC address to the extension and make sure that the extension is opened up for provisioning/pairing with the phone.
Power the device up and look up the IP address of the phone. This can be done with the keyboard of the phone.
Log in to the web interface of the phone. The username is "admin" and the password is printed on the back of the device. The PBX will provision the domain admin password into the phone after the phone was configured the first time.
Navigate to "maintenance" and "upgrade and provisioning". Set the "Config Server Path" to the address of the PBX, e.g. 192.168.1.2 and make sure that the "Config Upgrade via" is set to HTTPS.
Press the "save and apply" button. The phone should go ahead and fetch the configuration from the PBX. You will see a symbol on the screen of the device indicating it's pulling the configuration from the network.
After the phone receives its original configuration, you can go ahead and change the button configuration or make other changes to the configuration.
Buttons: The phones need at least one private line for the buttons. If there is no private line, the phone may reject the entire configuration.
Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.
PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.
V70 introduces emergency alerts and notifications designed to ensure critical events are not missed and responses happen immediately. Alerts can be triggered directly by users, delivered across multiple channels including phones, email, mobile apps, and SMS, and can automatically initiate calls to predefined numbers. Administrators have full control over how alerts are configured, enabling consistent, reliable handling of incidents across real-world, multi-tenant environments.