Genesys Cloud - Main

 View Only

Discussion Thread View
  • 1.  User is on Queue but shows that the person is not responding

    Posted 03-18-2025 10:00

    I have been getting a lot of complaints about the agents who are on queue, but they are not getting the ring, and they are being shown as not responding. I am capturing the network logs. I am not sure how to go about this, as this happening to random users and I do not want to keep opening tickets with Genesys on this. How can this be addressed?

    Thanks


    #SystemAdministration
    #Telephony
    #Unsure/Other

    ------------------------------
    John Francis
    NA
    ------------------------------


  • 2.  RE: User is on Queue but shows that the person is not responding

    Posted 03-18-2025 13:59

    Hey John,

    Based on the information that you've provided (agents being randomly marked as not responding, not being notified of ringing, etc.) this sounds like it may be an issue with your network. When we've seen this issue in the past, it's been caused by firewall or proxy settings that are affecting traffic to and from Genesys Cloud. I would recommend reverting any changes that your network team may have made recently. We recommend that all Genesys traffic be white listed or bypassed to avoid interruptions of service.



    ------------------------------
    Jason Kleitz
    Online Community Manager/Moderator
    ------------------------------



  • 3.  RE: User is on Queue but shows that the person is not responding

    Posted 03-19-2025 08:15
    Edited by Tristen Schwarzenberger 03-19-2025 08:20

    Hey John,

    We've been having this exact issue and it's incredibly tough to capture because it's so sporadic. We can't recreate it on the spot. All of our agents are work at home as well. We thought it was network related at first, but so many people we've monitored have very solid connections and we even have them do a diagnostic check afterward and it's always green. We are bypassing all Genesys traffic via split tunneling.

    The best thing we've been able to do so far is enable the Persistent Connection setting on their WebRTC phones and also put them on the desktop app instead of accessing via the chrome app.
    It's not perfect, but I'd say both of these things have helped to reduce the problem.

    Another thing we believe that is also causing these problems is for whatever reason very randomly Genesys sound settings keep reverting back to "Use Computer Settings" and don't know why. Happens to some people and this will cause the notifications to alert in their headsets instead of their speakers and since they don't have their headset on, they'll miss the call.



    ------------------------------
    Tristen Schwarzenberger
    IT Engineer
    ------------------------------



  • 4.  RE: User is on Queue but shows that the person is not responding

    Posted 03-19-2025 09:46

    Hey Tristen, 

    We have been having this issue on and off for over a year now. I share the sentiment that it is difficult to capture the issue due to the sporadic nature. 

    One thing I have noticed is that the majority of users having the issue (not all) will have their WebRTC phone profile reverted back to "Use Computer Settings". Additionally, the profile they were using is also greyed out and unusable even though the actual devices it points to are still connected and working properly. We are in a VPN environment so audio routing can be finicky at times, and if your hardware PC is pointing to a different audio input/output than your VPN or than your Genesys that can cause issues. 

    We have figured out a work-around that works 80-90% of time to fix the issue, but it is only a temporary fix as the issue will inevitably pop up again later. I will post the steps for the work-around issue below. Any advice/feedback would be appreciated. 

    1. Genesys Calls Tab
    2. "Settings" Icon (Little gear at the top)
    3. Select the dropdown for "User Computer Settings"
    4. Delete all profiles
    5. Add New profile. Check the box for "Default Profile" and select your input/output hardware. Save. 
    6. "Quit" Genesys by right-clicking the Genesys icon in your Windows toolbar and selecting Quit (Don't just X out of the program, completely quit it)
    7. Open Genesys on the web. 
      1. This will often result in the web browser asking for permissions to access your microphone. Click "allow"
    8. Double-check the new profile is there, close the browser tab, and then re-open the desktop app. 

    This will eventually result in the WebRTC profile reverting back to "Use Computer Settings", causing the same issue. But this does usually correct the problem for a few days/weeks.

    Thanks,

    Matt Pleus



    ------------------------------
    [Matt] [Pleus]
    [Business Systems Analyst]
    ------------------------------



  • 5.  RE: User is on Queue but shows that the person is not responding

    Posted 03-19-2025 09:52

    Just wanted to add to my own comment as I feel this may be relevant:

    This issue often occurs either first-thing in the morning, upon login, or after coming back from a break or a lunch. It's almost as if the connection between Genesys and the audio device (headset, speakers, mic, etc.) has "gone to sleep" or disconnected somehow. 

    Thanks, 

    Matt Pleus



    ------------------------------
    [Matt] [Pleus]
    [Business Systems Analyst]
    ------------------------------



  • 6.  RE: User is on Queue but shows that the person is not responding
    Best Answer

    Posted 03-19-2025 10:25

    As you say, it is often hard to track down especially for agents working at home.

    "Network issues" can be wide-ranging. For WAH agents it is always recommended (industry standard) to have them physically connect the computer to the router, not use Wi-Fi.

    The data path for Client operations takes a different route across the internet than does WebRTC communications, so sometimes the data signal and WebRTC are not in sync, which leads to a call alert timing out and sending the agent to Not Responding. You can have them run the WebRTC troubleshooter in the client right away to check for issues...though if they are intermittent it may not show anything.

    This article has useful info on how to troubleshoot WebRTC problems in various browsers:

    https://www.webrtc-developers.com/debugging-webrtc-in-the-browsers/

    That is separate from the genesys Cloud troubleshooter and gives you more logging similar to Console and network logs.

    Windows Performance Monitor is another tool you can use to gather info over time to see what's happening on the agent's computer...but that requires having a user who has it happen fairly often.



    ------------------------------
    George Ganahl GCCX-AI, GCP, GCSME, ICCE, ICHD, etc.
    Technical Adoption Champion
    Genesys
    ------------------------------



  • 7.  RE: User is on Queue but shows that the person is not responding

    Posted 03-19-2025 12:14

    Hi,

    Maybe check this as well; Call Queue / Voice / Alerting Timeout (Seconds)

    We had an issue when we programmed Alerting Timeout for agents to 12 seconds before call Re-Queues. Genesys started causing issues: agents couldn't press Answer button, call didn't ring on agent's desktop etc. I opened a ticket and Genesys support informed me that the alerting time was too short and that Alerting Timeout (Seconds) should be minimum 18 - 20 seconds. This resolved the issue.



    ------------------------------
    Tahir Filipovic
    Senior IT Specialist
    ------------------------------



  • 8.  RE: User is on Queue but shows that the person is not responding

    Posted 03-19-2025 13:19

    I've also had this issue and it has not returned since.  We use the WebRTC softphone with the Chrome browser and GCBA installed on all agent laptops.  All work remote.  I had to create an audio profile for the agent making speaker, mic & alert all route to the headset then saved that as the default profile.  I then showed the agents how to confirm their audio profile in Genesys is correct.  I enabled persistent connection also.  All of that helped, yet there were still agents being put into alert-not responding.  I put a filter up for abandons and short abandons and discovered two things.  First, we had a campaign that gave an option to press 1 to  speak with an agent but the callers were hanging up within 2-3 seconds placing the agent in not responding.  Often the agent didn't see the call or it dropped too quickly to answer it.  We changed the short abandon threshold and made an adjustment to the campaign.  Problem solved.



    ------------------------------
    Rial Coleman
    Sr. VoIP Administrator
    District of Columbia Water and Sewer Authority
    ------------------------------



Need Help finding something?

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