Telephony and Conferencing
The following sections outline common problems and solutions for conventional (non-IP) Public Switched Telephone Network (PSTN) telephony deployment.
Computer cannot find 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:
The telephony server is not available or has not been correctly set up. Contact the administrator of the telephony server.
The Tcmsetup tool has not been run. Run the Tcmsetup tool with the /c parameter to specify the correct servers.
The Tcmsetup tool has been run, but an incorrect telephony server was specified. Run the Tcmsetup tool with the /c parameter to specify the correct servers.
The Tcmsetup tool has been run multiple times, overwriting the original telephony configuration. Run the Tcmsetup tool with the /c parameter, listing all telephony severs in the single command.
The Tcmsetup tool has been run with the /d (delete) parameter. Run the Tcmsetup tool with the /c parameter to enable telephony services and to specify the correct server(s).
One or more client computers cannot find a line on the telephony server
If one or more client computers cannot see the lines of a telephony server, it might 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 the client cannot see lines on the telephony server, it is possible that the lines have not been configured on the server to allow access by the client. Contact the system administrator for the server.
After the lines have been configured, the new settings are not available until TAPI on the client computer restarts. The solution is to stop all client TAPI applications and restart Windows 2000 Professional. When the client applications restart, they are able to see the newly allocated lines.
An application fails to start after you have canceled the Location Information dialog box
If an application fails to start after you have canceled 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 find 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.