Nortel Web Center Portal Installation And Administration Manual page 482

Troubleshooting
TAPI server
When you are working with the TAPI server, keep in mind that
you must verify the Meridian Link Services Manager (MLSM) link on
!
Symposium Call Center Server and the TAPI server
if you must restart the MLSM link, you must restart the TAPI server
!
when you restart the TAPI server, you must restart the DTH on the
!
Symposium Web Center Portal server. You must also log off all of the
Symposium Web Center Portal agents, and then log them back on. For
more information, refer to "To restart the Portal Desktop" on page 480.
For more information about troubleshooting the TAPI server, refer to the TAPI
documentation.
TAPI dedicated lines
If, during periods of high-volume network traffic over the CLAN, you notice
that the pop-up notification window does not appear, or you experience
communication problems with the TAPI call data over the network, you can
design a dedicated CLAN to be used only between the Symposium Web Center
Portal server, the TAPI server, and the agent PCs.
The DTH presents calls in bursts and then remains idle
The DTH presents calls to the CDNs continuously until all the DTH TAPI lines
are in use. Once this occurs, the DTH waits until a line becomes free to present
another call.
Any new transactions that arrive in the Symposium Web Center Portal database
are not presented to the agents until the current queued calls are dealt with (no
matter what the priority). This includes the next transactions the DTH has
already chosen to present to Symposium Call Center Server.
Example
If a call center has 40 DTH TAPI lines configured, after two cycles of the DTH,
40 calls are made (one for each transaction) to Symposium Call Center Server. If
the system is configured for Keep Mode and the agents are available, these calls
are routed to the available agents, and all the DTH TAPI lines remain busy.
482 Nortel Networks Symposium Web Center Portal
Standard 2.0