Unable to answer second incoming call via API

[WardBrink]

Hi there!

We are experiencing a problem to pickup a second call via the API using a WebRTC phone. We are doing the following request:

PATCH https://api.mypurecloud.de/api/v2/conversations/{conversationId}/participants/{participantId}
with the body

{
"state": "connected"
}

For the PATCH of the first incoming call we implemented the workaround as suggested by the folowing forum post:

Answering inbound calls via JS SDK with WebRTC Station

In our setup the internal calls are being handled by the purecloud webinterface/desptop client so I am afraid we do not have the same situation as you have. Only routed incoming calls are being picked up by our internal application. What also helps it accepting the internal call through the purecloud web interface and check which calls are being made to the purecloud API (+ the information sent)I in the networktab when pressing F12. Perhaps you need to perform an intermediate action or pass som…

We are able to succesfully pickup the first call, but if we are already in a call, we are unable to answer a second call. I already tried setting the first conversation On Hold, since that is what happens if you transfer via the web interface.

Hope anyone can help!