[asterisk-bugs] [Asterisk 0014347]: Transfer executes callers channel in wrong context
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Feb 3 07:51:12 CST 2009
The following issue has been UPDATED.
======================================================================
http://bugs.digium.com/view.php?id=14347
======================================================================
Reported By: alesz
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 14347
Category: Channels/chan_sip/Transfers
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Asterisk Version: 1.6.0.5
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: fixed
Fixed in Version: 1.6.0.6
======================================================================
Date Submitted: 2009-01-27 06:58 CST
Last Modified: 2009-02-03 07:51 CST
======================================================================
Summary: Transfer executes callers channel in wrong context
Description:
hen call is transfered using blind or attended transfer using dtmf code
defined in features.conf or using phone transfer (tested on GXP2000 and
polycom 330) it appears callers channel goes to same context as callee's
last context instead of continuing on typed in extension in context defined
by TRANSFER_CONTEXT global variable.
Callee-s channel hangups ok.
Using Asterisk 1.6.0.5 & Freepbx 2.5.1.1. This started happening somewhere
around 1.6.0.3-rc1.
workaround: manually send call to correct context using goto. does not
work with consecutive transfers: first > second > third
======================================================================
----------------------------------------------------------------------
(0099331) blitzrage (administrator) - 2009-02-03 07:51
http://bugs.digium.com/view.php?id=14347#c99331
----------------------------------------------------------------------
Closing this issue as it appears to be fixed now.
alesz, please open a separate issue for the 603 part you described.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2009-02-03 07:51 blitzrage Note Added: 0099331
2009-02-03 07:51 blitzrage Status feedback => closed
2009-02-03 07:51 blitzrage Resolution open => fixed
2009-02-03 07:51 blitzrage Fixed in Version => 1.6.0.6
======================================================================
More information about the asterisk-bugs
mailing list