RONA calls are calculated as abandoned Ring

Unanswered Question
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
david.macias Tue, 02/02/2010 - 03:32

The only reason why I would think that is that the RONA timer might be expiring in ICM, but that's just a shot in the dark.  Can you post your RONA timers?  CVP, UCM, ICM?

david

Nathan Luk Tue, 02/02/2010 - 05:37

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.

Hope that helps.

Cheers,

Nathan

Michael Whaley Tue, 02/02/2010 - 10:02

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).

Frustrating to say the least.

Chad Stachowicz Tue, 02/02/2010 - 10:44

nathan hit this nail square on the head, its doucmented in the CVP guide, I would say not very well or largely noted within the community though :/

Chad

Actions

This Discussion