P Serial PBX supports 3 modes to do the auto provisioning for IP phones.
(1) PnP
(2) DHCP
(3) RPS (P Cloud Edition only uses RPS mode.)
Here introduce separately if auto provision failed by the 3 modes of auto provision failed on P Serial PBX.
(1) PnP
Step1
If the IP phone can't be scanned out after the phone reboot on the auto provision webpage.
Check the network. Make sure the IP phone is in the same segment as PBX.
Step2
If the step1 is finished and has done the auto provision, follow below to check, please.
Check the auto provision URL and PnP setting on the IP phone webpage.
Step3
If it doesn't show auto provision URL on the IP phone webpage.
①Check the blocked IP on PBX.
②Check the IP Phone concurrent registrations.
③Phone reset and phone reboot if it is the first time to auto provisioning.
④Disable the phone certificate authority. If the certificate is out of date, it will fail to auto provision.
Step4
If it shows the auto provision URL on the IP phone webpage.
①Check whether the server IP/Domain in the URL is your PBX or not.
If not, it means has been auto provisioned on the other PBX before.
Try to login the other PBX and release then delete the record.
②Try to paste the link with your IP phone mac name to check if the file can be downloaded or not.
e.g.The URL format would be like this:
http://192.168.29.122:7778/api/autoprovision/zqtYxQfwqk0JmjCJ
Then add the mac in the end with the file suffix. ( Mac name should be lowercase.)
e.g. Paste the link to the browser to check if it can be downloaded or not.
http://192.168.29.122:7778/api/autoprovision/zqtYxQfwqk0JmjCJ/805ec0e1450b.cfg
The suffix of different IP phone as below:
- Alcatel: config.MAC.xml
- Fanvil: MAC.cfg
- Flyingvoice: MAC.cfg
- Gigaset: MAC.xml
- Grandstream: cfgMAC.xml
- Htek: cfgMAC.xml
- Snom: MAC.xml
- Yealink: MAC.cfg
(2) DHCP
It is similar to PnP mode to do the auto provision.
The difference and special is as below.
- DHCP Active setting on IP phone
- When PBX is the DHCP server in the network, make sure there is only one DHCP server in the same network.
(3) RPS
Step1
If it shows gray of RPS mode you can not select RPS mode on PBX.
Check the PBX network first, especially the DNS server. Try to ping google.com to check it.
1.1 When you are using FQDN, follow below.
Check the FQDN status and whether there is a restriction on Web Access and SIP Access.
Check whether the certificate is valid. If not, you can disable the IP phone certificate authority
to set it up first and contact Yeastar.
1.2 When you are using Public IP and Ports, follow below.
Check the Public IP and Ports on PBX and the port mapping on the router.
PBX certificate is valid or not.
Step2
If the step1 is finished and has done the auto provision, follow below to check, please.
Check the auto provision URL on the IP phone webpage.
Check whether the RPS request is successful or not.
If not, contact Yeastar support directly.
2.1 If it doesn't show auto provision URL on the IP phone webpage.
① Phone connect to the Internet and the DNS server works. Make sure the firmware is in the supported list.
②Check the blocked IP on PBX.
③Check the IP Phone concurrent registrations.
④Check the extension remote registration and ip restriction on PBX.
⑤Phone reset and phone reboot if it is the first time to auto provisioning.
⑥Disable the phone certificate authentic. If the certificate is out of date, it will fail to auto provision.
2.2 If it shows the auto provisioning URL on the IP phone webpage.
①Check whether the server IP/Domain in the URL is your PBX.
If not, it means has been auto provisioned on the other PBX before.
Try to login the other PBX and release then delete the record.
②Check whether the IP phone show LOGIN or not if you have set authentication.
③Try to paste the link with your IP phone mac name to check if the file can be downloaded or not.
e.g.The URL format would be like this:
https://chnagiuang-No1.ras.yeastar.com:443/api/autoprovision/zqtYxQfwqk0JmjCX
Then add the mac in the end with the file suffix. (Mac name should be lowercase.)
e.g. Paste the link to the browser to check if it can be downloaded or not.
https://chnagiuang-No1.ras.yeastar.com:443/api/autoprovision/zqtYxQfwqk0JmjCX/805ec0e1450b.cfg
The suffix of different IP phone as below:
- Alcatel: config.MAC.xml
- Fanvil: MAC.cfg
- Flyingvoice: MAC.cfg
- Gigaset: MAC.xml
- Grandstream: cfgMAC.xml
- Htek: cfgMAC.xml
- Snom: MAC.xml
- Yealink: MAC.cfg
In The End:
Still failed? Get the below log and contact us!
We need PCAP+System Log+Phone Log to check in advance.
(1) PCAP
- Choose "Any" (if there is only LAN, choose LAN), and click the 'Start' button.
- Start to make a call or start to replicate the issue.
- If the issue is replicated, end the call or stop your action.
Click the 'Stop' button and download the package
- Post us the package and tell us which extension/call has the problem.
(2) System Log with SIP Debug
Enable the SIP Debug before replicating the issue and download the system log after replicating it.
(3) Phone Log
0 Comments