Installation Guide for Cisco Unified Communications Integration for Microsoft Office Communicator Release 8.0
Support for Microsoft Business Productivity Online Standard Suite
Downloads: This chapterpdf (PDF - 169.0KB) The complete bookPDF (PDF - 2.26MB) | Feedback

Support for Microsoft Business Productivity Online Standard Suite

Table Of Contents

Support for Microsoft Business Productivity Online Standard Suite

Requirements for Using Cisco UC Integration for Microsoft Office Communicator with BPOS

Architecture of Cisco UC Integration for Microsoft Office Communicator in a BPOS Environment

User Phone Numbers Must Use +E.164 Formatting

User Authentication

Using Cisco UC Integration for Microsoft Office Communicator with Microsoft Exchange in a BPOS Environment


Support for Microsoft Business Productivity Online Standard Suite


Revised: July 7, 2011

Cisco UC Integration for Microsoft Office Communicator supports environments where a Microsoft Office Communications Server is hosted within the Microsoft Business Productivity Online Standard Suite (BPOS).

The following sections provide an overview of the configuration consideration when you deploy the Cisco UC Integration for Microsoft Office Communicator in an environment that is hosted by BPOS:

Requirements for Using Cisco UC Integration for Microsoft Office Communicator with BPOS

Architecture of Cisco UC Integration for Microsoft Office Communicator in a BPOS Environment

User Phone Numbers Must Use +E.164 Formatting

User Authentication

Using Cisco UC Integration for Microsoft Office Communicator with Microsoft Exchange in a BPOS Environment

Requirements for Using Cisco UC Integration for Microsoft Office Communicator with BPOS

You can use Cisco UC Integration for Microsoft Office Communicator with Microsoft Office Communicator and BPOS if the following conditions are met:

The Active Directory server required by the Cisco UC Integration for Microsoft Office Communicator, and used as an LDAP server is located within the enterprise network.

The BPOS user accounts are synchronized from the Active Directory user accounts in the enterprise. You can use the following tools to do this:

Active Directory Synchronization Tool.

Microsoft Online Services Administration Center. You add the user accounts manually with this tool.

All phone numbers in the BPOS environment are defined in +E.164 format.

Cisco UC Integration for Microsoft Office Communicator supports the version of Microsoft Office Communicator that is being used. For more information about the supported versions of Microsoft Office Communicator, see the Release Notes for Cisco Unified Communications Integration for Microsoft Office Communicator at the following location:

http://www.cisco.com/en/US/products/ps9829/prod_release_notes_list.html

Architecture of Cisco UC Integration for Microsoft Office Communicator in a BPOS Environment

The following illustration shows how the Cisco UC Integration for Microsoft Office Communicator operates in a BPOS environment:

The Cisco UC Integration for Microsoft Office Communicator has no direct interaction with the hosted Microsoft Office Communicator servers. All interaction happens through the Microsoft Office Communicator application programming interfaces (APIs).

The Cisco UC Integration for Microsoft Office Communicator uses LDAP to interact with an enterprise-based Active Directory server. The Cisco UC Integration for Microsoft Office Communicator also interacts with Cisco Unified Communications Manager for voice and video media services.

User Phone Numbers Must Use +E.164 Formatting

When you call a contact, the Cisco UC Integration for Microsoft Office Communicator mostly gets contact phone numbers from the Microsoft Office Communicator address book. In a BPOS environment, the address book is downloaded from the BPOS service.

To populate the address book with the phone numbers of the Microsoft Office Communicator users, the OCS address book service in the BPOS data center must enter the phone numbers into address book files correctly.

The OCS address book service only enters +E.164-formatted phone numbers into the address book. Phone numbers that are not in this format are excluded from the address book. All phone numbers provided to the BPOS service must be in +E.164 format.

For more information about the +E.164 standard and Cisco UC Integration for Microsoft Office Communicator, see the Installation Guide for Cisco Unified Communications Integration for Microsoft Office Communicator at the following URL:

http://www.cisco.com/en/US/products/ps10317/tsd_products_support_series_home.html


Note Do not use spaces in +E.164 phone numbers.


User Authentication

The Microsoft Online Services Sign In tool performs Microsoft Office Communicator authentication. This tool manages the Microsoft Office Communicator sign-in process.

The Cisco UC Integration for Microsoft Office Communicator sign-in process is authenticated using Cisco Unified Communications Manager and/or Active Directory, depending on how the authentication is set up. The BPOS environment does not change the default authentication process for the Cisco UC Integration for Microsoft Office Communicator.


Note If your organization uses a dedicated BPOS environment your users might not be required to use the Microsoft Online Services Sign in tool with Microsoft Office Communicator.


Using Cisco UC Integration for Microsoft Office Communicator with Microsoft Exchange in a BPOS Environment

The BPOS service can also provide a Microsoft Exchange service. The Cisco UC Integration for Microsoft Office Communicator includes an option that users can select to save conversation history in Microsoft Outlook. This option has been tested with an Outlook client integrated into a BPOS-hosted Exchange server.

The Cisco UC Integration for Microsoft Office Communicator can also operate in an environment where OCS is hosted within BPOS, and Exchange is hosted within the enterprise data center.