[asterisk-bugs] [Asterisk 0014926]: Multiple "unreachable" and "reachable" messages for each SIP registrations
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Aug 10 17:14:34 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 17:14 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)
======================================================================
----------------------------------------------------------------------
(0108874) sohosys (reporter) - 2009-08-10 17:14
https://issues.asterisk.org/view.php?id=14926#c108874
----------------------------------------------------------------------
bluefox,
what is the datatype of your lastms field in your mysql table? does it
allow nulls? i think i am seeing in the cdoe that there are times when the
lastms needs to be set to null, but at least in our db null is not allowed
for lastms.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-10 17:14 sohosys Note Added: 0108874
======================================================================
More information about the asterisk-bugs
mailing list