I would like to use the Genesys Cloud WebRTC phone and operate it via the SDK.
In order to achieve this, I need to keep the persistent connection timeout (default is 600 seconds) active.
One way to achieve this is as follows:
- Create an In-Queue Call Flow in Architect which only contains a Disconnect block. For instance, let's name it
Dummy_Call_Flow.
- Create a Queue and set this In-Queue Call Flow to the queue. For example, name the queue
Dummy_Call and assume its generated ID is 12345678-90ab-cdef-fedc-ba9876543210.
- Make a call to the queue via API:
POST /api/v2/conversations/calls
Body: { "callQueueId": "12345678-90ab-cdef-fedc-ba9876543210" }
- Afterward, respond to the call using the following API:
PATCH /api/v2/conversations/calls/{conversationId}/participants/{participantId}
Body: {"state": "connected"}
However, my current need is to achieve this functionality when using the MediaHelper (https://apps.mypurecloud.jp/mediahelper).
When I use only the MediaHelper screen, the persistent connection timeout (default 600 seconds) does not seem to be established.
As a result, Step 3 above does not function effectively, making it impossible to proceed with the outlined steps.
It might be possible to resolve this by keeping both Genesys Cloud's standard user interface and the MediaHelper screen open simultaneously.
However, I want to achieve the desired behavior (established persistent connection and successful SDK execution) with only the MediaHelper screen open from start to finish.
Could you please advise the best way to handle this scenario?
#PlatformAPI#PlatformSDK------------------------------
Naoki Ono
------------------------------