Does anyone have any idea what might seem to cause CAD to stay in the reserved state longer than normal? I'm talking about 20 seconds plus. However, all calls got through just fine finally. Nothing has recently been changed on the servers as well as on the agents. This has been happening intermittently and only appears to occur to certain agents. It doesn't switch from one agent to another. It seems to always stay with same agents. Never happened before. So I don't believe there is anything to do with the phone config.
Any explanations or suggestions on where I should be looking in order to fix the issue would be greatly appreciated.
Thanks for the link. No, they are not part of the same CSQ. I just double-checked the prompt in my queue step just to be sure it's not accidentally mis-configured and it looks good to me. So I think the document doesn't seem to apply here.
Question, does it have to be only the first prompt in the queue that must allow interruptible. I'm asking this because I'm showing my 3rd prompt down is not interruptible and I'm not sure why it was configured that way. By mistake perhaps. It would make sense to go interruptible all the way. Just wanted to confirm.
Sometimes you don't want the caller to be able to hit # or whatever and skip prompts - to prevent that, set 'Barge In' on the prompt and other steps to 'No'.
Interruptible means the system can interrupt that step; i.e. when it decides something else needs to be done (such as transfer to agent).
So generally, anythign in the queue branch that can be interruptible should have interruptible set to the default of 'Yes'. The third one down would make it quite random, as it's one of a few prompts and not the first in the list...
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Since you have a 3rd prompt that is set to be uninterruptable it would kind of make sense that only the calls that were being transferred to an agent at that prompt are seeing this issue. Calls that are transferred to agents prior to hitting that prompt would never have the issue because the prompts get interrupted.
I believe you should set that prompt to be interruptable and give that a shot. It seems to be a reasonable step at this point.
If this works for you please rate the original post. This helps with future searches for others having the same issue.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...