Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)
Interdomain Federation and Intradomain Federation Deployment Integration
Downloads: This chapterpdf (PDF - 1.2MB) The complete bookPDF (PDF - 4.16MB) | The complete bookePub (ePub - 767.0KB) | Feedback

Interdomain Federation and Intradomain Federation Deployment Integration

Interdomain Federation and Intradomain Federation Deployment Integration

IM and Presence Service Integration with Interdomain Federation Capability of Microsoft Servers

You can integrate the IM and Presence Service with the Interdomain Federation capability of Microsoft servers.

Microsoft servers support Interdomain Federation with remote enterprises or public IM providers. This Interdomain Federation capability is still available to Microsoft Lync or Microsoft Office Communicator users when Partitioned Intradomain Federation is configured between the Microsoft server and the IM and Presence Service.

Furthermore, you can configure the IM and Presence Service so that users who migrate to an IM and Presence Service supported client can still use the Interdomain Federation capability that is configured on the Microsoft server.

For information about configuring Interdomain Federation on IM and Presence Service, see Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager.

Interactions and Restrictions

  • Do not use Email for Federation when you have an integrated Interdomain and Partitioned Intradomain Federation deployment. Email Address for Federation is not supported in deployments where Partitioned Intradomain Federation is configured. Email Address for Federation is also not supported for Interdomain Federation if your deployment uses the interdomain federation capabilities of Lync/OCS/LCS. Confirm that Email Address for Federation is not enabled anywhere in the deployment in these deployment scenarios.
  • When Partitioned Intradomain Federation with the Microsoft server is enabled, it is also possible to configure both SIP-based and XMPP-based Interdomain Federation to remote domains on the IM and Presence Service. However, this federation capability is available to users on the IM and Presence Service supported clients only.

IM and Presence Service Integration with Interdomain Federation Capability of Microsoft Servers

You can integrate the IM and Presence Service with the Interdomain Federation capability of Microsoft servers.

Microsoft servers support Interdomain Federation with remote enterprises or public IM providers. This Interdomain Federation capability is still available to Microsoft Lync or Microsoft Office Communicator users when Partitioned Intradomain Federation is configured between the Microsoft server and the IM and Presence Service.

Furthermore, you can configure the IM and Presence Service so that users who migrate to an IM and Presence Service supported client can still use the Interdomain Federation capability that is configured on the Microsoft server.

For information about configuring Interdomain Federation on IM and Presence Service, see Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager.

Remote Domain Setup for Interdomain Federation through Intradomain Federation Connections on Microsoft Servers

IM and Presence Service users can communicate with external domains using either the existing Lync/OCS/LCS interdomain federation connections or using connections to those external domains that you configure directly on IM and Presence Service.

When you configure interdomain federation through existing Microsoft server intradomain federation connections, all requests to the remote domain are routed through the SIP interface between the IM and Presence Service and the Microsoft server. You must configure the remote domain on the IM and Presence Service to be a Microsoft server SIP Federation domain before you proceed to configure interdomain federation through existing intradomain federation connections. Do this for each remote domain.

See procedures related to adding a SIP federated domain in the Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager for detailed instructions on how to configure a SIP federation domain.

Choose the following options when you configure a SIP Federation domain for interdomain federation using existing intradomain connections that are configured on Microsoft servers:

  • For Domain Name, enter the remote domain.
  • For Integration Type, choose Inter-domain to OCS/Lync
  • Ensure that the Direct Federation check box is checked.

Note


If you have a multicluster deployment, you must perform this procedure on each cluster. These settings are cluster-wide; therefore you need to set them only on the IM and Presence Service database publisher node within any given cluster.


Configure a Static Route for a Remote Domain

When you integrate the IM and Presence Service with Lync/OCS/LCS Interdomain Federation capability, you must configure static routes on the IM and Presence Service for each remote domain.


Caution


Email Address for Federation is not supported in deployments where Partitioned Intradomain Federation is configured. Email Address for Federation is also not supported for Interdomain Federation if your deployment uses the interdomain federation capabilities of Microsoft servers. Confirm that Email Address for Federation is not enabled anywhere in the deployment in these deployment scenarios.


For Standard Edition Microsoft servers, the static routes must point to the IP address of a specific Standard Edition server.

For Enterprise Edition Microsoft servers, the static routes must point to a specific Enterprise Edition front-end server or front-end load balancer (if you route through a Microsoft server's front-end load balancer).

If you are using a Microsoft server's front-end load balancer, note the following:

  • The IM and Presence Service has been tested with the Cisco Application Control Engine (ACE) as the Microsoft server's front-end load balancer.
  • Other load balancers can be used in place of ACE; see the following URL for a list of alternative load balancers: http:/​/​technet.microsoft.com/​en-us/​office/​ocs/​cc843611. However, it is your responsibility to ensure that those load balancers are deployed and managed correctly. Cisco does not support the configuration of static routes to point to such load balancers.
  • In deployments in which ACE is not the configured front-end load balancer, Cisco recommends that you configure static routes to bypass the front-end load balancer.

For High Availability purposes, you can configure additional backup static routes for each remote domain. The backup route has a lower priority and is used only if the next hop address of the primary static route is unreachable.


Note


If you have a multicluster deployment, you must perform this procedure on each cluster. These settings are cluster-wide; therefore you need to set them only on the IM and Presence Service publisher node within any given cluster.


Procedure
    Step 1   Lin to the Cisco Unified Communications Manager IM and Presence Administration user interface. Choose Presence > Routing > Static Routes.
    Step 2   Click Add New.
    Step 3   Enter the destination pattern value so that the domain, or FQDN, is reversed. For example, if the domain is remote.com, the Destination Pattern value must be .com.remote
    Step 4   Choose domain for the Route Type.
    Step 5   In the Next Hop field, enter the IP address of the next hop.
    Step 6   Set the Next Hop Port and the Protocol Type as follows:
    • For TLS Encryption:
      • Next Hop Port number is 5061
      • Protocol Type is TLS
    • For TCP:
      • Next Hop Port number is 5060
      • Protocol Type is TCP
    Step 7   Enter the Priority value as follows:
    • For primary static routes, enter the default Priority value of 1.
    • For backup static routes, enter a Priority value of greater than 1. (The lower the value, the higher the priority of the static route.)
    Step 8   Leave the default values for all other parameters.
    Step 9   Click Save.

    Related Information

    Remove IM and Presence Service Integration with Microsoft Server Interdomain Federation Capability

    At some stage, you may want to configure the IM and Presence Service for Interdomain Federation with one of the remote domains that you previously configured on Lync/OCS/LCS. The most likely scenario for this is when all Microsoft Lync or Microsoft Office Communicator users have been migrated to the IM and Presence Service. At this point, the Microsoft server deployment can be shut down, and any Interdomain Federation capability can instead be enabled directly from the IM and Presence Service.

    To remove an IM and Presence Service integration with Microsoft server Interdomain Federation capability, you must complete Remove Static Route for Remote Domain and Remove the SIP Federation Domain.

    Remove Static Route for Remote Domain

    Procedure
      Step 1   Log in to the Cisco Unified IM and Presence Administration user interface. Choose Presence > Routing > Static Routes.
      Step 2   Choose the appropriate static route from the list provided. If no list is shown, click Find.
      Step 3   Click Delete Selected.
      Step 4   Click OK to confirm the deletion.

      What to Do Next

      Remove the SIP Federation Domain

      Remove the SIP Federation Domain


      Note


      If you have a multicluster deployment, you must perform this procedure on each cluster. These settings are cluster-wide; therefore you need to set them only on the IM and Presence Service database publisher node within any given cluster.


      Procedure
        Step 1   Log in to the Cisco Unified IM and Presence Administration user interface. Choose Presence > Inter-Domain Federation > SIP Federation.
        Step 2   Choose the domain from the list provided. If no list is shown, click Find.
        Step 3   Click Delete Selected.
        Step 4   Click OK to confirm the deletion.

        What to Do Next

        After you remove the static route to the remote domain and remove the SIP Federation domain, you can proceed to configure the IM and Presence Service for Interdomain Federation with the remote domain. See Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager for more information.