Yealink Forums

Full Version: PNP Provisoning on V7 Firmware Issues
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

I have a PNP server that manages my auto provision. (through a tftp server).

This process has been working fine for Yealink (pre v7 firmware) and Fanvil phones. I have now updated one of my T20P phones to v7. (hardware version 7.0.0.60,software version 9.70.23.2 ).

Since i have done this the T20P does not react on the SIP notify my PNP server sends it. If i manually add the tftp server on the phone GUI, the update does work. (using both the old style and new style of config files.). PNP is enabled on the phone.

Here is the SIP notify i send back once i have received the multicast subscribe message.

Code:
NOTIFY sip:192.168.100.142:5059 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.142:5059;branch=z9hG4bK47969
Max-Forwards: 20
Contact: <sip:10.0.50.100:1036;transport=TCP;handler=dum>
To: <sip:MAC0015651be910@224.0.1.75>
From: <sip:MAC0015651be910@224.0.1.75>;tag=47876
Call-ID: 47875@192.168.100.142
CSeq: 3 NOTIFY
Content-Type: application/url
Subscription-State: terminated;reason=timeout
Event: ua-profile;profile-type="device";vendor="Yealink";model="SIP-T20P";version="9.70.23.2""
Content-Length: 19

tftp://10.0.50.100/

the config files does sit in the root directory of the tftp server.

Any suggestions. I urgently need the PNP server to work with v7 firmware.

Thank you
Hi Baddah,
What about upgrade to the firmware 9.70.0.140 on our website ?
http://www.yealink.com/Upload/firmware/T....0.140.zip

The firmware "9.70.23.2" is for UK customer, so you are from UK?
Hi,

Thank you for the reply. I am not UK based no, so i have uploaded the above firmware.

Unfortunately it did not fix the issue. The phone ignores the sip notify i send it. It still works if i manually specify the tftp server from the GUI.

Any other suggestions? Can you confirm that you are not ware of any PNP issues with the new firmware.

Firmware i used now. (Firmware Version 9.70.0.140,Hardware Version 7.0.0.60).

SIP subscribe and corresponding sip notify.

Code:
SUBSCRIBE sip:MAC0015651be910@224.0.1.75 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.142:5059;branch=z9hG4bK42268
From: <sip:MAC0015651be910@224.0.1.75>;tag=41758
To: <sip:MAC0015651be910@224.0.1.75>
Call-ID: 41758@192.168.100.142
CSeq: 1 SUBSCRIBE
Contact: <sip:MAC0015651be910@192.168.100.142:5059>
Max-Forwards: 70
User-Agent: Yealink SIP-T20P 9.70.0.140
Expires: 0
Event: ua-profile;profile-type="device";vendor="Yealink";model="SIP-T20P";version="9.70.0.140"
Accept: application/url
Content-Length: 0

NOTIFY sip:192.168.100.142:5059 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.142:5059;branch=z9hG4bK42268
Max-Forwards: 20
Contact: <sip:10.0.50.100:1036;transport=TCP;handler=dum>
To: <sip:MAC0015651be910@224.0.1.75>
From: <sip:MAC0015651be910@224.0.1.75>;tag=41758
Call-ID: 41758@192.168.100.142
CSeq: 3 NOTIFY
Content-Type: application/url
Subscription-State: terminated;reason=timeout
Event: ua-profile;profile-type="device";vendor="Yealink";model="SIP-T20P";version="9.70.0.140""
Content-Length: 19

tftp://10.0.50.100/
Hi,

Any more suggestions? I cannot see any reason for this not to work other than something in the new firmware causing it?
Hi Baddah,
I am afraid we need your phones logs to analyze the problem, so could you provide PCAP trace, syslog(level 6) and config.bin file to us, so we can analyze?

Before you export the syslog, please set log level as 6, and reboot the phone, then click Start,and reproduce the issue, then click Stop,and export the trace, syslog, config,bin to us.
(About where to export these files, please refer to attached screenshot.)
These three files are very important for us, hope you can kindly understand.
Thanks.
Hi Baddah,
Did you send your PNP notify packet to the phone port 5059?
Our new V70 firmware require you to send to the port 5059, could you try again?
We tried it at our side, and works well.
Thanks.
Reference URL's