Nortel Symposium TAPI Service Provider for Succession 3.0, User Manual, Page: 141 / 198

Chapter 6 Networked TAPI/IVR 141
Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0
sends an IVR request call data message over TCP/IP to the TAPI server for
M1-A.
9
The Symposium TAPI server for M1-A receives the message and, after
searching its call data list, finds the call data for the call appearing on the
M1-B TAPI server. M1-A TAPI server sends a caller info data message back
to the M1-B TAPI server.
10 The M1-B TAPI server receives the caller info data message and replaces the
CLID field with the M1-B current local call ID.
11 The M1-B TAPI server passes the data to any TAPI applications monitoring
the agent’s telephone via a LINECALLINFO message and the subsequent
lineGetCallInfo function call.
Verifying NACD overflow with TAPI operations
Verify that the IVR system and mlinksp.ini file are properly configured before
starting Symposium TAPI SP. Also verify that NACD overflow time is set on the
switch for the ACD queue on M1-A to overflow calls to an ACD queue on M1-B.
To verify that NACD overflow is functioning correctly with Symposium TAPI
SP, perform the following tasks in the TAPI browser application:
1
Select lineInintializeEx function in the left pane of the TAPI browser
application to display initialization information for the line.
(Figure 53)