17CUCIMOC CKN Sept 09 Final

Cisco Unified Communications
Integration™ for Microsoft Office

Communicator 7.1
September 22, 2009
Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1
Welcome
Hosts – Karen Manning, Gene Papula, Andy White

Cisco Knowledge Network
http://www.CiscoKnowledgeNetwork.com/UC
Today’s presentation posted
Past program recordings
Cisco UC Integration for MOC demonstration immediately available
Two question & answer periods

Please use the Webex Q&A window to enter questions
BM – Cisco UC Integration™ for Microsoft Office Communicator © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 2
Resources…
Today’s Presenters
Bryan Morris
Technical Marketing Engineer, Voice Technology Group
Kalpesh Patil
Network Consulting Engineer, Advanced Services Delivery Team
Greg Hinson
Network Consulting Engineer, Advanced Services Delivery Team
Today’s Panelists for Q&A Chat

Heather Paunet, Product Manager
Priten Gandecha, Product Manager Marketing
Louis Pratt, Technical Marketing Engineer
Survey
Cisco Knowledge Network – Feedback
Scale: 5=Agree; 4=Somewhat Agree; 3=Neutral; 2=Somewhat Disagree; 1=Disagree
This Cisco event was a good use of my time. [1-5]
Overall, the speakers were knowledgeable, informative, and engaging. [1-5]
I would recommend this event to others. [1 - 5]
Is your organization currently using Microsoft Office Communicator client on your

desktop to exchange presence & instant messaging between employees, partners, &
customers?
Are you planning on implementing a unified or integrated desktop communications

experience (e.g. presence, instant messaging, voice, video, conferencing, &
messaging) to streamline business communications & enhance productivity?
Please indicate which Cisco Unified Communications & Collaboration applications & solution
your organization currently uses
I am interested in having Cisco, or my Cisco Partner, contact me to continue today’s conversation around
Cisco UC Integration capabilities and the Client Services Framework. [Y/N]
Bryan Morris Kalpesh Patil Greg Hinson
Technical Marketing Engineer Network Consulting Engineer Network Consulting Engineer
Cisco Unified Communications Cisco Advanced Services Cisco Advanced Services
Cisco UC Integration™ for Microsoft Office Communicator
Agenda
Product Overview
Product Architecture
Product Requirements
Unified Client Services Framework (CSF)
Configuration & Deployment
Agenda
Product Overview
Cisco Desktop UC portfolio
Cisco Unified Cisco Webex Cisco Unified
Personal Communicator Connect Communications Integrations
IBM Microsoft
Cisco Unified Cisco UC

Communications Cisco WebEx Interoperability
• Single end-to-end, on- • Hybrid architecture – • Market-leading

prem UC solution with best of both worlds Microsoft and IBM
seamless User • On-demand IM, integrations
Experience Presence and Collab • Focus on native UE
• Builds on CUCM, • On-prem Enterprise- • Single call control
CUP, Jabber & CSF grade Voice & Video solutions - TCO & UE
• Integrated Mobility • Seamless User • Cisco enterprise-
and Contact Center Experience with CSF grade Voice & Video
Collaboration Architecture for Clients
Cisco Unified
Infrastructure
Services
Introducing the Cisco UC Integration™ for
Microsoft Office Communicator
Designed for customers
with Microsoft OCS based
IM solution.
Seamless collaboration
with Cisco UC & Microsoft
instant messaging (IM)
Extends proven Cisco UC
services to Microsoft
Office Communicator with
a single easy-to-manage
communications platform
Delivers Seamless Communications
with Cisco UC & Microsoft (IM)
Fully integrated soft phone
Control desk phone
Cisco IP Phone like audio quality
and call control
Phone presence displayed in
Inbound call notification & divert
Click to call from Office, browsers
Client call history
Voicemail MWI & access
The Communication Pane
Users interact with desktop
integration to Unified
Communications Manager via
the Communications Pane
Users initiate calls by dragging
contacts from the contact list to
call icon
Users may also right click a
contact to make a call
1 2 3 4 5 6
1. Call Icon: Drag contacts to this button to place a call

2. Voicemail Access Button: Select to call your voice message
service.
Message Waiting Indicator (MWI) appears if there is a voicemail
message
3. Communications History: Select to display incoming or
outgoing received, placed and missed calls
4. Phone Mode: Select to switch from softphone mode to deskphone
mode
5. Options: Select to modify particular user options, such as call
forwarding
6. Integrated Key Pad: For ad hoc dialing
The Communication Pane will show different views

based on the current status of the client
Feature Overview: Making a Call (1)
Calls can be
Drag and drop made by dragging
the contact and dropping a
to call Icon
contact on to the
call Icon
Feature Overview: Making a Call (2)
If multiple numbers exist

for the contact, the Cisco
UC Integration™ for
Microsoft Office
Communicator contact
card is displayed
The user then clicks on
the required destination
Note: Call destinations include Business, Mobile, Home
Feature Overview: In Call Functions
Note: Image shows

encrypted call in
progress
Conference / Merge Calls

Transfer Call
Transfer to alternative device (Cell etc)
Call Park / Retrieve
Hold
Mute
Feature Overview: Call Conference/Merge
Merged into a
conference with
Two Calls in roster
the Conversation
Window
Tools menu extensions
The desktop integration extends the
Microsoft Office Communicator tools
menu to add other functions
User Help Device selection
Sign Out Status information
Feature Overview : Call History
Call History is
available from within
Microsoft Office
Communicator
A user may also

choose to have
Call History placed
in the Conversation
History in Outlook
with IM History
Feature Overview : User Options
Options Icon provides access

to call forwarding functions
and other options.
The Communication Pane can also exist outside the
Microsoft Office Communicator application
Typically, this would happen if Office Communications

Server becomes unavailable
The desktop integration can also be started in this mode.
Microsoft Office Suite Integration
The desktop integration provides click to call support in
Word, Excel, Outlook and in applications that support
the MS Personal Menu
Browser Integration (IE & Firefox)
The UC Integration™ adds

“Click to Call”support to both
firefox and Internet Explorer
Desktop Integration
The UC Integration also provides a “click with edit”
which is added to the quick launch toolbar.
The user can click the Icon to key a number to dial
The text in the clipboard is shown in the window if
available
NOTE: This functionality is also available using the

Cisco Unified Click to Call Widget.
Desktop Integration
The UC Integration™ provides for “TEL” URI Hyperlinks.
Example: Tel:+14082224444 ( Click to call link)
TEL URI’s can be used to UC enabled business
applications to support the click to call function.
Agenda
Product Overview
Component Overview
The desktop integration brings
together the following components
to deliver the Solution and
User Experience
Microsoft Active Directory
Microsoft Office
Communications Server
2007
Cisco Unified
Communications Manager
6.1(4) or later
Cisco UC Integration™ for Microsoft
Office Communicator including
Cisco Unified Client Services Framework
Cisco Unified Communications Manager
Cisco Unified Communications
Manager is the call control
component of the solution.
Softphone Calls are setup
using SIP signalling.
Deskphone Calls are setup using
CTI based setup.
Unified CM provides Call conferencing
services
Unified CM provides mobility
services for simultaneous ringing
and call hand-off to remote device.
Unified CM provides call routing to
voicemail service with MWI indication.
Unified CM provides Call admission
control and alternative routing for voice
quality
Active Directory / Domain Controller
Active directory is providing
directory services for both
the Cisco UC and Office
Communications
server environment
User Information, Telephone
Numbers and Organisation
information is help in AD
AD is used for authentication
Note: Cisco recommends Unified CM

is configured for both LDAP synchronisation
and authentication when used with UC Integration for
Microsoft Office Communicator.
Microsoft Office Communication Server
Microsoft Office Communications Server
provides IM and Presence
services for the Solution…
Point to Point and Multi-party
Chat capabilities
IM logging for compliancy
Presence/Availability indication
Address Book Update,
management and distribution
NOTE: Microsoft Enterprise Voice is neither

enabled nor required for this solution
Cisco Soft phone Integration
The desktop may be
operated as a soft phone using
a USB headset to make and
receive calls
In Soft Phone mode the desktop
ntegration will register with
Unified CM as a SIP based
endpoint.
Soft phone mode provide
support for multiple standards
based audio codecs
including G.711, G.729, G.722
and iLBC.
Phone presence is provided to
Microsoft Office Communications
Server by the desktop integration.
Presence with the Cisco UC Integration™
The UC Integration™ provides phone status to Microsoft Office
Communications Server environment.
The Integration receives line events from Unified Communications
Manager, This update is passed to Office Communicator as a
status change.
Presence is shown across multiple shared line devices.
UC Integration
Unified CM
receives line
is aware of
state events
line state
Update sent
to server
Integration updates
Office Communicator
presence to show
Busy State
Cisco Desk Phone Integration
The desktop integration may
control a Cisco Unified IP
deskphone providing 3rd
party call control.
In desk phone control mode
the desktop integration
communicates with the UC
Manager CTI Manager.
Phone presence is
provided to Microsoft Office
Communications Server
by the desktop integration.
Conferencing
The desktop
integration uses
Unified CM ad-hoc
conferencing.
Conference resources
are defined by the
administrator
Resources can be
Software or Hardware
based
Mobility (Soft phone Mode Only)
The Cisco UC Integration™
supports call hand off using
Unified CM Unified
Mobility
User must be enabled
for Mobility in Unified
Communications Manager
Voicemail
The desktop integration provides TUI
access to a Unified CM configured
messaging service
Clicking the Voicemail
Icon initiates a voice
call to the messaging
service
MWI is displayed in the
client when running in Soft
phone mode
No specific configuration
required on the server to support
voicemail
Agenda
Product Overview
Supported Versions of Microsoft Components
Microsoft Office Communications Server

Version supported:
Microsoft Office Communications Server 2007
Microsoft Office Communications Server 2007 R2
Microsoft Office Communicator Version

Supported:
Microsoft Office Communicator 2007
build number 2.0.6362.36 or greater
A Microsoft hot-fix to upgrade Microsoft Office Communicator is available from
http://support.microsoft.com/default.aspx/kb/957465
Microsoft Office Communicator 2007 R2

build number 3.5.6907.0 or greater
Unified Communications Manager Versions
* 6.1.(3) or later, with Cisco Options Package (COP) file to create the Client Services Framework device type
Desktop Hardware/Software Min. Requirements
Desktop PC Property Minimum Requirements:

Audio Only
Installed RAM XP 1GB, Vista 2GB
Free disk space 120 MB
CPU speed/type 2.4 GHz
I/O ports USB 2.0 port
Operating System Windows XP SP2 SP3, Vista
Laptop PC Property Minimum Requirements:

Audio Only
Installed RAM XP 1GB, Vista 2GB
Free disk space 120 MB
CPU speed/type 1.8 GHz
I/O ports USB 2.0 port
Operating System Windows XP SP2 SP3, Vista
Desktop Hardware/Software Min. Requirements
Desktop OS Requirements
Operating System 32 - Bit 64 – Bit (WOW)
Windows XP SP2 Supported Not Supported
Windows XP SP3 Supported Not Supported
Windows Vista Business SP1 Supported Supported
Windows Vista Enterprise SP1 Supported Supported
Windows Vista Ultimate SP1 Supported Supported
Other Desktop Software Requirements / Options

Microsoft Office 2003 (Click to Call & Outlook Integration)
Microsoft Office 2007 (Click to Call & Outlook Integration)
Internet Explorer 6.x, 7.X (Click to Call)
Mozilla Firefox (Click to Call)
Agenda
Product Overview
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
Cisco Unified Call History Management
Client Services
Framework
Unified Client Services Framework
Microsoft Office
Microsoft
Communicator Outlook
Cisco UC Tab
Cisco UC Integration for MOC
Client Services Framework

Call History
Media Conf V-Mail LDAP
Ctrl
Unified CSF Device Configuration
Device Naming Convention
Free form, no correlation to username
required
Any character [A-Z,0-9] up to 15
characters Example Device Names
Required Device Parameters CSFBMORRIS
(username)
Parameters without default values
(must be explicitly set) WXP-112442
(workstation name)
Device Name (as described CSF489232
above), Device Pool, Phone (Directory Number)
Buttons Template, Device Security
Profile, SIP Profile
Unified CSF Software Codec
Cisco Unified
Client Services
Framework
Cisco UC Integration™ for Microsoft Office
Communicator– Unified Workspace License
Cisco UC Integration™ for Microsoft Office
Communicator can be licensed using Cisco Unified
Workspace Licensing
Using Cisco Unified Workspace Licensing the desktop

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 (or mobility) licenses
à le carte Licensing
À la carte licensing allows an organization to purchase component based
licenses.
Client
License Client Client
License License
A la carte part number for UC Integration™ for Microsoft Office

Communicator is UCIMOC-7.1-K9
Device License Units (DLU) are required for softphone operation of the
desktop integration
Notes: 1) Adjunct License DLU Count doesn’t include desk phone DLU requirement.
2) CSF adjunct license support requires UC Manager 6.1(4)+,7.0(2a)su1+ or 7.1(3)+ 49
BM – Cisco UC Integration™ for Microsoft Office Communicator © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public
Cisco
Q&A
Agenda
Product Overview
•Server Configuration
•Client Deployment
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

Enable LDAP Integration
Create devices for users
Assign devices to users
Configuring Users
Office
Active Communications
Directory Server
2
OCS
3
1 Address Book
Service
4
1) Administrator adds user to Active directory Unified
2) Administrator enables user for Office Communications
Communications server Manager
3) OCS adds user to OCS address book and
distributes to MOC clients
4) User is synchronised to Cisco Communications
Manager and is associated with devices.
AD User Configuration
Active
Directory
Server
1
Administrator adds a User to Active Directory

Administrator populates telephone information in full E.164 format,
Telephone, Mobile and Home numbers can be populated.
For completeness we suggest Organization information such as
title and company is populated as this is all displayed on the UC
Integration contact card.
Microsoft User Configuration
Active Directory
Domain Controller
OCS
• Telephone DN Address
• Mobile DN Book
• Home DN Server
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
Enable users as OCS users
1
Active Directory Office Communications
Server Server
Administrator enables users as Office Communications

Server users.
This can be accessed from within the “Active directory
users and computers” console
OCS Address Book Service
Address
Distribution of
Book Service
address book
Extract User details to MOC Cients
from OCS and
creates an address
book with normalized
telephony details
Active Directory Office Communications

Server Server
Cisco UC Integration takes phone numbers from the OCS address book
OCS Address book service scans AD once a day to create a normalized
address book. (default run at 01:30am*)
Address book will reject any numbers that can’t be normalized
Address book/updates are downloaded by MOC clients over a secure
HTTPS connection.
* Note:Manual Address books scans are also possible
UC Manager User ID
User Synchronisation
& Authentication
CUCM Bob Bob
Active
End Users Directory
Alice Alice
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
UC Integration 7.1(2) provides support for non synchronized systems
How UserID is used.
Communications Manager Active Directory (LDAP)
Services
UC Client will
UC Client will access AD using
LDAP for:
access various
CUCM services Contact Details
including: (not phone details)
Reverse Number
CCMCIP Service Lookup
User Photo
CTI Manager
Location
Call Control (SIP) CUCIMOC will

User enter credentials into the append domain
to login
Communication Pane login window“name@domain”
(Credentials can be maintained in an encrypted cache)
UC Manager User Configuration
Synchronization
IP
Phone
User CSF
Authentication
Association Device
Active Directory Unified Comms
Server Manager
The UCM Administrator needs to associate the devices which will
be used by the UC Integration™ with the end user.
The end user must be configured with the “End User” CUCM roles
to be able to access the CCMCIP Server.
The end user must be configured with a CTI role to allow desk
phone control from the UC Integration™
Desk phones must also be configured with CTI enabled.

Calling a Contact
When you initiate a call with
the Cisco UC integration™ for
MOC you get a contact
window displayed to select a
telephone number.
Calling a Contact
When you initiate a call with
the Cisco UC integration™ for
MOC you get a contact card
displayed to select a
telephone number.
The telephone numbers
shown in the contact window
have been retrieved from the
OCS address book.
Dial Plan
Two different approaches to dial plan design with the
Cisco UC Integration.
1) E.164 / Private Numbers
AD configured with CUCM configured with
E.164 Addresses Private Dial plan
“+1 408 222 333” “8222333”
2) Full E.164 Numbers

AD configured with CUCM configured with
E.164 Addresses E.164 Addresses
“+1 408 222 333” “+1 408 222 333”
(requires CUCM 7.x+)
Dialling with a Private Number Plan
Application Dial
Dial 815674 Rules
example: Dial rules

6 digit dial plan transform
numbers
from E.164
Dial rules downloaded from

TFTP Server
When using a private dial plan we need to translate the

E.164 number to the private dial plan.
We do this using Application dial rules which the Client
Services Framework will download from Communications
Manager
Application Dial Rules
The Unified CM administrator creates the Application
dial rules in the CM admin interface.
Application Dial Rules
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
Microsoft AD/OCS
+ 1 4 0 8 5 7 1 5 6 7 4 E.164 address
Begins “+1408571”
Number of digits = 12
1 2 3 4 5 6 7 8 9 10 11 12
Communications
+ 1 4 0 8 5 7 1 5 6 7 4 Manager DN
Digits to remove = 7
Prefix with 8
Reverse Number Lookup
LDAP
UC Integration Server
For MOC (AD) Unresolved
Search for
Incoming +14442215682
Call
from 15682
Resolved
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)
Directory Lookup Rules
The Unified CM administrator also creates the Directory

Lookup rules in the CM admin interface.
Directory Lookup Rules
If AD is populated with E.164 addresses, the client will need to map DN
to full E.164 address before performing LDAP searches.
1 2 3 4 5 6
Communications
8 1 5 6 7 4 Manager DN
Begins “81”
Number of
digits = 6 1 2
Digits to remove = 2 8 1
X X
(Remove Internal site code “81”)
1 2 3 4 5 6 7 8 9 10 11 12
Microsoft AD/OCS
+ 1 4 0 8 5 7 1 5 6 7 4 E.164 address
Prefix with “+1408571”

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
Each time any rules are created, modified or deleted the
Dial Rules Wizard COP file MUST be applied to ALL
TFTP Servers
Process: Upload Dial Rules Wizard COP files,
Apply Dial Rules Wizard COP file,
Restart TFTP Server
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 active
directory 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”
Agenda
Product Overview
•Server Configuration
•Client Deployment
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 Install
Includes UC Integration, Client Services
Framework and MS .NET 3.5(SP1) Install Stub
.MSI : Designed for “Push” Install
Includes UC Integration and Client Services
Framework. 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
Cisco UC Integration for Office AD Group
Batch/Script
Communicator will read it’s configuration Policy
file
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 Registry
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
Client
Workstations
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 Configuration
LDAP Servers, Search Bases (upto 5),
Authentication Domain
LDAP Field Mapping
Configuration Data: LDAP
LDAP Server What is the
Example: ldap://10.53.52.106:389 address
of the LDAP
server?
LDAP Authentication Domain How do I
Example: tme-lab.com Address of
authenticate to
DC/GC
the LDAP
server?
LDAP Search Bases
Where do you
[Username]@tm
Example:
OU=TME_Team,DC=tme-lab,DC=com want
e-lab me to
search?
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
Client Policy
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
Sample Registry Settings
The following file is for example only
Outlook Integration
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 available
Exchange and OCS should be
in the same domain/forest
The outlook profile should
contain the users SIP URI
Summary
Extends Cisco UC to Microsoft
Office Communicator with
easier to manage single call
control architecture
Enables seamless
collaboration with Cisco UC
Communications and
Microsoft IM
Provides investment
protection and business-class
communications with
Microsoft
Survey
Cisco Knowledge Network – Feedback
Scale: 5=Agree; 4=Somewhat Agree; 3=Neutral; 2=Somewhat Disagree; 1=Disagree
This Cisco event was a good use of my time. [1-5]
Overall, the speakers were knowledgeable, informative, and engaging. [1-5]
I would recommend this event to others. [1 - 5]
Is your organization currently using Microsoft Office Communicator client on your

desktop to exchange presence & instant messaging between employees, partners, &
customers?
Are you planning on implementing a unified or integrated desktop communications

experience (e.g. presence, instant messaging, voice, video, conferencing, &
messaging) to streamline business communications & enhance productivity?
Please indicate which Cisco Unified Communications & Collaboration applications & solution
your organization currently uses
I am interested in having Cisco, or my Cisco Partner, contact me to continue today’s conversation around
Cisco UC Integration capabilities and the Client Services Framework. [Y/N]
Cisco
Q&A
Release 7.1: Feature Summary
Operation Modes Audio Support
Soft phone (CSF based SIP Endpoint) Codecs : G.722, G.711, G.729a, iLBC voice
Desk phone Control (CTI based) codecs, including SRTP
User switch between modes SRTP – Secure Audio
Audio tuning wizard
User Calling
Drag and Drop Contact(s) Calling In Call Features
Right-click Contact(s) from buddy list Conversation information … call status,
participants, participant presence (OCS),
Right Click Contact(s) from IM duration
Call from Contact search DTMF, mute, transfer (blind, consultative),
Direct dial via dial pad conference, redial, hold, hang up, merge,
park
Incoming Call Alerts (Defer to Voicemail)
Volume (Soft Phone Mode)
Launch IM
Call Control
SIP call control, including TLS
Call forwarding Presence / Availability
E164 Number translation (Dial rules) On/Off Hook Line Presence (across devices)
Reverse Number lookup (Dir. Lookup rules) DND – set via Office Communicator/IP Phone
Release 7.1: Feature Summary
User/Support Tools
Mobility Features
Online Help
Single Number Reach
Call statistics
Mobile Handoff (Soft phone Mode)
Server health tool
Extension mobility
Error reporting Tool
Call History Deployment

Placed, missed, received calls “Push to Desktop” Deployment
Call history in Outlook (Optional) Configuration using Microsoft Group Policies
Application Integration Localisation

Click to Call from Microsoft Office Suite French Swedish
Click to Call from Web browsers Japanese Russian
Call from Clipboard Spanish Danish
TEL: URI Support German Chinese (Simplified)
Italian Chinese (Traditional)
Operation outside Office Communicator Dutch Portuguese (Brazilian)
Call survival if Office Communications server Korean Arabic
becomes unavailable

17CUCIMOC CKN Sept 09 Final

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

17CUCIMOC CKN Sept 09 Final

Încărcat de

Drepturi de autor:

Formate disponibile

Cisco Unified Communications

Integration™ for Microsoft Office

September 22, 2009

 Hosts – Karen Manning, Gene Papula, Andy White

 Two question & answer periods

Today’s Panelists for Q&A Chat

Scale: 5=Agree; 4=Somewhat Agree; 3=Neutral; 2=Somewhat Disagree; 1=Disagree

This Cisco event was a good use of my time. [1-5]

Overall, the speakers were knowledgeable, informative, and engaging. [1-5]

I would recommend this event to others. [1 - 5]

Is your organization currently using Microsoft Office Communicator client on your

Are you planning on implementing a unified or integrated desktop communications

Cisco Unified Cisco UC

• Single end-to-end, on- • Hybrid architecture – • Market-leading

1. Call Icon: Drag contacts to this button to place a call

 The Communication Pane will show different views

 If multiple numbers exist

Note: Call destinations include Business, Mobile, Home

Note: Image shows

 Conference / Merge Calls

A user may also

 Options Icon provides access

 Typically, this would happen if Office Communications

The UC Integration™ adds

 NOTE: This functionality is also available using the

 Note: Cisco recommends Unified CM

 NOTE: Microsoft Enterprise Voice is neither

 Microsoft Office Communications Server

 Microsoft Office Communicator Version

Microsoft Office Communicator 2007 R2

 Desktop PC Property Minimum Requirements:

 Laptop PC Property Minimum Requirements:

 Other Desktop Software Requirements / Options

 A Frame work of Client Services

Cisco UC Integration for MOC

Client Services Framework

 Using Cisco Unified Workspace Licensing the desktop

 A la carte part number for UC Integration™ for Microsoft Office

 Office Communications Server

 Cisco Unified Communications Manager

 Administrator adds a User to Active Directory

 Administrator adds User and E.164 Telephony details to AD

 Administrator enables users as Office Communications

Active Directory Office Communications

 CUCIMOC connects to both UC Manager and Active Directory

Call Control (SIP) CUCIMOC will

Desk phones must also be configured with CTI enabled.

2) Full E.164 Numbers

example: Dial rules

Dial rules downloaded from

 When using a private dial plan we need to translate the

 The Unified CM administrator also creates the Directory

Prefix with “+1408571”

 Product is configured using Group Policy or

 A Sample Batch file will

Scale: 5=Agree; 4=Somewhat Agree; 3=Neutral; 2=Somewhat Disagree; 1=Disagree

This Cisco event was a good use of my time. [1-5]

Overall, the speakers were knowledgeable, informative, and engaging. [1-5]

I would recommend this event to others. [1 - 5]

Is your organization currently using Microsoft Office Communicator client on your

Are you planning on implementing a unified or integrated desktop communications

Call History Deployment

Hosts – Karen Manning, Gene Papula, Andy White

Two question & answer periods

The Communication Pane will show different views

If multiple numbers exist

Conference / Merge Calls

Options Icon provides access

Typically, this would happen if Office Communications

NOTE: This functionality is also available using the

Note: Cisco recommends Unified CM

NOTE: Microsoft Enterprise Voice is neither

Microsoft Office Communications Server

Microsoft Office Communicator Version

Desktop PC Property Minimum Requirements:

Laptop PC Property Minimum Requirements:

Other Desktop Software Requirements / Options

A Frame work of Client Services

Using Cisco Unified Workspace Licensing the desktop

A la carte part number for UC Integration™ for Microsoft Office

Office Communications Server

Cisco Unified Communications Manager

Administrator adds a User to Active Directory

Administrator adds User and E.164 Telephony details to AD

Administrator enables users as Office Communications

CUCIMOC connects to both UC Manager and Active Directory

When using a private dial plan we need to translate the

The Unified CM administrator also creates the Directory

Product is configured using Group Policy or

A Sample Batch file will