Chapter 6 Networked TAPI/IVR 129Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0The numbers on the illustration correspond to the numbers of the followingevents:1 A caller dials into the Succession switch over the PSTN.2 The Succession switch queues the call to a CDN for the SCCS.3 The SCCS opens a voice session with the IVR system.4 The IVR system plays a prompt for the caller, for example a request for a PIN.5 The IVR system passes the CED to the Symposium TAPI SP IVR driver,where the CED and associated CLID are stored.6 At the same time, the IVR system passes the CED to the SCCS, which assignsthe call to a destination DN, based on skill-based routing.7 The SCCS instructs the Succession switch to transfer the call to thedestination DN.8 At the same time, the SCCS passes the CLID and destination DN toSymposium TAPI SP, where the IVR driver searches for CED associated withthe CLID.9 The Succession switch transfers the call to the selected agent’s telephone set.10 Symposium TAPI SP passes this CED to a TAPI-compliant application on thePC associated with the destination DN.LAN configurationIVR communication with Symposium TAPI SP should be on a dedicated LANand not on the main C-LAN. It can share the same LAN as Meridian LinkServices, which is installed on SCCS / SECC. Refer to “Configuring an isolatedC-LAN for TAPI traffic” on page 49 for further information.IVR-CTI integration in a Succession environmentIntegrated IVR-CTI functionality is possible in a Succession environment throughthe following Meridian capabilities:• The Succession switch provides the telephony switching requirements forIVR activities.
