Auto Provisioning - FAQ

This topic provides answers to commonly asked questions about Auto Provisioning.

FAQs

Why the devices in the local network are not displayed in the Auto Provisioning list?

The causes and solutions are as follow:

Cause Solution
The device's IP address is not in the same network segment as the PBX. Change the device's IP address to an IP address that is in the same network segment as the PBX.
The device does not support the PnP function. Contact your device vendor to check if the device supports PnP.
The PnP function is not enabled on the device. Enable the PnP feature for the device.
The PBX did not detect the devices in the local network.

The PnP-enabled devices will broadcast a PnP SUBSCRIBE message during startup, and then the PBX can detect the devices by receiving the PnP SUSCRIBE message. If the devices do not receive PnP SUBSCRIBE message, the PBX cannot detect the devices.

Reboot your devices to allow your devices to send PnP SUBSCRIBE message.

What provisioning protocol does Auto Provisioning support?

Yeastar P-Series PBX System Auto Provisioning uses HTTP protocol to transmit configuration files.

Why can't the devices be auto provisioned?

The causes and solutions are as follow:

Cause Solution
The devices are not supported for Auto Provisioning by Yeastar P-Series PBX System. See Auto Provisioning - Supported Devices and make sure that your devices are supported.
The features or parameters to be provisioned are not supported on the devices. Contact your device vendor to ensure that the features or parameters are supported for the devices.
You don't trigger the devices to update configuration after modifying the settings for an extension user. Go to Auto Provisioning > Phone or Gateway, re-provision the corresponding devices after modifying settings.
The configuration parameters configured in the advanced custom template are incorrect. Check the custom template to see if the parameters are correct.
The variable of parameters defined in the advanced custom template is modified, which causes configuration failure on PBX management portal. Check the custom template to see if the variables are correct.

For more information, see Variables in-templates.

Why can't some function keys be displayed on the IP phone?

The number of function keys you assign to an extension exceeds the number of programmable keys, the redundant function keys cannot take effect.

Why don't see the RPS Auto Provisioning method option?

The causes and solutions are as follow:
Cause Solution
The devices are not supported for RPS Auto Provisioning. Check the supported Auto Provisioning method of the device in Auto Provisioning - Supported Devices.

Network settings for remote registration is not configured on the PBX.

To register remote extension on IP phones, you need to configure SIP NAT on the PBX and forward ports on router.
For more information, see Configure Network for Remote Access by a Domain Name and Configure Network for Remote Access by a Public IP Address.
Note: Yeastar-provided FQDN is not supported for remote registration of IP phones.