Ive got a problem with calls sticking as reported in q even though they are not and it doesnt seem to be the usual problems.
The senario is that that I have two CSQs on two separate route points. One is my main line and one is the customer service queue.
I get stuck calls only if a customer calls the main line and the agent answer and then does a transfer (consultative) to the Customer service number. they wait till the C/S agent answers and then finish the transfer.
However in this senario the C/S CSQ will show a stuck call in the queue in the csq stats. The next time someone transfers it will go up to two and onwards.
any ideas what might be triggering this. I wondered is IPCC could be incorrectly tracking the call.
Sanjeev, Thanks for help. Unfortuantely this didnt fix the issue. I did some debugging and it seems the select resource step without connect was causing some kind of issue. If I loose this it works. I was using this to accertain if any agents were available so I wrote this logi using getreportingstatistic instead.
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...