RPS Can't Work
Last modified date: 2016/11/25 views: 1717
Description

The devices didn´t get the provisioning files from the provisioning server configured in the RPS server.


Cause

1. The Version is not RPS version

2. The MAC address of the phone hasn’t been added to the RPS server or configured with auto provisioning server

3. There is not related CFG file in the provisioning server

4.  The phone can’t connect to the public network

5.  The phone has done auto provisioning successfully once before.


Resolution

1. What is the version the phone use? Only specific version can support RPS, so please make sure the phone is using the RPS version, if you don’t know ,you can send the version to support@yealink.com ,then we will check .(All the version from V73 are default RPS version , only V72 or lower version has RPS or none RPS version )

2. Make sure the Mac address of the phone have been preconfigured in the RPS server and assigned the provisioning server, make sure the URL is available.

3. Make sure you have added the related CFG files under your provisioning server

4. Make sure the phone can connect to the public network, the RPS server located in the US.

5. The phone will disable the RPS feature after the phone done provisioning successfully one time. You can reset the phone to factory to do test.

If you can’t get help from your vendor or distributor, then please send the problem description, test result of above steps, country to Suppot@yealink.com .

 

Only for distributor or professional engineer:

If after check above items, the phone still can’t work, would you please send Yealink below information that we can check what the reason is?

1) Config.bin file

2) Level 6 syslog

3) PCAP trace


More Information

1.RPS process

When you reset the phone , the phone will show “sending request …” which means the phone are trying connect to the RPS server to obtain the auto provisioning URL ,after obtain the URL the phone will go to the URL to download the related CFG files.

If the phone has connected to the RPS server successfully, you will find the record in the server like below,

In the Log page in the RPS server feature.

 55.jpg

2. For how to catch Config.bin file, Level 6 syslog and PCAP trace, you can refer to below link,

http://forum.yealink.com/forum/showthread.php?tid=1319

3.All version can support RPS feature from V73, all DECT version support RPS.

4. RPS user guide, you can refer to below( Yealink website)

Yealink Redirection and Provisioning Service(RPS) VAR Manual-V1.0-ENG

Yealink Redirection and Provisioning Service(RPS) User Manual-V1.0-ENG


Product Type
SIP-T48G , SIP-T46G , SIP-T42G , SIP-T41P , SIP-T38G , SIP-T32G , SIP-T29G , SIP-T28P , SIP-T26P , SIP-T27P , SIP-T23G , SIP-T23P , SIP-T21P , SIP-T20P , SIP-T19P , SIP-T22P , W52P , VP530
Version
RPS version
200/200
Please login to post your comment