Use the Federation tab to enable internal users to exchange Session Initiation Protocol (SIP) messages with users outside your organization's network, including federated partners, public instant messaging (IM) service providers, and remote users, as well as to track the presence of these external users. This requires setting a global default route for outgoing messages. This default route is set at the global level for all servers in a forest. The global default route can be overridden for any single Standard Edition server or Enterprise pool.
Enable Federation and Public IM connectivity
Select this check box to enable users to exchange messages with federated partners and public IM service providers.
Specify the fully qualified domain name (FQDN) of the next hop server, a Director or Access Edge Server, used by internal servers to send outbound messages to external users, including remote users.
Specify the port number through which internal servers send outbound messages to external users. This port number should match that of the next hop server or, if the connection is direct, of the Access Edge Server itself. The default value is 5061.
Learn More Online
Click to expand or collapse
The global default route is the route (that is, the next hop server) configured at the global level for all internal Communications Servers in the forest to use to send all outbound SIP traffic (that is, communication requests) to domains that do not match the SIP domains supported by your organization. You can override this default route on any Standard Edition server or Enterprise pool.
The FQDN of the next hop server configured in the global default route can be any of the following:
FQDN of the Director that is used to route SIP traffic outside your organization. A Director is recommended for security and scalability.
FQDN of the internal interface of your Access Edge Server.
FQDN of the virtual IP address of the hardware load balancer that is used to connect the internal edge of Access Edge Servers to the internal network.
If you are using a Director, this server is typically configured as the next hop server at the global level and then, on the Director, you override this setting and configure the Access Edge Server as the next hop server.
To override the global default route for any single Standard Edition server or any single Enterprise pool, configure a specific route on the Federation tab in Front End Properties for the specific server or pool.