[asterisk-users] AMI eventmask question

[Daniel Jenkins]

On Thu, Jan 23, 2014 at 9:05 PM, Daniel Jenkins <dan.jenkins88 at gmail.com>wrote:

>
>
>
> On Thu, Jan 23, 2014 at 8:46 PM, Matthew Jordan <mjordan at digium.com>wrote:
>
>> On Thu, Jan 23, 2014 at 9:31 AM, Michelle Dupuis <mdupuis at ocg.ca> wrote:
>> > Thanks - I've been through that doc before and couldn't find the info
>> > needed, which is why I went to the source code eventually.
>> >
>> > All events are grouped, and each group is given a name/flag like
>> 'system',
>> > 'call', etc.  The docs just don't say which events are in which
>> group/flag.
>> >
>> > Perhaps something Digium could add at some point :)
>>
>> Or someone from the open source community... this is an open source
>> project, after all :-)
>>
>> The managerEventInstance XML elements already have an attribute for
>> the manager class, which is populated:
>>
>>     <managerEvent language="en_US" name="ParkedCallTimeOut">
>>         <managerEventInstance class="EVENT_FLAG_CALL">
>>             <synopsis>Raised when a parked call times out.</synopsis>
>>             <syntax>
>>                 <parameter name="Exten">
>>                     <para>The parking lot extension.</para>
>>                 </parameter>
>>                 <parameter name="Channel"/>
>>                 <parameter name="Parkinglot">
>>                     <para>The name of the parking lot.</para>
>>                 </parameter>
>>                 <parameter name="CallerIDNum"/>
>>                 <parameter name="CallerIDName"/>
>>                 <parameter name="ConnectedLineNum"/>
>>                 <parameter name="ConnectedLineName"/>
>>                 <parameter name="UniqueID"/>
>>             </syntax>
>>             <see-also>
>>                 <ref type="managerEvent">ParkedCall</ref>
>>             </see-also>
>>         </managerEventInstance>
>>     </managerEvent>
>>
>> You could actually grep the core-en_US.xml file and get all of the
>> events that match to a particular class authorization.
>>
>> It doesn't show up in the CLI due to the xmldoc API not parsing out
>> that attribute. The same is true for the wiki documentation; that
>> project is up on github [1]. It wouldn't be a large patch to either to
>> have that attribute displayed.
>>
>> Matt
>>
>> [1] https://github.com/asterisk/publish-docs
>>
>> --
>> Matthew Jordan
>> Digium, Inc. | Engineering Manager
>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>> Check us out at: http://digium.com & http://asterisk.org
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> New to Asterisk? Join us for a live introductory webinar every Thurs:
>>                http://www.asterisk.org/hello
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>
> Thanks Matt, I was going to ask where the tool was that generated from
> source, I'll take a look and see if I can contribute that back,
>
> Dan
>


Hi, just to let you know that this is partially done now,

https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+ManagerEvent_AgentConnect

At the bottom you'll see a Class

Next stage is to create a page which has all the classes and the events
grouped by class.

But at least you can see which event is what class now.

Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140128/b9ebe4ce/attachment.html>