Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

IPCC Ent Queue Manager - Call Unhold doesn't

Unanswered Question
Dec 12th, 2007
User Badges:
  • Silver, 250 points or more
  • Community Spotlight Award,

    Best Publication, November 2015

I have a script on my Queue Manager (very similar to IPCC Exp 3.5(4)) that has the following steps:

Play a prompt

Call hold (provides MOH)

delay for 20 seconds

Call Unhold

loop back to the beginning

The caller gets the prompt the first time, hears the music, and the script loops back. But they never here the prompt on subsequent loops (after the first one). I've added delays after the call unhold, put it in multiple times....cannot figure out why the media stream isn't returning.

This is IPCC Enterprise version 7.0 using translation routing. Any ideas?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
hadbou Wed, 12/19/2007 - 08:54
User Badges:
  • Bronze, 100 points or more

IP Contact Center (and EA) are virtual ACDs whcih use a Service Controlled IVR connected via teh IVR PG. As such, the service level reporting for the IPCC/EA services do not reflect abandons at the IVR queue point.

The IVR PG service control reporting has been enhanced to report time spent in the IVR at a queue point as queue time, and calls abandoned by the calls as abandoned. Calls that are routed are counted as answered. By mapping IVR PG and IPCC/EA PG service together, and pulling abandon information out out of the IVR PG Services, we can create a report that has a more accurate service level for the virtual ACD.

For real time reports, this would require joining the service real time table with the peripheral table to get the client type. Normal

statistics would be pulled for the IPCC/EA client, and appropriate abandon information would be pulled for the VRU client to create a combined service level report.

clarkjason Wed, 12/19/2007 - 09:39
User Badges:

I usually structure mine where I have an initial announcementthen hold, then LABEL then unhold, then secondary prompt, then hold, then LOOP to LABEL




This Discussion