Cisco Cisco Administrative Workstation
1-3
ICM-to-ICM Gateway User Guide for Cisco ICM Enterprise & Hosted Editions Release 7.1(1)
ICM-to-ICM Gateway Overview
ICM-to-ICM Gateway Call Flow
ICM-to-ICM Gateway Call Flow
illustrates basic ICM-to-ICM Gateway call flow.
Figure 1-1
Basic ICM-to-ICM Gateway Call Flow
1.
A Client ICM receives a request. This could be a pre-route request from a
service provider network (in which case the routing client is a NIC) or a
post-route request from an ACD/IVR (in which case the PG acts as the
routing client)
service provider network (in which case the routing client is a NIC) or a
post-route request from an ACD/IVR (in which case the PG acts as the
routing client)
2.
The Client ICM executes a script. At some point the script initiates a route
request to the other ICM, referred to as the Server ICM. At this point the
Server ICM must find a destination label for the call.
request to the other ICM, referred to as the Server ICM. At this point the
Server ICM must find a destination label for the call.
3.
The Server ICM executes a script to select a destination label for the call. The
Server ICM handles this call as a normal route request, save for the fact that
the routing client is another ICM and not a service provider network or an
ACD/IVR. Once a destination label is selected the Server ICM sends it back
to the Client ICM.
Server ICM handles this call as a normal route request, save for the fact that
the routing client is another ICM and not a service provider network or an
ACD/IVR. Once a destination label is selected the Server ICM sends it back
to the Client ICM.
4.
When the Client ICM receives the destination label from the Server ICM, it
passes the label directly to the routing client that initiated the route request.
This does not happen under script control, but is an automatic process.
passes the label directly to the routing client that initiated the route request.
This does not happen under script control, but is an automatic process.