There are a couple of reasons for this. This includes: Not logged in station, permission check failing, and using client credentials instead of user credentials. could you provide a correlation id so that I confirm what is going on? If not I will redirect you to the support group for a better explanation/help
The correlation id : 5a7b2829-1c3d-4fc4-8ab3-8a978adc8362
I am guessing it has something to do with webrtc connectivity although we are not not using it explicitly.
Here's a little background-
We login the agent and receive notifications for incoming interactions using the java sdk. Now we want to answer calls using the sdk only( we are not using webRTC explicitly). The calls do get accepted but audio is never audible and when we tried testing it using api's we faced the same issue.
Status 202 is returned but call does not gets connected.
The user is a valid logged in user.
Is it possible to do without webRTC explicitly. If yes, what's going wrong?
This could be a potential bug. I would open a ticket with our Care team. I would provide the correlation id to the Care team as this will help them when they go through the problem resolution process and assign it to an engineering team for further review.
Thanks,
John Carnell
Manager, Developer Engagement