30 Overview
Routes are associated with a single peripheral and are not organized on
an enterprise-wide basis. Figure 10 shows some examples of routes and
how they map to individual peripheral targets.
Routes
Denver Sales
Denver.Sales.Pri
Agent 325
Denver.Trunks + DNIS ACD
ACD
ACD
Dallas.Sales
Dallas.Sales.Pri
Agent 81
Dallas.Trunks + DNIS
Boston Sales
Boston.Sales.Sec
Agent 123
Boston.Trunks + DNIS
Figure 10: Routes
The ICR converts the route value that is returned by the routing script to
a routing label. This routing label is then returned to the routing client.
The routing client uses the routing label to deliver the call to the
appropriate trunk group and DNIS combination.
See also:
The Intelligent CallRouter System Manager Guide contains a more
in-depth discussion of routes and how they are mapped to specific
targets.
1.2.6. Other Parts of the Enterprise
In addition to viewing data for services, skill groups, agents, trunk
groups, and routes, you can view data for the following call center
entities:
Application Gateways
You can report on data related to the Application Gateways set up in the
system. The GEOTELìGateway feature allows the ICR to interface to
host systems that are running other call center applications.
The Application Gateway is implemented via a node in the ICR Script
Editor. A routing script that contains an Application Gateway node can
query an application running on a host system in order to obtain data to
use in call routing. The ICR can then base subsequent routing decisions
on the results obtained from the query.