Jeremy_Gillip | 2017-04-25 15:02:20 UTC | #1
I am working on testing disconnecting calls that are stuck to users. I was able to use the developer tools to get all the information that i need for the
/api/v2/conversations/callbacks/{conversationId}/participants/{participantId}/communications/{communicationId}
call but i get this in return
{ "status": 403, "code": "forbidden", "message": "Access to Conversation 65d818fe-7194-4132-812f-e42b3eb9a049 is forbidden.", "contextId": "8344a211-978e-42e6-8c16-ab2e00ad4f6f", "details": [], "errors": [] }
From reading older posts on similar 403 errors its looks like since my session is my support account in the developer tools dosent match the participant ID. Is there a way my support account can take ownership of the interaction to disconnect it or is there a better way to disconnect stuck calls ?
Thank you.
tim.smith | 2017-04-25 15:18:25 UTC | #2
This isn't possible for you to do manually. You will need to open a ticket with PureCloud Support to investigate and remove the stuck call.
Jeremy_Gillip | 2017-04-25 15:30:16 UTC | #3
I was afraid of that, Thank you for the quick reply Tim as always.
system | 2017-08-28 19:34:07 UTC | #4
This post was migrated from the old Developer Forum.
ref: 1221