[asterisk-bugs] [JIRA] (ASTERISK-29234) Queue Gosub option runs before channels are bridged

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp updated ASTERISK-29234:
--------------------------------------

    Assignee: Bill Kervaski
      Status: Waiting for Feedback  (was: Triage)

The 'b' option is a pre-dial handler, that is executed before a channel is dialed. The gosub option you reference is when they are connected, but I think where the confusion is coming from is that by connected it means they are essentially paired up. The gosub option executes before any bridge between them occurs, and thus BRIDGEPEER would not be set.

> Queue Gosub option runs before channels are bridged
> ---------------------------------------------------
>
>                 Key: ASTERISK-29234
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29234
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 18.1.0
>         Environment: Linux
>            Reporter: Bill Kervaski
>            Assignee: Bill Kervaski
>            Severity: Minor
>
> The Queue docs state for the gosub option:
> gosub - Will run a gosub on the called party’s channel (the queue member) once the parties are connected. The subroutine execution starts in the named context at the s exten and priority 1.
> However, when using a gosub the CLI shows:
> == Spawn extension (predial, foo, 1) exited non-zero on ‘PJSIP/peer-0000016d’
> Which indicates the same behavior as the b(context^exten^priority) option.
> The result is without the channels bridged first, the ${BRIDGEPEER} channel variable is missing.



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