Auto Provision Grandstream IP Phone with Yeastar P-Series Software Edition
This topic takes Grandstream GPR2602 (firmware: 1.0.3.67) as an example to introduce how to auto provision a Grandstream IP phone with Yeastar P-Series Software Edition in Local Area Network (LAN).
Requirements
The firmwares of Grandstream IP Phone and Yeastar PBX meet the following requirements.
Model | Phone Requirement | PBX Requirement | Supported Auto Provisioning Method |
---|---|---|---|
GXP1610 | 1.0.7.13 or later |
83.4.0.17 or later |
|
GXP1620 | 1.0.7.13 or later |
83.4.0.17 or later |
|
GXP1625 | 1.0.7.13 or later |
83.4.0.17 or later |
|
GXP1628 | 1.0.7.13 or later |
83.4.0.17 or later |
|
GXP1630 | 1.0.7.13 or later |
83.4.0.17 or later |
|
GXP2130 | 1.0.11.16 or later |
83.4.0.17 or later |
|
GXP2135 | 1.0.11.16 or later |
83.4.0.17 or later |
|
GXP2140 | 1.0.11.16 or later |
83.4.0.17 or later |
|
GXP2160 | 1.0.11.16 or later |
83.4.0.17 or later |
|
GXP2170 | 1.0.11.16 or later |
83.4.0.17 or later |
|
GAC2500 | 1.0.3.45 or later |
83.11.0.22 or later |
|
GAC2570 | 1.0.1.36 or later |
83.11.0.22 or later |
|
GRP2601 | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2601P | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2602 | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2602P | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2602G | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2602W | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2603 | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2603P | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2604 | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2604P | 1.0.3.63 or later |
83.7.0.51 or later |
|
GRP2612 | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2612P | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2612G | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2612W | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2613 | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2614 | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2615 | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2616 | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2624 | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2634 | 1.0.7.25 or later |
83.7.0.51 or later |
|
GRP2670 | 1.0.7.25 or later |
83.7.0.51 or later |
|
Scenarios
The provisioning methods and operations vary depending on the network environment of Grandstream IP phone and Yeastar PBX, as the following table shows:
Scenario | Description |
---|---|
IP Phone and PBX are in the SAME subnet | In this scenario, you can provision the Grandstream IP phone
with the PBX via PnP
method. For more information, see Auto provision a Grandstream IP phone in the same subnet (PnP). |
IP Phone and PBX are in DIFFERENT subnets | In this scenario, you can provision the Grandstream IP phone
with the PBX via DHCP method. For more information, see Auto provision a Grandstream IP phone in different subnets (DHCP) |
Auto provision a Grandstream IP phone in the same subnet (PnP)
In this example, the Grandstream IP phone (IP: 192.168.28.205
) and
the Yeastar PBX (IP: 192.168.28.39
) are both deployed in subnet
28.
- Prerequisites
-
- Make sure that you have downloaded the template for the desired phone model (Path: ).
- If the IP phone is previously used, you need to RESET the IP phone, then re-configure the network settings for the phone.
- Procedure
-
- Log in to PBX web portal, go to
The IP phones detected by the PBX via PnP are displayed in the phone list.
. - Click beside the Grandstream IP phone.
- Optional: In the Options section,
select a desired template from the Template
drop-down list.Note: You can select the default template corresponding to the phone model, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
- In the Assign Extension
section, assign an extension to the IP phone.Note: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with an IP phone or gateway.
- To release the extension from the associated IP phone or gateway, see Release an Extension from a Provisioned IP Phone/Gateway.
- To assign the extension to the phone without releasing it from the previously associated device, you can configure the concurrent registration setting for the extension, as the PBX only allows an extension to register with one SIP endpoint by default.
- Click Save.
- Log in to PBX web portal, go to
- Result
-
Note: Some IP phones will reboot automatically. If not, you need to manually reboot the phone to make the configurations take effect.
- What to do next
- By default, Grandstream IP phone enables all available codecs for its accounts, which may lead to issues with outgoing calls. Therefore, it is recommended to remove unnecessary codecs for the account that has been registered with the PBX extension.
Auto provision a Grandstream IP phone in different subnets (DHCP)
In this example, the Grandstream IP phone and DHCP server are deployed in subnet 28,
while the Yeastar PBX (IP: 192.168.20.58
) is deployed in subnet
20.
- Prerequisites
-
- Make sure that there is only one DHCP server running in the subnet where the IP phone is deployed, or the IP phone would fail to obtain an IP address.
- Make sure that the IP phone and PBX can communicate with each other over the subnets.
- Make sure that you have downloaded the template for the desired phone model (Path: ).
- RESET the IP phone if it is previously used.
- Gather information of IP phone, including Vendor, Model, and MAC address.
- Procedure
- Step 1. Enable Remote Registration feature for the extension on PBX
- Enable the Remote Registration feature for the extension to be assigned to the phone, so that the extension can be registered in a different subnet.
- Step 2. Add the Grandstream IP phone on PBX
Add the IP phone on PBX. The PBX will generate a configuration file based on the phone's MAC address.
- On PBX web portal, go to .
- Click .
- In the IP Phone section, enter the following
phone information.
- Vendor: Select Grandstream.
- Model: Select the phone model. In this example, select GRP2602.
- MAC Address: Enter the MAC address of the IP phone.
- In the Options section, configure the
following settings.
- Template: Select a desired template
from the drop-down list.Note: You can select the default template corresponding to the phone model, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
- Provisioning Method: Select
DHCP (In the Office).
A provisioning link is automatically generated and displayed in the Provisioning Link field. This provisioning link points to the location where the phone's configuration file is stored.
- Template: Select a desired template
from the drop-down list.
- In the Assign Extension
section, assign an extension to the IP phone.Note: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with an IP phone or gateway.
- To release the extension from the associated IP phone or gateway, see Release an Extension from a Provisioned IP Phone/Gateway.
- To assign the extension to the phone without releasing it from the previously associated device, you can configure the concurrent registration setting for the extension, as the PBX only allows an extension to register with one SIP endpoint by default.
- Click Save.
- Step 3. Configure DHCP option 66 on DHCP server
In the subnet where the IP phone is deployed, use the generated provisioning link to configure option 66 on the DHCP Server.
- On PBX web portal, copy the provisioning link from the phone's detail page.
- On the DHCP server, set up option 66 with the
provisioning link.
In this example, the configuration on a router's DHCP server is shown below.
- Result
-
Note: Some IP phones will reboot automatically. If not, you need to manually reboot the phone to make the configurations take effect.
- What to do next
- By default, Grandstream IP phone enables all available codecs for its accounts, which may lead to issues with outgoing calls. Therefore, it is recommended to remove unnecessary codecs for the account that has been registered with the PBX extension.