[asterisk-bugs] [Asterisk 0018548]: CHANNEL variable is set incorrectly by Asterisk

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18548 
====================================================================== 
Reported By:                greenfieldtech
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18548
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.15 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-12-29 02:22 CST
Last Modified:              2011-01-03 10:44 CST
====================================================================== 
Summary:                    CHANNEL variable is set incorrectly by Asterisk
Description: 
Ever since I installed version 1.6.2.14 of Asterisk, the CHANNEL variable
appears to behave differently that before - specifically saying: it now
doesn't return the technology type, and the the ID appears to be a little
chopped.
====================================================================== 

---------------------------------------------------------------------- 
 (0130096) tilghman (manager) - 2011-01-03 10:44
 https://issues.asterisk.org/view.php?id=18548#c130096 
---------------------------------------------------------------------- 
This isn't a problem with the CHANNEL variable; it's a problem with AEL. 
Try doing the following:

__INBOUND_CHANNEL="${CHANNEL}";

The issue is that AEL does no semantic parsing of the input line; it
leaves that to the dialplan.  Instead, it wraps all values with the
expression delimiters, so a channel name actually looks to the expression
parser as a complex math problem:  SIP divided by (name) minus
[identifier].  This is garbage, of course, so you're left with the somewhat
cryptic identifier.  Quoting the value should ensure that it is not
interpreted as a math problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-03 10:44 tilghman       Note Added: 0130096                          
======================================================================