deploying cisco uc integration for microsoft office ......cisco uc integration for microsoft office...

© 2009 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID

Deploying Cisco UC Integration for Microsoft Office Communicator.

김병구 (Ryan Kim)

Unified Communications & Collaboration

UC Office of the CTO


Agenda

Client Services Framework

Server Configuration

Desktop Deployment & Configuration


Client

Services

Framework


Cisco UC Integration™ for Microsoft Office Communicator

Cisco Unified Client Services Framework

A Frame work of Client Services enabling Unified Communications Applications.

Audio / Video Engine

Secure Call Control Stacks

Text Conferencing Servers (IM)

Presence Rendering

Audio/Video Conferencing Controls

Advanced Voicemail controls

Call History ManagementCisco Unified

Client Services

Framework

© 2009 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 5



Cisco UC Integration for MOC

Microsoft Office Communicator

Cisco UC Tab

Microsoft

Outlook

Call Ctrl

Media V-Mail Conf LDAPHistor

y




CCMCIP (CCM Cisco IP Phone Service)

The CCMCIP Service was originally used to support Phone Directory, Services, Authentication & Help

The CCMCIP service provides access to retrieve user and phone information

The CSF uses CCMCIP to obtain a list of devices associated with a user that it can use

CCMCIP

Login

Request Devices

Device Info

Client Svcs

Framework

App



Enable Communications Manager for CSF

Cisco UC Manager can support CSF based devices from version 6.1(3) and later

A COP File is used to update UC Manager to provide support for CSF Devices

Admin uploads COP file using FTP/SFTP via UC Manager OS Admin Interface

UC Manager applies update to Database

Admin restarts UC Manager TFTP Server Only

Admin can create CSF devices in UC Manager Admin interface.

FTP / SFTP

Upload


Device Naming Convention

Free form, no correlation to username required

Any character [A-Z,0-9] up to 15 characters

Required Device Parameters

Parameters without default values (must be explicitly set)

Device Name (as described above), Device Pool, Phone Buttons Template, Device Security Profile, SIP Profile


CSF Device Configuration

Example Device Names

CSFBMORRIS

(username)

WXP-112442

(workstation name)

CSF489232

(Directory Number)



Communications Manager Administration

Add Screen shot of CSF Config Page


Codec selection is based on the region configuration on the Unified Communications Manager.

Current Software Audio Codecs Supported

G.711a, μ-law

G.722 wide band

G.729a, G.729ab

iLBC (free narrowband speech codec)


CSF Software Codec

Cisco Unified

Client Services

Framework



Client Licensing – Cisco Unified Workspace License

The MOC CSF Integration can be licensed using Cisco Unified Workspace Licensing.

Using CUWL the Integration is enabled for both desk phone control and soft phone modes of operation.

Cisco Unified Workspace Licenses also includes all call control licenses, telephony device licenses, Messaging licenses and simultaneous ring mobility licenses/



Client Licensing – Cisco à le carte Licensing

À le carte licensing allows an organization to purchase component based licenses.

ClientLicense

ClientLicense

ClientLicense

A Client license is required for ALL UC Integration users.

Device License Units are required for Softphone Operation of the integration.

* Note: DLU Count don‟t include deskphone DLU requirement.


Server

Configuration

© 2007 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 14


Configuration Steps

Active Directory

Create / Update users and assign E.164 number

Office Communications Server

Enable AD users for Office Communications Server

Verify OCS Address Book Synchronization is configured and operational

Cisco Unified Communications Manager

Apply new device type to Unified CM

Enable LDAP Integration

Create devices for users

Assign devices to users

Create Dial/Directory Rules



Microsoft User Configuration

Administrator adds User and E.164 Telephony details to AD

Administrator will enable User as an OCS user

Once a day OCS will create an address book with E.164 Normalization - (Default time is 1:30 am)

Address book is downloaded by Microsoft Office Communicator clients

OCS

Address

Book

Server

Active Directory

Domain Controller

• Telephone DN

• Mobile DN

• Home DN



Dial Plan

Two different approaches to dial plan design with CUCIMOC

1) Private / E.164 Dialing

2) Full E.164 Dialing

AD configured with

E.164 Addresses

“+1 408 222 333”

CUCM configured with

Private Dial plan

“8222333”

AD configured with

E.164 Addresses

“+1 408 222 333”

CUCM configured with

E.164 Addresses

“+1 408 222 333”(requires CUCM 7.x+)



Client Dialling

When a user initiates a call the dialling number is take from the OCS address book

If UC Manager is using a private dial plan then Dial Rules are used to translate the number from the OCS E.164 format

LDAP (AD) is used for additional destination information

Note: Translation Patterns could alternatively be used for mapping

OCS

Address

Book

Server

Address book

downloaded

using HTTPS

UC Integration

Client

Dial rules downloaded from

TFTP Server

Dial 815674example:

6 digit dial plan

OCS Address

Book

Application Dial

Rules

Dial rules

transform

numbers

from E.164



Application Dial Rules

1 2 3 4 5 6 7 8 9 10 11 12

+ 1 4 0 8 5 7 1 5 6 7 4Microsoft AD/OCS

E.164 address

Communications

Manager DN

Begins “+1408571”

Number of digits = 12

1 2 3 4 5 6 7 8 9 10 11 12

+ 1 4 0 8 5 7 1 5 6 7 4

Digits to remove = 7

Prefix with 8

This slide shows how to create a Application Dial Rule from an OCS E.164 address to a Cisco private dial plan.




1 2 3 4 5 6 7 8 9 10 11 12

+ 3 4 9 1 2 0 1 2 6 0 5Microsoft AD/OCS

E.164 address

Communications

Manager DN

Begins “+34”


1 2 3 4 5 6 7 8 9 10 11 12

+ 3 4 9 1 2 0 1 2 6 0 5


(No Prefix required)

This slide shows how to create a Application Dial Rule from an OCS E.164 address to a Cisco private dial plan.



Example Translation Pattern

This example shows a translation pattern used instead of a dial rule



Reverse Number Lookup

The client integration will attempt a reverse number lookup to identify incoming callers

The client integration will download Directory Lookup Rules from UC Manager which will map from UC Manager Dial plan to E.164 numbers in Active Directory (LDAP)

LDAP

Server

(AD)

UC Integration

For MOC

Search for

+14442215682Incoming Call

from 15682

Unresolved

Resolved



Directory Lookup Rules

1 2 3 4 5 6 7 8 9 10 11 12

+ 3 4 9 1 2 0 1 2 6 0 5Microsoft AD/OCS

E.164 address

Communications

Manager DN

Begins “91”


4 5 6 7 8 9 10 11 12

9 1 2 0 1 2 6 0 5


Prefix with “+34”

If AD is populated with E.164 addresses, the client will need to map DN to full E.164 address before performing LDAP searches.



Directory Lookup Rules



Configuration of UC Manager Dial rules

Application / Directory Dial rules are configured on UC Manager

The CSF based client will download the XML rules files using TFTP

UC Manager currently doesn‟t dynamically create the rules in the TFTP directory

Each time any rules are created, modified or deleted the Dial Rules Wizard COP file MUST be applied to ALL TFTP Servers

Process: Upload COP files, Apply COP file, Restart TFTP Server



UC Manager User ID

Cisco strongly recommends – synchronize User Id‟s between AD and UC Manager for UC integration for MOC deployments

CUCIMOC connects to both UC Manager and Active Directory (LDAP) using the Users Login Credentials

The Username and Password need to be synchronized for successful login to both systems

Manual Synchronization requires passwords to be kept in sync

Bob Bob

Alice Alice

Active

Directory

CUCM

End Users

User Synchronisation

& Authentication



How UserID is used.Active Directory (LDAP)Communications Manager Services

User enter credentials into the

Communication Pane login window(Credentials can be maintained in an encrypted cache)

UC

Services

Directory

Lookup

UC Client will

access various

CUCM services

including:

CCMCIP Service

CTI Manager

Call Control (SIP)

UC Client will

access AD using

LDAP for:

Contact Details

(not phone details)

Reverse Number

Lookup

User Photo

Location

CUCIMOC will

append domain

to login

“name@domain”

Sync

Sync



Conferencing

Cisco UC integration for MOC provides an ad-hoc conferencing facility

Client uses conference resources defined by administrator

Resources can be Software or Hardware based

Supports up to 6 parties in default configuration

DSP Conference

Resources



Mobility (Soft phone Mode Only)

Cisco UC Integration for MOC supports call hand off using UC Manager Unified Mobility

User must be enabled forMobility and have remote destinationsconfigured in UC Manager



Voicemail

Cisco UC Integration for MOCprovides TUI access to a UC Manager configured messaging service

Clicking the VoicemailIcon initiates a voice call to the messagingservice

MWI is displayed in theclient when running in Softphone mode

No specific configuration required on the server to supportvoicemail



Photo Display Cisco UC Integration for MOC can

display user Photos for contacts

Photos are retrieved from a web server or file location. (Photos are NOT stored in active directory)

The file location is stored in activedirectory and is retrieved during LDAP lookups

The client will then fetch the photo file

A photo attribute can be created in AD which will hold the location

Example

photouri = “http://hr.cookie.ie/staff/mredding.jpg”


Desktop

Deployment &

Configuration



Product Deployment

The Client Integration has been designed to be deployed using desktop Management Tools

An administrator can choose to deploy the application using one of the following mechanisms:

AD Group Policy

SMS/Altris push

Self-extracting executable and script/batch file

A standalone install can also be performed

Cisco will publish a Group Policy Template File (ADM)



Product Deployment

Installer Files includes both the Client Integration and Client Services Framework

Two version of the Installer are provided

.EXE : Designed for Standalone InstallIncludes UC Integration, Client ServicesFramework and MS .NET 3.5(SP1) Install Stub

.MSI : Designed for “Push” InstallIncludes UC Integration and Client ServicesFramework. MS .NET 3.5(SP1) should be pre installed

Product is configured using Group Policy or Configuration Script directly to the workstation registry



Client Configuration

Batch/Script

file

Client

Workstations

Registry

AD Group

Policy Cisco UC Integration for Office

Communicator will read it‟s configuration information from the registry of the workstation

The registry needs to be populated prior to using the client

For deployments across multiple machines, we recommend using an AD group policy or other software deployment tool

Alternatively, the registry could be populated using a batch file or script file maybe as part of a login script

Registry Location:HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Client Services Framework\AdminData



Configuration Data

Communication Manager Configuration

TFTP Server (used by SIP client and for dial rules)

CCMCIP Server (used to learn about devices)

CTI Server (used for desk phone control)

Voicemail Pilot (used for desk phone access to VM)

LDAP Confiiguration

LDAP Servers, Search Bases (upto 5),

Authentication Domain

LDAP Field Mapping



Client Configuration

A group Policy administration template will be available for CUCIMOC which can be imported into Group Policy Object Editor.



Sample Batch File

A Sample Batch file will be available to populate the registry with CUCIMOC configuration data for single workstation installs

Note: Partial file displayed


We Strongly recommend Microsoft Office Communicator Telephony Mode Policy is set to “IM and Presence” and “DisableAVConferencing” is true when deploying the Cisco integration

Changing this Policy will mean only a single set of Call options are shown in the Microsoft client user experience

To do this, administrators should apply Microsoft Office Communicator policy settings users to „IM and Presence Only‟

This policy can also be applied directly to the workstation registry


Client Policy


The following file is for example only


Sample Registry Settings


When the Integration starts up it will look of a valid Outlook profile. If the profile exists, the user will able to select to have conversation history passed to outlook.

This will be stored in the “Conversation History” folder along with IM history placed there by Microsoft Office Communicator.

For this option to be availableExchange and OCS should bein the same domain/forest

The outlook profile shouldcontain the users SIP URI


Outlook Integration



Outlook Integration



Outlook Integration

The UC Integration also provides click to call from Outlook



Office Suite Integration

By Default, the Integration will install click to call support in Word, Excel, Outlook and in the MS Personal Menu



Browser Integration (IE & Firefox)



Desktop Integration

The installer will install a “click with edit” icon in the quick launch bar

This quick launch icondisplays a window to dialfrom the clipboard

The installer will configure a URI handler for the TEL: uri.

Tel:+14082224444 - Creates a link to the “Call with Edit” app.

tel:+14082224444

deploying cisco uc integration for microsoft office ......cisco uc integration for microsoft office...

Documents