Genesys Cloud - Main

 View Only

Sign Up

  • 1.  Did something change with Web Sockets?

    Posted 18 days ago

    I am using web sockets and API for our phone.  Out of blue, starting from 11/21 some of our deployments  started to have sporadic wss socket errors timeout. Seems to be limited to a small pocket of deployments for now. Is anyone else facing the same issue ? 

    ERROR - _handle_websocket_messages - WebSocket closed: Connection to remote host was lost. url: wss://streaming.mypurecloud....


    #API/Integrations
    #Telephony

    ------------------------------
    Amit Abdul
    ------------------------------


    #API/Integrations
    #System/PlatformAdministration
    #Telephony

    ------------------------------
    Amit Abdul
    ------------------------------


  • 2.  RE: Did something change with Web Sockets?
    Best Answer

    Posted 17 days ago

    Hello Amit, 

    I can give you some troubleshooting steps, but ultimately when it comes to websockets my best recommendation would be to open a support case. 

    Some common issues related to the error:

    • Connection timeout during the initial handshake
    • Network Connectivity issues
    • server-side connection limits
    • client-side buffer overflow

    Having these in mind here are some troubleshooting recommendations. 

    1. Check if your WebSocket connection timeout settings match Genesys Cloud's requirements, 10 seconds.
    2. Verify that your client maintains proper buffer, 20 seconds of audio buffer. 
    3. Monitor network stability between your deployment and Genesys. 
    4. Implement proper reconnection logic if not already in place. 

    I have seen this issue come up and its usually the app or whatever you are using is taking longer than 10 seconds for the initial handshake and the web socket closes. 

    Hope this helps. 



    ------------------------------
    Cameron
    Online Community Manager/Moderator
    ------------------------------