Hi everyone,
We've been experiencing a lot of similar issues in our implementations across various regions and with different types of setups, such as BYOC Cloud trunks and Premises Edges. This has been both frustrating and problematic.
Like you, we've opened cases and worked through them, but without a conclusive resolution. We've been told it's either a "problem with reaching DNS," a "client issue," or simply that "everything appears normal." At one point, support even suggested using a time machine to revert to the previous version, but unfortunately, that didn't help.
It seems like a systemic issue with how the client handles calls globally, as it's occurring across different regions and deployment models.
I wish I could say the problems are resolved and no longer recurring, but that's not the case. I'm sharing my experience in the hope that someone will endeavor to make improvements in the product.
------------------------------
Раско Радојевић
Rasko Radojevic
Serbia
------------------------------
Original Message:
Sent: 05-30-2024 17:08
From: suyog gupta
Subject: User into Not Responding despite Auto Ans enabled
Hello folks,
We have auto answer enabled for all of the agents but for some of them they get Alerted for 30s for an incoming call via queue and then they go into Not Responding status. I am unable to figure out why would this happen? Why it will alert for that long on auto answer configured. Status of those agents when they got call was On Queue. After looking at the timeline details it shows Disconnect type as Client (which per resource center means Genesys Cloud user interface caused the disconnect. For example, an agent clicked End Call during a voice interaction) for that agent but agent can not click on End Call in this situation.
Has someone run into this situation and were able to figure out an answer? Appreciate any insights anyone can share or possible scenarios when this can happen.
Thanks!
#Routing(ACD/IVR)