[asterisk-bugs] [Asterisk 0014926]: Multiple "unreachable" and "reachable" messages for each SIP registrations
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Aug 10 16:59:50 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-10 16:59 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)
======================================================================
----------------------------------------------------------------------
(0108873) sohosys (reporter) - 2009-08-10 16:59
https://issues.asterisk.org/view.php?id=14926#c108873
----------------------------------------------------------------------
I would agree that "trivial" is not correct based on the fact that we too
experienced a race or deadlock situation as a result that required a
restart to correct. We too had a spike in network traffic that appears to
be related.
bluefox, are you realtime settings the same as what i posted above? how
many sip peers on your box? we have about 500 on this box. With a near
identical configuration (less some minor 1.4 specific tweaks) we run
https://issues.asterisk.org/view.php?id=504#c2000
on our 1.2 boxes without this issue.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-10 16:59 sohosys Note Added: 0108873
======================================================================
More information about the asterisk-bugs
mailing list