Cisco Cisco E-Mail Manager Unity Integration Option Technische Referenzen
12
Overview
1.1. Avaya ARS PG Architecture
Figure 1 shows the high-level components in a Cisco ARS PG installation
and its interactions with other Unified ICM components.
and its interactions with other Unified ICM components.
The ARS PIM interacts with the Avaya Gateway using the ISAGI protocol.
The Avaya Gateway acts as a translator to translate ISAGI messages to
Adjunct Switch Application Interface (ASAI) messages in order to
communicate with the Avaya switch. In turn, the Avaya Gateway translates
ASAI messages to ISAGI and passes this information to the ARS PIM.
The Avaya Gateway acts as a translator to translate ISAGI messages to
Adjunct Switch Application Interface (ASAI) messages in order to
communicate with the Avaya switch. In turn, the Avaya Gateway translates
ASAI messages to ISAGI and passes this information to the ARS PIM.
Call queuing and caller treatment are available on the Avaya through the use
of the Gateway’s Virtual VRU (VVRU) functionality. This is controlled via
the Service Control Interface (SCI) of the ISAGI protocol. An installation
may include an external VRU for queuing calls and offering call treatment
instead of, or in addition to, the functionality offered by the Avaya through
the SoftACD interface.
of the Gateway’s Virtual VRU (VVRU) functionality. This is controlled via
the Service Control Interface (SCI) of the ISAGI protocol. An installation
may include an external VRU for queuing calls and offering call treatment
instead of, or in addition to, the functionality offered by the Avaya through
the SoftACD interface.
Figure 1: Avaya ARS PG Architecture