Integrating Lync into 2010 OWA

tsukraw
tsukraw used Ask the Experts™
on
Hey Experts.
I am getting the good old "Contact List will appear when the service becomes available" on a new Exchange 2010 setup where we are integrating lync.  

I have looked a the document on this website
http://blogs.technet.com/b/ilvancri/archive/2010/10/10/troubleshooting-lync-exchange-owa-integration.aspx

Any Ideas?
When i look at the log i am seeing the following.
TL_INFO(TF_CONNECTION) [0]088C.0B30::08/05/2011-07:45:40.792.0000000c (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(164))$$begin_record
LogType: connection
Severity: information
Text: Connection was closed because it was inactive for too long
Local-IP: 192.168.0.30:5061
Peer-IP: 192.168.0.30:60136
Peer-FQDN: 123-lync.business.com
Peer-Name: 123-lync.business.com
Connection-ID: 0x879C00
Transport: M-TLS
$$end_record
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Have you checked firewall settings?  Perhaps on the local servers.  Are the client PCs and the exchange server on the same network?

Author

Commented:
Firewalls are turned off on servers.  PCs are on the same network.
Did you run through the steps he gave?

•Is the certificate used on Lync, and Exchange issued by a trusted CA for both Lync and Exchange
•Does the certificate have the correct name, both for Lync and Exchange
•Did you ran Enable-CSTopology after adding Exchange as a csTrustedApplication
•Is your replication working as it should on Lync, check by using the cmdlet Get-CsManagementStoreReplicationStatus

Author

Commented:
Replication is good.
As far as the certificate.  Our Lync server is using a self signed certificate but our Exchage is using a GoDaddy cert.  Is that alright?
That may be an issue.  Do you do external access?  Usually Lync needs a public CA for that.  Make sure that the self signed cert is in the Trusted Root for the computer with Exchange and vice versa.  See if that does it.  Man, now that you say that I am really wondering if your issue is cert based.

But we can also try to ping the addresses from each other and make sure that is at least working.  there are tools to make sure the ports are open as well, you may want to verify that, even though, the firewalls are turned off, that you can get to those ports on the respective machines.

Author

Commented:
I will try telnet to that port number that i made in setup and see if it responds?  And i can ping each server.  The self signed was one by our Ca Authority server i think it is called so that cert is trusted on all domain computers so the Exchange should like it i would think wouldnt it?
Yes it should, so maybe the cert isn't it then.  Well try the telnet and see what happens.

Author

Commented:
Telnet does not work on port 4789 but not sure if it should or not anyways as on the Lync server i cannot run telnet localhost 4789 which running it from its self shouldnt be a firewall issue.  But i did put it in the exceptions anyways.  Does the log file for lync do anything that I listed above?
one thing I just noticed....

Local IP and Peer IP are the same... should they be the same or different?  I may be reading it wrong, but doesn't it seem like it is sending it to itself?

Also, is your cleint access server on a seperate server from exchange itself?

Author

Commented:
Hmm good question i am not sure. Below are the IP configurations for our server setup.  When i the IM settings i pointed it to the Pool server like it had in the documentation do you know if that is correct to do?
30 - Lync Sever
31 - Pool Server
32 - Edge Server
it should work if you point it any of them really.  But I would test going right to the FE server to cut out variables.

Author

Commented:
Ok so i got a new certificate fro my Lync server.  How do i go about loading it though?  I remember back when lync first got setup in the wizard you were able to load it there but now that lync is fully running how do i change it?
where did you get the cert from, a public CA?

Author

Commented:
GoDaddy cert.
Are you using a Reverse Proxy?
Here is the thing.  When you are first loading the FE server the certificate comes up and that is an internal CA certificate.  The one for the Edge server is for a public Ca cert, like GoDaddy.  Did you use the Edge server to request the cert?  Because if it isn't exactly right none of this will work.

Also did you ever figure out what the peer vs local thing was all about.  Becuase they look like they should be different and that may be the problem as well.

Local-IP: 192.168.0.30:5061
Peer-IP: 192.168.0.30:60136

Author

Commented:
Ended up going to Office365 where it is already setup.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial