we are using IPCC 7.1.4 CVP 3.1 with gatekeeper, we have aproblem with RONA calls that they are counted as abandoned ring , even after we upgraded to ICM 7.2.5 the call disposition flag continue to appear with 3 rather than 19 which is the RONA flag.
This is how RONA reporting works with CVP. Since call control is with CVP, when it pulls the call back when the call RONAs, it is reported back to the PG as an abandon while ringing. No way around this unfortunately. This is also important to communicate back to the business as the normal abandon stat in the out of the box webview reports generally includes aban + aban while ringing so RONAs will be artificially inflating their abandonment rates.
The only way to get a RONA stats at the agent level with CVP would be to do a count of how many times an agent went into not ready reason code 32767. The Cisco docs say to create a separate call type for RONA calls if you wish to count RONA calls at the Call Type level.
We had something similar messed up with our reporting on RONA calls, only they were not showing up as abandoned ring. I'm the not a reporting guru, but we tracked it down to BugID CSCtb51878 "Calls abandoned not displayed in "Router calls Abandoned on ring"
It's fixed in 7.5(7). Sometimes it's hard to tell from the bug descriptions, but you might check to see if this fits your issue.
We also had an issue where RONA calls were not coming up properly in the TCD. This bug is CSCsy14835 and is also fixed in 7.5(7).
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...