[asterisk-bugs] [Asterisk 0015056]: [patch] Blank FORWARD_CONTEXT is not ignored

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15056 
====================================================================== 
Reported By:                p_lindheimer
Assigned To:                seanbright
====================================================================== 
Project:                    Asterisk
Issue ID:                   15056
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.21.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-07 17:53 CDT
Last Modified:              2009-05-29 15:43 CDT
====================================================================== 
Summary:                    [patch] Blank FORWARD_CONTEXT is not ignored
Description: 
Once you have set FORWARD_CONTEXT=some-context in your dialplan, it is not
possible to "unset" the channel variable. Therefore the only way to unset
it is to set it blank:

exten => exten,n,Set(FORWARD_CONTEXT=)

However this appears to result in Asterisk using a non-existent blank
context for the forwarded call resulting in it failing.

Since there is no way to reset a context, I would expect this to treat a
blank context as if the variable was not set.
====================================================================== 

---------------------------------------------------------------------- 
 (0105758) p_lindheimer (reporter) - 2009-05-29 15:43
 https://issues.asterisk.org/view.php?id=15056#c105758 
---------------------------------------------------------------------- 
that does not seem to do the trick, here is the CLI results, as you can
see, it forwards it to a non-existent context, Local/7361234

    -- Executing [s at macro-dial:7] Dial("SIP/222-b7921e50",
"SIP/700|24|tTwWr") in new stack
    -- Called 700
    -- Got SIP response 302 "Moved Temporarily" back from 192.168.1.61
    -- Now forwarding SIP/222-b7921e50 to 'Local/7361234@' (thanks to
SIP/700-08ff4ec0)

where as if FORWARD_CONTEXT were never set here is the results you get
with a Noop inserted in the call flow to print out the FORWARD_CONTEXT to
confirm it is not set to anyhting:

    -- Executing [445 at from-internal:19] NoOp("SIP/222-b7922258",
"FORWARD_CONTEXT VALUE IS: ") in new stack

...

    -- Executing [s at macro-dial:7] Dial("SIP/222-b7922258",
"SIP/700|24|tTwWr") in new stack
    -- Called 700
    -- Got SIP response 302 "Moved Temporarily" back from 192.168.1.61
    -- Now forwarding SIP/222-b7922258 to 'Local/7361234 at from-internal'
(thanks to SIP/700-090a9968) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-29 15:43 p_lindheimer   Note Added: 0105758                          
======================================================================