Network Call Data - Nortel TAPI User Manual

• A request call data message is sent by the receiving IVR driver to a remote
IVR driver if a call is overflowed from one site to another in a networked
TAPI environment. If this message does not include a network CLID, the
receiving IVR driver searches for the network CLID in its IVR server
database table in order to respond.
• A caller info data message is sent by the remote IVR driver to the receiving
IVR driver in response to a request call data message in a networked TAPI
environment.

Network call data

Nortel Networks recommends that the IVR system is centralized at the main site
in a networked environment. To receive IVR treatment, all incoming calls are
routed into the Succession switch at the main site. The IVR system passes the
CLID and CED to the central Symposium TAPI SP IVR driver which stores this
information.
When a call is routed to a remote site, the TAPI server at that site extracts the
HLOC from the network CLID. It checks if this HLOC is in its IVR host database
table, and sends a request call data message over TCP/IP to the TAPI server at the
main site. The main TAPI server then sends a caller data message to the remote
TAPI server. All TAPI servers must be configured with the IP address and HLOC
of the main TAPI server. These common configurations ensure that when a call
arrives into a remote site, the remote TAPI server can match the HLOC contained
in the network CLID with the HLOC for the main TAPI server stored in its IVR
host database table.
There are two ways of attaching data from the IVR system to TAPI:
• If call data is associated with a network CLID, Symposium TAPI SP does not
monitor the incoming IVR port.
• If call data is associated with a specific DN port, Symposium TAPI SP must
monitor the incoming IVR port.
For information about configuring and maintaining the IVR host database table
refer to "Configuring the network TAPI/IVR table" on page
The Symposium TAPI SP IVR driver performs the following tasks:
• monitors IVR DNs and records associated network CLIDs
Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0
Chapter 6 Networked TAPI/IVR
104.
131