|
Steps to configure an Access Edge Server |
Followings are the steps to configure an Access Edge Server
In
Internal Interface IP Address box, click the
internal interface IP address. If this server will be
connected to a load balancer, use the IP address of the
local computer.
In FQDN for the internal interface,
type the FQDN of the internal interface. If this server
will be connected to a load balancer, use the virtual
name of the load balancer.
For an Access Edge Server that will be connected to a
load balancer, specify the IP address (public or private
IP Address NATED with public IP) of the edge server and
FQDN of the virtual IP address of the load balancer. The
default federation port is set to 5061 and cannot be
changed. The default TCP port for remote access is 5061.
To specify a port other than 5061 for remote user
access, click either 443 or
Other. If you click Other, type the port
number.
On the Enable Features on
Access Edge Server page, select the features that
you want to enable on this Access Edge Server as
follows:
·
To make it possible for remote users to
connect to Office Communications Server 2007 from the
Internet to view presence information and exchange
instant messages with internal users using this Access
Edge Server, select the Allow remote user access to
your network check box.
o
To make it possible for external anonymous
users to join conferences through this Access Edge
Server, select the Allow anonymous user to join
meetings check box. Anonymous users are external
users who do not have credentials in the Active
Directory® Domain Services.
o
In your edge server deployment, you can
optionally use one Access Edge Server for remote user
access and a different Access Edge Server for federation
and public IM connectivity. In this configuration on the
Access Edge Server used for remote access, if you plan
to enable federation or public IM connectivity for your
remote users, click the Allow remote users to
communicate with federated contacts; otherwise, your
remote users cannot send messages to federated or public
IM contacts.
·
To enable federation or public IM
connectivity through this Access Edge Server, select the
Enable federation check box.
o
To use DNS to automatically locate Access
Edge Servers of your federated partners, select the
Allow discovery of federation partners using DNS
check box. We recommend this configuration.
o
To enable public IM connectivity through
this Access Edge Server, select the Federation with
selected public IM providers check box, and
then and select the IM providers that you want to use
with federated partners.
On the FQDN of the Internal Next Hop
Server page, in the FQDN of next hop server
box, type or click the
FQDN of
the next hop server to which this Access Edge Server
routes internal traffic or, if you are using a Director
to route incoming traffic, type the FQDN of the
Director, or type the pool name or the FE name, and
then click Next.
On the Authorized Internal SIP
Domains page: type the name of the SIP
domain, and then click Add. After adding all SIP
domains to be supported, click Next.
Specify
each internal server that can connect to your Access
Edge Server. If you are routing all outbound traffic
through a Director, type only the FQDN of the Director,
and then click Add. If you are not using a
Director, type the FQDN of each Enterprise pool and
Standard Edition server in your organization, clicking
Add
after each.
Note:
Now you need to configure the
OCS Global properties to complete the deployment of an
Access Edge Server.
