Despite its name, TAPI helps the system create a number of connection types, so correct setup is
important. For example, this setup can define physical connectivity to the corporate Private Branch
Exchange (PBX). You must use this utility to perform some setups, such as designating a Windows
2000 server as a resource for TAPI clients. This utility uses the following syntax:
tcmsetup [/r] [/q] [/x] /c Server [Server...]
tcmsetup [/q] /c /d
The following list describes each of the command line arguments.
/r
Disables automatic server discovery. Only the servers that you specify with this command
appear as TAPI resources.
/q
Prevents the utility from displaying message boxes. Use this feature with batch files to prevent
the system stopping to wait for user input.
/x
Specifies that TAPI relies on connection-oriented callbacks. Use this feature on heavy traffic
networks where packet loss is high. The default setting uses connectionless callbacks, which
offer better efficiency at the expense of reliability.
/c
Defines this request as a client setup. You must include this command line switch.
Server
Specifies one or more remote servers to use as TAPI service providers.
Pages:
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011