Auto Provision Cisco SPA500 IP Phone with Yeastar P-Series PBX System

This topic takes Cisco SPA502G (firmware: 7.6.2c) as an example to describe how to auto provision Cisco SPA500 IP phone with Yeastar P-Series PBX System.

Note: The process in this topic is applicable only to IP phones of Cisco SPA500 Series. For more information about auto provisioning IP phones of other series, see Auto Provision Cisco IP Phone with Yeastar P-Series PBX System.

Requirements

The firmwares of Cisco IP phone and Yeastar PBX meet the following requirements.
Model Phone Requirement PBX Requirement Supported Auto Provisioning Method
SPA501G 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA502G 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA504G 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA508G 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA509G 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA512G 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA514G 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA301 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA303 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link
SPA525G2 7.4.7 or later

37.19.0.110 or later

  • DHCP
  • Provision Link

Scenarios

According to the network environment of Cisco IP phone and Yeastar PBX, you can auto provision IP phones using the PBX's built-in DHCP server or a third-party DHCP server, as the following table shows.

Scenario Description
IP Phone and PBX are in the SAME subnet In this scenario, you can provision the Cisco IP phone using the PBX built-in DHCP server to deliver a PBX-provided provisioning link to the IP phone. In this way, the phone can retrieve configurations from the PBX using the given link.
Note: If there is already a DHCP server running in the subnet, you can directly set up DHCP option 66 with PBX-provided provisioning link on the DHCP server.

For more information, see Auto provision a Cisco IP phone in the same subnet.

IP Phone and PBX are in DIFFERENT subnets (within the same LAN) or DIFFERENT networks In this scenario, you can provision the Cisco IP phone using DHCP option 66 of a third-party DHCP server to deliver a PBX-provided provisioning link to the IP phone. In this way, the phone can retrieve configurations from the PBX using the given link.

For more information, see Auto provision a Cisco IP phone in different subnets (within the same LAN) or different networks.

Auto provision a Cisco IP phone in the same subnet

Prerequisites
  • Make sure that you have downloaded the template for the desired phone model (Path: Auto Provisioning > Resource Repository > Default Templates).
  • Make sure that no DHCP server is active on the same subnet as the IP phone.
  • RESET the IP phone if it is previously used.
  • Gather information of IP phone, including Vendor, Model, and MAC address.
Procedure
Step 1. Set the PBX as a DHCP server
  1. Log in to PBX web portal, go to System > Network, click DHCP Server tab.
  2. Turn on the DHCP Server, and complete the following network configurations.
    • Gateway: Specify the IP address of the default gateway for the DHCP server.
    • Subnet Mask: Specify the subnet mask used to subdivide your IP address.
    • Preferred DNS Server: Specify a DNS server for the DHCP server.
    • Alternative DNS Server: Optional. Specify a secondary DNS server for the DHCP server.
    • DHCP Address Range: Specify the IP address range that will be allocated to DHCP clients.
    • NTP Server: Enter the IP address of an NTP server.
      Note: The default value is the IP address of the PBX, which can synchronize the network time of the client devices with the PBX.
  3. Click Save.

    The Status field displays Running, indicating the DHCP server is running.

Step 2. Add the Cisco IP phone on PBX
  1. On PBX web portal, go to Auto Provisioning > Phones.
  2. Click Add > Add.
  3. In the IP Phone section, enter the following phone information.

    • Vendor: Select Cisco.
    • Model: Select a phone model. In this example, select SPA502G.
    • MAC Address: Enter the MAC address of the IP phone.
  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 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.

  5. 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.
  6. Click Save.
Result
Note: Some IP phones will reboot automatically. If not, you need to manually reboot the phone to make the configurations take effect.
  • After the phone is rebooted, it gets an IP address from the PBX built-in DHCP server, download the configurations from the PBX and applies the settings automatically.
  • The extension is successfully registered on the IP phone. You can check the extension registration status on Auto Provisioning > Phones on the PBX web portal.

Auto provision a Cisco IP phone in different subnets (within the same LAN) or different networks

Prerequisites
  • Make sure that there is only one DHCP server running in the same subnet as the IP phone, or the IP phone would fail to obtain an IP address.
  • RESET the IP phone if it is previously used.
  • Gather information of IP phone, including Vendor, Model, and MAC address.
  • Make sure that you have downloaded the template for the desired phone model (Path: Auto Provisioning > Resource Repository > Default Templates).
  • Make sure that you have completed the corresponding settings shown below according to the network environment of Cisco IP phone and Yeastar PBX.
    Network Environment Setting
    IP Phone and PBX are in DIFFERENT subnets (within the same LAN)
    • Make sure that the two subnets can communicates with each other.
    • Enable the Remote Registration feature for the extension (Path: Extension and Trunk > Extension > > Security > SIP Security > Allow Remote Registration).

    IP Phone and PBX are in DIFFERENT networks Remotely provision an IP phone using Yeastar FQDN
    • Subscribe to Enterprise Plan or Ultimate Plan for the PBX to ensure that the FQDN is available.
    • Grant remote SIP access permission for the extension (Path: System > Network > Yeastar FQDN > Features > SIP Access).

    Remotely provision an IP phone using public IP address / domain name
    • Configure PBX network for remote access by a public IP address, by an external host domain name, or by a Yeastar domain name.
      Important: The following PBX ports MUST be forwarded for RPS provisioning.
      • RTP ports
      • SIP port
      • Web Server port
    • Complete the following settings for the extension to be assigned to the IP phone:
      • Enable NAT for the extension (Path: Extension and Trunk > Extension > > Advanced > VoIP Settings > NAT).

      • Enable the Remote Registration feature for the extension (Path: Extension and Trunk > Extension > > Security > SIP Security > Allow Remote Registration).

Procedure
Step 1. Add the Cisco IP phone on PBX

Add the IP phone on PBX. The PBX will generate a configuration file based on the phone'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 phone information.

    • Vendor: Select Cisco.
    • Model: Select a phone model. In this example, select SPA502G.
    • MAC Address: Enter the MAC address of the IP phone.
  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 phone model, or customize your own template. For more information, see Create a Custom Auto Provisioning Template.
    • Provisioning Method: Select the provisioning method according to your needs.
      Provisioning Method Description
      DHCP (In the Office) Suitable for provisioning the IP phone that is located in different subnets within the same LAN.
      Provision Link (Remote) Suitable for provisioning the IP phone located in a remote network, and the IP phone will access the PBX using public IP address / domain name to retrieve configuration files.
      Provision Link - FQDN (Remote) Suitable for provisioning the IP phone located in a remote network, and the IP phone will access the PBX using Yeastar FQDN to retrieve configuration files.
      Note: Note down the provisioning link, as you will use it later.
  5. 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.
  6. Click Save.

    The IP phone is added and displayed in the Auto Provisioning phone list.

Step 2. Configure DHCP option 66 on DHCP server

On the DHCP server in the same subnet as the IP phone, use the provisioning link obtained from Yeastar P-Series PBX System to configure option 66 on the DHCP Server.

In this example, the configuration is shown below.

Results
  • After the IP phone is 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 extension registration status on Auto Provisioning > Phones on the PBX web portal.