[asterisk-bugs] [Asterisk 0014926]: Multiple "unreachable" and "reachable" messages for each SIP registrations

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14926 
====================================================================== 
Reported By:                bluefox
Assigned To:                lmadsen
====================================================================== 
Project:                    Asterisk
Issue ID:                   14926
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-17 13:18 CDT
Last Modified:              2009-08-10 15:24 CDT
====================================================================== 
Summary:                    Multiple "unreachable" and "reachable" messages for
each SIP registrations
Description: 
Shown in the CLI:
[Apr 17 14:16:02] NOTICE[31274]: chan_sip.c:13019
handle_response_peerpoke: Peer '1234-2' is now Reachable. (32ms / 2000ms)
[Apr 17 14:16:02] NOTICE[31274]: chan_sip.c:13019
handle_response_peerpoke: Peer '1234-2' is now Reachable. (32ms / 2000ms)
[Apr 17 14:16:02] NOTICE[31274]: chan_sip.c:13019
handle_response_peerpoke: Peer '01234-2' is now Reachable. (29ms / 2000ms)
[Apr 17 14:16:02] NOTICE[31274]: chan_sip.c:13019
handle_response_peerpoke: Peer '1234-2' is now Reachable. (31ms / 2000ms)
[Apr 17 14:16:02] NOTICE[31274]: chan_sip.c:13019
handle_response_peerpoke: Peer '1234-2' is now Reachable. (41ms / 2000ms)

====================================================================== 

---------------------------------------------------------------------- 
 (0108864) sohosys (reporter) - 2009-08-10 15:24
 https://issues.asterisk.org/view.php?id=14926#c108864 
---------------------------------------------------------------------- 
we are also experiencing this. version 1.4.25.1. sometimes as many as 15
unreachable log entries per second per event and 70 unreachable events per
second per event, all for the same peer. heavy system load.
 
rtcachefriends=yes
rtsavesysname=no
rtupdate=yes
rtautoclear=no
ignoreregexpire=no
qualify=yes

it looks like either the qualify timer values are not what is set in the
code (60sec OK, 10sec UNREACHABLE) or the SIP qualify packets are being
retransmitted and every retransmission and/or late reply is creating a new
event.

sample console output

[Aug 10 13:40:53] NOTICE[1020]: chan_sip.c:16612 sip_poke_noanswer: Peer
'5555267136' is now UNREACHABLE!  Last qualify: 125

[Aug 10 13:40:56] NOTICE[1020]: chan_sip.c:16612 sip_poke_noanswer: Peer
'5555267136' is now UNREACHABLE!  Last qualify: 1474

[Aug 10 13:40:57] NOTICE[1020]: chan_sip.c:16612 sip_poke_noanswer: Peer
'5555267136' is now UNREACHABLE!  Last qualify: 119

[Aug 10 13:40:58] NOTICE[1020]: chan_sip.c:16612 sip_poke_noanswer: Peer
'5555267136' is now UNREACHABLE!  Last qualify: 126

 

[Aug 10 13:41:03] NOTICE[1020]: chan_sip.c:12985 handle_response_peerpoke:
Peer '5555267136' is now Reachable. (120ms / 2000ms)

[Aug 10 13:41:06] NOTICE[1020]: chan_sip.c:12985 handle_response_peerpoke:
Peer '5555267136' is now Reachable. (93ms / 2000ms)

[Aug 10 13:41:08] NOTICE[1020]: chan_sip.c:12985 handle_response_peerpoke:
Peer '5555267136' is now Reachable. (101ms / 2000ms)

[Aug 10 13:41:08] NOTICE[1020]: chan_sip.c:12985 handle_response_peerpoke:
Peer '5555267136' is now Reachable. (127ms / 2000ms) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-10 15:24 sohosys        Note Added: 0108864                          
======================================================================