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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14457 
====================================================================== 
Reported By:                e-tsik
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14457
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 174644 
Request Review:              
====================================================================== 
Date Submitted:             2009-02-11 09:51 CST
Last Modified:              2009-03-03 04:14 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0101070) e-tsik (reporter) - 2009-03-03 04:14
 http://bugs.digium.com/view.php?id=14457#c101070 
---------------------------------------------------------------------- 
I have discovered something else that may shed light on the issue.
It seems that blind transfer always begins the new call from the same
context of the transferred call. The user would expect the transferred call
to begin from the transferring user's context, because users dial extension
codes relative to their extension.

Example:
An incoming call to the DID context hits a target that calls Dial() to an
extension. The call is now in a did context.
A user bind-transfers the call to another extension using an extension
number, but the did context only contains full inbound numbers, so the call
either reaches the 'i' extension or drops. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-03 04:14 e-tsik         Note Added: 0101070                          
======================================================================