Call Tracing: Tracking a call that does not reach Unified Expert Advisor

From DocWiki

Revision as of 19:22, 18 December 2009 by Docwikibot (Talk | contribs)
Jump to: navigation, search

Tracking a call that does not reach Unified Expert Advisor

Problem Summary ICM Script Editor – Script Monitor
Error Message None.
Possible Cause
  1. The call does not reach the script.
  2. The call tries to queue but fails SendToVRU or RunExtScriptnodes.
  3. The call fails the queue node before queuing.
  4. The call fails the queue node after queuing
Recommended Action
  1. Verify your Unified ICM and CVP configuration. See the Unified CVP troubleshooting guide: http://www.cisco.com/en/US/products/sw/custcosw/ps1006/prod_troubleshooting_guides_list.html
  2. Verify your Unified CVP > CallServer > SIP > DNIS length. See the Unified CVP troubleshooting guide: http://www.cisco.com/en/US/products/sw/custcosw/ps1006/prod_troubleshooting_guides_list.html
  3. Verify the Unified Expert Advisor assignment queue and the Unified ICM Skill Group configuration. Check the Skill Group real-time data. See the Unified Expert Advisor administration guide: http://www.cisco.com/en/US/products/ps9675/prod_maintenance_guides_list.html
  4. Verify the following configuration settings and see the Unified ICM configuration guide: http://www.cisco.com/en/US/products/sw/custcosw/ps1001/products_installation_and_configuration_guides_list.html4 (or the Unified CVP and Expert Advisor documents listed above):
  • The translation route configuration in Unified ICM and Expert Advisor :
  • The CUP static routes: TransRoute DN's should bemapped to runtime servers.
  • The Unified CVP SIP tab: Proxy Server should point to CUP server.
  • The script variable call.RequeryStatus for reason code.
Release Release 7.6(1).
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Call_Tracing:_Tracking_a_call_that_does_not_reach_Unified_Expert_Advisor"
Personal tools