Cisco Cisco Customer Voice Portal 8.0(1) Design Guide
11-2
Cisco Unified Customer Voice Portal (CVP) 8.x Solution Reference Network Design (SRND)
OL-15989-06
Chapter 11 Using the GKTMP NIC
Typical Applications of GKTMP with Unified CVP
To force the gatekeeper to reject the Admission Request (ARQ) and return an Admission Reject (ARJ)
to the requesting endpoint, the Unified ICM script can return a BUSY label, optionally with an additional
reason code (for example, DESTINATION_UNKNOWN).
to the requesting endpoint, the Unified ICM script can return a BUSY label, optionally with an additional
reason code (for example, DESTINATION_UNKNOWN).
For information on how to configure the GKTMP NIC, consult the ICM Setup and Installation Guide,
available at:
available at:
Typical Applications of GKTMP with Unified CVP
The GKTMP NIC can be used with Unified CVP in both pre-routing and post-routing call scenarios. The
former is used to process the Admission Request from the ingress gateway before the call is routed to
the Unified CVP Call Server (Call Server) and answered, the latter for transfers being performed by the
Unified CVP Call Server.
former is used to process the Admission Request from the ingress gateway before the call is routed to
the Unified CVP Call Server (Call Server) and answered, the latter for transfers being performed by the
Unified CVP Call Server.
•
Intelligent rejection before the call is answered by Unified CVP
When the Call Server receives an H.225 SETUP message, it answers the call by returning a
CONNECT message immediately. Sometimes it is necessary to make a routing decision before
delivering the call to Unified CVP and before the call is answered. One example is the use of
look-ahead routing, in which the Unified ICM script determines the availability and reachability of
other Unified ICM peripherals that will be required for the overall call scenario once the call has
been delivered to Unified CVP. With the GKTMP NIC, it is possible to reject calls intelligently for
alternate routing via the TDM network rather than answering them and not having the resources to
handle them subsequently.
CONNECT message immediately. Sometimes it is necessary to make a routing decision before
delivering the call to Unified CVP and before the call is answered. One example is the use of
look-ahead routing, in which the Unified ICM script determines the availability and reachability of
other Unified ICM peripherals that will be required for the overall call scenario once the call has
been delivered to Unified CVP. With the GKTMP NIC, it is possible to reject calls intelligently for
alternate routing via the TDM network rather than answering them and not having the resources to
handle them subsequently.
•
Selection of Call Server based on H.323 call information
Occasionally the gatekeeper static configuration is not sufficient for selection of the most
appropriate Call Server to handle an incoming call. For example, the routing decision might need to
be based on the calling line ID or source signalling address.
appropriate Call Server to handle an incoming call. For example, the routing decision might need to
be based on the calling line ID or source signalling address.
•
Manipulation of the calling line ID
Modification of the sourceInfo Alias is sometimes useful in order to overload the calling line ID with
additional information required by the destination endpoint, where translation routing is not
possible.
additional information required by the destination endpoint, where translation routing is not
possible.
•
Unified ICM-based dial plan
Unified ICM implements a centralized H.323 voice network dial plan, reducing the need for dial
plan configuration on individual gatekeepers. This approach is appropriate only if the dial plan is
large, complex, dynamic, and difficult to maintain across multiple gatekeepers.
plan configuration on individual gatekeepers. This approach is appropriate only if the dial plan is
large, complex, dynamic, and difficult to maintain across multiple gatekeepers.
•
Time-of-day routing
This feature allows the gatekeeper routing to be supplemented with decisions based on date and
time, possibly to handle time-dependent resource availability.
time, possibly to handle time-dependent resource availability.
•
Back-end system and database queries
Unified ICM database lookup or application gateway capabilities data from external systems can be
incorporated into routing decisions.
incorporated into routing decisions.