Also see the "Deploying TAPI-Based Solutions" link under Publications in Links.

Subject: Re: NT 4.0 installing a PBX
Date: Tue, 8 Jun 1999 10:30:11 +0100
From: "Eduardo Suarez" esuarez@exepos.com

I think the first quick checks are :

On the Server PC: (What Service Pack have you got?, you should install at
least SP4).
------------------------------

1.- Are the Server and client PC's part of the same Domain. (Not workgroup).
2.- Is the administrator (Domain Admin) account you used in TCMSETUP /S
domain\user ..., a Global account? (You should not have a local account
with the same name and password on the server pc, I have found that the
Server gets confused and thinks it is the local account....).
3. Using Regedit check that
(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Server)
should have at least the following entries (You may have more if you
are also installing management dll's):
"DisableSharing"=dword:00000000
"MapperDll"="TSEC.DLL"
4. Make sure that the Admin account you used has the "Log on as a service"
privilege.
5. After TCMSETUP reboot the server.

On the Client PC:
------------------------------------

Windows 98 & NT (SP4):

1. User logged on to the same domain as the TAPI server.
2. TCMSETUP /C servername. (alternatively try tcmsetup /Y /C servername).
3. Make sure that the Domain Admin on the TAPI server can access a share on
your client PC.

Windows 98:

1. File and Print sharing should be enabled.
2. Access control should be set to User Level Access control, with the
Domain name entered in the edit box...
3. Share the C drive on your PC and make sure that the Domain admin
configured in the TAPI Server can access the share.

REBOOT.

JUST AS A TEST : Try using a domain admin account on the client pc. A
domain admin account should be able to see all configured telephony lines
from the server (even if you don't specifically assign them with tcmapp).

-*-*-*-*-

Subject: Re: TAPI 2.1 Client/Server : WORKING AT LAST!!!!!!!!!!!!!!
Date: Fri, 4 Jun 1999 17:28:40 +0100
From: "Eduardo Suarez" esuarez@exepos.com
Newsgroups: microsoft.public.win32.programmer.tapi

Since I could not get the tcmsetup program to run properly on the NT server
I was using to install the TAPI Server, I used the Windows NT Domain
Controller instead to get TAPI 2.1 up and running.

1. FROM Domain controller: I run tcmsetup /S /N DOMAINNAME\USERNAME and I
got the exact same error as before. ("It's not an administrator account",
etc....).
2. I run tcmsetup /S /N domainname\username (all lower case this time), and
it worked!!! TAPI 2.1 was successfully installed. (Weird!!, probably
spelled something wrong the first time.).
3. I went to the registry to copy (export to file) the Telephony/Server key
entry that tcmsetup had just created.
FYI: The Server key
(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Serv
er)
should have at least the following entries (You may have more if you
are also installing management dll's):
"DisableSharing"=dword:00000000
"MapperDll"="TSEC.DLL"
4. I went back to the original NT Server where I had all the problems and
tried tcmsetup again. (It failed again).
5. So, I manually configured the TAPI Service in control panel to start
Automatically and to use the domain\administrator account I created for it.
6. I imported the registry file I created in step 3. This created the
Server subkey and added the entries in step 3.
7. REBOOT TAPI SERVER.
8. From various client PC's I run tcmsetup /c tapiservername.

AND IT WORKS!!!!!!!!!

(BTW: It works fine now but I still get only 1 \pipe\tapsrv)