68 Chapter 3 Preparing the TAPI environment213346.02Client user issuesThe 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 alineInitialize command to the TAPI server. If a TAPI-based application, such asremote access services (RAS) or Microsoft Fax, is configured to wait forincoming telephone calls, the application can start before a user logs on to theTAPI server. In this situation the client user is the TAPI application, not thelogged on user, and the server denies any line devices to Symposium TAPIservices. It is not possible to renegotiate with the server to establish the logged onuser as the client user.The solution is not to install a modem on the client user machine, and not to installmodem-based applications. If you encounter such problems, check if telephonyservices are running immediately after you log on, before starting any TAPIapplications. If telephony services are running, identify the application that iscausing TAPI to start up too early. It may be possible to change configurations tostop the application starting automatically. However, Nortel Networksrecommends that you uninstall the application.Configuring Microsoft TAPI for Symposium TAPI SPThe information in this section is designed to supplement the TAPIdocumentation provided by Microsoft. Before you install Microsoft TAPI, consultthe Microsoft TAPI readme.txt file. Follow the installation procedures provided inthat document.This section provides guidelines for configuring the following elements of theTAPI environment:• Assigning lines to users• Configuring client PCsBefore you begin, verify the following:
