Cisco Jabber Federation Office 365 Upload Certificate Imp Service Server

Planning for Integration

Supported Partitioned Intradomain Federation Integrations

For partitioned intradomain federation with Microsoft Lync or Skype for Business, you lot must configure TLS; TCP is not supported. For more information, meet Microsoft Lync Configuration for Partitioned Intradomain Federation or Skype for Business organization Configuration for Partitioned Intradomain Federation.

This chapter describes the configuration steps for enabling partitioned intradomain federation betwixt IM and Presence Service and Microsoft Skype for Business/Lync/OCS . The post-obit Microsoft server platforms are supported:

• Microsoft Skype for Concern Server, 2015, Standard Edition and Enterprise Edition

• Microsoft Lync Server 2013, Standard Edition and Enterprise Edition

• Microsoft Lync Server 2010, Standard Edition and Enterprise Edition

• Microsoft Office Communications Server 2007 Release ii, Standard Edition and Enterprise Edition

IM and Presence Service does non back up an ASA in partitioned intradomain federation.

Annotation

If yous take a mixed deployment of both Lync and OCS servers, you must run the user migration tools for the Lync users, and and so run the user migration tools for the OCS users.

Nosotros recommended that you use the Federation Sorcerer to configure Partitioned Intradomain Federation. This Federation Magician allows you to automatically configure partitioned intradomain federation with Microsoft Lync or Skype for Business, by creating the Static Routes, Admission Control Lists and TLS peers that are required for Partitioned Intradomain Federation and provides the Windows server PowerShell CLI commands required to configure modifications on the Microsoft server.

To launch the Federation wizard from the Cisco Unified CM IM and Presence Assistants, click .

Even so you can still manually configure this feature.

Presence Spider web Service API Support

The Presence Spider web Service is an open interface that allows client applications to share user presence information with IM and Presence Service. Third political party developers utilize this interface to build customer applications that can send and retrieve updates virtually the presence state of a user. Note the following restriction nigh Presence Spider web Service API back up:

• For partitioned intradomain federation, yous cannot use the Presence Web Service API to obtain presence information from not-Cisco clients.

For more information about the Presence Web Service, see the IM and Presence Service Developer Guide at https://developer.cisco.com/site/collaboration/call-control/unified-presence/documentation/index.gsp.

Limitations for Microsoft Lync Integrations

At that place are two scenarios where adding partitioned intradomain federation breaks existing Microsoft Lync integrations:

• Y'all already have intradomain federation configured for video with Cisco VCS or Cisco Expressway and want to add partitioned intradomain federation with IM and Presence Service: Microsoft Lync is integrated with Cisco VCS or Cisco Superhighway and you lot take a static route configured on Lync to route video and voice traffic for the local Lync presence domain to Cisco VCS or Cisco Freeway. If you modify the static road to point to IM and Presence Service (a requirement for partitioned intradomain federation) you volition break the existing video integration because the traffic that is intended for Cisco VCS or Cisco Pike would instead be routed to IM and Presence Service. You cannot accept both video integration and partitioned intradomain federation to IM and Presence Service.

• You already have integration with Microsoft Exchange Unified Messaging and want to add partitioned intradomain federation with IM and Presence Service: You have a Microsoft Lync server configured for Unified Messaging to Microsoft Exchange (either on-premises, or to the cloud (Office365). If you add a static route from Lync for the local Lync presence domain to betoken to IM and Presence Service (a requirement for partitioned intradomain federation), Unified Messaging integration between Lync and Microsoft Exchange for the domain volition be terminated considering all Unified Messaging SIP traffic for that domain volition be routed to IM and Presence Service. Yous cannot take both integration to Microsoft Exchange Unified Messaging and partitioned intradomain federation to IM and Presence Service.

Annotation

Neither Microsoft Substitution Unified Messaging nor Cisco VCS (or Cisco Expressway) integrations are supported with partitioned intradomain federation if you are sharing the same domain betwixt Microsoft Lync and IM and Presence Service.

Hardware Requirements

The post-obit Cisco hardware is required:

• IM and Presence Service node. For IM and Presence Service hardware support, refer to the IM and Presence Service compatibility matrix.

• Cisco Unified Communications Manager node. For Cisco Unified Communications Director hardware back up, refer to the compatibility information for Cisco Unified Communications Manager document available on Cisco.com.

Annotation

In Release 10.0(i) and later, Cisco supports simply virtualized deployments of Cisco Unified Communications Director (Unified Communications Director) and IM and Presence Service on Cisco Unified Computing Organisation servers, or on a Cisco-approved third-political party server configuration. In Release 10.0(one) and subsequently, Cisco does not back up deployments of Cisco Unified Communications Director or IM and Presence Service on Cisco Media Convergence Server servers. For more information well-nigh the deployment of Cisco Unified Communications Manager or IM and Presence Service in a virtualized environment, see: http://docwiki.cisco.com/wiki/Unified_Communications_in_a_Virtualized_Environment.

Software Requirements

The following sections outline the software required for partitioned intradomain federation.

Server Software

The following server software is required for partitioned intradomain federation:

Cisco Software

• IM and Presence Service

• Cisco Unified Communications Managing director

Microsoft Software

• Depending on the deployment, ane of:

  • Microsoft Skype for Concern Server, 2015, Standard Edition and Enterprise Edition

  • Microsoft Lync Server 2013, Standard Edition or Enterprise Edition

  • Microsoft Lync Server 2010, Standard Edition or Enterprise Edition

  • Microsoft Office Communications Server 2007 Release 2, Standard or Enterprise Edition

• Depending on the deployment, one of:

  • Lync Administrative Tools (optional install item bachelor during installation of Lync)

  • OCS Administrative Tools (optional install item bachelor during installation of OCS)

• Microsoft Active Directory

Other Software

Each of the user migration tools that Cisco provides requires that at least version 2.0 of the .NET Framework is installed on the server where you are running the tool. While attempting to run any of the user migration tools you may receive the following fault: "Awarding failed to initialize properly". The reason for this mistake is that you are attempting to run the user migration tools without the .NET 2.0 or newer Framework installed.

The .Internet 2.0 Framework comes installed as standard on Windows Server 2003 R2 or newer.

Client Software

The customer software required for partitioned intradomain federation deployment between the IM and Presence Service and Skype for Business/Lync/OCS depends on your deployment. You tin have whatever combination of IM and Presence Service supported clients in a partitioned intradomain federation deployment.

IM and Presence Service Supported Clients

The following IM and Presence Service clients are supported in a partitioned intradomain federation deployment between IM and Presence Service and Skype for Business organisation/Lync/OCS :

Cisco Software

• Cisco Unified Personal Communicator Release 8.v

• Cisco Jabber for Mac

• Cisco Jabber for Windows

• Cisco Jabber IM for Mobile (iPhone, Android, Blackberry)

• Cisco Jabber for iPad

• Cisco Jabber for Cius

Notation

For version compatibility for all Cisco Jabber clients, see the appropriate Cisco Jabber client documentation. If the Directory URI IM address scheme is used in your deployment, your client software must support Directory URI.

3rd-Political party Software

Third-party XMPP clients

Microsoft Server Supported Clients

Depending on the deployment, the following clients are supported:

• Skype for Business 2015

• Microsoft Lync 2013

• Microsoft Lync 2010

• Microsoft Role Communicator 2007 Release two

• Microsoft Role Communicator 2005

• Communicator Spider web Admission 2007 Release 2

• Communicator Web Admission 2005

Related Topic

Hardware Requirements

Integration Preparation

It is essential that you lot plan carefully for the configuration of partitioned intradomain federation between IM and Presence Service and Skype for Business/Lync/OCS . Read the items in this section before you brainstorm any configuration for this integration.

Presence Domains

Partitioned Intradomain Federation, by its nature, supports integration between IM and Presence Service and the Microsoft server inside a common presence domain that is configured on both systems. Both IM and Presence Service and the Microsoft server support the configuration of multiple presence domains. Nonetheless, any Microsoft Lync or Microsoft Office Communicator users that are not configured for a matching IM and Presence Service domain cannot participate in partitioned Intradomain federation communications.

For example, in the following effigy, users who are configured in the synergy.online.com domain cannot share IM availability or emails withIM and Presence Service users who are configured in synergy.com and synergy.co.uk domains considering the synergy.online.com domain is not configured on IM and Presence Service. Y'all must add the synergy.online.com domain to IM and Presence Service before those users tin can share availability with the other users in intradomain federation.

Effigy 1. Partitioned Intradomain Federation with Multiple Domains

User Migration

If users are being migrated from Skype for Business organisation/Lync/OCS to the IM and Presence Service as part of this integration, consider the information beneath.

If users are existence migrated from Lync/OCS to IM and Presence Service as role of this integration, please exist aware that IM and Presence Service maintains the Microsoft server identities of users when the Directory URI IM accost scheme is configured, which tin can in turn be mapped to the Lync SIP URI.

Note	To employ the Directory URI IM accost scheme, all clients on the IM and Presence Service cluster must back up Directory URI.

For more information about planning for user migration, see topics related to planning for user migration.

DNS Configuration

Domain Proper name System (DNS) "A" records must be published within the enterprise for all IM and Presence Service nodes and Skype for Business/Lync/OCS servers.

Microsoft servers must be able to resolve Fully Qualified Domain Names (FQDN) and IP addresses for all IM and Presence Service nodes.

Likewise, IM and Presence Service nodes must exist able to resolve FQDNs and IP addresses for all Microsoft server and puddle FQDNs.

Certificate Authorization Server

If TLS encryption is enabled as role of this partitioned intradomain federation integration, an external or internal Certificate Authority (CA) may exist used to sign security certificates on IM and Presence Service and Skype for Business/Lync/OCS . Cisco recommends that you utilize the same CA to sign the Microsoft server and the IM and Presence Service certificates. If not, the root certificates for each CA must exist uploaded onto the Microsoft server and the IM and Presence Service nodes.

Loftier Availability

Yous need to consider how you lot are going to configure availability in your partitioned intradomain federation deployment.

If you wish to make your IM and Presence Service partitioned intradomain federation capability highly available, y'all can deploy a load balancer in front of your designated (routing) IM and Presence Service nodes.

Note	To deploy load balancing (for example, circular robin), a hardware load balancer needs to be installed. The static route in IM and Presence Service points to the load balancer.

Related Topic

High Availability for Intradomain Federation

Prerequisite Configuration for IM and Presence Service

You must consummate the following tasks on the IM and Presence Service before you lot brainstorm to configure partitioned intradomain federation.

1. Install and configure IM and Presence Service.

2. Perform the post-obit checks to ensure that your IM and Presence Service system is operating properly:

   • Run the IM and Presence Service Organization Configuration Troubleshooter.

   • Check that y'all can add together local contacts to the Jabber client of IM and Presence Service.

   • Cheque that your clients are receiving availability states from the IM and Presence Service node.

Additional Configuration for Routing IM and Presence Service Node

In multi-server deployments, an IM and Presence Service node must be dedicated equally the Routing IM and Presence Service node. This means that it is a front-end server that accepts all new entering SIP requests from the Skype for Concern/Lync/OCS and routes them onwards to the IM and Presence Service node on which the request recipient is homed.

Cisco recommends that you do not assign any users to the Routing IM and Presence Service node; as this ensures that the Routing IM and Presence Service node has the chapters to handle the book of SIP traffic from the Microsoft server.

Because no users are assigned to the Routing IM and Presence Service node, you tin can deactivate many of the feature services to free up resources on the Routing IM and Presence Service node. Conciliate the following feature services on the Routing IM and Presence Service node:

• Cisco Presence Engine

• Cisco XCP Text Conference Manager

• Cisco XCP Spider web Connectedness Manager

• Cisco XCP Connection Manager

• Cisco XCP SIP Federation Connection Manager

• Cisco XCP XMPP Federation Connection Manager

• Cisco XCP Message Archiver

• Cisco XCP Directory Service

• Cisco XCP Authentication Service

Related Topic

Configure the Routing Node

Plan Services Restarts during Off-Peak Periods

During the integration process, you lot need to restart the Skype for Business/Lync/OCS server front-cease services. Plan to perform the services restart during off-acme periods, such as during a maintenance window, to minimize the impact to users. For more information, run across the partitioned intradomain federation configuration workflows and topics related to restarting services for your server type.

crawfordwaskepter.blogspot.com

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/intradomain_federation/11_5_1_SU2/cup0_b_partitioned-intradomain-federation-imp-1151su2/cup0_b_partitioned-intradomain-federation-imp-1151su2_chapter_01.html

Share this post