[asterisk-bugs] [JIRA] (ASTERISK-29020) Regression: Fix for app_queue: track masquerades in app_queue to avoid leaked stasis subscriptions broke queue log
Grzegorz Garlewicz (JIRA)
noreply at issues.asterisk.org
Fri Aug 14 07:58:43 CDT 2020
[ https://issues.asterisk.org/jira/browse/ASTERISK-29020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251644#comment-251644 ]
Grzegorz Garlewicz commented on ASTERISK-29020:
-----------------------------------------------
It seems to be a race condition. Most of the time I'm getting the values the old way but if I manage to do the transfer just when the queue starts (I think so) then I'm getting them the new way.
{code}
1597409056|1597409054.52|test|NONE|ENTERQUEUE||916547207|1
1597409058|1597409054.52|test|Sip/103|CONNECT|2|1597409056.53|2
1597409068|1597409067.54|test2|NONE|ENTERQUEUE||103|1
1597409068|1597409054.52|test|Sip/103|ATTENDEDTRANSFER|APP|Queue|2|10|1
1597409077|1597409054.52|test2|Sip/101|CONNECT|9|1597409075.56|1
1597409078|1597409054.52|test2|Sip/101|COMPLETEAGENT|9|1|1
{code}
{code}
1597409085|1597409084.57|test|NONE|ENTERQUEUE||468126461|1
1597409089|1597409084.57|test|Sip/103|CONNECT|4|1597409085.58|3
1597409099|1597409098.59|test2|NONE|ENTERQUEUE||103|1
1597409099|1597409098.59|test|Sip/103|ATTENDEDTRANSFER|APP|Queue|4|10|1
1597409102|1597409084.57|test2|Sip/101|CONNECT|3|1597409099.60|3
1597409103|1597409084.57|test2|Sip/101|COMPLETEAGENT|3|1|1
{code}
The dialplan is:
{code}
exten => 666,1,NoOp
same => n,Playback(welcome)
same => n,Queue(test)
exten => 777,1,NoOp
same => n,Playback(welcome)
same => n,Queue(test2)
{code}
I call 666. Agent picks up and initiates an attended transfer to 777. After the welcome message, agent completes the transfer. Another agent picks up and after the call hangs up.
> Regression: Fix for app_queue: track masquerades in app_queue to avoid leaked stasis subscriptions broke queue log
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-29020
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-29020
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_queue
> Affects Versions: 13.35.0
> Reporter: Grzegorz Garlewicz
> Assignee: Grzegorz Garlewicz
>
> {code}handle_masquerade{code}'s
> {code}ast_string_field_set(queue_data, caller_uniqueid, new_channel_id);{code}
> makes all subsequent entries in the queue_log use the new uniqueid which is not in any way associated to the original one.
> This way you can no longer rely on the log entries.
> {code}
> 1596621010|1596620945.17555|Consultant|NONE|ENTERQUEUE||209899255|1
> 1596621016|1596620945.17555|Consultant|Sip/3873|CONNECT|6|1596621010.17570|5
> 1596621065|1596621064.17580|Specialist|NONE|ENTERQUEUE||3873|2
> 1596621066|1596621064.17580|Consultant|Sip/3873|ATTENDEDTRANSFER|APP|Queue|6|50|1
> {code}
> the last entry used to have original uniqueid
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list