Re: [asterisk-users] Asterisk 1.4.41 - Warning and Notice about contact info and stale nonce
Hi, Nobody on this? Le 16/05/2011 23:35, Administrator TOOTAI a écrit : Le 16/05/2011 18:27, Jose P. Espinal a écrit : Administrator TOOTAI wrote: Of course it's 1.4.41. And the result is that devices doesn't register anymore. Thanks for any hint. If you are installing from source, check out if some modules did not load properly due to undefined symbols. # asterisk -gvvc | tee output.txt CLI stop gracefully Then review that output.txt file. Don't think that the problem is here: the devices are working well with previous version of asterisk on the same server. Also, other devices from other manufacturer are still working ok. Question is why auth is OK but registration failed? On 1.4.40 we juste had to change the device local port (eg from 5061 to 5062) and registration was OK. On 1.4.41 this trick is no more working. And stale nonce should have an end of life in our mind, but doesn't. Thanks for your tip. -- Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Asterisk 1.4.41 - Warning and Notice about contact info and stale nonce
Of course it's 1.4.41. And the result is that devices doesn't register anymore. Thanks for any hint. Le 14/05/2011 17:37, Administrator TOOTAI a écrit : Hi list, We have devices since more then 4 years which where running well with Asterisk. But with latest version (1.38 or more) we face problem with those devices when they try to register. We got [2011-05-14 17:18:06] WARNING[28559]: chan_sip.c:9950 register_verify: Failed to parse contact info --- Transmitting (NAT) to XXX.XXX.XXX.XXX:5062 --- SIP/2.0 400 Bad Request Followed by [2011-05-14 17:19:06] NOTICE[28559]: chan_sip.c:9502 check_auth: Correct auth, but based on stale nonce received from 'sip:7...@yyy.yyy.yyy.yyy;user=phone;tag=63d2ba80bffb016f' Checking logs we found Contact: * in headers before the failed parse contact info. We checked in source chan_sip and saw the parse info reject with Error 400 after the auth is correct comment. We modified in sip.conf the type=peer in type=friend, same result. Could someone explain us what happends here? Thanks -- Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Asterisk 1.4.41 - Warning and Notice about contact info and stale nonce
Administrator TOOTAI wrote: Of course it's 1.4.41. And the result is that devices doesn't register anymore. Thanks for any hint. If you are installing from source, check out if some modules did not load properly due to undefined symbols. # asterisk -gvvc | tee output.txt CLI stop gracefully Then review that output.txt file. -- Jose P. Espinal http://www.eSlackware.com IRC: Khratos @ #asterisk / -doc / -bugs -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Asterisk 1.4.41 - Warning and Notice about contact info and stale nonce
Le 16/05/2011 18:27, Jose P. Espinal a écrit : Administrator TOOTAI wrote: Of course it's 1.4.41. And the result is that devices doesn't register anymore. Thanks for any hint. If you are installing from source, check out if some modules did not load properly due to undefined symbols. # asterisk -gvvc | tee output.txt CLI stop gracefully Then review that output.txt file. Don't think that the problem is here: the devices are working well with previous version of asterisk on the same server. Also, other devices from other manufacturer are still working ok. Question is why auth is OK but registration failed? On 1.4.40 we juste had to change the device local port (eg from 5061 to 5062) and registration was OK. On 1.4.41 this trick is no more working. And stale nonce should have an end of life in our mind, but doesn't. Thanks for your tip. -- Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
