[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
noreply at bugs.digium.com
Wed Nov 19 17:29:34 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13862
======================================================================
Reported By: hagrawal
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13862
Category: Core/ManagerInterface
Reproducibility: always
Severity: major
Priority: normal
Status: new
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:
======================================================================
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.
======================================================================
----------------------------------------------------------------------
(0095138) qwell (administrator) - 2008-11-19 17:29
http://bugs.digium.com/view.php?id=13862#c95138
----------------------------------------------------------------------
Showing the actual extension is intended behavior.
Adding the pattern would be a feature request, which shouldn't be handled
here. I would suggest the asterisk-dev mailing list, or publishing a
bounty to have it written.
Issue History
Date Modified Username Field Change
======================================================================
2008-11-19 17:29 qwell Note Added: 0095138
======================================================================
More information about the asterisk-bugs
mailing list