BenjaminRamsay | 2017-01-20 18:01:20 UTC | #1
I'm trying to use /api/v2/conversations/calls/{callId}/participants/{participantId}/replace to transfer a call from a queue to a user. The call is sitting on hold in the queue. I issue this command and get a 202 back, but nothing happens.
I've tried this from Developer Tools (authenticated as myself) and from my c# code (authenticated using Client Credentials). Here's my C# code if that helps:
var convApi = new ConversationsApi(); var call = convApi.GetCallsCallId(callId);
string participantId = call.Participants.First(x => x.Purpose == "acd").Id; TransferRequest transferBody = new TransferRequest("xxxxx-my-user-id-here-xxxxxx", null, null, null, false); convApi.PostCallsCallIdParticipantsParticipantIdReplace(callId, participantId, transferBody);
tim.smith | 2017-01-20 22:05:22 UTC | #2
The short answer is that unfortunately it isn't possible to transfer calls waiting in queue.
- CS-765 has been opened as a bug to return 400 in this scenario instead of 202 for now
- CS-763 and IONEDGE-3761 have been opened to add support for transferring calls waiting in queue
BenjaminRamsay | 2017-01-20 22:07:36 UTC | #3
Bummer, I thought this would be possible since the documentation article about Transfers specifically mentions the ability to transfer from queue to queue (third bullet point).
This was my latest attempt to come up with a clever way to simulate the straight-to-on-hold functionality I was trying to create in my other post. I was going to transfer the call to an empty queue where it can sit "on hold" until the user is ready for it, then transfer it back to them. Really thought I had it this time, but looks like I'm thwarted once again =)
Thanks for letting me know
tim.smith | 2017-01-20 22:12:11 UTC | #4
Dang, looks like someone got a little ahead of themselves with the documentation. Thanks for pointing that out.
system | 2017-08-28 19:30:54 UTC | #5
This post was migrated from the old Developer Forum.
ref: 818