Cisco Systems ICM Software Version 4.5 1.2.4. Service Arrays

28 Overview
A network trunk group is a group of trunks organized to reflect the
routing client’s view of trunks. A network trunk group can map to one or
more peripheral trunk groups. For example, say you have two VRUs at a
call center site in Dallas. Each VRU has two T1 circuits (see Figure 8).
ACD2
ACD1
NY.Megacom.Trkgrp103
NY.Megacom.Trkgrp104
NY.Megacom.Trkgrp1
NY.Megacom.Trkgrp2
NY
Trunks
Peripheral Trunk
Groups
T1’s
T1’s
Network Trunk
Group
Routing Client
(IXC, PG)
Figure 8: Network and Peripheral Trunk Groups
The VRU may divide its trunk groups differently than the routing client
(for example, the IXC). In this example, the VRUs view each T1 circuit
as a trunk group (two trunk groups on each VRU). To the routing client,
however, the four T1 circuits might represent a single pool of 96 trunks.
The routing client can deliver calls with the same Dialed Number
Information Service (DNIS) to any of these 96 trunks, so it treats this
pool of trunks as a single entity—a network trunk group.
The use of network trunk groups simplifies the configuration of trunk
groups for some types of ACDs. Rather than deliver calls to specific
trunk groups and peripherals, the routing client need only deliver the call
to a network trunk group. The peripheral can then choose a target that
matches the DNIS and thereby classify the call.
1.2.4. Service Arrays
Service arrays are closely tied to network trunk groups. Typically,
service arrays are defined in instances where you have similar peripheral
services defined on multiple VRUs and the VRUs all share the same
network trunk group. By grouping the services of multiple VRUs into a
service array, you can send calls to a single target (a service array) and
let the network deliver the call to any one of the peripheral services that
make up the service array.