This presentation will discuss what integration technologies consist of. We will also discuss the Cisco Collaboration architecture, call flow, and Jabber use case.

1. New aspects of Cisco
UC Interoperability
#CiscoPlus

2. What is integration?
• Is my home phone integrated with your home phone?
• Is my corporate email system federated with yours?
• Does integration imply connecting two of the same type
of system or different systems?
• The objective: Let me collaborate with
Anyone Anywhere
#CiscoPlusCA

3. Cisco Collaboration Architecture
Devices Desktop Mobile In-Room
Provisioning
Federation
Conferencing Customer Care
Collaboration Enterprise Social Software IP Communications
Applications
Encryption
Maintenance
Messaging Telepresence
Client Services Medianet Services
Client Services Framework Interface
Lightweight APIs
Administration
AAA
COMMUNICATION
Presence / Location Real-time Messaging Metadata Tagging
Policy
Session Mgmt Real-time Data Sharing Social Graphing
Collaboration
Services
Operations
Scheduling and
Authoring Semantic Processing
Calendaring
Identity
Workflow Recording/Playback Search
CONTENT
Management Services
Transcoding Transrating Transcribing
Security Services
Medianet Services
Auto-Discovery Auto-Configuration Resource Control
Network Services Transport Signaling QoS
#CiscoPlusCA

4. Session Management
#CiscoPlusCA

5. What is a Session Management Edition cluster ?
CUBE
CUBE
CUBE
H323 Trunk
MGCP Trunk
SIP Trunk
A CUCM cluster and SME cluster use exactly the same software
A CUCM cluster is typically used to register 10,000s of Phones
An SME cluster is typically used as a platform for Trunk and Dial Plan aggregation
Both CUCM and SME support Voice, Video and Encrypted calls
Support for SME deployments was introduced with UC version 7.1(2)
UC version 8.5 introduces a number of features that enhance SME functionality :
Improved SIP Trunk and H323 Inter Cluster Trunk functionality
Improved through-cluster routing
SIP Normalization and Transparency scripts
#CiscoPlusCA

6. Why deploy Session Management Edition ?
An SME cluster at the core of your network allows you to flexibly manage your UC system as it
grows and changes…….
PSTN
Voicemail Conferencing
CUBE CUBE
System System
H323
Unified CM MGCP
Session SIP
Management
Edition Cluster
CUCM PBXs/ CUCM CUCM PBXs with PBXs with CUCM/PBX
Clusters with Clusters with Clusters with MGCP QSIG MGCP Q931 with SIP QSIG
H323 QSIG SIP Trunks to H323 Trunks to Trunks to SME Gateway Trunks to SME
Trunks to SME SME SME Trunks
Leaf Unified CM Clusters/ Leaf UC Systems
An SME cluster can interconnect 1000’s of UC systems using SIP, H323, or MGCP Trunks
SME allows you to reduce UC system complexity by centralizing your dial plan and call
routing rules in the SME cluster which in turn allows you to simplify the dial plan and
management of the connected UC systems
#CiscoPlusCA

7. Reasons for deploying an SME cluster
PSTN
Voicemail CUBE CUBE Conferencing
System System
H323
Unified CM MGCP
Session SIP
Management
Edition Cluster
PBXs/ CUCM CUCM
CUCM Clusters with PBXs with PBXs with MGCP CUCM/PBXs with
Clusters with Clusters with MGCPTrunks to Q931 Gateway SIP QSIG Trunks
SIP Trunks to H323 Annex M1
H323 QSIG SME Trunks to SME
SME Trunks to SME
Trunks to SME
A centralized Dial Plan in SME allows you to :
Globalize and Normalize the called and calling numbers used by all Leaf systems
Manage overlapping number ranges in Leaf systems
Configure “find me” call routing using Route List and Route Groups
Re-route calls via the PSTN when the device cannot be reached via and IP path
SME Mobility features allow you to offer Single Number Reach functionality to devices on 3rd
Party UC systems
SME Normalization scripts allow you to modify any inbound or outbound SIP message and
SDP body content – simplifying interoperability with 3rd party UC systems
#CiscoPlusCA

8. SME cluster - PBX aggregation
SME migration to a CUCM cluster
PSTN
CUBE CUBE
PSTN PSTN PSTN PSTN PSTN PSTN
Phase 1 – PBX Phase 2 – Centralized IP
Aggregation PSTN
PSTN
PSTN
CUBE CUBE
CUBE CUBE
Phase 3 – PBX Phase 4 – CUCM cluster
decommissioning #CiscoPlusCA

9. Extend and Connect Architecture & Call Flow
Jabber Use Case CUCM
CTI
Cisco Jabber
client
Enterprise DN: 3000
CSF/Jabber device
DVO-Enabled
Office Phone
3000 Remote Destination:
4155551212
Remote Destination:
9195551313
PSTN
Home Phone
4155551212
Cisco User PBX Phone 3rd Party
9196661313
PBX
CTI applications have limited monitoring and call control capabilities for remote
destinations
#CiscoPlusCA

10. Extend and Connect Architecture & Call Flow
CTI Remote Device Use Case CUCM
CTI
Enterprise DN: 3000
CTI Remote Device
3rd-Party DVO-Enabled
client
Office Phone
3000 Remote Destination:
4155551212
Remote Destination:
9195551313
PSTN
Cisco User Home Phone
4155551212
PBX Phone 3rd Party
9195551313
PBX
CTI applications have limited monitoring and call control capabilities for remote
destinations
#CiscoPlusCA

11. MS Lync Integration
#CiscoPlusCA

12. Different options exist – How to choose the right one?
Blended: Customer
Full Full
Microsoft
Microsoft
Desktop +
Cisco Deployment
UC Solution UC Solution
Cisco Phone scenario
UC Gateway Cisco UC Integration for MOC Cisco Jabber
or Lync
#CiscoPlusCA
13

13. Cisco Unified Clients…
Cisco Soft Client Architecture
Cisco Cisco UC Cisco UC Cisco Developer &
Cisco Webex
Unified Personal Integration Integration Quad Phone Integrator SDK
Connect
Communicator for Microsoft for RTX
Cisco Unified
Infrastructure
Services
#CiscoPlusCA

14. Cisco Jabber
Introduction
Cisco Enterprise
Call Control Video & Desktop
Instant Messaging Share Engine
Application
Jabber Technology Integration
(MS Office) Cisco Secure
Remote Access
Conferencing
Cisco Unity
Cisco Jabber Webex Connection
& CuciLync Collaboration Voice Messaging
Environment
#CiscoPlusCA

15. Cisco BYOD Architecture
One network, One policy, Unified Management
Good
#CiscoPlusCA

16. Different options exist – How to choose the right one?
Blended: Customer
Full Full
Microsoft
Microsoft
Desktop +
Cisco Deployment
UC Solution UC Solution
Cisco Phone scenario
UC Gateway Cisco UC Integration for MOC Cisco Jabber
or Lync
#CiscoPlusCA
17

17. Cisco Collaboration Architecture
Devices Desktop Mobile In-Room
Provisioning
Federation
Conferencing Customer Care
Collaboration Enterprise Social Software IP Communications
Applications
Encryption
Maintenance
Messaging Telepresence
Client Services Medianet Services
Client Services Framework Interface
Lightweight APIs
Administration
AAA
COMMUNICATION
Presence / Location Real-time Messaging Metadata Tagging
Policy
Session Mgmt Real-time Data Sharing Social Graphing
Collaboration
Services
Operations
Scheduling and
Authoring Semantic Processing
Calendaring
Identity
Workflow Recording/Playback Search
CONTENT
Management Services
Transcoding Transrating Transcribing
Security Services
Medianet Services
Auto-Discovery Auto-Configuration Resource Control
Network Services Transport Signaling QoS
#CiscoPlusCA

18. Cisco UC Integration for Microsoft
What is the Cisco Integration for Microsoft
• The UC Integration provides a Cisco UC client with controls exposed
with the Microsoft client interface
• Provides phone presence to OCS/Lync
• Supports Microsoft Office Communicator R2 and Microsoft Lync 2010
• Runs on Microsoft Windows XP SP3, Windows Vista 32/64bit and
Windows 7 32/64bit
• Provides soft phone audio and video and desk phone control using UC
manager call control
• Visual voicemail with Cisco Unity or Unity Connection
• Desktop collaboration using Cisco MeetingPlace and Webex
• Calling from Microsoft Office, Internet explorer and other applications
#CiscoPlusCA

19. Cisco UC Integration™ for Microsoft Lync
Microsoft Client
Microsoft Office Communicator
Microsoft Lync (shown)
User Experience
Simply drag or right
click a contact to
start a voice, video
or collaboration
session
Conversation
Voice, Video and
Conference calling
and in Call Controls
Cisco Communication Panel
Voicemail, Communications History,
Soft phone / Desk phone control
Options & Dial #CiscoPlusCA
pad

20. Cisco UC Integration™ for Microsoft Lync
High Definition Video for Rich Interactions
• Video calls – both in Softphone and Desk Phone mode
• Point to Point & Multipoint calls
• High quality, standards-based H.264 video
• CIF, VGA and HD resolutions supported
• Interoperable with Cisco and 3rd party video solutions
• Leverages CUCM CAC to manage video traffic on the WAN
#CiscoPlusCA

21. Cisco UC Integration™ for Microsoft Lync
Phone Presence
• Availability in Lync is updated to reflect Softphone/Hardphone state
• Shows your current Softphone/Hardphone state to your contacts
• Users showed “On the phone” also for calls to Video Bridge, VC stations or
any other video system (Cisco or Third Party)
#CiscoPlusCA

22. Microsoft & Cisco Interoperability
Use cases and Scenarios – SIP-Trunk / Direct-SIP Audio
OCS 2007 / Lync 2010 (no media bypass)
Front-End Mediation CUCM
Lync Clients Pool Server Pool
RTaudio G.711
OCS 2007 / Lync 2010 (no media bypass), none G.711 on IP-PBX
Front-End Mediation CUCM
Pool Server Pool Transcoder
Lync Clients
RTaudio G.711 G.729/iLBC
• The two call flows above show the signaling and media paths in a SIP-trunk
interoperability scenario.
• Lync Mediation Server ONLY supports G.711, requires additional transcoding resource if
any other codec is used in such an scenario.
With CUCM 8.x and above a MTP is not required in this configuration.
#CiscoPlusCA

23. Microsoft & Cisco Interoperability
Use cases and Scenarios – SIP-Trunk / Direct-SIP Audio
Lync 2010 (with media bypass)
Front-End Mediation CUCM
Lync Clients Pool Server Pool
G.711 G.711
MTP
• With the introduction of Media Bypass in Lync 2010 the Lync client can initiate direct
G.711 not requiring media to be transcoded in the Mediation Server.
• Signaling still has to flow via the Mediation Server.
• Media Bypass mandatorily requires all media to come from a single IP address.
Which is the reason why a MTP has to be inserted into this scenario.
#CiscoPlusCA

24. Video Integration with MS
#CiscoPlusCA

25. Microsoft Lync 2010 - video capabilities summary
 Point to Point video call:
o Still uses the RTVideo codec as default - CIF, VGA and HD (with Quad Core CPU) as
possible resolutions
o Single codec supported for interoperability with standard VC is H263 (max resolution
is CIF@15fps)
 Multi-Point video call using Internal A/V MCU:
o Support RTVideo codec only
o Support CIF and VGA as resolutions (No HD)
o Support Voice Activated Switching only (no Continuous Presence)
o Utilize Microsoft CCCP as protocol to create, extend and manage the
Multi-party Video Conference
 Content Sharing:
o Use Microsoft specific solution both for Point to Point and Multi-Point calls (no
BFCP support)
#CiscoPlusCA

26. VCS and B2BUA Service
Introduction
VCS X7.0 introduces the concept of Back to Back User Agent (B2BUA):
 Service running on “Lync-OCS Gateway” VCS
 Keep standard based and OCS / Lync signalling separate
 Recommended scenario (Old way still supported in X7.x, not in X8.x)
 Simplified configuration (one menu with all the options listed together)
 Publishing VCS Presence into OCS/Lync is supported and strongly
recommended to have a full User Experience
 Allows interoperability with OCS/Lync Clients connected from Internet through
Microsoft Edge Server
 AMG is supported and improved in terms of features support (Call Transfer, Hold
and Multi-way)
 End to End encryption for Media and Signaling
#CiscoPlusCA

27. Lync / VCS Deployment Guide
http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/
Cisco_VCS_Microsoft_OCS_2007_R2_and_Lync_2010_Deployment_Guide_X7-­‐1.pdf
#CiscoPlusCA

28. UC Gateway Solution for MS Video Interop
UC Gateway
Video Advanced Media
Communication Gateway (AMG)
Server (VCS)
Scalable and resilient Transcodes Microsoft
Interoperability with RTV to HD or VGA
Microsoft OCS 2007 R2 standard compliant
and Lync 2010 video codec
#CiscoPlusCA

29. MS Office Integration
#CiscoPlusCA

30. Microsoft & Cisco Interoperability
Microsoft Applications enabled with Cisco Collaboration
Microsoft SharePoint 2007
Cisco Presence Light-Ups
W
or
d
Cisco Click to IM/Call
Microsoft Outlook 2007
#CiscoPlusCA

31. Microsoft & Cisco Interoperability
d in
Microsoft Applications enabled with Cisco Collaboration Supporte 0(3)
CUPC 8.
Microsoft Outlook 2010
Cisco Presence Light-ups Cisco Click to IM/Call
#CiscoPlusCA

32. Cisco Jabber
#CiscoPlusCA

33. Introducing Cisco Jabber for Windows
Cisco Jabber is our new UC and Collaboration client:
 User Interface and experience built to be
highly intuitive.
 Full Office integration
 Standards based Interoperability
 Based on the second generation CSF, optimized in
terms of memory and resource utilization
 Range of extensibility points and application
integrations
 Also available for Mac
#CiscoPlusCA

34. Voice & Video Call Control
Jabber for Windows provides two call control options
 Enterprise Call control (ECC)
o ECC allows a customer to integrate Jabber for
Windows with Unified Communications Manager.
o ECC provides control of a Cisco desktop phone as
well as soft phone operation.
o URI dialling planned with CUCM 9.0
 Cloud Call Control [subject to change]
o Only available in cloud deployment
o Provides computer to computer calling between two
users of the Webex cloud
#CiscoPlusCA

35. Voice & Video Call Control
Desk phone Soft phone
Control Operation
• Users can select mode of operation using the system tray icon.
• Drop down list will provide a list of hardware/software associated to user.
• Users can be configured to use just desk phone, just soft phone or both.
#CiscoPlusCA

36. The Cisco Precision Video Engine
• Precision Video Engine is a H.264 AVC
software library designed to handle voice
and video related tasks
• This library is based on the Video Engine
used in the Cisco “Movi” product (*)
• Provides full HD interoperability between
Jabber desktop clients and any standard based VC systems
• PVE also provides audio codecs
G.711a/u, G.722, G.729a, iLBC (and subject to change AAC-LD, G.722.1)
• PVE supports frame size QCIF to 720p based on attached camera. Note: HD 720p will
be possible using DUAL CORE CPU!
(*) Note – “Movi” has been recently renamed Cisco Jabber Video for TelePresence
#CiscoPlusCA

37. Desktop Sharing
• Video Desktop Share is based on the BFCP standard.
• Video Desktop Share allow you to share your desktop not only with other
Jabber clients but also Telepresence Systems and Rooms...how many
customer are waiting for this?
• CUCM 8.6.x needed for BFCP support
• Point to Point and Multipoint (MCU based) scenario are possible
Other Jabber
Clients
Personal Telepresence
Systems
Telepresence
Rooms
#CiscoPlusCA

38. Desktop Sharing
Some Screen shot from Tobias Lab.....
#CiscoPlusCA

39. Searching for Contacts
Search and
dial bar
Auto detect AD/LDAP
• Client (on premise)
provides search
Recommended pre 8.6(2)
Recent across multiple contact
Contacts
Returned record sources.
UC Manager UDS Service
• Clientuses premise)
(on predictive
Recommend for 8.6(2) +
search to refine resolution
Local Contacts list as you type.
Returned
[subject to change] Webex Corporate
Directory (Cloud)
Directory
Contacts
Returned
#CiscoPlusCA

40. Solution Summary
• Suggested approach for customer, advantages with Cisco standards
based IPT/Video (LCS/OCS can be easily migrated to Jabber)
 Full Office integration
• Designed with the goal to optimize resource utilization (CSF2G)
• Supports standard based audio and video codecs
• High Definition 720p (with a Dual Core CPU), also for calls to Video
Conference systems
• BFCP Desktop Sharing with any standard Video Device
#CiscoPlusCA

41. Q&A
#CiscoPlusCA

42. We value your feedback.
Please be sure to complete the Evaluation Form for
this session.
Access today’s presentations at cisco.com/ca/plus
Follow @CiscoCanada and join the #CiscoPlusCA conversation
#CiscoPlus