Quick Setup Guide

4-11
Getting Started with Cisco Unified IP IVR, Release 6.0(1)
Chapter 4 Basic Call and Contact Flow Concepts
Debugging Problems in the Unified IP IVR System
be used when necessary. Expanded Call Variables are configured both in the Unified ICME system and
in the CRS system. In the CRS system, they are configured from the CRS ICM subsystem configuration
web page.
Script Parameter Separators
One function that can prove useful is the ability to use the Unified ICME RUN_SCRIPT node with a
name that includes parameter separators. The Parameter Separator is defined from the CRS ICM
subsystem configuration web page. By default it is the | (pipe) symbol.
One example of its usefulness is if you have one main script. Within that script, you can have multiple
branches that would execute based on the value of a parameter that is passed by the Unified ICME
system.
Example
Configuration data:
• CRS Script name = testscript.aef
• VRU Script name = testscript ICM VRU Scripts
• Run VRU Script node in Unified ICME = testscript|100
Get ICM Data step in script testscript.aef:
• Field Name: VRU Script Name
• Token Index: 1
• Decoding Type: String
• Local Variable: param1 (of type string)
In the preceding example of a script parameter separator, the script variable param1 will contain the first
parameter (after the |) In this case, that would be 100. This example allows the variable param1 to be
tested and for the script to take the desired branch based on its value. The benefit is that only one VRU
Script needs to be defined in the CRS system, and you do not have to use any other variables as
parameters to determine which branch to take in the script.
Note When you use parameter separators in CRS, the Unified ICME script name must include the parameter
as part of its name. If you want to pass a different parameter like “testscript|200” then you need to
configure another VRU script on the Unified ICME system and name it testscript|200.
For more information on script parameters, see the Cisco Customer Response Solutions Editor Step
Reference Guide and the Cisco Customer Response Solutions Getting Started with Scripts Guide.
Debugging Problems in the Unified IP IVR System
The SS_TEL or SS_SIP (Telephony subsystems) debug traces can be used to debug the CM or CME
Telephony aspect of a call.
When debugging Unified ICME problems in the Unified IP IVR system, turn on the ICM related debugs.
The CRS LIB_ICM (ICM library) and the SS_ICM (ICM subsystem) show the Unified ICME events
messaging. Use the Cisco Customer Response Solutions Servicing and Troubleshooting Guide for
instructions on how to interpret the messages and how to use Trace.