Yealink Forums

Full Version: W52P Provision not working (FW 25.73.0.40)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi all,

I'm the founder of FlexiPBX and want to use the W52P as the dect solution for my customers. I have a provisioning template based on the provided "Yealink W52P AutoProvisioning Template_V50" which is requested and deliverd by the web server but the W52P doesn't do anything.

I checked the pcap trace if the right content is delivered and it is:
[attachment=2018]

I checked the log file in log level 6 and always get the same result.
"response process finish!"
"recv : 0 bytes"

Also if I get the local log from the W52P there are some strange *.pcap files and memcheck info files. (log attached)

here the log section:
Code:
Mar 22 10:35:37 Log [458]: WEB <6+info  > AutoProvision now
Mar 22 10:35:37 Log [458]: WEB <6+info  > Write autop config success!
Mar 22 10:35:37 ATP [400]: ATP <6+info  > Upgrade by default
Mar 22 10:35:37 ATP [400]: ATP <6+info  > Try upgrade by dhcp options
Mar 22 10:35:37 ATP [400]: ATP <6+info  > Upgrade by DHCP option Fail
Mar 22 10:35:37 ATP [400]: ATP <6+info  > Upgrade by static config
Mar 22 10:35:37 Log [422]: ETLL<6+info  >Processing message 0x30007 ...
Mar 22 10:35:37 Log [422]: CUIT<6+info  >TalkLogic: PHONE_MSG_GETWORKSTATUS[0][0]!
Mar 22 10:35:37 Log [422]: TALK<6+info  >talklogic_SessionExist [iSessionNum=0]
Mar 22 10:35:37 ATP [400]: ATP <6+info  > Upgrade from com.cfg
Mar 22 10:35:37 LIBD[400]: DCMN<6+info  > Connecting <provisioning url>:80
Mar 22 10:35:37 LIBD[400]: DCMN<6+info  > Connecting IP = <server IP>, Port = 80
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > Request Line: GET /provision/y000000000025.cfg HTTP/1.1^M
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > Host: <provisioning url>
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > User-Agent: Yealink SIP-W52P 25.73.0.40 00:15:65:96:ad:f7
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > process response
Mar 22 10:35:37 LIBD[400]: HTTP<5+notice> response code: 401
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > Chunked Encoding
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > http auth type: 1,
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > Cleaning cache
Mar 22 10:35:37 LIBD[400]: HTTP<5+notice> response code: 200
Mar 22 10:35:37 LIBD[400]: HTTP<6+info  > Content-Length: 19524
Mar 22 10:35:37 LIBD[400]: HTTP<5+notice> response process finish!
Mar 22 10:35:37 LIBD[400]: HTTP<5+notice> recv : 0 bytes
Mar 22 10:35:37 ATP [400]: ATP <3+error > Can't read 23 byte
Mar 22 10:35:37 ATP [400]: ATP <6+info  > need_cmp_md5=1
Mar 22 10:35:37 ATP [400]: ATP <6+info  > cfg md5 same!
Mar 22 10:35:37 Log [422]: ETLL<6+info  >Processing message 0x30007 ...
Mar 22 10:35:37 Log [422]: CUIT<6+info  >TalkLogic: PHONE_MSG_GETWORKSTATUS[0][0]!
Mar 22 10:35:37 Log [422]: TALK<6+info  >talklogic_SessionExist [iSessionNum=0]
Mar 22 10:35:38 ATP [400]: ATP <6+info  > Upgrade from mac.cfg
Mar 22 10:35:38 LIBD[400]: DCMN<6+info  > Connecting <provisioning url>:80
Mar 22 10:35:38 LIBD[400]: DCMN<6+info  > Connecting IP = <Server IP>, Port = 80
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > Request Line: GET /provision/00156596adf7.cfg HTTP/1.1^M
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > Host: <provisioning url>
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > User-Agent: Yealink SIP-W52P 25.73.0.40 00:15:65:96:ad:f7
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > process response
Mar 22 10:35:38 LIBD[400]: HTTP<5+notice> response code: 401
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > Chunked Encoding
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > http auth type: 1,
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > Cleaning cache
Mar 22 10:35:38 LIBD[400]: HTTP<5+notice> response code: 200
Mar 22 10:35:38 LIBD[400]: HTTP<6+info  > Content-Length: 43057
Mar 22 10:35:38 LIBD[400]: HTTP<5+notice> response process finish!
Mar 22 10:35:38 LIBD[400]: HTTP<5+notice> recv : 0 bytes
Mar 22 10:35:38 ATP [400]: ATP <3+error > Can't read 23 byte
Mar 22 10:35:38 ATP [400]: ATP <6+info  > need_cmp_md5=1
Mar 22 10:35:38 ATP [400]: ATP <6+info  > cfg md5 same!

the config is delivered but not applied to the W52P. Can anybody please help me with this issue?

Best regards,
Roman
From the log,we can find that "cfg md5 same!",so the phone will not update.

So I suggest you change some parameters,then test again.
(03-23-2016 05:04 AM)Yealink_Klaus Wrote: [ -> ]From the log,we can find that "cfg md5 same!",so the phone will not update.

So I suggest you change some parameters,then test again.

I have changed the parameters several times in both y000000000025.cfg and {mac}.cfg files but I always get "cfg md5 same!". I also reset to factory defaults several times and started all over again. Didn't help. Also with the first provisioning attempt after a "reset to factory defaults" I get "cfg md5 same!". In the meanwhile I also could test another W52P and there I have the same issue.

On my T38G everything worked fine from the first provisioning attempt on!

Best regards,
Roman
we will fix this issue in ticket 23531.
Where can I find this ticket, it seems that I have the same problem ?

(04-01-2016 08:07 PM)Yealink_Klaus Wrote: [ -> ]we will fix this issue in ticket 23531.
Hi All.

How can I get firmware fix for provisioning issue resolving?
Reference URL's