[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 09: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)

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

---------------------------------------------------------------------- 
 (0108902) sohosys (reporter) - 2009-08-11 09:38
 https://issues.asterisk.org/view.php?id=14926#c108902 
---------------------------------------------------------------------- 
bluefox, trying to find similariities between our system to isolate this.
one thing i hav enoticed is that 1.4 responds to SIP NOTIFY sent by our
ATAs with "489 bad event", and then tears down the dialog. 1.2 gracefully
responded to NOTIFY from the ATA with "603 declined". we have all of our
ATAs configured to sent NAT keppalives to keep firewalls and NAT devices
open, and the message they are configured to periodically send is NOTIFY.
Do you also have ATAs set to use NOTIFY as a NAT keepalive? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-11 09:38 sohosys        Note Added: 0108902                          
======================================================================