Call Data Networking Between Tapi Servers With Nacd Overflow - Nortel TAPI User Manual

140 Chapter 6 Networked TAPI/IVR
Call data networking between TAPI servers with NACD
overflow
This section provides an example of how call data is communicated from a local
Symposium TAPI SP to a remote Symposium TAPI SP. In this scenario two
Succession switches are connected via ISDN/PRI trunks: M1-A and M1-B. An
IVR system is attached to M1-A. Both switches use Symposium TAPI SP and the
ACD queue to which the IVR system transfers the call is configured to
immediately 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 the
TAPI server. Because M1-A is part of a network of Succession switches, the
CLID contains an identifier that uniquely identifies it as a CLID on M1-A, the
home 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 the
port or DN on which the data was collected to the Symposium TAPI SP for
M1-A.
4 The Symposium TAPI SP for Succession-A updates its call data objects and
stores them in an index-based STL data structure.
5
The IVR system transfers the call from its port to a destination DN on the
switch. 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 mandatory
information elements, the message contains the network CLID. The M1-B
TAPI server interprets the message as if the call originated from the remote
Succession.
8
The M1-B TAPI server extracts the HLOC from the network CLID field and
searches its IVR host database table for the HLOC. If a match is found, it
213346.02
Note: The list of all participating TAPI service providers is read from the
database during initialization of Symposium TAPI SP.