Cisco Cisco E-Mail Manager Unity Integration Option Betriebsanweisung
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.
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.
• The Call Variables are used in "SET" node by several customers in an Admin Script as
temporary placeholders for complex calculation. However, since any call context is only
existent as long as the call itself, the Variables cease to exist once the Route Request (a.k.a
Call) has been completed (be it by virtue of a successful Routing Script Execute Completion
or an Administrative Script Execute Completion). They cannot be used to store values, so as
to be re-used in Routing Scripts, as the Routing Scripts itself will have a new set of Call
Variables created for the Route Request.
existent as long as the call itself, the Variables cease to exist once the Route Request (a.k.a
Call) has been completed (be it by virtue of a successful Routing Script Execute Completion
or an Administrative Script Execute Completion). They cannot be used to store values, so as
to be re-used in Routing Scripts, as the Routing Scripts itself will have a new set of Call
Variables created for the Route Request.
• When comparing two Call Variables of Numeric string, the Built-In Function "value()" must
be used in the IF Node to perform Numeric comparison, otherwise there will be a String
comparison. Ex: value(Call.PeripheralVariable1)>=value(Call.PeripheralVariable2) where
Call.PeripheralVariable1 and Call.PeripheralVariable2 are given as Numeric string.
comparison. Ex: value(Call.PeripheralVariable1)>=value(Call.PeripheralVariable2) where
Call.PeripheralVariable1 and Call.PeripheralVariable2 are given as Numeric string.
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.
Scripting and Media Routing Guide Cisco Unified ICM/Contact Center Enterprise & Hosted Release 7.5(1)
132
Chapter 7: Using Formulas
Variables