[asterisk-bugs] [Asterisk 0014457]: Blind transfer uses the wrong context when blind transffering, combined with 'h' extension.

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14457 
====================================================================== 
Reported By:                e-tsik
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14457
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 174644 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-02-11 09:51 CST
Last Modified:              2009-03-04 09:08 CST
====================================================================== 
Summary:                    Blind transfer uses the wrong context when blind
transffering, combined with 'h' extension.
Description: 
Hello

As with 0013978, I blind-transferring results in invalid contexts, and I
also use the Macro command in conjunction with the 'h' extension.
The 'h' extension is used in the calling context - in my instance
'internal_p1'. What the 'h' extension does is
- Check for a variable's presence
- On a false condition - makes a goto to a certain function (calls a URL,
actually irrelevant to this bug because it never gets called) and hangs up
- On a true condition - Makes a goto to hangup|features_p1|1 . I use a
goto because it makes it easier to call from a GotoIf (there isn't a
HangUpIf).

Example how I reproduce it is under "Additional Information".
Also note that this is reproducible both by using the phone's (tecom
IP2008) transfer button or by using the "##" sequence.
====================================================================== 

---------------------------------------------------------------------- 
 (0101187) file (administrator) - 2009-03-04 09:08
 http://bugs.digium.com/view.php?id=14457#c101187 
---------------------------------------------------------------------- 
This is the way the code is written to work. Channels have no concept of
what the context that should be used for transfers should be EXCEPT for the
TRANSFER_CONTEXT dialplan variable. It was put there for this reason and
can be used in your situation to control what context to use. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-04 09:08 file           Note Added: 0101187                          
2009-03-04 09:08 file           Status                   new => resolved     
2009-03-04 09:08 file           Resolution               open => no change
required
2009-03-04 09:08 file           Assigned To               => file            
======================================================================