[asterisk-bugs] [Asterisk 0014875]: [patch] New dialplan application that tell Asterisk to not generate/send Manager Event for the current call
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Nov 2 08:50:45 CST 2009
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=14875
======================================================================
Reported By: jvandal
Assigned To: junky
======================================================================
Project: Asterisk
Issue ID: 14875
Category: Core/ManagerInterface
Reproducibility: N/A
Severity: feature
Priority: normal
Status: resolved
Target Version: Feature Tracker
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!):
Request Review:
Resolution: won't fix
Fixed in Version:
======================================================================
Date Submitted: 2009-04-10 10:28 CDT
Last Modified: 2009-11-02 08:50 CST
======================================================================
Summary: [patch] New dialplan application that tell Asterisk
to not generate/send Manager Event for the current call
Description:
We heavily use Asterisk Manager Interface (AMI) to get events and in some
call scenarios, like using Page application to dial 300 local channel, we
receive lots of events that we want to ignore.
I have add a new NoAMI() dial plan application that tell Asterisk to not
generate/send Manager Event for the current call.
By example :
exten => s,1,NoAMI()
exten => s,n,NoCDR()
exten => s,n,Page(Local/101 at paging&Local/102 at paging&Local/1-3 at paging&...)
exten => s,n,Hangup
======================================================================
----------------------------------------------------------------------
(0112957) russell (administrator) - 2009-11-02 08:50
https://issues.asterisk.org/view.php?id=14875#c112957
----------------------------------------------------------------------
Thank you very much for the contribution.
As you have seen, the manager interface does not lend itself to only
getting the events you want because of a number of design decisions. I'm
not willing to add a patch that relies on checking a variable throughout
the code base every time manager_event() is used. I honestly think to
solve what you really want the "right" way, it will require a new interface
completely.
Issue History
Date Modified Username Field Change
======================================================================
2009-11-02 08:50 russell Note Added: 0112957
2009-11-02 08:50 russell Status assigned => resolved
2009-11-02 08:50 russell Resolution open => won't fix
======================================================================
More information about the asterisk-bugs
mailing list