[asterisk-bugs] [JIRA] Commented: (ASTERISK-20318) Include channel uniqueid in "AsyncAGI" and "AGIExec" events

Jonathan Rose (JIRA) noreply at issues.asterisk.org
Tue Sep 11 17:17:07 CDT 2012


    [ https://issues.asterisk.org/jira/browse/ASTERISK-20318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196957#comment-196957 ] 

Jonathan Rose commented on ASTERISK-20318:
------------------------------------------

EDIT:  Nevermind, it looks like the patch you wrote might still be introduced in trunk. It won't be going into 10 or 11 though.

> Include channel uniqueid in "AsyncAGI" and "AGIExec" events
> -----------------------------------------------------------
>
>                 Key: ASTERISK-20318
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20318
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_agi
>    Affects Versions: 10.3.1, 10.7.0
>         Environment: Debian 64 bit, virtual machine, SIP.
>            Reporter: Dan Cropp
>            Assignee: Jonathan Rose
>            Severity: Minor
>         Attachments: res_agi patch.txt
>
>
> We are using AMI and during load testing we occasionally see two calls with the same channelname.  
> For the load test, we originate calls to ourselves.  Basically a loop back.  We go through a few thousand calls before encountering a case where the channel name matches another channel name.
> We decided to use the UniqueId for identification purposes.  This works great for the calls.  However, since we are using AsyncAGI, we rely on the AsyncAGI related events to also have the UniqueId.
> The channel's uniqueid is not included in the "AsyncAGI" and "AGIExec" events.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list