Troubleshooting PSTN Telephony

The following sections outline common problems and solutions for conventional (non-IP) Public Switched Telephone Network (PSTN) telephony deployment.

One or more client computers cannot "see" the telephony server

If the telephony server cannot be reached through the network, for example, a user cannot 'ping' the telephony server, it is possible that:

1. The telephony server has not been correctly set up. Consult Windows 2000 Server Help for how to manage telephony servers.
2. The Unicast IP protocol is not installed. Consult Windows 2000 Server Help for installing and troubleshooting Unicast IP.
3. A Windows 2000 domain has not been correctly established. Consult Windows 2000 Server Help for installing a domain controller.

One or more client computers cannot "see" lines on the telephony server

If one or more client computers cannot see the lines of a telephony server, it could be because they are unable to be authorized for access to lines on the telephony server. When a TAPI application accesses lines on the telephony server, the user context associated with the application process is first authenticated. This means that those lines must have been configured on the server to allow access by that client. If client cannot see lines on the telephony server, it is possible that:

1. The lines have not been configured on the server to allow access by the client. Consult Windows 2000 Server Help on how to set up and manage telephony servers.
2. The user process context in which the application is running has not been associated with lines. Consult Windows 2000 Server Help on how to manage TAPI clients and users on the server.

For information about Active Directory domains and trusts, and authorizing users, see Windows 2000 Server Help.

An application fails to start after you have cancelled the Location Information dialog box

If an application fails to start after you have cancelled out of the Location Information dialog box, the problem might be that address translation required by TAPI applications has not been specified. This can be solved by using the Local Information dialog box to enter your country/region code, local area code, and pulse or tone and external line access settings.

A client cannot "see" a new line appearance on the server, even though the server administrator has assigned the client to the line

When you assign a currently running client to a line on the telephony server, the new settings are not available until TAPI on the client computer restarts. The solution is to stop all client TAPI applications so that TAPI shuts down. When the client applications restart, they are able to see the newly allocated lines.

For information about how to manage TAPI clients and users, see Windows 2000 Server Help.

© 1985-2000 Microsoft Corporation. All rights reserved.