[asterisk-bugs] [Asterisk 0016936]: [patch] Qualify frequency has big pauses. Asterisk stops sending SIP OPTIONS to keep NAT alive

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Apr 30 11:16:33 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16936 
====================================================================== 
Reported By:                ib2
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16936
Category:                   Channels/chan_sip/General
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.4 
JIRA:                       SWP-993 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-03-01 13:54 CST
Last Modified:              2010-04-30 11:16 CDT
====================================================================== 
Summary:                    [patch] Qualify frequency has big pauses. Asterisk
stops sending SIP OPTIONS to keep NAT alive
Description: 
We have several SIP phone peers that that becomes UNREACHABLE since
upgrading to Asterisk 1.6.2.x

[10:08:44] chan_sip.c: Peer '202_117' is now UNREACHABLE!  Last qualify:
100
[10:11:25] chan_sip.c: Peer '202_117' is now Reachable. (86ms / 2000ms)
[11:59:03] chan_sip.c: Peer '202_117' is now UNREACHABLE!  Last qualify:
91
[12:11:27] chan_sip.c: Peer '202_117' is now Reachable. (85ms / 2000ms)
[13:17:21] chan_sip.c: Peer '202_117' is now UNREACHABLE!  Last qualify:
90
[13:41:27] chan_sip.c: Peer '202_117' is now Reachable. (92ms / 2000ms)

The phone is UNREACHABLE until it registers again. The phone does not know
that it is UNREACHABLE.
Asterisk reports the phone as UNREACHABLE after a big pause in sending SIP
OPTIONS to keep NAT alive. Therefore NAT table is lost and asterisk cannot
receive SIP OK reply from the phone.

The typical interval between the occurrence is shown above
====================================================================== 

---------------------------------------------------------------------- 
 (0121231) cappucinoking (reporter) - 2010-04-30 11:16
 https://issues.asterisk.org/view.php?id=16936#c121231 
---------------------------------------------------------------------- 
p.s. this is on a 1.6.2.7-rc2 talking to 1.6.2.7rc-1
I've tried versions before these and I'm having the same problems.
Does anyone know for definate a version this doesn't happen on?

rsw686 - you mention not having problem on your previous 1.6.1 release -
what release number are you using?

This is happening approx 3 - 8 times per day.
But not over weekends, when traffic is fairly minimal anyway.

I can see in the logs

[Apr 30 10:17:12] NOTICE[18576] chan_sip.c: Peer '0301000' is now
Reachable. (1ms / 4000ms)
[Apr 30 11:57:33] NOTICE[18576] chan_sip.c: Peer '0301000' is now
Reachable. (2ms / 4000ms)
[Apr 30 12:20:09] NOTICE[18576] chan_sip.c: Peer '0301000' is now
Reachable. (1ms / 4000ms)
[Apr 30 13:14:45] NOTICE[18576] chan_sip.c: Peer '0301000' is now
Reachable. (1ms / 4000ms)
[Apr 30 14:24:25] NOTICE[18576] chan_sip.c: Peer '0301000' is now
Reachable. (1ms / 4000ms)
[Apr 30 15:10:12] NOTICE[18576] chan_sip.c: Peer '0301000' is now
Reachable. (1ms / 4000ms)


However, there is no corresponding UNREACHABLE message.
Doing sip show peers it sees it is offline - but why isn't this getting
logged as an unreachable? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-30 11:16 cappucinoking  Note Added: 0121231                          
======================================================================




More information about the asterisk-bugs mailing list