21 august 2007 13:54
I am getting the following error in Communicator with our OCS 2007 server:
"Cannot synchronize with the corporate address book because the file could
not be found. Please contact your system administrator with this information."
Here's how we are setup:
Our Access server (ege01.domain.ad) has the external name sip.domain.com
Our OCS (FE) server has the internal name OCS01.domain.ad and no external address.
Service records are published and working properly.
From my testing if I go to https://sip.domain.com/abs I get: "Page cannot be
displayed" - meaning nothing is there, if I go to https://ocs01.domain.ad/abs
I get "The server declined to show the page" - meaning the service is there
When I'm on our LAN and connecting directly to the OCS server everything is great, when I'm outside of our LAN and connecting through the proxy server I can't get the address book.
So my questions is, why isn't https://sip.domain.com/abs getting directed to
https://ocs01.domain.ad/abs, that would provide a working copy of the address
book for both internal and external users.
21 august 2007 14:44
You have to implement a reverse proxy for external abs access. Please refer to the Edge Server Deployment Guide for more info or search for posts regarding "reverse proxy" on this forum.
21 august 2007 15:14
On the Edge deployment guide it only says how to accomplish this with ISA. Our environment has the 2 OCS servers and a firewall, any ideas on how we could make this work? All of the other services (voice, video, live meeting, etc..) are all working properly inside and outside.
22 august 2007 16:25
Ok, to work this out I had to PAT (port address translation) 443 back to my FE server (instead of the edge) and then PAT 5061 and the other ports to the Edge. I also had to install the public certificate for the edge server on the FE server in IIS as well. This seems like a bit of a design issue to me, especially for anyone not using ISA. Anyone have any thoughts on this?
22 august 2007 18:23Kevin, just a thought. You can also implement a reverse proxy with apache. I'm sure that there will be enough documents on the internet on how to implement this. Anyway, it seems that you have found a solution. Way to go!