[asterisk-bugs] [JIRA] Feedback Entered: (ASTERISK-20318) We are using AMI and during load testing we occasionally see two calls with the same channelname. We decided to use the UniqueId for identification purposes, but discovered the channel's uniqueid is not included in the "AsyncAGI" and "AGIExec" events

[Dan Cropp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Cropp updated ASTERISK-20318:
---------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

Unfortunately, all our code has been changed for a few months to rely on the Uniqueid instead of the channel name.

What we did is originate 20 calls simultanteously.  These calls would come back to us, we would answer them.  Then we automated behaviors on the calls.

This was back in May and I don't remember if it was the originated call that had a duplicate channel name or if it was the incoming call that had the duplicate channel name.

One slight correction to my original note.

These are Local channels that we were using, not SIP.
Channel: Local/333 at IS-0ccc;1

> We are using AMI and during load testing we occasionally see two calls with the same channelname.  We decided to use the UniqueId for identification purposes, but discovered the channel's uniqueid is not included in the "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: Dan Cropp
>            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