Client User Issues; Configuring Microsoft Tapi For Symposium Tapi Sp - Nortel TAPI User Manual

68 Chapter 3 Preparing the TAPI environment

Client user issues

The scenarios described above assume that the logged on user is the client user.
Problems can occur because the client user is the first application that sends a
lineInitialize command to the TAPI server. If a TAPI-based application, such as
remote access services (RAS) or Microsoft Fax, is configured to wait for
incoming telephone calls, the application can start before a user logs on to the
TAPI server. In this situation the client user is the TAPI application, not the
logged on user, and the server denies any line devices to Symposium TAPI
services. It is not possible to renegotiate with the server to establish the logged on
user as the client user.
The solution is not to install a modem on the client user machine, and not to install
modem-based applications. If you encounter such problems, check if telephony
services are running immediately after you log on, before starting any TAPI
applications. If telephony services are running, identify the application that is
causing TAPI to start up too early. It may be possible to change configurations to
stop the application starting automatically. However, Nortel Networks
recommends that you uninstall the application.

Configuring Microsoft TAPI for Symposium TAPI SP

The information in this section is designed to supplement the TAPI
documentation provided by Microsoft. Before you install Microsoft TAPI, consult
the Microsoft TAPI readme.txt file. Follow the installation procedures provided in
that document.
This section provides guidelines for configuring the following elements of the
TAPI environment:
• Assigning lines to users
• Configuring client PCs
Before you begin, verify the following:
213346.02