This article will help you to have a quick check with Auto Provisioning issues, as we know there are 3 different modes(PNP Mode, DHCP Mode, RPS Mode(Cloud PBX & FQDN)), so please confirm your Auto provisioning mode and go to the corresponding section directly.
If you prefer to use online checklist please click the links according your AutoP mode, we will receive your feedback and give the response. If you prefer to check article please skip the below links and go to the main text.
PNP Mode online checklist
DHCP Mode online checklist
RPS Mode (Cloud PBX) online checklist
RPS Mode (FQDN) online checklist
PNP Mode
- Make sure the SIP phone model is supported (Auto Provisioning - Supported Devices (yeastar.com))
- Make sure the SIP phone enabled the PnP
- Reset the SIP phone if it was registered via AutoP before
- Make sure the SIP phone in the same segment with PBX
- Make sure the SIP phone’s IP is not blocked by PBX
- Check if the SIP phone get the URL or not?
- Check if the URL is available to download configuration file
- If your issue happens on step 6 or 7, contact us and provide the below files for further troubleshooting. PBX Pcap trace
PBX system log (After the SIP phone reboot)
SIP phone log (Take Yealink Phone as an example)
DHCP Mode
1. Make sure the SIP phone model is supported(Auto Provisioning - Supported Devices (yeastar.com)
2. Make sure there is only one DHCP server in the network
3. Make sure the SIP phone enabled the DHCP for AutoP
4. Reset the SIP phone if it was registered via AutoP before
5. If using an independent DHCP server, make sure it support setting OPTION 66, and the URL has been set to the OPTION 66. (If you are using the PBX as the DHCP server, please skip this step)
6. Make sure the SIP phone IP is not bloacked by the PBX
7. Check if the SIP phone get the URL or not?
8. Check if the URL is able to download the configuration file?
9. If your issue happens on step 7 or 8, contact us and provide the PBX pcap trace, system log and SIP phone local log for troubleshooting. (Please Refer the above PNP mode Step 8 to get the logs)
RPS Mode-(Cloud PBX)
1. Make sure the SIP phone model is supported(Auto Provisioning - Supported Devices (yeastar.com)
2. Reset the SIP phone if it was registered via AutoP before
3. Make sure the SIP phone IP is not bloacked by the PBX
4. Make sure PBX adds the SIP phone to the RPS server successfully
5. Make sure the SIP phone has configured correct DNS to be able to resolve the RPS server.
6. Make sure the SIP phone gets the URL and you can download the configuration file with the URL.
7. If you enabled the Authentication for first time, make sure you input correct credentials
8. Disable the 'Only Accept Trusted Certificates' on the SIP phone to try.
9. If all above steps can not resolve the problem please contact us and provide the PBX pcap, system log, and SIP phone local for the troubleshooting.(Refer to the Step 8 of PNP mode to get the logs)
RPS Mode (FQDN)
1. Make sure the SIP phone model is supported(Auto Provisioning - Supported Devices (yeastar.com)
2. Reset the SIP phone if it was registered via AutoP before
3. Make sure the SIP phone IP is not bloacked by the PBX
4. Make sure PBX adds the SIP phone to the RPS server successfully
5. Make sure the SIP access and Web access have been enabled
6. Make sure the SIP phone has configured correct DNS to be able to resolve the RPS server
7. Make sure the SIP phone gets the URL and you can download the configuration file with the URL
8. If you enabled the Authentication for first time, make sure you input correct credentials
9. Disable the 'Only Accept Trusted Certificates' on the SIP phone to try.
10. If all above steps can not resolve the problem please contact us and provide the PBX pcap, system log, and SIP phone local for the troubleshooting.(Refer to the Step 8 of PNP mode to get the logs)
0 Comments