[asterisk-bugs] [Asterisk 0013862]: The Extension field of the Newexten event shows the actual extension even if that in the dial plan involves a pattern

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13862 
====================================================================== 
Reported By:                hagrawal
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   13862
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.21.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-11-07 14:12 CST
Last Modified:              2008-11-19 17:29 CST
====================================================================== 
Summary:                    The Extension field of the Newexten event shows the
actual extension even if that in the dial plan involves a pattern
Description: 
The Newexten event has three attributes -- context, extension, and priority
-- that uniquely identify the exact location in the dialplan from where the
corresponding application was invoked. If, however, the extension specified
in the dialplan involves a wildcard pattern, the Newexten event returns the
actual extension involved, not the pattern specified in the dialplan.
Consider, for example, the following dialplan fragment:

   exten => _NXX.,1,Playback(message1)
   exten => _ZXX.,1,Playback(message2)
   exten => _XXX.,1,Playback(message3)

When I receive a Newexten event that corresponds of one of these Playback
invocations, I want to know which of these three three Playback invocations
caused that event. Determining this manually is not that difficult in this
simple case, but in general it can be quite tricky and the application I am
working on needs to automate this determination. 

If the current behavior is intentional, is there a way to determine the
corresponding wildcard pattern when a NewExten event involves one? If not,
can you please add another field to the Newexten event, say "Pattern", that
returns the corresponding pattern?

Any fix/help/suggestions/pointers would be greatly appreciated.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-19 17:29 qwell          Status                   new => resolved     
2008-11-19 17:29 qwell          Resolution               open => suspended   
2008-11-19 17:29 qwell          Assigned To               => qwell           
2008-11-19 17:29 qwell          Status                   resolved => closed  
======================================================================