[asterisk-bugs] [JIRA] (ASTERISK-29234) Queue Gosub option runs before channels are bridged
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Tue Jan 5 13:14:16 CST 2021
[ https://issues.asterisk.org/jira/browse/ASTERISK-29234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-29234:
-------------------------------------
Assignee: Asterisk Team (was: Bill Kervaski)
Status: Triage (was: Waiting for Feedback)
> 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: Asterisk Team
> 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)
More information about the asterisk-bugs
mailing list