Cisco Cisco E-Mail Manager Unity Integration Option

Normal label type and a correlation ID.

1

Required: Translation Route to VRU.
Optional: Queue and Run VRU Script.

Normal label type and a DNIS.

2

Optional: Send to VRU, Queue, and
Run VRU Script.

Resource label type and a correlation ID. The
routing client can automatically take back the call

3

from the VRU when the system software returns a
destination label.

Note: Use this type (rather than Type 7) when the
routing client can automatically take back the call
from the VRU when the system software returns a
destination.

Resource label type and a DNIS.

4

Required: Send to VRU. Optional:
Queue and Run VRU Script.

Resource label type and either a correlation ID or a
DNIS.

5

Note: Use this type (rather than a Type 3 or Type
7) when the routing client itself takes care of
mapping the call to requests from the system
software.

The VRU for this type is programmed
so that it can recognize such a request

No label, no correlation ID, and no DNIS (call is
already at the VRU).

6

based on the call qualifiers, so you can
then assume the call is already at the
VRU.

Optional: Queue and Run VRU Script.

Optional: Send to VRU1, Queue, and
Run VRU Script.

Similar to Type 3, but the system software
automatically instructs the VRU to release the call
when it sends a destination label to the routing client.

7

Note: Use this type (instead of Type 3) when the
routing client cannot take back the call from the
VRU. That is, the system software automatically
instructs the VRU to release when it sends a route
response to the routing client; for example, CWC
Network VRUs.

Required: Translation Route to VRU.
Optional: Queue and Run VRU Script.

Similar to Type 2, but a Type 8 VRU is used when
the NAM has a routing client that controls the call
to the VRU.

8

Required

Queuing for Unified SCCE.

9

Configuration Guide for Cisco Unified ICM/Contact Center Enterprise and Hosted Release 8.0(2)