corona Posted May 27, 2009 Report Share Posted May 27, 2009 Hi, I installed pbxnsip in a FreeBSD box and use two snom300 to do a small trial. However, I keep seeing registered extensions got dropped frequently. Is there any settings I have to adjust in pbxnsip or snom? Here is the sip log I got. Thanks a lot. [5] 20090527184319: SIP port accept from 172.110.0.156:4357 [7] 20090527184319: SIP Rx tls:172.110.0.156:4357: REGISTER sip:SIP.AAA.COM.TW SIP/2.0 Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-bq8x0dzk8dk4;rport From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW> Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4917 REGISTER Max-Forwards: 70 Contact: <sip:711@172.110.0.156:4357;transport=tls;line=yra73fxq>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:2863965b-e672-4b52-9c94-a7f53bfefa30>" User-Agent: snom300/7.3.14 Supported: gruu Allow-Events: dialog X-Real-IP: 172.110.0.156 WWW-Contact: <http://172.110.0.156:80> WWW-Contact: <https://172.110.0.156:443> Proxy-Require: buttons Expires: 3600 Content-Length: 0 [7] 20090527184319: SIP Tx tls:172.110.0.156:4357: SIP/2.0 401 Authentication Required Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-bq8x0dzk8dk4;rport=4357 From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW>;tag=e642085ba4 Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4917 REGISTER User-Agent: pbxnsip-PBX/3.3.1.3177 WWW-Authenticate: Digest realm="SIP.AAA.COM.TW",nonce="c0a4bec37f25e4a216bd3c960d89f77a",domain="sip:SIP.AAA.COM.TW",algorithm=MD5 Content-Length: 0 [7] 20090527184319: SIP Rx tls:172.110.0.156:4357: REGISTER sip:SIP.AAA.COM.TW SIP/2.0 Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-54zndw569roy;rport From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW> Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4918 REGISTER Max-Forwards: 70 Contact: <sip:711@172.110.0.156:4357;transport=tls;line=yra73fxq>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:2863965b-e672-4b52-9c94-a7f53bfefa30>" User-Agent: snom300/7.3.14 Supported: gruu Allow-Events: dialog X-Real-IP: 172.110.0.156 WWW-Contact: <http://172.110.0.156:80> WWW-Contact: <https://172.110.0.156:443> Authorization: Digest username="711",realm="SIP.AAA.COM.TW",nonce="c0a4bec37f25e4a216bd3c960d89f77a",uri="sip:SIP.AAA.COM.TW",response="82c44588ec45e7846157d31b662670ed",algorithm=MD5 Proxy-Require: buttons Expires: 3600 Content-Length: 0 [7] 20090527184319: SIP Tx tls:172.110.0.156:4357: SIP/2.0 200 Ok Via: SIP/2.0/TLS 172.110.0.156:4357;branch=z9hG4bK-54zndw569roy;rport=4357 From: "711" <sip:711@SIP.AAA.COM.TW>;tag=q53dvjkfmo To: "711" <sip:711@SIP.AAA.COM.TW>;tag=e642085ba4 Call-ID: 3c273098f32d-90293snf3ceu CSeq: 4918 REGISTER Contact: <sip:711@172.110.0.156:4357;transport=tls;line=yra73fxq>;expires=181 Date: Wed, 27 May 2009 10:43:19 GMT Content-Length: 0 [5] 20090527184419: Registration 3c273098f32d-90293snf3ceu closed connection, removing it Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 27, 2009 Report Share Posted May 27, 2009 It looks like the firewall closes TCP connections after 60 seconds. Try making the "Maximum Registration Time (s)" shorter, for example 50 seconds. Quote Link to comment Share on other sites More sharing options...
corona Posted May 31, 2009 Author Report Share Posted May 31, 2009 It looks like the firewall closes TCP connections after 60 seconds. Try making the "Maximum Registration Time (s)" shorter, for example 50 seconds. it works great. Thanks a lot. 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.