jlumby Posted July 22, 2009 Report Share Posted July 22, 2009 I am having an issue with several different products registering to PBXnSIP, mostly Audiocodes, Grandstream, Quickphones, and Adtran. The following is a packet capture of an Audiocodes gateway. When I set the registration expiration to 3600 on the audiocodes (as you can see in the packet capture below), the PBX replies with 29 I am not sure why this is. There is no nat going on between the gateway and the PBXnSIP, as well as other devices such as cisco phones do not have this problem, and they successfully register for the full 3600 to the same domain on the same switch. I am very concerned about such short registration time, since when I once had all of my extensions set to register every 60 this high frequency caused processor spikes that led to poor call quality. Now that I have the majority of my extensions set for 3600 the spikes, and quality issues have instantly gone away. I have even noticed that this same problem exists when registering one PBXnSIP to another. My current PBXnSIP version is 3.3.2.3183 (Win32) From AudioCodes to PBXnSIP: No. Time Source Destination Protocol Info 11 0.612851 10.0.0.131 10.0.0.6 SIP Request: REGISTER sip:voipp.twincitytelephone.com Frame 11 (832 bytes on wire, 832 bytes captured) Ethernet II, Src: AudioCod_18:a8:e9 (00:90:8f:18:a8:e9), Dst: Supermic_83:f6:cb (00:30:48:83:f6:cb) Internet Protocol, Src: 10.0.0.131 (10.0.0.131), Dst: 10.0.0.6 (10.0.0.6) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: REGISTER sip:voipp.twincitytelephone.com SIP/2.0 Method: REGISTER [Resent Packet: False] Message Header From: <sip:213@voipp.twincitytelephone.com>;tag=100eb030-8300000a-13c4-50029-a-215d8afe-a SIP from address: sip:213@voipp.twincitytelephone.com SIP tag: 100eb030-8300000a-13c4-50029-a-215d8afe-a To: <sip:213@voipp.twincitytelephone.com> SIP to address: sip:213@voipp.twincitytelephone.com Call-ID: 100fc348-8300000a-13c4-50029-a-2a94a760-a CSeq: 2 REGISTER Sequence Number: 2 Method: REGISTER Via: SIP/2.0/UDP 10.0.0.131:5060;rport;branch=z9hG4bK-b-2b4a-2a9b4f24 Transport: UDP Sent-by Address: 10.0.0.131 Sent-by port: 5060 RPort: rport Branch: z9hG4bK-b-2b4a-2a9b4f24 Max-Forwards: 70 Supported: replaces,100rel Allow: REGISTER, INVITE, ACK, BYE, REFER, NOTIFY, CANCEL, INFO, OPTIONS, PRACK, SUBSCRIBE Expires: 3600 Authorization: Digest username="213",realm="voipp.twincitytelephone.com",nonce="afa4b325771a1d526dd8f81c14701937",uri="sip:voipp.twincitytelephone.com",response="a9e3feb7a512a2ec7762275f25a30797",algorithm=MD5 Authentication Scheme: Digest Username: "213" Realm: "voipp.twincitytelephone.com" Nonce Value: "afa4b325771a1d526dd8f81c14701937" Authentication URI: "sip:voipp.twincitytelephone.com" Digest Authentication Response: "a9e3feb7a512a2ec7762275f25a30797" Algorithm: MD5 Contact: <sip:213@10.0.0.131:5060> Contact Binding: <sip:213@10.0.0.131:5060> URI: <sip:213@10.0.0.131:5060> SIP contact address: sip:213@10.0.0.131:5060 User-Agent: MP202 B 2FXS/2.6.4_p5_1_build_9 Content-Length: 0 From PBXnSIP to AudioCodes No. Time Source Destination Protocol Info 12 0.623656 10.0.0.6 10.0.0.131 SIP Status: 200 Ok (1 bindings) Frame 12 (458 bytes on wire, 458 bytes captured) Ethernet II, Src: Supermic_83:f6:cb (00:30:48:83:f6:cb), Dst: AudioCod_18:a8:e9 (00:90:8f:18:a8:e9) Internet Protocol, Src: 10.0.0.6 (10.0.0.6), Dst: 10.0.0.131 (10.0.0.131) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Status-Line: SIP/2.0 200 Ok Status-Code: 200 [Resent Packet: False] Message Header Via: SIP/2.0/UDP 10.0.0.131:5060;rport=5060;branch=z9hG4bK-b-2b4a-2a9b4f24 Transport: UDP Sent-by Address: 10.0.0.131 Sent-by port: 5060 RPort: 5060 Branch: z9hG4bK-b-2b4a-2a9b4f24 From: <sip:213@voipp.twincitytelephone.com>;tag=100eb030-8300000a-13c4-50029-a-215d8afe-a SIP from address: sip:213@voipp.twincitytelephone.com SIP tag: 100eb030-8300000a-13c4-50029-a-215d8afe-a To: <sip:213@voipp.twincitytelephone.com>;tag=1a11ed798c SIP to address: sip:213@voipp.twincitytelephone.com SIP tag: 1a11ed798c Call-ID: 100fc348-8300000a-13c4-50029-a-2a94a760-a CSeq: 2 REGISTER Sequence Number: 2 Method: REGISTER Contact: <sip:213@10.0.0.131:5060>;expires=29 Contact Binding: <sip:213@10.0.0.131:5060>;expires=29 URI: <sip:213@10.0.0.131:5060> SIP contact address: sip:213@10.0.0.131:5060 Date: Tue, 21 Jul 2009 22:16:12 GMT Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
pbx support Posted July 22, 2009 Report Share Posted July 22, 2009 Try to increase the Minimum registration time under Admin->Settings page and see that takes care of the problem. Quote Link to comment Share on other sites More sharing options...
jlumby Posted July 22, 2009 Author Report Share Posted July 22, 2009 It changes to whatever the minimum time is. That seems to be a major problem. Why is the PBX sending that out? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 22, 2009 Report Share Posted July 22, 2009 It changes to whatever the minimum time is. That seems to be a major problem. Why is the PBX sending that out? Because he rport parameter is set, the PBX assumes that the device is behind NAT. I admit it is goofy, we'll make it smarter in version 4. 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.