[asterisk-bugs] [Asterisk 0015363]: 1.6.2.0_beta3 locks up in certain SIP scenario
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jul 27 15:42:29 CDT 2009
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=15363
======================================================================
Reported By: klaus3000
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15363
Category: Channels/chan_sip/General
Reproducibility: always
Severity: block
Priority: normal
Status: feedback
Target Version: 1.6.2.0
Asterisk Version: 1.6.2.0-beta3
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-06-19 12:25 CDT
Last Modified: 2009-07-27 15:42 CDT
======================================================================
Summary: 1.6.2.0_beta3 locks up in certain SIP scenario
Description:
Hi!
In this scenario 1.6.2.0-beta3 locks up:
--INVITE-->
<-407------
[ACK is lost]
--INVITE w/credentials-->
As soon as the second INVITE is received, chan_sip does not do anything
anymore. I see SIP packets sent to asterisk but they do not show in in the
log anymore.
If I make a call from dahdi to SIP I see that chan_sip sends out the
INVITE request, but the incoming SIP requests are not processes by
chan_sip.
I tested the above scenario and this beahvior is only in 1.6.2.0-beta3.
Asterisk 1.4.25 and svn-trunk r201907 behave different, see
https://issues.asterisk.org/view.php?id=14239
======================================================================
----------------------------------------------------------------------
(0108295) russell (administrator) - 2009-07-27 15:42
https://issues.asterisk.org/view.php?id=15363#c108295
----------------------------------------------------------------------
Can you please provide "core show locks" output for this issue?
Build Asterisk with DEBUG_THREADS enabled. Then, when it locks up, grab
the output of the "core show locks" CLI command. That should tell us where
it has locked up.
Issue History
Date Modified Username Field Change
======================================================================
2009-07-27 15:42 russell Note Added: 0108295
2009-07-27 15:42 russell Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list