[asterisk-bugs] [Asterisk 0014926]: Multiple "unreachable" and "reachable" messages for each SIP registrations
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Aug 18 20:06:44 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-18 20:06 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)
======================================================================
----------------------------------------------------------------------
(0109256) bluefox (reporter) - 2009-08-18 20:06
https://issues.asterisk.org/view.php?id=14926#c109256
----------------------------------------------------------------------
Ok, here is what happened now:
I did this:
"sip prune realtime PEERNAME" then "sip show peer PEERNAME load" (as
described in Wiki) to reload one specific peer (one that was giving my
multiple UNREACHABLE messages". This also happens regularly, through a web
app, because I need to change values in SIP realtime.
Specifically, after the first command (prune) my specified peer started
giving me MANY MANY UNREACHABLE messages. After the second, everything
went to heck.
I am pretty sure this is the cause of the bug. Suddently my server starts
throwing up 11Mbit/s, link was totally congested, I had to restart the
server (restart now in CLI). Now everything works fine.
Please bump this up to "Major"
Regards,
Issue History
Date Modified Username Field Change
======================================================================
2009-08-18 20:06 bluefox Note Added: 0109256
======================================================================
More information about the asterisk-bugs
mailing list