[asterisk-bugs] [Asterisk 0010636]: Meetme with Redirect leaves channel after hangup and crashes
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Sep 4 07:47:51 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=10636
======================================================================
Reported By: atis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 10636
Category: Applications/app_meetme
Reproducibility: sometimes
Severity: crash
Priority: normal
Status: new
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 81434
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 09-04-2007 07:30 CDT
Last Modified: 09-04-2007 07:47 CDT
======================================================================
Summary: Meetme with Redirect leaves channel after hangup and
crashes
Description:
Scenario:
1) SIP/21167 dials to SIP/21168
2) I'm sending a manager action Redirect, with both open channels to
context that sends them to meetme room.
3) Caller hears "you are only person", this creates 3rd Zap/pseudo
channel.
4) Both channels go to meetme room, they talk
5) On hangup, very often, but not every time third pseudo channel is
left.
Repeating this scenario for several times (from 2 up to more than 40),
makes asterisk crash.
For this, it is important that there is prompt "only person" played,
without this prompt (if in unaccessible format or removed) there isn't
third pseudo channel, and crashes haven't been noticed (for over than
consecutive 10 calls)
I will attach example dialplan with php script - redirect.php that takes
first two active channels and sends them to meetme room. This is minimal
asterisk configuration that actually makes asterisk to crash. On my
complete dialplan crashes are happening more often (usually at second
hangup).
I first tested it with Asterisk 1.4.10, but today i tested with latest
version from SVN (branch 1.4). I enabled DEBUG_CHANNEL_LOCKS, DEBUG_THREADS
and DONT_OPTIMIZE in menuselect. Also i did "core show channels verbose"
and "core show locks" after every call (almost). I will attach full log,
and CLI output.
Unfortunately, no core was dumped (i used ulimit -u unlimited). Also at
some point one call didn't got hanged up, and there were two AsyncGoto
channels left, i tried (unsuccessfully) to kill them with soft hangup - i'm
not sure that it won't make log worse. If it is bad, i can do another
testing (it takes several hours)
Similar problem was also noted in bug http://bugs.digium.com/view.php?id=7373 in
first comment, but nobody
made an issue of that, as that was a new experimental application.
======================================================================
----------------------------------------------------------------------
atis - 09-04-07 07:47
----------------------------------------------------------------------
Just to include this issue in search engines:
Significant errors before crash:
WARNING[19894] channel.c: Hard hangup called by thread -1214784624 on
Zap/pseudo-994643193, while fd is blocked by thread -1213555824 in
procedure ast_waitfor_nandfds! Expect a failure
...
ERROR[19903] /usr/dist/asterisk-svn-1.4/include/asterisk/lock.h: channel.c
line 4879 (ast_channel_lock): Error obtaining mutex: Invalid argument
I will provide full asterisk log within a short time. For now - last lines
before crash are in full_last_call.gz
Issue History
Date Modified Username Field Change
======================================================================
09-04-07 07:47 atis Note Added: 0069872
======================================================================
More information about the asterisk-bugs
mailing list