skansakar | 2016-09-09 14:03:24 UTC | #1
The notification message on a consult transfer completion does not have a 'disconnectType' set. This seems to be same in v2 and v1 (tested using PureCloud UI)
On a single step transfer the 'disconnectType' for agent participant is set to 'TRANSFER'. However, for a consult transfer the 'disconnectType' is not set at all. Would have expected this to be set to 'TRANSFER_CONSULT'
Is this a bug or is there someway I can set this when disconnecting the initiator to complete the transfer?
tim.smith | 2016-09-09 18:43:20 UTC | #2
I've created ES-4296 to address the missing value for disconnectType.
skansakar | 2016-09-09 19:56:50 UTC | #3
Is this likely to be fixed anytime soon?
skansakar | 2016-09-28 15:26:44 UTC | #4
@tim.smith Is there any update when this will be available?
skansakar | 2016-09-30 10:47:35 UTC | #5
Can anyone give me a status of ES-4296 please?
I would like to know the timeline so I know whether to wait for this fix or look into other options. @KevinGlinski @tim.smith @anon84847021 @pierrick @rob.gevers
KevinGlinski | 2016-09-30 13:30:39 UTC | #6
work hasn't started on it yet, so we don't have an ETA
skansakar | 2016-09-30 13:46:14 UTC | #7
Thanks for getting back. I will look at other options
skansakar | 2016-09-30 22:09:42 UTC | #8
@KevinGlinski Is there any property I can rely on to differentiate between a normal disconnect and disconnection due to consult transfer?
How do PureCloud make this distinction?
KevinGlinski | 2016-10-03 13:46:18 UTC | #9
testing it this morning, for the agent in a consult, i'm getting "disconnectType": "transfer". If you aren't yet getting disconnectType, you should in a couple days. As for determining if it was a blind or consult, you would have to compare the start and end times of the other conversation segments.
skansakar | 2016-10-04 09:29:11 UTC | #10
I do get a disconnectType of transfer when doing a blind transfer. Not just on the consult transfer. :disappointed:
tim.smith | 2016-10-04 20:05:08 UTC | #11
For ACD calls, I'm seeing the agent's last segment have disconnectType set to peer now after consult transferring. I confirmed this with a new test today. Are you seeing a value in this scenario?
For non-ACD calls, I am not seeing a value for disconnectType on the user segment. I've asked that ES-4296 be reopened for this. (it was closed due to unable to reproduce; it was likely a different change that caused the value of peer to start being set.)
skansakar | 2016-10-05 08:34:14 UTC | #12
I guess by ACD calls and non-ACD calls, you mean the second calls is to an ACD or not?
Anyways, I will give it a try today and get back.
Either way, if it is a consult transfer should not disconnectType not be 'TRANSFER_CONSULT' rather than 'PEER'? :smiley:
tim.smith | 2016-10-05 14:38:07 UTC | #13
I was referring to the initial call being ACD vs calling a user's DID. In my testing, the consult call was to an external number.
I'm working with the dev team to see what we can do to improve what data is logged.
system | 2017-08-28 19:27:06 UTC | #14
This post was migrated from the old Developer Forum.
ref: 381