Provision Grandstream FXS Gateway with Yeastar P-Series Cloud Edition

This topic takes Grandstream HT802 (firmware: 1.0.63.3) as an example to introduce how to provision a Grandstream FXS gateway with Yeastar P-Series Cloud Edition.

Requirements

The firmwares of Grandstream FXS gateway and Yeastar PBX meet the following requirements.
Model Phone Requirement PBX Requirement
GXW4216 1.0.23.4 or later 84.6.0.24 or later
GXW4224 1.0.23.4 or later 84.6.0.24 or later
GXW4232 1.0.23.4 or later 84.6.0.24 or later
GXW4248 1.0.23.4 or later 84.6.0.24 or later
HT801 1.0.63.3 or later 84.6.0.24 or later
HT802 1.0.63.3 or later 84.6.0.24 or later
HT812 1.0.5.10 or later 84.6.0.24 or later
HT814 1.0.63.3 or later 84.6.0.24 or later
HT818 1.0.63.3 or later 84.6.0.24 or later

Prerequisites

  • Make sure that there is only one DHCP server in the subnet where the gateways are deployed, or the gateways may fail to obtain IP addresses.
  • Make sure that you have downloaded the template for the desired model (Path: Auto Provisioning > Resource Repository > Default Templates).
  • RESET the gateway if it is previously used, then assign an IP address to it.
  • Gather information of the gateway, including Vendor, Model, and MAC address.

Procedure

Step 1. Add the Grandstream gateway on PBX

Add the gateway on PBX. The PBX will generate a configuration file based on the gateway's MAC address.

  1. Log in to PBX web portal, go to Auto Provisioning > Phones.
  2. Click Add > Add.
  3. In the IP Phone section, enter the following information.

    • Vendor: Select Grandstream.
    • Model: Select a model. In this example, select HT802.
    • MAC Address: Enter the MAC address of the gateway.
  4. 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 model, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
    • Provisioning Link: A provisioning link is automatically generated, which points to the location where the gateway's configuration file is stored.
  5. In the Assign Extension section, assign extensions for handsets according to your needs.
    Note: The assigned extensions will be associated with the gateway's FXS ports, and the analog terminals connected to the ports will then use the extension numbers for calls.
    • To assign extensions one by one, select the checkbox of corresponding handset, then select the desired extension in the Extension drop-down list.

    • To assign extensions in bulk, set the extension range in the Start Extension and End Extension drop-down lists, then click Assign Extension.

      Handsets are automatically enabled and assigned with available extensions in sequence.

    Tip: If your desired extension is not listed in the drop-down list, it indicates that the extension has been associated with an IP phone.
  6. Optional: In the Preference section, change the admin password in the Admin Phone Password field as needed.
    Note: The default admin password of the gateway is admin.

  7. Click Save.

Step 2. Configure DHCP option 66 on DHCP server

In the subnet where the gateway is deployed, use the generated provisioning link to configure option 66 on the DHCP Server.

  1. On PBX web portal, copy the provisioning link from the gateway's detail page.

  2. On the DHCP server, set up option 66 with the provisioning link.

    In this example, the configuration is shown below:

Result

  • After the gateway is manually rebooted, it gets an IP address from the DHCP server, downloads the configurations from the PBX via the provisioning link, and applies the settings automatically.
  • The extension is successfully registered on the IP phone. You can check the registration status on Auto Provisioning > Phone on the PBX web portal.