Edit Federated Partner

Use this dialog box to edit an entry for a company with which you want to enable federation.

Federated partner domain name

The fully qualified domain name (FQDN) of the Session Initiation Protocol (SIP) domain of the federated partner that you want to authorize to connect. This name should be unique and should not already exist in the Block list for the Access Edge Server. The name may be up to 256 characters in length. Multiple domains can be assigned to a single Access Edge Server.

Federated partner Access Edge Server

The FQDN of the Access Edge Server for the federated partner. Specification of this FQDN is only necessary if you want to establish a higher level of trust and the partner does not publish its federation records for automatic discovery.

Note: To add an audio conferencing provider (ACP) as a federated partner, you must add both the domain and FQDN of the ACP to the Allow list. For details about how to configure support for an ACP, see the Microsoft Office Communications Server 2007 R2 Technical Library on TechNet.

Learn More Online

Click to expand or collapse

Federation is a trust relationship between two or more SIP domains that permits users in separate organizations to communicate in real-time across network boundaries as federated partners. Internal users can communicate with external users of a federated partner by using instant messaging (IM) or conferencing.

A federated partner can also be an ACP providing telephony integration. Using Office Communications Server, you can enable access by federated partners, including other organizations and ACPs who provide telephony integration for your organization.

Note: Federated partner access is not required for SIP trunking service providers.

For details, see the Operations section of the Office Communications Server Technical Library.

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!