[asterisk-bugs] [Asterisk 0015363]: 1.6.2.0_beta3 locks up in certain SIP scenario
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Jul 28 01:44:10 CDT 2009
A NOTE has been added to this issue.
======================================================================
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-28 01:44 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
======================================================================
----------------------------------------------------------------------
(0108304) klaus3000 (reporter) - 2009-07-28 01:44
https://issues.asterisk.org/view.php?id=15363#c108304
----------------------------------------------------------------------
tested with Asterisk 1.6.2.0-beta3:
After the above described scenario "core show locks":
=======================================================================
=== Currently Held Locks ==============================================
=======================================================================
===
=== <pending> <lock#> (<file>): <lock type> <line num> <function> <lock
name> <lock addr> (times locked)
===
=== Thread ID: -1301283952 (do_monitor started at [21574]
chan_sip.c restart_monitor())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_sip.c): MUTEX
21083 handle_request_do &netlock
0xb31db8a0 (1)
asterisk(ast_bt_get_addresses+0x19) [0x810bbd8]
/usr/lib/asterisk/modules/chan_sip.so [0xb31543a0]
/usr/lib/asterisk/modules/chan_sip.so [0xb31aea5e]
/usr/lib/asterisk/modules/chan_sip.so [0xb31ae7fc]
asterisk(ast_io_wait+0x14d) [0x81017c7]
/usr/lib/asterisk/modules/chan_sip.so [0xb31b043a]
asterisk [0x8186166]
/lib/i686/cmov/libpthread.so.0 [0xb7aac4c0]
/lib/i686/cmov/libc.so.6(clone+0x5e) [0xb7ce16de]
=== ---> Lock https://issues.asterisk.org/view.php?id=1 (chan_sip.c): MUTEX 6959
find_call sip_pvt_ptr 0xa16b8d0
(1)
asterisk(ast_bt_get_addresses+0x19) [0x810bbd8]
asterisk [0x8084704]
asterisk(_ao2_lock+0x4a) [0x80845bc]
/usr/lib/asterisk/modules/chan_sip.so [0xb31687b5]
/usr/lib/asterisk/modules/chan_sip.so [0xb31aea7a]
/usr/lib/asterisk/modules/chan_sip.so [0xb31ae7fc]
asterisk(ast_io_wait+0x14d) [0x81017c7]
/usr/lib/asterisk/modules/chan_sip.so [0xb31b043a]
asterisk [0x8186166]
/lib/i686/cmov/libpthread.so.0 [0xb7aac4c0]
/lib/i686/cmov/libc.so.6(clone+0x5e) [0xb7ce16de]
=== -------------------------------------------------------------------
===
=======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-07-28 01:44 klaus3000 Note Added: 0108304
======================================================================
More information about the asterisk-bugs
mailing list