WIN 2003 sever standart & Telephony server

[Vsevolod Parfenov]

When try to enable telephony server on WIN 2003 sever standart
I have message "unidentified error 62791". What is it and how to fix it?

Probably error message spells another way. It's translation from russuan.
But sure number is correct

[Andreas Marschall [MVP TAPI]]

"Vsevolod Parfenov" <vsevo...@mail.ru> schrieb im Newsbeitrag
news:uomqxpA6...@TK2MSFTNGP09.phx.gbl...

> When try to enable telephony server on WIN 2003 sever standart
> I have message "unidentified error 62791". What is it and how to fix it?

Vsevolod,
to enable Telephony service on WS2k3 you need an ActiveDirectory.

--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
* Please post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.

[Zdenko]

We have Win2003 Server standard edition which is not in domain (There is no
AD), and TAPI works.
We have 2 TSPs: Cisco CM 4 TSP, Nortel Symposium TSP
Zdenko

"Andreas Marschall [MVP TAPI]" <Andreas....@I-B-A-M.de> wrote in
message news:uZfjQwA6...@TK2MSFTNGP14.phx.gbl...

[Andreas Marschall [MVP TAPI]]

"Zdenko" <s.zdenko-at-Softhome.net> schrieb im Newsbeitrag
news:%23o7zmrW...@TK2MSFTNGP12.phx.gbl...

> We have Win2003 Server standard edition which is not in domain (There is no
> AD), and TAPI works.
> We have 2 TSPs: Cisco CM 4 TSP, Nortel Symposium TSP

Zdenko,
yes, TAPI works on WS2k3 without AD.
But this wasn't the question.
The questions was about TAPI Server, i.e. using TAPIMGMT.MSC to activate
Telephony at the properties of computer. That's what you need for MS TAPI
Client/Server architecture , i.e. accessing the lines on the TAPI Server from
Client PCs via RemoteSP.TSP.
See my TAPI and TSPI FAQ:
Q: What is the Microsoft® TAPI client / server architecture ?
http://www.i-b-a-m.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm#_Q:_What_is_10

Regarding the original issue I got this info from MS (that I will add to my
FAQ; I guess there will be also a KB article on it):

To enable Telephony service in W2k3 , it requires Active directory to publish
service connection point (SCP) to allow automatic discovery of the telephony
servers from the clients. If the W2k3 machine is in a workgroup or if the
machine is joined to a Nt4 Domain (which doesn't have AD) , it cannot publish
SCP and hence enabling telephony server fails.
Only if the W2k3 machine is joined to a domain (which has AD) OR if w2k3
machine is made Domain Controller, then only enabling telephony server works.
So in the customer scenario, they might either need to have a W2k/W2k3 domain
and join this W2k3 m/c to that domain OR make this w2k3 machine a DC to
enable telephony server.

If you are wondering why W2k worked even if the AD is not installed on the
machine, in W2k while enabling telephony server it won't try to publish SCP
(W2k server doesn't support automatic discovery)

When a server enables Telephony server , it publishes itself in the Active
Directory of the domain server. When a Xp Client is joined to a domain and
then tcmsetup to point to telephony servers, using LDAP , client gets lines
from all telephony servers(that are published in that domain ) For eg. If
there are 5 telephony servers in domain TestDomain , a Xp client in that
domain does tcmsetup /c Testmachinename - It actually gets lines from
TestMachinename + all telephony servers in that domain

Creating SCP fails with 62791 & 62795 errors. Error 62791 is returned when
the W2k3 machine is in workgroup and 62795 will be returned if the W2k3
machine is joined to a Nt4 domain and tried to enable telephony server .