Cisco Cisco IPCC Web Option Release Note
User Setable
Description
Data Type
Variable
Select nodes to determine the specific
network cause of failure and conditionally
retry the attempt as necessary.
network cause of failure and conditionally
retry the attempt as necessary.
No
An encoded value that indicates the date
on which ICM software processes the call.
on which ICM software processes the call.
Integer
RouterCallDay
No
A value that is unique among all calls ICM
software has processed since midnight.
software has processed since midnight.
Integer
RouterCallKey
RouterCallDay and RouterCallKey
combine to form a unique call identifier.
combine to form a unique call identifier.
No
The name of the routing client that made
the route request.
the route request.
String
RoutingClient
No
Number of seconds a call has been queued.
Integer
TimeInQueue
Yes
ISDN private network User to User
information
information
String
UserToUserInfo
No
Indicates the result of a previous VRU
node.
node.
Integer
VruStatus
Note: For a Post-Routing® request from an Aspect ACD, PeripheralVariable1 through
PeripheralVariable5 map to the Aspect variables A through E. The Aspect routing client passes
these variables to ICM software as part of the request and ICM software returns them with the
response. Other routing clients might use some of these variables for other purposes. The values
of these variables are also stored in the Route_Call_Detail table of the ICM database.
PeripheralVariable5 map to the Aspect variables A through E. The Aspect routing client passes
these variables to ICM software as part of the request and ICM software returns them with the
response. Other routing clients might use some of these variables for other purposes. The values
of these variables are also stored in the Route_Call_Detail table of the ICM database.
What are Expanded Call Context (ECC) Variables?
Expanded Call Context (ECC) variables store values associated with the contact.
ECC values are written to Termination Call Detail records only if, and when, an ECC value is
explicitly set (which can be done any numbers of ways, such as using a script, an IVR, a NIC,
CTI, and so on). This applies to null values as well as non-null values.
explicitly set (which can be done any numbers of ways, such as using a script, an IVR, a NIC,
CTI, and so on). This applies to null values as well as non-null values.
If an ECC variable has been defined, but never assigned a value, it will not have a row in the
Termination Call Variable table when a Termination Call Detail record is written.
Termination Call Variable table when a Termination Call Detail record is written.
Generally speaking, ECC values are passed from leg to leg on the call. Once a value has been
assigned, the value is recorded in the Termination Call Variable for every Termination Call
Detail Segment. Note, however, that this depends on how each new call segment is created. If
it does not involve translation routes or IPCC, and is outside the original peripheral, ECC
variables, like all call variables, cannot be propagated.
assigned, the value is recorded in the Termination Call Variable for every Termination Call
Detail Segment. Note, however, that this depends on how each new call segment is created. If
it does not involve translation routes or IPCC, and is outside the original peripheral, ECC
variables, like all call variables, cannot be propagated.
ICM software is delivered with some ECC variables, and you can create others through
Configuration Manager. For more information, see the
Configuration Manager. For more information, see the
(http://www.cisco.com/en/US/products/sw/custcosw/
ps1001/tsd_products_support_series_home.html).
ICM Scripting and Media Routing Guide Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.0(0)
138
Chapter 7: - Using Formulas
Variables