Unified Communications Integration Into Microsoft Environments

Unified Communications Integration into
Microsoft Environments
BRKUCC-2601
Cisco Unified Communications with Microsoft
BRKUCC-2601
Cisco
Call Control with
Microsoft
Cisco
Collaboration with
Microsoft
Cisco
Presence with
Microsoft
Cisco
Messaging with
Microsoft
Cisco
Contact Centre
with Microsoft
Cisco
Network with
Microsoft
2011 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Whats New in the Microsoft Unified

Communications Solution?
BRKUCC-2601
Cisco Public
Microsoft Unified Communications Solution

Architecture Review of the Microsoft Unified Communication Solution
New Features and Functionality available in Lync 2010
Lync 2010 considerations

Architecture of New Features and Functionality
BRKUCC-2601
Cisco Public

Lync Client
PIC
XMPP
3rd Party
XMPP
Gateway
Archiving
Monitoring
Remote
Users
AD, DNS
Federated
Business
Edge
Service
AV
Front-End Back-End
Conferencing
Incl. Mediation SQL
Standalone
Mediation Server
IP PBX
PSTN
BRKUCC-2601
Exchange
UM
On-Premise
Or Online
Media Gateway
SBA
Cisco Public
Direct SIP
Analog Devices

Architectural Details
Lync Server
TLS
TLS
SIP-Invite Call-ID 1234
SIP 200 OK Call-ID 1234
SIP ACK Call-ID 1234
RTaudio/RTvideo
Lync Server 2010 is a SIP Proxy

MOC 2007 by default uses the proprietary Microsoft
RTaudio and RTvideo codecs (other codecs are
supported per SDP, but not used in the default setup
utilising a mediation server)
Media by Pass features allows for G.711 only*
Limited to no integration into existing TDM or IP systems
(QSIG, H.323, etc.)
BBUA i.e. CUCM
B2BUA creates to separate sessions, full control on

SIP and SDP header
Codec selection based on topology and
administrative control
CAC centrally administrated either static (i.e.,
locations-based)
or network aware (RSVP) transparent to endpoints
BRKUCC-2601
Cisco Public
TLS
TLS
RTaudio/RTvideo

Architectural Details
Fundamental architectural difference between SIP proxy vs. B2BUA model
B2BUA more feature-rich functionally enhanced (intelligent codec selection, CAC,
media control, etc.)
SIP proxy less functional higher scalability based on limited signalling capabilities
SIP proxy doesnt provide advanced media services, i.e., music on hold, etc.
SIP proxy cant provide interoperability services between different protocols (SIP,
H.323, MGCP, etc.)
BRKUCC-2601
Cisco Public
New Features and Functionality* in Lync 2010

Mediation Server Role can be co-located
Media By-Pass
Branch Survivability
Static Call Admission Control
Virtualisation supported All or Nothing, 50% reduced scalability
Telephony Features (MCID, Call Park etc.)
*Please consult www.microsoft.com for detailed list of new features and functionalities
*E911 for United States only
BRKUCC-2601
Cisco Public
Lync 2010 Considerations

Still No Centralised MoH on Lync
Malicious Call Trace no Signalling to PSTN
Static CAC only
3rd Parties required for:

- PSTN Connectivity
- Survivable Branch Appliance
- Mobile Clients
- Contact Centre
- IP Phones
Lync Server
Initiate Hold
Re-Invite
Session Established
200 OK
ACK
A=inactive - also called dead air on hold

No MoH stream available in Lync 2010
MoH only available with Attendant Console or
by enabling Lync Client Policy for Lync client, (local WAV
file will be played on hold)
Call on Hold Example

BRKUCC-2601
Cisco Public

Architectural Details Co-Located Med. Server
Mediation Server required to transcode between
proprietary RTaudio and G.711
Requires significant resources in OCS 2007 R2
separate server hardware required
OCS 2007 R2
Front-End
Med. Server
SIP Signalling
RTaudio
G.711
Lync 2010
Front-End Role
Med. Server Role
SIP
Signaling
Front-End
TLS 5061
Med.Server
TLS 5067
TCP 5068
Lync 2010 allows for Mediation Server

role be co-located on Front-End Server
Significant Caveats
(NOT MISSION CRITICAL)
G.711 with Media Bypass
Lync Server Logging Tool shows same invite in

trace 3 times (different port numbers)
BRKUCC-2601
Cisco Public
10

Architectural Details Media Bypass
Lync Server
Front-End
Lync Server
Med. Server
IP-PBX
Gateway
SIP Signalling
Media G.711
Direct between Lync Client and IP device
Signalling traffic remains through Mediation Server

Potential mid-call switch from Media Bypass to Transcoding via Mediation
Server
Media Bypass requires single media IP address
Invocation model valid for local entities (Details in SIP Trunking Chapter)
BRKUCC-2601
Cisco Public
11

Architectural Details Survivable Branch Appliance
Server Pool-2
Client 2
Registrar
SBA
User Services
Server Pool-1
Load Balancer
Communicator
Client-2 SBA
IP
WAN
Mediation
Server
Server Pool-1
Load Balancer
PSTN
Communicator
Client-1
During a WAN failure these User Services are unavailable:
Conferencing, Presence, Contact List, Response Group and Park
BRKUCC-2601
Cisco Public
12

Architectural Details Call Admission Control Off Path, Basic
Communicator
SBA
Client
IP
WAN
Mediation
Server
Server Pool
New Policy Server Role
for CAC
Load Balancer
Manage Bandwidth
between Logical Sites
PSTN
Communicator
Client
CAC Profile Type
WAN Link Per

Session Audio Limit
Available Audio
WAN Link per Session

Video Limit
Available Video
Optimized for Session

Count
(w/ Wide Band P2P)
60 kbps
RTAudio NB + FEC
Siren + FEC
RTAudio WB (no FEC)
350 kbps
RTVideo CIF (15fps)

RTVideo Pano (15fps)
Balanced
95 kbps
(Above plus)
RTAudio WB + FEC
G.711 (no FEC)
G.722 (no FEC)
600 kbps
(Above plus)
RTVideo VGA (30fps)
Optimized for Quality
165 kbps
1500 kbps
(All Above plus)

RTVideo HD (30fps)
BRKUCC-2601
(All Above plus)

G.711 + FEC
G.722 + FEC
Cisco Public
13

Call Admission Control Approaches Off Path, Basic
Call Control
Application
Static configuration in application

At each physical location, a logical site is defined and
bandwidth limit assigned to it
CAC decision is based on per-site BW counters kept by the
application
media
stream
Cannot handle non-trivial topologies (i.e., everything other

than traditional hub and spoke e.g. MPLS mesh)
CONS
Limited to a single call control application instance
Unaware of the underlying network (no idea of network traffic)

Unaware of other applications (such as 3rd party video)
Difficult to stop rogue applications (no authorisation for access to priority queues)
BRKUCC-2601
Cisco Public
14
Cisco Unified Communications ManagerCall Control

Call Admission Control Approaches On-path Cisco RSVP CAC
Based on a network-aware QoS aligned
protocol that:
follows the media path
Application
Call Control
Application
checks for actual network resources

along the path
QoS signalling
protocol
CAC decision driven by interaction

between call control, endpoints and QoS
Protocol
media
stream
Pros:
Very scalable and Handles any network topology
Checks for available bandwidth before setting up call or video
Can support different policies (i.e. one for audio and one for video)
Optimal use of resources (accurate tracking of path and bandwidth, quick reaction to network
failures/changes)
Preserves user experience (deterministic behaviour)
Works with multiple applications and instances interoperable
BRKUCC-2601
Cisco Public
15
Call Control Interoperability
BRKUCC-2601
Cisco Public
16
Interoperability with Microsoft Office

Communications Solutions
Direct SIP
Dual Call Control

Solutions
Single Call Control

Solutions
Two separate call

systems linked by
simple SIP trunking
Limited Support from

Microsoft
Dual
Forking
Seamless, Simple
Integration. Clear
functional split
Complex, requires
RCC
BRKUCC-2601
Remote Call
Control
(RCC)
Cisco UC
IntegrationTM
for Microsoft
Lync
Cisco Public
17
Direct SIP
BRKUCC-2601
Cisco Public
18
SIP Trunk Integration

OCS 2007 R2 vs. Lync 2010
OCS 2007 R2
Med. Server
Data-Centre
Gateway or
CUCM
OCS 2007 R2
Med. Server
OCS 2007 R2
Front End
BRKUCC-2601
One to one relationship based on Gateway or CUCM

IP Address
Multiple destinations require multiple Mediation
Server (i.e. redundancy)
Calls are hair pinned through the Mediation Server at the central location
WAN Bandwidth usage
Suboptimal media flows
Potentially High Delay causing voice quality issues
Potentially requires additional transcodes as the Mediation Server
supports G.711 ONLY
Cisco Public
19
SIP Trunk Integration - Lync 2010

Single Site Deployment CUCM and Lync local
Single Site
CUCM Node1 IP 10.1.1.10
SW MTP1 10.1.1.10
Single Server
HW MTP1 IP 10.1.1.11

SW MTP2 10.1.1.20
Med. Server
FE
HW MTP2 IP 10.1.1.21
Media Bypass requires a common IP address for signalling and media (optional 2 IP addresses one for
signalling and one for media)
For all media traffic to come from a single IP address a Media Termination Point (MTP) is required
Load sharing on multiple MTPs not supported (single IP address for media)
Each node in CUCM cluster has to be defined in Lync as Gateway, other common methods for SIP trunking
(DNS FQDN or SRV) would break the requirements of Media Bypass for IP addressing. CUCM to Lync load
sharing via Route-List and Route-Group
BRKUCC-2601
Support for Media By-Pass is still under investigation, Slides show preliminary results
Please consult www.cisco.com/go/interoperability for more recent and updated information
Cisco Public
20

Centralised Call Control Deployment CUCM and Lync centralised
Data-Centre
CUCM
Lync
Front End
MTP
MTP available
NOT utilised
BRKUCC-2601
Single Server
When Co-Located
Lync
Med. Server
Media Bypass does not solve the problem of hair pinning calls
Media Bypass mandatory requirement for single media IP
address, therefore requiring the insertion of an MTP causes hair
pinning
Distributed MTPs can not be utilised for media IP address
limitations (see prev. slide for static configuration example of
media IP address)
Cisco Public
21

Centralised Call Control Deployment CUCM and Lync centralised
Mediation Server Pool
SW MTP1 10.1.1.10
Front End

SW MTP1 10.1.1.20
Individual SIP-Trunks pointing to individual
nodes in the CUCM cluster each node a Gateway
In Lync Topology
Pseudo Gateway
branch01.suchandsuch.com
10.1.1.10
SBA with co-located
Mediation Server
Media Bypass required
BRKUCC-2601
To associate single gateway or SIP Trunk destination

with more than one Mediation Server or Mediation
Server Pool Pseudo DNS entries are
recommended by Microsoft
With the requirement of single Media IP address
even with Media Bypass all calls are hair pined
Utilisation of local Mediation Resources will not keep
media local based on single IP for media
requirement
Cisco Public
22

Considerations
Co-Location of Mediation Server only with Media Bypass and if Enterprise
Voice not mission critical
Media Bypass mandatory requirements still cause hair pinning of calls
Media Bypass does not allow for utilisation of distributed media resources
(MTP)
Media Bypass only recommended for local (LAN) interoperability to IPPBX or Gateway. Significant caveats in centralised call control
deployments
Media Bypass forces G.711 only sub-optimal for low bandwidth
environments, no wide band capabilities. Further requiring a transcoding
device to support other standard codecs such as G.729, G.726, iLBC,
iSAC, etc.
BRKUCC-2601
Cisco Public
23

Considerations continued
With SIP-trunk Integration Users will potential have different user
experiences
i.e. Music on Hold when Lync Clients initiates Hold, Cisco IP Phone will
not have Tone or Music on Hold, when Cisco IP Phone will initiate Hold
Lync Client will be streamed MoH (local MoH from client adds complexity
and increases operation to achieve corporate standard MoH on all devices
contrary to a unicast or multicast streamed solution)
Malicious Call Trace (MCID)
With Lync a user can flag a call as a malicious on Lync Client, Lync Client
Phone Edition or the Lync Attendant Console. This will case the CDR to
be marked for further processing by the Administrator (CID).
MCID on CUCM will initiate ISDN supplementary services signalling to the
PSTN providing Caller-ID even if the Calling Party ID was suppressed.
BRKUCC-2601
Cisco Public
24
Remote Call Control
BRKUCC-2601
Cisco Public
25
Remote Call Control Integration Lync 2010

Architecture
Active Directory
Cisco Unified
Communications
Manager
Licensing
Database
LDAP or LDAPS
synchronisation
Active Directory
Integration
User & Device

Database
AXL
SOAP
CTI
Manager
CTI
QBE
SIP Proxy, Registrar
CSTA CTI
Gateway
ACL
Security
SIP
BRKUCC-2601
CSTA
Stack
Microsoft Office
Communications
Server 2007
Cisco Unified
Presence Server
User & Configuration
Database
Enduser Bob
Enabled for RCC
Call
Control
Microsoft Office
Communicator
2007
Cisco Public
User & Configuration

Database
SIP Proxy Registrar
ACL
Security
Routing
CSTA tunnelled
through proprietary
SIP messaging
26

CSTA RCC & Presence Interworking
Alice answers the
Call either using
the phone or the
MOC client
Connected
Incoming Call
User: Bob
BRKUCC-2601
User: Alice
Cisco Unified
Communications
Manager
Cisco Unified
Presence Server
CTI QBE Alerting
Office
Communications
Server 2007
CSTA SIP
CTI QBE
Connected
CSTA
SIP
SIP Presence
CSTA
SIP
SIP
Ring!!!
CSTA SIP
Cisco Public
SIP Presence
Notification to
Watchers
27

Considerations
Long signalling path, based on codec interaction and/or suboptimal network path can cause
clipping at start of call. One way delay of more than 80 ms can cause media-stream setup times
in excess of 500 ms; clipping occurs and first spoke sentence gets cut off or distorted
Media Bypass required to keep media-stream local

Redundancyissue to be looked at from a server side prospective as well as local client
survivability for remote sites
User Experience, in particular for Mobile Users
BRKUCC-2601
Cisco Public
28
Client Integration
BRKUCC-2601
Cisco Public
29
Types of Client Integration

Cisco Unified Communication Integration for Microsoft Office
Communicator (CUCIMOC)
Cisco Unified Communication Integration for Microsoft Lync (CUCILYNC)
Cisco Unified Personal Communicator, Cisco Webex Connect
Standards based collaboration
Feature Rich Integration into Microsoft Office, Microsoft
Sharepoint,
Cisco Unified Communication Widget Click2Call
BRKUCC-2601
Cisco Public
30
Cisco UC Integration for Microsoft Office

Communicator (CUCIMOC)
CUCIMOC provides customers a
comprehensive integration of Microsoft
IM & Presence with Cisco UC
Some of CUCIMOC shipping features.
Soft phone & Desk phone Control
Standards-based wide-band audio
Standards-Based High-definition video (720p)
Phone presence displayed in Microsoft
Office Communicator
Click to call from Office, browsers

Integrated web collaboration
Visual Voicemail
Survivable Remote Site Telephony
Windows 7 Support
BRKUCC-2601
Cisco Public
31
Cisco UC Integration for Microsoft Office

Communicator User Interface enhancements
New enhanced conversation
control pane
New pane design
Drag Icon integrated into panel
styling, drop target is now full icon
pane
BRKUCC-2601
Cisco Public
32
Cisco UC Integration for Microsoft Lync

2010(CUCILYNC)
Released in Dec 2010
UC Integration 8.5 introduces Microsoft Lync
2010 support.
Cisco participated in the Wave 14 TAP
program to develop the Cisco UC integration
for the Lync 2010 client.
Integration detects version of Microsoft

product and displays communication pane in
a style to match Microsoft product
All CUCIMOC 8 features are available in the
Lync 2010 client.
The Microsoft client shown on this slide is the Lync Release candidate which is publicly downloadable from Microsoft.com
BRKUCC-2601
Cisco Public
33
Cisco UC Integration for Microsoft Lync 2010

Common Product Questions
Microsoft Office Communicator and Lync both have a number of APIs for 3rd
party integration.
Microsoft have removed the Web based tab area from the Lync 2010 client
CUCIMOC 7.1 WAS a tab based integration to office communicator

CUCIMOC 8.0 and 8.5 are NOT tab based integrations and are not affected by
Microsoft Tab API change.
CUCIMOC 7.1
(TAB Based)
CUCIMOC 8.0
(NOT TAB Based)
CUCIMOC 8.5
(NOT TAB Based)
Joint Statement of Unified Communications Interoperability from Cisco and Microsoft

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=78814f28-2df5-4cff-a166-73622c7830bb&displaylang=en
BRKUCC-2601
Cisco Public
34

Single Sign On (SSO)
By logging into their desktop users can seamlessly login
to the integration
Login sequence
No additional requirement to provide a username &

password for UC Manager / LDAP directory
End user authentication is based on windows desktop
login to a domain
Designed around Active Directory with Kerberos

environment to achieve Windows desktop SSO
Requires upgrade to UC Manager 8.5 & CUCIMOC 8.5
The solution requires the ForgeRock OpenAM Server 9.x
BRKUCC-2601
Cisco Public
Following Communicator
login, Integration login process
automatically initiated
35

Single Sign On - Architecture
Active Directory
OpenAM Server
Key Distribution
Centre
Windows
Domain Login
using Kerberos
SSO
Session
SPNEGO
Token
CUCIMOC
CSF 8.5
JTAPI
SSO
Session
SSO
Session
TGT - Ticket Granting Ticket

CTI
Manager
Policy
&
Identity
manager
UC Manager 8.5
Windows Desktop
BRKUCC-2601
UDS
- ST - Service Ticket
Cisco Public
36
Cisco Unified Personal Communicator

Microsoft Integration Office,
Sharepoint,
BRKUCC-2601
Cisco Public
37
Cisco Unified Personal Communicator 8.5
True enterprise class IM client
Softphone/Video
CUP High Availability (HA) Support
Meeting Escalation
Click to Call
Microsoft Presence Integration
Microsoft Office 2010 Support
Basic VDI Support

BRKUCC-2601
Cisco Public
38

Microsoft Office 2007 Integration
Microsoft SharePoint 2007
Cisco Presence Light-Ups
W
or
d
Cisco Click to IM/Call
Microsoft Outlook 2007

BRKUCC-2601
Cisco Public
39

Microsoft Outlook 2010
Cisco Presence Light-ups

BRKUCC-2601

Cisco Public
40
Cisco Webex Connect

Cisco Webex Connect 6.7
Presence, IM, Click to X integration
with Outlook and Office 2007/2010
and with Sharepoint
BRKUCC-2601
Cisco Public
41

Microsoft Word 2010
Cisco Presence Light-Ups

BRKUCC-2601
Cisco Public
42
Cisco Unified Personal Communicator &

CUCIMOC/LYNC Click to Call 8.0 Functionality
Inclusion
Same Click to Call experience on Microsoft Office applications
with CUPC
New ribbon button in Microsoft Word, Excel & PowerPoint
BRKUCC-2601
Cisco Public
43
Presence and IM Interoperability
BRKUCC-2601
Cisco Public
44

Inter Domain Federation
Pseudo Intra Domain Federation
Definition of Terms:
Inter Domain Federation with Cisco Unified Presence
allows the exchange of Instant Messaging (IM) and
Presence utilising the SIP/SIMPLE or the XMPP Standard
between Domains. A Domain in this context usually refers
to an organisation.
BRKUCC-2601
Cisco Public
45

Inter Domain Federation - Overview
Organisation
Alpha.com
Organisation
Beta.com
Lync Server
Edge
CUPS
ASA55xx
Lync Server
Public
Internet
DMZ
CUPC
Lync Client
In this example Users in both organisations can

add federated contacts to their respective
clients. Cisco Unified Presence provides
federations services independent of protocol
(SIP/SIMPLE or XMPP) or type of client (Cisco
or 3rd party).
BRKUCC-2601
Cisco Public
46

Inter Domain Federation Microsoft
Lync Server 2010 Supports SIP/SIMPLE Intra Domain Federation

OCS 2007 R2 XMPP Gateway provides XMPP Federation
SIP/SIMPLE Federation fully tested and recommended
Subset of MOC presence
states federated across interdomain link
OCS maps MOC states to
Federated states when
sharing presence over interdomain link
Cisco user only see subset of
MOC presence states
BRKUCC-2601
Cisco Public
47

Pseudo Intra Domain Federation - Overview
subsidary1.alpha.com
Organisation
alpha.com
CUPS
subsidary2.alpha.com
Lync Server
Lync Client
For environments where the Cisco and the Microsoft solutions are
being used, federation within the enterprise can be achieved by
utilising sub-domains.
http://docwiki.cisco.com/wiki/Cisco_Unified_Presence%2C_Release_7.x_-_Overview_of_this_Integration#Federation_and_Subdomains
BRKUCC-2601
Cisco Public
48

Pseudo Intra Domain Federation Considerations
Federated Contacts can not be added from directory search
Contact-Lists can not automatically be migrated between the
different presence domains
Presence and IM different from email address
Basic Presence Information only
..Stay Tuned..
BRKUCC-2601
Cisco Public
49
Voice Messaging / Unified Messaging
BRKUCC-2601
Cisco Public
50
Voice Messaging / Unified Messaging

Microsoft Exchange 2007 / 2010
Unified Messaging
SIP-Trunk Integration
Version dependent separate Software for Message
Waiting Indicator (Exchange 2007)
Cisco Unity Connection

Voice Mail only or Unified Messaging (Exchange)
Fully Integrated Single Inbox User Experience
Loosely coupled with Active Directory & Exchange
Support for Exchange 2003, 2007 and 2010
BRKUCC-2601
Cisco Public
51
Unified vs Integrated Messaging
BRKUCC-2601
Unified Messaging
Integrated Messaging
One inbox for email,
Separate inbox for email
vmail and fax
and voicemail
Cisco Public
52
Cisco Unified Communications Manager

and Microsoft Exchange 2007 & 2010
Cisco Communication Manager 5.x or higher can directly integrate with
Microsoft Exchange 2007 or 2010 utilising the SIP trunk interface
To provide Message Waiting Functionality a 3rd party product has to be
installed with Exchange 2007 which doesnt natively support this feature
Cisco Unified
Communications Manager
Microsoft Exchange 2007/2010

Unified Messaging
SIP Trunk
Microsoft Office
Outlook
BRKUCC-2601
Cisco Public
53
Unity Connection 8.5 Unified Messaging

Dual-Message Store Architecture
Cisco Clients
TUI/VUI/Midlet
Voice Mail System
Ucxn APIs
Email System
Exchange
2003
Exchange
2007 CAS
Cisco
Thick Clients
Cisco
Thin Clients
Cisco Unity Connection

8.5
Exchange
2010 CAS
Email Clients
Mobile Clients
EX APIs
Exchange
Servers 2007
Web Client (OWA)
Exchange
Servers 2010
Thick Client (Outlook)
Dual-Message Store Architecture

Message Synchronisation!
Web APIs used NOT MAPI!
Exchange Web Services Exchange 2007, 2010
WebDav Exchange 2003
BRKUCC-2601
Cisco Public
54
Unity Connection 8.5

Message Synchronisation Architecture
BRKUCC-2601
Cisco Public
55
Unity Connection 8.5

Message Synchronisation Behaviour
Unity Connection 8.5 = Authoritative Message Store
Messages pushed from Unity Connection
Deleted from Microsoft Exchange, Deleted from Unity Connection
Message in Microsoft Exchange, not in Unity Connection is

pushed to Unity Connection (e.g. moved to inbox from .pst folder)
Message properties synchronised (read, deleted, priority, subject)
Message sensitivity and security initially synchronised

Message Waiting Indicator (WMI) is synchronised
BRKUCC-2601
Cisco Public
56

Infrastructure Requirements
Microsoft Active Directory
Needed for Unified Messaging Service Account authentication

No Active Directory schema extensions required!
Microsoft Exchange Server(s)
Client Access Server (CAS) Exchange 2007, 2010

CAS Arrays supported
Database Availability Groups (DAG) supported on backend
Exchange 2003 Server(s)
Customer supported Storage Area Networks (SAN) supported
Optional Active Directory Integration
For user import, synchronisation, and authentication

Optional Certificate Authority
BRKUCC-2601
Cisco Public
57

Infrastructure Requirements
Location of Exchange Servers
Exchange
Network
Unity
Connection
Active/Active
Cluster
Exchange Client
Access Server
CUCM
Cluster
CUCM
Cluster
Main Office or
Primary DC
Satellite Office
BRKUCC-2601
MPLS
Branch Office or
DR DC
Unity Connection 8.5 can be local or placed

across geographical boundaries from the
Exchange servers its synchronising with
Cisco Public
58

Permissions Model
Unity Connection Accounts
Unified Messaging Service Account(s)
Exchange 2010
ApplicationImpersonation role on Mailbox servers
Exchange 2007
ms-Exch-EPI-Impersonation, ms-Exch-EPI-May-Impersonate,
Receive-As on Mailbox servers
Exchange 2003
Administer Information Store, Send As, Receive As
Directory Service Account (optional)

Active Directory
Minimum permissions set to "read" all user objects in the search base
BRKUCC-2601
Cisco Public
59
Contact Centre
BRKUCC-2601
Cisco Public
60
The Microsoft Windows Operating System

Server platform is a fundamental part of the UCCE/UCCH
Contact Centre solutions.
Server platform used for Quality Management, Work Force

Management, Reporting etc.
Cisco applications running on the desktop platform, from
Windows XP through to Windows 7.
BRKUCC-2601
Cisco Public
61
Microsoft CRM Contact Centre Integration

Integrated Microsoft CRM
application with Cisco IP
Telephony and/or Contact Centre
Solutions
Enables the following customer
service capabilities:
Click to dial outbound calling
Screen Pops (incoming or outgoing)
Call Tracking &
Call Duration tracking
Call information capture
Call association
BRKUCC-2601
Cisco Public
62
Combining Enterprise Presence and Contact

Centre
Extending the boundaries
Agent at the Contact

Centre receives a
customer call that
requires escalation to
an expert
BRKUCC-2601
Agent transfers to a
group of skilled experts
and using Presence,
available experts will be
automatically offered
the call
Using CMOC, an
Expert answers the
call offer via Instant
Messaging in
addition to receiving
caller information
Cisco Public
Expert then takes the call

on his or her IP or softphone/CMOC
63
Networking
BRKUCC-2601
Cisco Public
64
The Network Platform

Cisco ISRs and Catalyst Switches provide secure service delivery
for Microsoft Applications
Security, QoS, PSTN/PBX/ IP gateway, echo cancellation, and more for
business-class, real-time communications and collaboration
Interconnect with service providers and the public network
Cisco Voice Gateways

Cisco ISRs are used for connectivity between Microsoft Office
Communications Server 2007or Microsoft Lync 2010* and the PSTN
Interconnect with service providers and the public network
*Certification of Cisco ISRs as Gateway Devices for Microsoft Lync 2010 is currently underway
BRKUCC-2601
Cisco Public
65
Cisco Integrated Service Router Gateway

Interoperability with OCS 2007 / Lync 2010*
Transcoded Call Flow (not Media Bypass)
MOC 2007
Client
Microsoft OCS
Mediation Server
Cisco ISR/IOS
Gateway
PSTN
SIP
RTAudio Media
SIP
RTAudio Media
SIP over TCP or TLS Signalling

G711u or G711a Media
ISDN q931 Signalling

G711 Media
Features include:
Basic call, Call Transfer supervised, Call Transfer blind, Call Forward
(All, Busy and No Answer), Three-way
Conference, DTMF tones, Caller ID functionality between Microsoft Office Communicator (MOC)
and PSTN
*Certification of Cisco ISRs as Gateway Devices for Microsoft Lync 2010 is currently underway
BRKUCC-2601
Session ID
Cisco Public
66
In closing
BRKUCC-2601
Cisco Public
67
Cisco Unified Communications with Microsoft
BRKUCC-2601
Cisco
Call Control with
Microsoft
Cisco
Collaboration with
Microsoft
Cisco
Presence with
Microsoft
Cisco
Messaging with
Microsoft
Cisco
Contact Centre
with Microsoft
Cisco
Network with
Microsoft
Cisco Public
68
Q&A
BRKUCC-2601
Cisco Public
69
Complete Your Online Session Evaluation

Complete your session evaluation:
Directly from your mobile device by visiting
www.ciscoliveaustralia.com/mobile and login
by entering your badge ID (located on the
front of your badge)
Visit one of the Cisco Live internet stations
located throughout the venue
Open a browser on your own computer to
access the Cisco Live onsite portal
BRKUCC-2601
Cisco Public
70

Unified Communications Integration Into Microsoft Environments

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Unified Communications Integration Into Microsoft Environments

Enviado por

Direitos autorais:

Formatos disponíveis

Unified Communications Integration into

Cisco Unified Communications with Microsoft

2011 Cisco and/or its affiliates. All rights reserved.

Whats New in the Microsoft Unified

2011 Cisco and/or its affiliates. All rights reserved.

Microsoft Unified Communications Solution

Lync 2010 considerations

2011 Cisco and/or its affiliates. All rights reserved.

Microsoft Unified Communications Solution

Microsoft Unified Communications Solution

SIP-Invite Call-ID 1234

SIP-Invite Call-ID 1234

SIP 200 OK Call-ID 1234

SIP 200 OK Call-ID 1234

SIP ACK Call-ID 1234

SIP ACK Call-ID 1234

Lync Server 2010 is a SIP Proxy

B2BUA creates to separate sessions, full control on

2011 Cisco and/or its affiliates. All rights reserved.

SIP-Invite Call-ID 1234

SIP-Invite Call-ID 5678

SIP 200 OK Call-ID 1234

SIP 200 OK Call-ID 5678

SIP ACK Call-ID 1234

SIP ACK Call-ID 5678

Microsoft Unified Communications Solution

2011 Cisco and/or its affiliates. All rights reserved.

New Features and Functionality* in Lync 2010

Telephony Features (MCID, Call Park etc.)

2011 Cisco and/or its affiliates. All rights reserved.

Lync 2010 Considerations

3rd Parties required for:

A=inactive - also called dead air on hold

Call on Hold Example

2011 Cisco and/or its affiliates. All rights reserved.

Microsoft Unified Communications Solution

Lync 2010 allows for Mediation Server

G.711 with Media Bypass

Lync Server Logging Tool shows same invite in

2011 Cisco and/or its affiliates. All rights reserved.

Microsoft Unified Communications Solution

Signalling traffic remains through Mediation Server

2011 Cisco and/or its affiliates. All rights reserved.

Microsoft Unified Communications Solution

During a WAN failure these User Services are unavailable:

Conferencing, Presence, Contact List, Response Group and Park

2011 Cisco and/or its affiliates. All rights reserved.

Microsoft Unified Communications Solution

CAC Profile Type

WAN Link Per

WAN Link per Session

Optimized for Session

RTVideo CIF (15fps)

Optimized for Quality

(All Above plus)

(All Above plus)

Microsoft Unified Communications Solution

Static configuration in application

Cannot handle non-trivial topologies (i.e., everything other

Unaware of the underlying network (no idea of network traffic)

2011 Cisco and/or its affiliates. All rights reserved.

Cisco Unified Communications ManagerCall Control

follows the media path

checks for actual network resources