andrewgroup Posted January 8, 2010 Report Share Posted January 8, 2010 The following is the log from an extension that was previously working fine. After attempting to get an M3 to parallel this ext, and trying to confirm the SIP password, the result is 403 Forbidden.. Immediately below is another extension.. So what must one do to restore PNP to a single extension? The MAC is correct, and all looks well.... Must one remove generated files, etc, and what was the actual cause? If you can determine from this post? Thanks REGISTER sip:localhost SIP/2.0 Via: SIP/2.0/TLS 192.168.1.166:2141;branch=z9hG4bK-9b6ocpg84gks;rport From: "Kenny ACC MNG" <sip:302@localhost>;tag=a5pkwsegun To: "Kenny ACC MNG" <sip:302@localhost> Call-ID: 3c26701cbcf2-1rlt6ss1r4kn CSeq: 6 REGISTER Max-Forwards: 70 Contact: <sip:302@192.168.1.166:2141;transport=tls;line=yoxynt0d>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:4216b9d9-0985-478f-960e-2bb7b5bb915f>" User-Agent: snom360/7.3.30 Supported: gruu Allow-Events: dialog X-Real-IP: 192.168.1.166 WWW-Contact: <http://192.168.1.166:80> WWW-Contact: <https://192.168.1.166:443> Proxy-Require: buttons Expires: 3600 Content-Length: 0 [9] 2010/01/07 18:56:21: SIP Tx tls:192.168.1.166:2141: SIP/2.0 403 Forbidden Via: SIP/2.0/TLS 192.168.1.166:2141;branch=z9hG4bK-9b6ocpg84gks;rport=2141 From: "Kenny ACC MNG" <sip:302@localhost>;tag=a5pkwsegun To: "Kenny ACC MNG" <sip:302@localhost>;tag=48c390b7f1 Call-ID: 3c26701cbcf2-1rlt6ss1r4kn CSeq: 6 REGISTER User-Agent: pbxnsip-PBX/3.4.0.3201 Content-Length: 0 [8] 2010/01/07 18:56:21: Packet authenticated by transport layer [9] 2010/01/07 18:56:21: SIP Rx tls:192.168.1.145:2059: REGISTER sip:localhost SIP/2.0 Via: SIP/2.0/TLS 192.168.1.145:2059;branch=z9hG4bK-ktjxeqrfaf35;rport From: "Dan SALES 2" <sip:311@localhost>;tag=tmaab84wpy To: "Dan SALES 2" <sip:311@localhost> Call-ID: 3c26701cf29f-1rlt6ss1r4kn CSeq: 9712 REGISTER Max-Forwards: 70 Contact: <sip:311@192.168.1.145:2059;transport=tls;line=yoxynt0d>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:4216b9d9-0985-478f-960e-2bb7b5bb915f>" User-Agent: snom360/7.3.30 Supported: gruu Allow-Events: dialog X-Real-IP: 192.168.1.145 WWW-Contact: <http://192.168.1.145:80> WWW-Contact: <https://192.168.1.145:443> Proxy-Require: buttons Expires: 3600 Content-Length: 0 [8] 2010/01/07 18:56:21: Packet authenticated by transport layer [9] 2010/01/07 18:56:21: SIP Tx tls:192.168.1.145:2059: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.145:2059;branch=z9hG4bK-ktjxeqrfaf35;rport=2059 From: "Dan SALES 2" <sip:311@localhost>;tag=tmaab84wpy To: "Dan SALES 2" <sip:311@localhost>;tag=18e05bf06e Call-ID: 3c26701cf29f-1rlt6ss1r4kn CSeq: 9712 REGISTER Contact: <sip:311@192.168.1.145:2059;transport=tls;line=yoxynt0d>;expires=181 Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
andrewgroup Posted January 8, 2010 Author Report Share Posted January 8, 2010 Delete the Idendity seemed to do the Trick... Thanks Self, School of Hard Knocks So what must one do to restore PNP to a single extension? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 8, 2010 Report Share Posted January 8, 2010 If you have PnP set up the right way, you should always be able to nuke the phone (well, factory reset it) and it should then pull down the config from the PBX. Having local changes is always tricky; its that old problem of database replication/redundancy where the data originates from--you end up with problems like these where you have an inconsistent configuration. Quote Link to comment Share on other sites More sharing options...
andrewgroup Posted January 8, 2010 Author Report Share Posted January 8, 2010 Might you know if you can use the Snom 7.3 emergency recovery image to upgrade a 6.x snom to the latest? hitting 321 and entering an IP address and TFTP server seems to restore a Snom 360 to the latest firmware about 100 times faster than any on-line upgrade.... Keeping an TFTP server up is a mighty fast way of upgrading phones. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted January 9, 2010 Report Share Posted January 9, 2010 Well, if you know what you are doing tftp is better than a factory reset! Quote Link to comment Share on other sites More sharing options...
andrewgroup Posted January 9, 2010 Author Report Share Posted January 9, 2010 Well, if you know what you are doing tftp is better than a factory reset! To speed firmware upgrades we duplicated the Snom provisioning WEB site on in an internal server with a DNS record pointing to it so a group of Snoms would get the upgrade far fast on the LOCAL lan. Having rescued some phone with TFTP, the thought that TFTP can restore the rescue image pretty darn fast with no reboots or hassles. That said, moving from 5,6 or for that matter moving to the latest version seems to be done the fastest using the rescue image and TFTP.. Will check with Snom to determine if any hardware revisions on snom phones would prevent going from lower revs to the latest with the rescue image. Will post the reply here. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.