Genesys Cloud - Developer Community

 View Only

Discussion Thread View

Handling re-connects when collecting call-events / transcription

  • 1.  Handling re-connects when collecting call-events / transcription

    Posted 30 days ago

    Hi channel,

    Hope you are doing well. I was able to create my Genesys components that can collect the transcription in real-time. The application is quite stable, but I have some questions regarding token/channel/websocket expiration/reconnect and what happens to the call events/ transcription during reconnects.

    I'm considering the following cases:

    • Client token – Token used by the APIs – I reconnect 5min before expiring
    • Channel Expire – refresh channel 5min before expiry
    • Websocket Close  - When the websocket gets closed (or I receive a topicName "v2.system.socket_closing"), I'm simply reconnecting the full channel.

    Now my questions are:

    1 – Is there any case that I'm missing?

    2 – What happens, for example, to the channel associated with a transcription if I re-connect the channel, while there is a call-in place? Will I lose the transcription during that reconnect period?

    3 – The same for calls, what happens if I receive incoming calls while I reconnect the channel? After I reconnect, will I still see the calls that took place during the re-connect?

    4 – "v2.system.socket_closing" or websocket close event – Do I really need to re-connect the whole channel or just the websocket?

    5 – I noticed that I need to recreate the existing subscriptions, after reconnecting the channel. Will that apply if I only need to reconnect the websocket (in case you tell me in 4) that I only need to reconnect the websocket)?

    Thanks!!

    Luís


    #PlatformSDK

    ------------------------------
    Luis Silva
    ------------------------------


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources