[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-11 00:21 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)

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

---------------------------------------------------------------------- 
 (0108885) sohosys (reporter) - 2009-08-11 00:21
 https://issues.asterisk.org/view.php?id=14926#c108885 
---------------------------------------------------------------------- 
allowing null in the lastms field did not resolve this. a reload is
required to reproduce the problem. shortly after the reload, despite many
peers that have registered again, all peers go unreachable and the database
lastms value is updated to '-1' for all peers 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-11 00:21 sohosys        Note Added: 0108885                          
======================================================================