[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 17:38 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)

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

---------------------------------------------------------------------- 
 (0108876) sohosys (reporter) - 2009-08-10 17:38
 https://issues.asterisk.org/view.php?id=14926#c108876 
---------------------------------------------------------------------- 
for the reason stated in this bug
https://issues.asterisk.org/view.php?id=15615 i avoid allowing null in a
column unless it is required. I also got my field definition for lastms
from the wiki, and know of no other (reliable) source of this information.
we will need to wait for comment from a qualifed programmer, which i am
not. I can see how this might casue a loop where we qualify a known
unreachable peer, but cant explain why the multpile reachables are logged,
except that maybe the peer tries to respond to all options queries that
were sent during the loop. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-10 17:38 sohosys        Note Added: 0108876                          
======================================================================