Cisco Cisco IPCC Web Option Références techniques
26
Unified ICM Configuration
26
6.9. Labels
The format of label strings sent to the VRU in a Route Select, Connect,
Temporary Connect, or Connect-to-Resource message is not dictated by
the Unified ICM. The VRU is responsible for interpreting the label and
acting upon it; this interpretation may vary from one VRU implementation
to another.
Temporary Connect, or Connect-to-Resource message is not dictated by
the Unified ICM. The VRU is responsible for interpreting the label and
acting upon it; this interpretation may vary from one VRU implementation
to another.
For labels of type BUSY, RING, and DEFAULT the label type configured
in the Unified ICM is passed to the VRU in Route Select and Connect
messages. Other label types are marked as type NORMAL. The VRU may
use the label type (where available), in addition to the label itself, to
determine how to process the response.
in the Unified ICM is passed to the VRU in Route Select and Connect
messages. Other label types are marked as type NORMAL. The VRU may
use the label type (where available), in addition to the label itself, to
determine how to process the response.
6.10. Network Trunk Groups
Unified ICM supports a configuration in which several VRUs share a
single Network Trunk Group. In this configuration, the physical VRUs
combine to give the appearance of a single “virtual” VRU with increased
capacity. Since the network can deliver a call on any trunk in the Network
Trunk Group, the call may arrive on any of the VRUs sharing the Network
Trunk Group. For this reason, all the VRUs sharing the Network Trunk
Group should perform identical call processing.
single Network Trunk Group. In this configuration, the physical VRUs
combine to give the appearance of a single “virtual” VRU with increased
capacity. Since the network can deliver a call on any trunk in the Network
Trunk Group, the call may arrive on any of the VRUs sharing the Network
Trunk Group. For this reason, all the VRUs sharing the Network Trunk
Group should perform identical call processing.
Network
VRU 1
VRU 2
VRU 3
Network Trunk Group
VRU 2
Trunk Group
VRU 1
Trunk Group
VRU 3
Trunk Group
"Virtual" VRU
Fig u re 3: Ne two rk Tru n k Gro u p s
Configure one Network Trunk Group for the “virtual” VRU. Then, for
each physical VRU, configure the Trunk Group(s) on that peripheral. Set
the Network Trunk Group for each peripheral Trunk Group to be the
Network Trunk Group for the “virtual” VRU.
each physical VRU, configure the Trunk Group(s) on that peripheral. Set
the Network Trunk Group for each peripheral Trunk Group to be the
Network Trunk Group for the “virtual” VRU.
Note that all Peripheral Targets associated with any of the VRUs are
defined in terms of the Network Trunk Group. It is therefore not possible
defined in terms of the Network Trunk Group. It is therefore not possible