?– Set external DNS so that inbound messages can fi nd the OCS 2007 edge server to
route inbound messages through the new server.
?– Change the fully qualifi ed domain name (FQDN) external route for communications
to formally route public IM information and federated IM communications through
the new OCS 2007 edge server.
All of these confi guration settings require a properly confi gured DNS name and IP
address on a zone such that users or servers can fi nd the servers they are to connect to.
For example, if a user needs to access a server for IM, the FQDN of the server the user
needs to access must be published externally for the user to access the server externally.
However, if the user only needs to access the server from within the organization??™s fi rewall,
the server only needs to be published in the organization??™s Active Directory for the user to
fi nd the server.
Likewise, if an internal server needs to route messages to an edge server in the perimeter,
the edge server and its corresponding IP address and DNS name need to be published internal
to the network. And if an edge server needs to communicate with an internal OCS 2007
server, although the organization likely won??™t publish the DNS name of the internal server
to mask the server for security purposes, the IP address of the internal server needs to be
accessible from the edge server.
Note that OCS 2007 uses Secure Sockets Layer (SSL; port 443) for encrypted communications
between servers instead of the proprietary port 5061 that was used for LCS 2005.
Pages:
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368