In Unified ICME,
Network VRU is a configuration database entity. It is accessed using the
Network VRU Explorer tool of ICM Configuration Manager. A Network VRU entry
contains the following information:
number from 7, 8, and 10, which corresponds to one of the types.
Labels: This is a list
of labels, which
Unified ICME can
use to transfer a call to the particular Network VRU that is being configured.
These labels are relevant for Network VRUs of Types 7 and 10. These types use
the Correlation ID mechanism to transfer calls. Labels for Type 8 are defined
in the Translation Route Explorer tool of ICM Configuration Manager, and are
invoked using a Translation Route to VRU node.
comprises the following components:
string, which becomes a DNIS that is understood by a SIP Proxy Server, by a
static route table, or by gateway dial-peers.
client, also known as a switch leg peripheral. Each peripheral device that can
act as a switch leg must have its own label, even if the digit strings are the
same in all cases.
introduced Network VRU Type 10, which simplifies the configuration of Network
VRU’s for Unified CVP. For most call flow models, a single Type 10 Network VRU
can take the place of the Type 3, 5, 7, or 8 Network VRUs, which were
associated with the Customer Instance and the Switch and VRU leg peripherals.
The VRU-Only call flow models still require Type 8. However, in a specific case
Type 7 is required.
configuration entries themselves have no value until they are associated with
active calls. Following are the three places in Unified ICME where you can
perform this association:
for a given peripheral in the PG Explorer tool of the ICM Configuration
Instance configuration in the ICM Instance Explorer tool of the ICM
On every VRU
Script configuration in the Network VRU Script List tool of the ICM
Depending on the
call flow model, use Unified ICME to search either the peripheral or the
customer instance to determine how to transfer a call to a VRU. Unified ICME
examines the following:
VRU and the Network VRU using the Translation Route mechanism. The network VRU
is associated with the switch leg peripheral when the call first arrives on a
switch leg and Network VRU is associated with the VRU leg peripheral when the
call is being transferred.
VRU from the System Information tool, when the call is being transferred to the
VRU using the Correlation ID mechanism. The Network VRU is associated with the
Customer Instance or the default Network VRU.
VRU, which is associated with the VRU Script every time it encounters a
RunExternalScript node in its routing script. If the call is currently not
connected to the designated Network VRU, Unified ICME does not execute the VRU
supported VRU types still work with
7.1(1) and later for existing deployments. However, new installations should
use Type 10 and existing deployments should switch to Type 10 on upgrade.