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

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Aug 12 09:01:42 CDT 2009


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-12 09:01 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)

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

---------------------------------------------------------------------- 
 (0108943) sohosys (reporter) - 2009-08-12 09:01
 https://issues.asterisk.org/view.php?id=14926#c108943 
---------------------------------------------------------------------- 
both the polycom and the xlite are capabable of sending notify messages for
NAT keepalive. would you be able to run sip debug for one of each device
and see if you are getting a SIP 489, bad event for each notify packet, and
if it is followed by some message about ending the sip dialog with the
phone? we are going to try turning off notify on the endpoints for a while. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-12 09:01 sohosys        Note Added: 0108943                          
======================================================================




More information about the asterisk-bugs mailing list