[asterisk-bugs] [Asterisk 0019247]: When a call is blind-transfered to another extension, the CLI wrongly display the transfered call as been hung up.
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon May 9 08:49:39 CDT 2011
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=19247
======================================================================
Reported By: thomas_foerster
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 19247
Category: Channels/chan_sip/Transfers
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2
SVN Revision (number only!): 307624
Request Review:
======================================================================
Date Submitted: 2011-05-05 15:41 CDT
Last Modified: 2011-05-09 08:49 CDT
======================================================================
Summary: When a call is blind-transfered to another
extension, the CLI wrongly display the transfered call as been hung up.
Description:
Phone A is on a call with PSTN caller (SIP/sbc2-00000063).
Phone A originates a blind transfer to extension B (992101)
CLI displays "== Spawn extension (customer, 992101, 1) exited non-zero on
'SIP/sbc2-00000063'"
Phone B is called and successfully bridged to PSTN caller.
There isn't any problem in the way the call is actually handled.
Nevertheless the CLI displays that the transfered call is being hang up and
then it bridges it to the destination SIP peer. This is happening on a
server that handles a heavy load of blind transfers and Asterisk is
crashing daily on this specific server. It seems that the server crashes
when an "already-closed-on-the-CLI" channel is really hung up.
All this does not happen when using attended transfer instead of blind
transfer.
======================================================================
----------------------------------------------------------------------
(0134647) lmadsen (administrator) - 2011-05-09 08:49
https://issues.asterisk.org/view.php?id=19247#c134647
----------------------------------------------------------------------
Per davidw, you'll have to address the crashing on Asterisk 1.8. If you can
reproduce there, then please follow up with an unoptimized backtrace.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2011-05-09 08:49 lmadsen Note Added: 0134647
2011-05-09 08:49 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list