devin | 2022-07-22 16:24:07 UTC | #1
Hello,
I'm receiving an error when trying to do a consult. I've implemented a softphone using the WebRTC SDK and am attempting to replace the "agent" participant with a queue. The softphone is authenticated using an OKTA token (Token Implicit Grant (Browser)), and can interact with the conversation API without problem. I've been able to implement a blind transfer, but now seem to run into this issue.
There are two participants on the calls:
- Customer: Outbound dialed phone number.
- Agent: Me, the authenticated user.
POST /api/v2/conversations/calls/ead990f2-ed24-4bc6-b41f-79b093d35cf8/participants/5faff9bc-2f97-41b4-aa11-df22522d2ee4/consult
{"speakTo":"DESTINATION","destination":{"queueId":"38a3c042-d214-4c1c-8068-62607f03a0c2"}}
-- RESPONSE -- {"message":"You are not a connected participant on the call","code":"not.a.participant","status":400,"contextId":"c4d5666d-a2d5-4bfb-8159-62803267a0dd","details":[],"errors":[]}
I saw a similar post from August '21 regarding this error, but I believe my situation is slightly different.
Can anyone advise what I'm doing wrong?
Context ID: c4d5666d-a2d5-4bfb-8159-62803267a0dd
devin | 2022-07-26 17:11:48 UTC | #2
Bump Is anybody able to help me with this item?
Jerome.Saint-Marc | 2022-07-27 13:23:48 UTC | #3
Hello,
If your agent is trying to create a consultation call between the customer and the queue (customer "talking" to the queue - while agent is on hold), you must use the customer's participantId in your request (not the agent's participantId).
I mean: POST /api/v2/conversations/calls/ead990f2-ed24-4bc6-b41f-79b093d35cf8/participants/8898195c-d2fa-4104-a9ec-85a66d5ae71f/consult
Regards,
system | 2022-08-27 13:24:36 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 15644