[asterisk-bugs] [Asterisk 0014926]: Multiple "unreachable" and "reachable" messages for each SIP registrations
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Sep 3 12:08:49 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=14926
======================================================================
Reported By: bluefox
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 14926
Category: Channels/chan_sip/General
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: SVN
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-09-03 12:08 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)
======================================================================
----------------------------------------------------------------------
(0110143) tilghman (administrator) - 2009-09-03 12:08
https://issues.asterisk.org/view.php?id=14926#c110143
----------------------------------------------------------------------
I can make the issue private. That will cut off sohosys for the duration,
but it will also make the issue invisible for all but managers and
administrators.
Issue History
Date Modified Username Field Change
======================================================================
2009-09-03 12:08 tilghman Note Added: 0110143
======================================================================
More information about the asterisk-bugs
mailing list