Dears,
I'm trying to integrate AES 5.2.3 with Super Patch 2 installed with Lync Server 2010. I installed one Lync Front-End Standard Edition and followe the instruction in the below URl:
http://support.avaya.com/css/P8/documents/100144425
Also, Customer has AD which use S-LDAP connection, so communication with AD over 389 port is not allowed, we are using 636 port.
I noticed that the CA server (Windows 2003) installed on the environment is Standalone Server, so I cannot find "Certificate Template" in the CA Console but i got it from MMC snap-in and created the required template according to the document (above URL) but and continue the steps.
when I enabled users to RCC, and login to Lync Client, i got an error "No Phone System Connection"
and from snooper, i found
ms-diagnostics: 1038;reason="Failed to connect to a peer server";WinsockFailureCode="10061(WSAECONNREFUSED)";WinsockFailureDescription="The peer actively refused the connection attempt";Peer="aesad.domain.com";Port="4723";source="LYNCFE.domain.com"
by reviewing the certificate on FE server and AES server, i found that, Enhanced Key Usage: Server Authentication although i used a template that afford Server & Client Authentication.
Also, I don't have another server to create Trusted App Pool, so when I run the power shell command I got a warning advise that this machine (App Pool Name) doesn't has Computer Object in AD.
My Questions:
- Is the certificate issued to Lync and AES correct or it should contain both Server & Client Authentication?
- Can I use Standalone CA to issue this type of Certificates or I have to install Enterprise CA?
- What is the cause of "No Phone System Connection" Error?
- How can I check if AES accept communication with Lync on 4723? I tried to telnet with no luck.
- Is it supported to allow AES to communicate S-LDAP?