[asterisk-bugs] [Asterisk 0011522]: [patch] DYNAMIC_FEATURES variable looked up in wrong channel during feature interpretation

[noreply at bugs.digium.com]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11522 
====================================================================== 
Reported By:                nic_bellamy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11522
Category:                   Resources/res_features
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 92423 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-11-2007 20:47 CST
Last Modified:              12-12-2007 13:12 CST
====================================================================== 
Summary:                    [patch] DYNAMIC_FEATURES variable looked up in wrong
channel during feature interpretation
Description: 
I just spent half a day banging my head against the dialplan before
discovering this.

When you are using ${DYNAMIC_FEATURES}, the features are only checked
against the channel that started the bridge. They should be checked against
the channel that pressed the digits and broke the bridge.

This broke the following config for me:

[test]
exten => 201,1,NoOp(Incoming for 201)
exten => 201,n,Dial(SIP/201,30,rtM(dynamic-features))

[macro-dynamic-features]
exten => s,1,Set(DYNAMIC_FEATURES=myfeature)

What I wanted was for the called channel (SIP/201) to be able to dial the
dynamic feature code, but not the calling channel; when attempting to dial
it, however, it wouldn't work.

There's a lot more detail that could be added, but instead, I'm going to
attach a patch - since when you read it, you'll go "Doh!" and instantly see
the problem.

This bug is probably the reason most people have avoided using dynamic
features - it was impossible to make them work correctly.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-12-07 13:12  eliel          Summary                  DYNAMIC_FEATURES
variable looked up in wrong channel during feature interpretation => [patch]
DYNAMIC_FEATURES variable looked up in wrong channel during feature
interpretation
======================================================================