[asterisk-bugs] [Asterisk 0014347]: Transfer executes callers channel in wrong context

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14347 
====================================================================== 
Reported By:                alesz
Assigned To:                otherwiseguy
====================================================================== 
Project:                    Asterisk
Issue ID:                   14347
Category:                   Channels/chan_sip/Transfers
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
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:              
====================================================================== 
Date Submitted:             2009-01-27 06:58 CST
Last Modified:              2009-01-29 11:40 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

====================================================================== 

---------------------------------------------------------------------- 
 (0099071) otherwiseguy (administrator) - 2009-01-29 11:40
 http://bugs.digium.com/view.php?id=14347#c99071 
---------------------------------------------------------------------- 
I have tried with:

[globals]
TRNASFER_CONTEXT=transfers

[default]
include => parkedcalls
exten => _600X,1,NoOp(Testing)
exten => _600X,n,Dial(SIP/${EXTEN},,tTk)
exten => _600X,n,Hangup

[transfers]
exten => _600X,1,Answer
exten => _600X,n,Playback(vm-goodbye)
exten => _600X,n,Hangup


In the 1.6.0 branch (r172317) and ever scenario for me goes to [transfers]
on a transfer, except SIP attended transfer.  Whether caller or callee does
the transfer on builtin-blind, builtin-attended, or SIP blind,
TRANSFER_CONTEXT seemed to be honored.  Can you verify this alesz?  A SIP
attended transfer wouldn't be able to honor this because the consultative
call is just like any other new call, so there would be no way to determine
that it was part of a transfer. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-29 11:40 otherwiseguy   Note Added: 0099071                          
======================================================================