[Home]

Summary:ASTERISK-26757: When a queue member transfers queue call, he remains marked as "in call"
Reporter:Andrej (tekach)Labels:
Date Opened:2017-01-29 08:41:57.000-0600Date Closed:2017-01-29 15:19:02.000-0600
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:Applications/app_queue
Versions:11.25.1 13.13.1 Frequency of
Occurrence
Constant
Related
Issues:
duplicatesASTERISK-26400 app_queue: Queue member stops being called after AMI "Redirect" action for queues with wrapuptime
duplicatesASTERISK-26715 app_queue: Member will not receive any new calls after doing a transfer if wrapuptime = greater than 0 and using Local channel
Environment:Centos 7 64bit, Asterisk 13.13.1, FreePBX 13.0.190.11Attachments:
Description:When a queue member transfers queue call, he remains marked as "in call", even though he is free, and is not able to take any new calls until the transferred call is hung up.

With other words:

Caller (A) calls a queue and queue member (B) transfers the call to external party (C). Queue member B is not given any new calls by the queue until call between caller A and external party C is hung up.

After the call transfer, queue show looks like this:
asterisk*CLI> queue show 298
298 has 0 calls (max unlimited) in 'rrmemory' strategy (3s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 15s
  Members:
     Local/381@from-queue/n with penalty 4 (ringinuse disabled) (dynamic) (in call) (Not in use) has taken no calls yet

Please note that queue member 381 is marked as "in call" even though he is not busy or in call anymore.

Queue is configured like this:

[298]
announce-frequency=0
announce-holdtime=no
announce-position=no
autofill=yes
autopause=no
autopausebusy=no
autopausedelay=0
autopauseunavail=no
joinempty=yes
leavewhenempty=no
maxlen=0
memberdelay=0
min-announce-frequency=15
penaltymemberslimit=0
periodic-announce-frequency=0
queue-callswaiting=silence/1
queue-thereare=silence/1
queue-youarenext=silence/1
reportholdtime=no
retry=2
ringinuse=no
rvolume=0
servicelevel=15
strategy=rrmemory
timeout=7
timeoutpriority=app
timeoutrestart=no
weight=0
wrapuptime=5
context=

By testing I've found out that last asterisk 13 version with correct behavior is 13.7.2.

Problem is also described here:
https://community.asterisk.org/t/agent-get-status-in-call-and-not-in-use-and-they-do-not-able-to-receive-new-calls-until-the-transferred-call-have-been-finished/69047
and here:
http://issues.freepbx.org/browse/FREEPBX-13248

Thanks,
Andrej
Comments:By: Asterisk Team (asteriskteam) 2017-01-29 08:41:59.529-0600

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].

By: Etienne Lessard (hexanol) 2017-01-29 11:51:14.042-0600

Hello Andrej,

Your ticket is a duplicate of ASTERISK-26400 and ASTERISK-26715.

By: Andrej (tekach) 2017-01-29 13:00:05.779-0600

Maybe, I am not sure - ASTERISK-26400 is related to AMI and redirects, my issue is related to attended and blind transfers using phone. However, I can confirm that issue is not present if I disable wrap up time, wasn't aware of that.

I'll leave it to experts to decide if ticket should be closed as duplicate.

Thanks,
Andrej


By: Rusty Newton (rnewton) 2017-01-29 15:19:02.903-0600

Yes I agree with [~hexanol], I think these are the same root issue. Please comment on ASTERISK-26400 if you have any further updates or info. I've linked the issues so developers can see your information here as well.