[asterisk-bugs] [JIRA] (ASTERISK-28310) Inconsistent Stasis event ordering for queue members calling

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28310:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> Inconsistent Stasis event ordering for queue members calling
> ------------------------------------------------------------
>
>                 Key: ASTERISK-28310
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28310
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 15.7.1, 16.1.1
>         Environment: any
>            Reporter: Nathan Bruning
>            Severity: Minor
>
> We are dialing queue members using local channels.
> The main channel will send out an {{AgentCalled}} event, followed by a {{DialBegin}} event.
> The dialing channel, started with {{ast_call}}, will also send events, for example a {{UserEvent}} in the dialplan.
> Because the main channel and dialing channel are handled on separate threads, the main- and dialing events may occur in any order; ie:
> - {{AgentCalled}}, {{DialBegin}}, and then {{UserEvent}} of dialing ch
> - {{UserEvent}} and then {{AgentCalled}}, {{DialBegin}}
> While this is not necessarily wrong, I believe the second ordering is very confusing for consumers of the events, as the {{AgentCalled}} event makes you aware of the logical connection between the queue channel and the dialing channel. It's even more confusing that the order changes now and then, semi-randomly.
> Therefore, I feel it's better to *first* send out the {{AgentCalled}} and {{DialBegin}} events, and *then* call {{ast_call}} on the dialing channel.
> I'll push a patch to gerrit for review.



--
This message was sent by Atlassian JIRA
(v6.2#6252)