Summary:ASTERISK-14696: SIP registration with a high latency peer fails
Reporter:Dave O (daveo)Labels:
Date Opened:2009-08-23 14:10:08Date Closed:2011-06-07 14:07:22
Versions:Frequency of
Description:I have 2 snom phones same config (via config server) and same firmware.  One is 20ms latency, the other is 650ms.  The 650ms seems to authenticate and then be challenged again.  The 2nd attempt fails (as below).  No such issue with the 20ms one.

The issue does not maninfest with asterisk- (compiled from source) but does with the latest SVN.

The happens 100% of the time.

I've attempted to adjust timeouts in sip.conf and chan_sip.c, but truthfully I'm hacking about beyond my understanding.  Nothing worked.

I did look at diff ./asterisk- ./asterisk/channels/chan_sip.c, but it's (again) a little beyond me.

I have this replicateable in a test environment so I can test scenarios if necessary.



[5]23/8/2009 20:51:34: sip::process_auth:Match challenge for user=SNOM300_BPS, realm=asterisk
[2]23/8/2009 20:51:35: Registered at registrar as SNOM300_BPS@a.b.c.d (Expires: 60 secs)
[5]23/8/2009 20:51:35: sip::process_auth:Match challenge for user=SNOM300_BPS, realm=asterisk
[5]23/8/2009 20:51:35: sip::process_auth:Match challenge for user=SNOM300_BPS, realm=asterisk
[2]23/8/2009 20:51:35: Registrar SNOM300_BPS@a.b.c.d refused with code 401
Comments:By: Dave O (daveo) 2009-08-24 03:10:49

Just a quick note to add that the "Additional Information" above is a copy-and-paste from the !SNOM!, not asterisk.

The issue doesn't occur if I comment out the secrect in sip.conf for  [SNOM300_BPS].

By: Olle Johansson (oej) 2009-09-10 14:23:09

Well, in order to help you with this we need you to read the bug guidelines, and produce the requested SIP debug output - there are detailed instructions there. I need to see both cases and would appreciate if the log file had timestamps (logger.conf).


By: Leif Madsen (lmadsen) 2009-09-16 10:25:53

Changing to Feedback status after oej's request for more information per the bug guidelines. Thanks!

By: Leif Madsen (lmadsen) 2009-09-30 10:03:00

I'm closing this issue as it has been waiting on feedback for more than 2 weeks. If the reporter has additional information that can be submitted, than they are welcome to reopen the issue. Thanks!