[asterisk-bugs] [Asterisk 0015014]: Asterisk loses SIP phones, possible deadlock, 1.6.1.0
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue May 5 11:39:29 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=15014
======================================================================
Reported By: madkins
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15014
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.6.1.0
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-05-01 11:03 CDT
Last Modified: 2009-05-05 11:39 CDT
======================================================================
Summary: Asterisk loses SIP phones, possible deadlock,
1.6.1.0
Description:
I have two Cisco 7905g SIP phones connected to an Asterisk 1.6.1.0 instance
running on a 64 bit Xen instance of Debian 4.0. My initial configuration
was more complex, but I've removed a lot of the complexity searching for
the problem.
Basically, I can start the Asterisk server and pick up a SIP phone and
call either a test extension or the other phone. Works fine. If I leave
it alone for a time ... say over a long lunch or overnight ... I come back
and the phones won't connect to Asterisk.
This repeats reliably but at unknown intervals.
======================================================================
----------------------------------------------------------------------
(0104232) madkins (reporter) - 2009-05-05 11:39
http://bugs.digium.com/view.php?id=15014#c104232
----------------------------------------------------------------------
i would change the category of this bug if i could (or knew how) as it now
seems to have nothing to do with SIP code
it seems like this should never be able to happen, but i'm unclear on what
a good fix would be, and now that i have a work-around i'm going to stop
looking
if there's a good place where i should document this behavior i'm happy to
write something up, but i need a pointer thereto
Issue History
Date Modified Username Field Change
======================================================================
2009-05-05 11:39 madkins Note Added: 0104232
======================================================================
More information about the asterisk-bugs
mailing list