140 Chapter 6 Networked TAPI/IVR213346.02Call data networking between TAPI servers with NACDoverflowThis section provides an example of how call data is communicated from a localSymposium TAPI SP to a remote Symposium TAPI SP. In this scenario twoSuccession switches are connected via ISDN/PRI trunks: M1-A and M1-B. AnIVR system is attached to M1-A. Both switches use Symposium TAPI SP and theACD queue to which the IVR system transfers the call is configured toimmediately overflow to M1-B.In this scenario the following processes occur:1 A call arrives on a line attached to the IVR system that is monitored by theTAPI server. Because M1-A is part of a network of Succession switches, theCLID contains an identifier that uniquely identifies it as a CLID on M1-A, thehome location code (HLOC).2 The IVR system plays prompts and collects data from the caller.3 The IVR system uses TCP/IP to send CED along with information about theport or DN on which the data was collected to the Symposium TAPI SP forM1-A.4 The Symposium TAPI SP for Succession-A updates its call data objects andstores them in an index-based STL data structure.5 The IVR system transfers the call from its port to a destination DN on theswitch. Typically, it transfers the call to an ACD queue.6 The call leaves M1-A and is delivered to an ACD queue on M1-B.7 The M1-B TAPI server receives the call. In addition to all the mandatoryinformation elements, the message contains the network CLID. The M1-BTAPI server interprets the message as if the call originated from the remoteSuccession.8 The M1-B TAPI server extracts the HLOC from the network CLID field andsearches its IVR host database table for the HLOC. If a match is found, itNote: The list of all participating TAPI service providers is read from thedatabase during initialization of Symposium TAPI SP.
