Student Guide PDF

Designing and
Implementing Cisco
Jabber
(DICJ)
V9.0
Student Guide
Fast Lane APAC

1/5/2013
Student Guide
2 Designing and Implementing Cisco Jabber Table Of Contents
Table of Contents
Introduction to Cisco Unified Collaboration................................................................................ 1-1
Cisco Collaboration Overview ....................................................................................................... 1-3
Cisco Jabber Portfolio...................................................................................................................1-11
Cisco Unified Client Services Framework Architecture...............................................................1-35
Cisco Jabber For Windows............................................................................................................ 2-1
Deploying Cisco Jabber for Windows............................................................................................ 2-3
Install and Configure Cisco Jabber for Windows ........................................................................ 2-35
Designing Cisco IM and Presence................................................................................................ 2-65
Integrating Cisco Unified CM and Cisco IM and Presence ......................................................... 2-97
Set Up Cisco Jabber On-Premises Deployments with Cisco UCM Version 9.x ....................... 2-117
Jabber for Everyone.................................................................................................................... 2-165
Cisco Unified IM and Presence Multi-Node deployments ........................................................ 2-179
Instant Messaging Compliance ,Logging and Chat Rooms........................................................2-197
Cisco Jabber For Mobile................................................................................................................ 3-1
Designing Cisco Jabber for Mobile Solution ................................................................................. 3-3
Provisioning Cisco Jabber for Mobile Cisco Unified Widgets .................................................... 3-53

Course Agenda
Day 1 Day 2 Day 3
Introduction to Cisco Unified

Cisco Jabber For Windows Cisco Jabber For Mobile
Collaboration
Lunch
Cisco Jabber For Windows Cisco Jabber For Windows Cisco Jabber For Mobile
www.flane.com.au

Module 1
Introduction to Cisco Unified

Collabortaion
Module Outlines
This Module covers the following topics:
Cisco Collaboration Overview
Cisco Jabber Portfolio:
Cisco Jabber for Windows
Cisco Jabber for iPhone
Cisco Jabber IM for iPhone
Cisco Jabber for Android
Cisco Jabber for iPad
Cisco Unified Client Services Framework Architecture
1-2 Designing and Implementing Cisco Jabber Introduction to Cisco Unified Collaboration
Lesson 1
Cisco Collaboration
Overview
POST PC Era
6 www.flane.com.au
The enterprise world faces a fundamental shift with the arrival of the post-PC era. Employees in
organizations exploring the bring-your-own-device (BYOD) movement can now work from
anywhere, on any device. But what kinds of challenges--and opportunities--does BYOD present
to both end-users and IT, and how can companies address them?
The New Collaboration Experience
7 www.flane.com.au
Collaboration is emerging as the next breakthrough source of effectiveness and innovation for
business. Multiple trends are converging to create a profound transition in the way people interact
and do business, including:
Mobile, dispersed workforces

Proliferation of video communication
New delivery and consumption models
Use of social software at work
But how do you go about embracing these important changes without introducing greater risk and
complexity?
Cisco continued to address this question at the Enterprise Connect conference with a set of new
announcements related to pervasive video, the collaborative workspace, and new value-priced IP
telephony solutions, that further the goal of transforming how people and organizations
collaborate.
Pervasive Video
Video transforms the collaboration experience. It is being adopted everywhere--at work and on
the road--and has gone far beyond 'meetings' to becoming a natural part of everyday activity.
Now everyone can be a video producer and consumer. Learn about new recording and streaming
solutions, video-enabled endpoints, a unified user interface for Cisco TelePresence, and more:
Find out how you can easily create and share video with new Cisco TelePresence Content
Server capabilities and integration with Cisco Show and Share
Experience the new range of video-enabled endpoints, including new video phones and a new
Telepresence endpoint
Make video easy with a new unified Telepresence user interface
Unlock the power of video with new analytics and media transformation capabilities
Take advantage of the power of video for face-to-face virtual meetings, events, training, and
organizational communications
The New Collaborative Workspace
The dramatic rise in the popularity of smartphones and tablet devices has marked the start of
a 'post-PC' era, where desktop PC applications are no longer the primary collaboration tool.
The new workspace is inherently mobile, social, visual and virtual, allowing people to work
anywhere, on any device, with any content. A key requirement of this new model is a
consistent user interface that fosters productivity and versatility of communication, no matter
where you are or what you're doing.
Experience Cisco's Unified Communications capabilities that provide presence, instant

messaging, voice and video, desktop sharing, conferencing, and more
See how these capabilities can be provided on a variety of platforms and devices including
Windows, Mac, iPhone, iPad, Android, and others
Learn how flexible deployment models--on-premises, in public or private clouds, or hybrid--
are supported
See how the Cisco Cius business tablet and Cisco desktop virtualization endpoints help
enable a highly secure and efficient virtual workspace that supports rich media
Unified Communications for Everyone
Improved responsiveness and streamlined communication are critical for any business no matter
their size. Cisco has drawn on its enterprise-proven IP telephony system to deliver a solution for
midsize businesses that is easy to set up and manage with value pricing to match:
Learn more about the Cisco Unified Communications Manager Business Edition 3000 and
how it can help you to better interact with customers, suppliers, and employees
Gain IT control and savings with Cisco Virtual Desktop Infrastructure, and provide greater
flexibility for your users.
Social Media Meets Customer Care
Every day, people express millions of opinions online using social media tools such as Twitter
and Facebook--maybe about your company. Are you listening? Now you can:
Engage with customers in their preferred medium, monitor what they're saying, and respond
quickly and personally
Find new customers, solve problems, and track buying trends quickly with Cisco SocialMiner
Enhance call-center productivity with Cisco Finesse to give representatives all the
information they need
The impact of the growth of mobile devices cannot be overstated. Feature phones capable of
voice and text messaging - and in some cases mobile email - have long been popular, but with the
introduction of the Apple iPhone and the Google Android mobile OS, a new category of devices
designed for accessing the Internet and collaboration appeared almost overnight. The market
penetration statistics are simply amazing:
100 million Apple iPhones sold to date

Google Android devices activated per day: 340,000 (10 million+ per month)
19.46 million Apple iPads sold to date
Unlike traditional desk-based personal computers, this new class of mobile devices came
equipped with all of the capabilities necessary to enable people to richly communicate and
collaborate with each other, such as front- and rear-facing cameras, high-quality LED
screens, fourth-generation (4G) and Wi-Fi network connectivity, and software to maximize
battery life.
Why Cisco?
Any to Any
Video Everywhere
New Collaborative Workspace
Cloud Collaboration
8 www.flane.com.au
Cisco Collaboration Architecture
9 www.flane.com.au
Collaboration Architecture Differentiates Business Value
This open, integrated foundation works with new and existing technologies, and positions you to
realize new business opportunities. By aligning this architecture with your strategic goals, the
technologies deployed within this framework allow you to:
Transform business processes

Boost organizational efficiency
Accelerate your time to market
The Cisco collaboration architecture offers you significant competitive advantages. It breaks
down the barriers to collaboration that traditionally exist between different content formats, tools,
devices, companies, and people working towards a common goal. As a result, it provides the
architectural flexibility and organizational agility you require to quickly respond to the changing
needs of your business.
Summary
The Cisco collaboration architecture offers you significant competitive

advantages.
Collaboration is emerging as the next breakthrough source of effectiveness and

innovation for business. Multiple trends are converging to create a profound
transition in the way people interact and do business.
Collaboration Architecture Differentiates Business Value by aligning this

architecture with your strategic goals, the technologies deployed within this
framework allow you to:
Transform business processes
Boost organizational efficiency
Accelerate your time to market

10 www.flane.com.au
Lesson 2
Cisco Jabber
Portfolio
Cisco Collaboration Clients
Overview
Provide an integrated user experience and extend the

capabilities and operations of the Cisco UCM.
Enable collaboration both inside and outside the company
boundaries by bringing together
Cisco clients use the Cisco Unified Client Services Framework to
integrate with underlying Unified Communication services
through a common set of interfaces.
12 www.flane.com.au
Cisco Collaboration Clients and Applications provide an integrated user experience and extend
the capabilities and operations of the Cisco Unified Communications System. These clients and
applications enable collaboration both inside and outside the company boundaries by bringing
together, in a single easy to use collaboration client, applications such as online meetings,
presence notification, instant messaging, audio, video, voicemail, and many more.
Several Cisco collaboration clients and applications are available. Third-party XMPP clients and
applications are also supported. Cisco clients use the Cisco Unified Client Services Framework to
integrate with underlying Unified Communication services through a common set of interfaces. In
general, each client provides support for a specific operating system or device type. Use this
chapter to determine which collaboration clients and applications are best suited for your
deployment. The client-specific sections of this chapter also provide relevant deployment
considerations, planning, and design guidance around integration into the Cisco Unified
Communications System.
Cisco Collaboration Clients
Overview (Cont.)
Supported Cisco Collaboration Clients :
Cisco Jabber for Windows and Mac
Cisco Jabber for Everyone
Cisco Jabber for mobile devices
Cisco Jabber Video for TelePresence

(Movi)
Cisco Virtual Experience Clients
Cisco UC IntegrationTM for Microsoft Lync
Third-party XMPP clients.
13 www.flane.com.au
The following collaboration clients and applications are supported by the Cisco Unified
Communications System:
Cisco Jabber for Windows and Cisco Jabber for Mac are Unified Communications clients
that provide robust and feature-rich collaboration capabilities including standards-based
IM and presence, audio and video, visual voicemail, desktop sharing, deskphone control,
Microsoft Office integration and directory integration.
Cisco Jabber for Windows and Cisco Jabber for Mac can be deployed to use on-premises
services in which Cisco IM and Presence (formerly Cisco Unified Presence) and Cisco
Unified Communications Manager provide client configuration, instant messaging and
presence, and user and device management. Cisco Jabber for Windows and Cisco Jabber
for Mac can also be deployed to use cloud-based services through integration with Cisco
WebEx Messenger service.
Cisco Jabber forms the basis of the next generation of Cisco collaboration clients, which
will supersede Cisco Unified Personal Communicator and Cisco Unified Integration for
WebEx Connect in future Cisco Unified Communications System releases. Therefore,
only Cisco Jabber for Windows and Cisco Jabber for Mac features and functionality are
discussed in this release of the Cisco Unified Communications System SRND. Cisco
Unified Personal Communicator and Cisco Unified Integration for WebEx Connect
clients are still available and supported, but their features and functionality have not
changed from Cisco Unified Communications System release 8.x. For design guidance on
Unified Personal Communicator and WebEx Connect clients, refer to the clients
information in the Cisco Unified Communications System 8.x SRND, available at
http://www.cisco.com/go/ucsrnd

Cisco Jabber for Everyone makes Cisco Jabber presence and instant messaging (IM)
available at zero cost. Jabber IM client applications and Cisco IM and Presence, zero-cost
licenses are available to Cisco Unified Communications Manager customers on the
following platforms: Windows, Mac, Android, BlackBerry, iPhone, iPad, and Cisco
Jabber Web SDK. For more information on Jabber for Everyone, refer to the Jabber for
Everyone Solution Overview, available at
http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_6/english/jabber_for_everyon
e/CUP0_BK_JE526021_00_jabber-for-everyone-solution-overview.html

Cisco provides collaboration clients for the following mobile devices: Android,
BlackBerry, and Apple iOS devices such as iPhone and iPad.
Cisco Jabber Video for TelePresence (Movi)

Cisco Jabber Video for TelePresence (Jabber Video) extends the reach of telepresence.
Jabber Video works with a compatible PC or Mac and a webcam or Cisco TelePresence
PrecisionHD camera to provide high-definition video communications to mobile workers,
allowing them to connect to telepresence systems. Cisco Jabber Video for TelePresence is
a video-only client that is used with the Cisco TelePresence Video Communication
Server (Cisco VCS). For more information on Cisco Jabber Video for TelePresence
(Movi), refer to the documentation at
http://www.cisco.com/en/US/products/ps11328/tsd_products_support_series_home.html

The Cisco Virtualization Experience Clients (VXC) are the integral collaboration
components of the Cisco Virtualization Experience Infrastructure (VXI). The VXCs
provide user access to data, applications, and services across various network
environments, as well as user preferences and device form factors for a fully integrated
voice, video, and virtual desktop environment.

Cisco UC IntegrationTM for Microsoft Lync allows for integrated Cisco Unified
Communications services with Microsoft Lync and Microsoft Office Communications
Server (OCS) R2 using the Cisco Unified Client Services Framework, while delivering a
consistent user experience. The solution extends the presence and instant messaging
capabilities of Microsoft Lync by providing access to a broad set of Cisco Unified
Communications services, including standards-based audio and video, unified messaging,
web conferencing, deskphone control, and telephony presence.
Third-party XMPP clients and applications

Cisco IM and Presence, with support for SIP/SIMPLE and Extensible Messaging and
Presence Protocol (XMPP), provides support of third-party clients and applications to
communicate presence and instant messaging updates between multiple clients. Third-
party XMPP clients, MomentIM, Adium, Spark, Pidgin, and others, allow for enhanced
interoperability across various desktop operating systems. In addition, web-based
applications can obtain presence updates, instant messaging, and roster updates using the
HTTP interface with SOAP, REST, or BOSH (based on the Cisco AJAX XMPP Library
API).
Cisco Jabber Product
Portfolio
All-in-one UC Application Collaborate from Any Workspace
Presence & IM PC, Mac, tablet, smart phone
Voice, Video, voice messaging On-premises and Cloud
Desktop sharing, conferencing Integration with Microsoft Office

14 www.flane.com.au
Best Experience Across PC, Tablet

and Phone
PC Tablet Phone
iPad Cius Samsung iPhone Android
Win OS Mac OS
Blackberry Nokia
15 www.flane.com.au
Product Overview
Highly productive toolset
User Interface and experience crafted to be highly
intuitive
Flexible deployment
Contact search
Enterprise IM/presence
Audio/video
Softphone & deskphone
Desk phone control Visual voicemail via Cisco Unity
HD quality video (up to 720p) Connection
Advanced call functions Citrix XenDesktop & XenApp support
Hold/resume Desktop sharing via WebEx or BFCP
Forward/Transfer Microsoft Office integration
SRST Escalation to web meeting
B2B inter-domain federation Language localization
17 www.flane.com.au
Cisco Jabber™ is a unified communications application that enables you to be more productive
from anywhere on any device. Find the right people, see if and how they are available, and
collaborate using your preferred method.
Today's global, distributed work environment has resulted in significant challenges for workers,
making it harder to connect with the right people and significantly increasing the quantity and
modes of communications. Organizations of all sizes are striving to improve communications in
order to retain customers, compete for new business, control costs, and grow their business
globally.
Cisco Jabber for Windows streamlines communications and enhances productivity by unifying
presence, instant messaging, video, voice, voice messaging, desktop sharing, and conferencing
capabilities securely into one client on your desktop. Cisco Jabber for Windows delivers highly
secure, clear, and reliable communications. It offers flexible deployment models, is built on open
standards, and integrates with commonly used desktop applications. You can communicate and
collaborate effectively from anywhere you have an Internet connection
The following are the supported presence features to view real-time availability of co-workers
and colleagues within and outside the enterprise network:
Exchange and display presence availability information and instant messages with other
Cisco Jabber users, Cisco Unified Personal Communicator, Cisco WebEx Connect®,
Microsoft Office Communicator and Lync, IBM Lotus Sametime, AOL, GoogleTalk, and
many other XMPP-compatible clients.
Exchange presence information with mobile handsets using Cisco Jabber or third-party
XMPP-compatible clients.
Display customized availability messages.
Your status is updated automatically when you are in a Cisco WebEx meeting or sharing
an application.
Show your availability based on the free and busy status in your Microsoft Outlook
Calendar or Exchange Server2.
Use the do-not disturb (DND) availability state to let others know you are unavailable.
The DND status is automatically synchronized between Cisco Jabber and your Cisco
Unified IP Phone to help ensure privacy for both instant messaging and phone
communications.
Cisco Jabber for Windows can be deployed in virtual environments using Citrix XenDesktop and
Citrix XenApp:
Citrix XenDesktop 5.0 or 5.5

Citrix XenApp 5.5 or 6.0 Enterprise Edition for Windows 2008 R2 64-bit, published
desktop
In a virtual environment Cisco Jabber for Windows supports presence, instant messaging, and
desk phone control.
Instant Message / Group Chat
Standard based XMPP protocol

Encryption point to point and group chat
Emoticons & rich text
Screen capture for content sharing
Escalation to voice/video
Federated chat to other organizations and
services
SIP: with Microsoft OCS and AOL
XMPP: IBM Sametime, Googletalk, Webex
Connect, and another IM and Presence Release
9.x enterprise.
Chat history and logging
18 www.flane.com.au
Encrypt instant messaging communications using up to 256-bit Advanced Encryption Standard

(AES) encryption and Transport Layer Security/Secure Sockets Layer (TLS/SSL) connections.
Signaling is also encrypted.
You can choose the right communication tool for your situation to escalate from a chat to an
audio call, video call, desktop share, or web meeting. Also you can access a history of your
instant messaging conversations.
You can exchange and display presence availability information and instant messages with other
Cisco Jabber users, Cisco Unified Personal Communicator, Cisco WebEx Connect®, Microsoft
Office Communicator and Lync, IBM Lotus Sametime, AOL, GoogleTalk, and many other
XMPP-compatible clients.
Voice & Video Communication
Industry standard based voice and video for greater

interoperability
Soft phone and desk phone operating modes with in
call features
Native interoperability with Telepresence systems.
High quality audio and high definition business video
Enterprise Class Voice,
experience Video and Call
Jabber supports both ad-hoc and scheduled video Control
conferences
Ad-hoc are initiated using drag and drop or escalated
group chat.
Ad-hoc media resources are allocated from UC
manager as required.
19 www.flane.com.au
Exchange ideas face-to-face with coordinated video display on the PC screen and voice
conversation with a soft phone.
Make, receive, and control your phone calls whether you are in or out of the office.
Click-to-call directly from your contact list or Outlook without the need to look up phone
numbers.
Business-quality video communication up to high-definition (720p) and high-fidelity
wideband audio is supported.
Standards-based video means you are not restricted to collaboration with just other
Jabber clients. You can use voice, video, and even desktop share when interacting with
telepresence endpoints and room-based and multipoint videoconferencing systems.
A variety of call-control options are available, including mute, call transfer, call
forwarding, and ad-hoc conferencing.
The enterprise-class IP telephony reliability and failover features of Cisco Unified
Communications Manager are supported.
Initiate multiparty voice and web meetings.
Group chat and audio conference sessions are as simple as clicking a button, eliminating
the need to use other applications and interfaces to schedule, invite, or join conferences.
Initiate a web meeting session directly from the Cisco Jabber client, using Cisco WebEx
conferencing to share content, such as a presentation, document, or your desktop
Status Bar – Device selection
/ Call Forward
Users can select mode of operation using the system tray icon.
Drop down list provide a list of hardware/software calling options.
Users can be configured to use just desk phone, just soft phone or both.
20 www.flane.com.au
Cisco Jabber delivers business-quality voice and video to your desktop. Powered by the market-
leading Cisco® Unified Communications Manager call-control solution, Cisco Jabber is a soft
phone with wideband and high-fidelity audio, standards-based high-definition video (720p), and
desk phone control features. These features mean that high-quality and high-availability voice
and video telephony is available at all locations and to your desk phones, soft clients, and mobile
devices. Cisco Jabber for Windows makes voice communications simple, clear, and reliable.
Desktop Share Options
WebEx Ad-hoc Desktop Share Video desktop Share (BFCP)

Only available in Cloud Mode Interoperates with Telepresence endpoints
Two way sharing Requires UC Manager 8.6
Supports Annotation Requires active voice call
Webex Ad-Hoc Desktop share using Available in both Cloud and on Premise Mode
the WebEx Connect service in the Standards based Video desktop share
Cisco collaboration cloud to host providing cross device interoperability.
desktop sharing session. Desktop share sent as primary or secondary
Two way control application control video stream.
Multi-party video desktop via MCU
21 www.flane.com.au
Communicate ideas quickly by instantly sharing what is on your desktop. With the Jabber
application you can share your desktop with other Jabber users as well as Cisco and other
standards-based video endpoints.
Jabber for Windows supports desktop sharing using either WebEx Desktop Share or Video
Desktop Share (using BFCP).
Visual Voice Mail and
Extensible Tab /HTML Apps
Visual Voicemail
Provides access to Unity connection.
Message is played back within the client.
Cisco Unity is not supported with Cisco Jabber
Extensible Tab /HTML Apps

HTML tabs can exist on web server.
Examples for tabs:
Company Helpdesk/Support info
Branch directory
Supplier search
Social Networking Tab
Tabs support click to IM / Call, presence support being investigated
22 www.flane.com.au
Visual voice message access. Access and manage your voice messages:
View, play back, and delete voice messages from Cisco Unity® Connection.
Secure messaging is provided, with support for private and encrypted voice messages.
Administrators can create additional HTML application tabs within the client.
Microsoft Office 2010 Integration
See who is available directly in Microsoft
2007/2010 Office suites
Easily start
Chat
Group Chat
Easily escalate to
Voice
Video
Web Share
Personal contact integration
Initiate calls
Initiate IM
Ribbon Bar Integration
23 www.flane.com.au
You can access the capabilities of the Cisco Jabber application from common desktop
applications such as Microsoft Office (Outlook, Word, Excel, PowerPoint, and SharePoint),
including lighting up presence and click-to-communicate (instant message and audio and video
calling) capabilities. For Microsoft Office 2010, you can use the Microsoft contact card click-to-
communicate icons directly from within the application to save time and streamline workflows
because you can view user availability and initiate communications such as personal and group
voice, video, and chat sessions without having to switch between applications.
Cisco Jabber for iPhone
Place, receive, and manage calls over your corporate
Wi-Fi network handover any Wi-Fi hotspot using a
VPN
Lower Mobility Costs
Mobile Privacy
Enterprise Telephony Features
Voice dialing
Voice dialing Enterprise Telephony Features

25 www.flane.com.au
The Cisco Jabber for Android and iPhone mobile clients enable Android smartphones and
iPhones and other Apple iOS devices to make and receive enterprise calls using voice over IP.
The Cisco Jabber mobile client application running on the Android or Apple iOS device registers
and communicates with Unified CM using the SIP signaling protocol. The Cisco Jabber mobile
client also enables additional features such as corporate directory access and enterprise visual
voicemail.
Cisco Jabber® for iPhone lets you place, receive, and manage calls over your corporate Wi-Fi
network. Cisco Jabber for iPhone also supports calls over any Wi-Fi hotspot using a VPN,
allowing you to take further advantage of your corporate telephony infrastructure whenever you
have access to a high-quality wireless network connection. You will benefit from the cost savings
from not using your wireless minutes, the capability to use your work phone number when
placing calls from your Apple iPhone, and the stronger in-building network coverage from a
wireless network.
Lower Mobility Costs
Cisco Jabber for iPhone allows you to place and receive calls over your corporate wireless LAN
(WLAN) and telephony infrastructure, reducing the number of mobile minutes used and saving
on roaming charges. Because Cisco Jabber for iPhone uses your Cisco Unified Communications
Manager call-routing capabilities, you can also avoid toll charges for international calls. You can
place and receive calls when at home, in hotels, or at Wi-Fi hotspots.
Mobile Privacy
Cisco Jabber for iPhone turns your iPhone into an extension on Cisco Unified Communications
Manager. You appear to receive and make calls from your desk phone when using Cisco Jabber
for iPhone. Executives benefit from this feature because they often want to keep their mobile
number private when placing calls.
Enterprise Telephony Features
Cisco Jabber for iPhone offers enterprise-class telephony functions including transfer, conference,
hold and resume, and park and recover calls. You can also hand off calls to your mobile
provider’s network as you leave Wi-Fi coverage. Finally, you can move iPhone calls to and from
your Cisco Unified IP Phone to continue a conversation on a different phone
With Cisco Jabber for iPhone, you have many dialing options. You can place a call from your
Contacts list, manually dial a number, or simply hold the phone up and say a name to dial. Cisco
Jabber for iPhone works in conjunction with Speech Connect for Cisco Unity® Connection to
allow you to dial contacts in this way
Apple iOS 5.0 or later running on an Apple iPhone 3GS, 4, or 4S, Apple iPod touch third or
fourth generation, or Apple iPad (1 or 2) is required for Cisco Jabber 8.6.
Apple iPod touch and iPad are not supported through Bluetooth headsets. Apple iPod touch third
generation requires a wired headset; you can use iPod touch fourth generation and iPad in
speakerphone mode or with a wired headset.
Cisco Jabber for iPhone supports multiple audio codecs (G.711a, G.711mu, and G.729) and
automatically selects the best option depending on whom you are calling and the bandwidth
available, providing you with the best audio experience possible.
Cisco Jabber for iPhone (Cont.)
Visual Voicemail
Call preservation
Integration with Cisco Mobile Connect (single-number
reach)
Handoff to GSM
Handoff to and from desk phone
Cisco Jabber supports Survivable Remote Site
Telephony (SRST).
Cisco Jabber allows you to sign in and out of the app
using Extension Mobility.
Users can cross-launch Cisco Jabber IM for iPhone.
26 www.flane.com.au
Visual Voicemail
Cisco Jabber for iPhone gives you visual access to your enterprise voicemail. You can view new
and saved voicemail messages, and play back messages in any order. Actions you take on your
iPhone, such as playing, marking as unheard, or deleting a message, are synchronized with your
corporate voicemail mailbox. Visual Voicemail requires Cisco Unity Connection or Cisco Unity
Express
Call preservation
Call preservation keeps your call connected when you receive a Global System for Mobile
Communications
(GSM) call while on an Internet call. You can retrieve the Internet call by returning to Cisco
Jabber for iPhone.
Integration with Cisco Mobile Connect (single-number reach)
Cisco Mobile Connect enables you to receive calls placed to your desk phone on your iPhone
(through GSM) whenever Cisco Jabber for iPhone is not running or not connected to Cisco
Unified Communications Manager
Handoff to GSM
You can hand off your Internet call to your mobile operator’s network as you leave buildings, so
you have freedom to move about without interrupting your calls.
You can hand off your call from your iPhone to your desk phone and continue your call using
your desk phone. Similarly, you can hand off calls from the desk phone to your iPhone, so you
have freedom to move about.
Failover Cisco Jabber for iPhone supports various failover scenarios, including failover to
another Cisco Unified Communications Manager or the failover features of Cisco Unified
Survivable Remote Site Telephony (SRST).
Integration with the Cisco Jabber IM for iPhone Application
You can initiate an instant message (IM) chat with a contact in your Cisco Jabber for iPhone
application or you can initiate a voice-over-IP (VoIP) call with a contact in your Cisco Jabber IM
for iPhone application. Each application can cross-launch the other in order to deliver a more
complete collaboration experience on the iPhone.
Always-on and always connected
Intuitive user experience
Lower mobility costs
Mobile privacy
Enterprise telephony features
Handoff to mobile voice network
Cisco Jabber for Android is officially supported on the following devices:
Samsung Galaxy S II (AT&T) running Android Version 2.2
Samsung Galaxy S i9000 (model number GT-I9000) running Android Version
2.2.1 or 2.3
Samsung Galaxy Tab international version (model number GT-P1000) running
Android Version 2.2 or 2.3
27 www.flane.com.au
With Cisco Jabber for Android you can turn your Android device into a full-featured Cisco
Unified IP Phone. You can place, receive, and manage calls whether using your corporate Wi-Fi
network, other Wi-Fi networks, or a mobile data network.
Cisco Jabber for Android features a secure connection capability to your corporate network so
that you remain transparently and automatically connected no matter where you choose to work.
You will also benefit from the cost savings from not using your wireless voice minutes, the
ability to use your work phone number when placing calls from your Android smartphone or
tablet, and the stronger network coverage from a Wi-Fi network.
Stay connected while mobile
Presence/IM application on iPhone
View presence states & conducting 1:1
chats
For both on-premises or on-demand
deployment
Take immediate action from your contact list

Start or join an instant WebEx meeting
Click to call, click to email, click to SMS
Cross launch with Cisco Jabber for
iPhone
29
Flexible & secure deployment www.flane.com.au
The Cisco Jabber IM client runs on specific BlackBerry smartphones and on the iPhone and other
Apple iOS devices and communicates via XMPP with on-premises Cisco IM and Presence
services or off-premises cloud-based Cisco WebEx Connect.
Stay connected while mobile: Cisco Jabber® IM for iPhone delivers instant messaging (IM) and
presence to your Apple iPhone.
Access your desktop IM contact list and take action with features such as click to IM,
click to call, click to email, and click to text from a person’s profile.
Start or join an instant Cisco WebEx® meeting from an IM conversation
Search for colleagues in your corporate directory
Maintain security using Secure Sockets Layer (SSL) encryption and by connecting your
IPhone directly to the Cisco IM infrastructure
Cisco Jabber IM for iPhone works with the following Apple devices:
iPhone 3GS and 4

iPod Touch (third and fourth generation)
iPad 1 and 2
Cisco Jabber IM for iPhone works with the following Apple iOS versions:
4.2
4.3
5.0
Cisco Jabber IM for BlackBerry
Delivers instant messaging (IM) and
presence to your BlackBerry.
Access your desktop IM contact list
Join an instant Cisco WebEx meeting from
an IM conversation
Maintain security using Secure Sockets
Layer (SSL) encryption and by connecting
your BlackBerry directly to the Cisco IM
infrastructure
Supported BlackBerry Devices:
Bold 9000, 9700, 9780, 9650, and
9900
Curve 8520, 8900, and 9330
Torch 9800, 9810, and 9850
Tour 9630
30 www.flane.com.au
Cisco Jabber IM for BlackBerry lets you reduce communication delays by knowing a person’s
availability with a presence status generated from multiple sources. When you are mobile and
using your BlackBerry device, viewing a person’s presence status lets you immediately know if
that person is available or busy, so you can determine the best way to reach that person. You can
use the application to connect quickly over IM and, if necessary, escalate to a phone call, send an
email, text message, start an instant Web conference, or use Short Message Service (SMS).
Cisco Jabber IM for BlackBerry lets you collaborate securely - even with colleagues outside your
organization.
The application uses the widely accepted Extensible Messaging and Presence Protocol (XMPP)
Internet and presence IM standard that supports communication with networks outside your
organization. You are ensured of communication privacy with user authentication and 128-bit
SSL encryption or 256-bit AES encryption (AES encryption requires Cisco WebEx Connect and
is not available with Cisco Unified Presence).
Cisco Jabber IM for BlackBerry is designed to work with either deployment model - a premises-
based or cloud-based presence solution.
Cisco Jabber IM for BlackBerry is an extension of the Cisco Enterprise IM applications:
Cisco WebEx Connect (cloud solution) versions 6.5, 6.7, and 7.0
Cisco Unified IM and Presence (on-premise solution) versions 8.0 and 8.5
This application allows users to stay in touch with their contacts any time, any place, on any
device. Users can join instant meetings and place phone calls without leaving Cisco Jabber IM for
BlackBerry. Cisco Jabber IM for Blackberry uses the BlackBerry Enterprise Server (BES) and
existing wireless networks.
Product Overview
Integrated voice, video, presence & IM client
Complete collaboration experience on the most popular tablet in the world
High-quality video experience
Interoperate with Cisco TelePresence endpoints
On-premises or the cloud

32 www.flane.com.au
Cisco Jabber™ for iPad is a unified communications client application that provides presence,
instant messaging (IM), voice, voice messaging, and video calling capabilities on the Apple iPad
(Figure 1). Conferencing and screen-sharing capabilities are delivered with an escalation to the
Cisco WebEx® for iPad application. This integrated collaboration experience is designed to take
advantage of the form factor of the iPad; it works with both a premises- and a cloud-based
collaboration architecture.
This application supports the following important functions:
Integrated voice, high-quality video, IM, presence, and visual voicemail functions
Flexibility of configuration for different communications infrastructure and
combinations of:
Voice and video: Cisco Unified Communications Manager
Video-only: Cisco TelePresence® Video Communication Server (VCS) or Cisco
Jabber Video for TelePresence
Peer-to-peer voice and video: Cisco WebEx Connect® service
Presence and IM: Cisco WebEx Connect service or Cisco Unified Presence
One-tap escalation to WebEx® meetings through cross-launching the Cisco WebEx

application
Interoperability with Cisco TelePresence and other video endpoints
Sneak Previews
33 www.flane.com.au
You can place a video call to a colleague using the Cisco WebEx Connect application using an
Internet call option on the Cisco Jabber for iPad client. You can set your presence status so your
contacts know whether or not you are available, helping them decide which method of
communication they use to reach you. You can also set your presence status to show colleagues
that you are "On Mobile" instead of at your computer.
720p HD resolution at 30 fps
Mobile video industry's best audio

performance from a PC or Mac*
Initiate Ad hoc multi-party calls utilizing

Cisco TelePresence Multiway
Maximum collaboration with others using

Far End Camera Control*
Supports the following codecs (H.264,

H.263+ and H.263)
Address book search (from Cisco TMS)

35 www.flane.com.au
Cisco Jabber Video for TelePresence (Jabber Video) is an application that extends the reach of
telepresence. Jabber Video works with a compatible PC or Mac and a webcam or Cisco
TelePresence PrecisionHD camera to provide high-definition video communications to more
people, on more devices, from more places. Jabber Video can connect to telepresence systems,
resulting in a wider community of colleagues, partners, and business customers.
Summary
Cisco Jabber for Windows, Cisco Jabber for Mac, and Cisco UC IntegrationTM
for Microsoft Lync all use the Client Services Framework as a base building block
for the client application.
The following collaboration clients and applications are supported by the Cisco
Unified Communications System:
Third-party XMPP clients.

36 www.flane.com.au
Lesson 3
Cisco Unified Client Services

Framework
Cisco Unified Client Services
Framework Overview
SIP-based call control for voice and video
Deskphone call control and "Click to Dial" services
Voice and video media termination
Instant messaging and presence services using XMPP
Scheduled audio, video and web conferencing services
Desktop sharing using either, video desktop sharing (BFCP)

or WebEx desktop sharing
Visual voicemail services from Cisco Unity Connection

using IMAP
Contact management
Microsoft Office Integration Cisco UC Integration for MS Lync

38 www.flane.com.au
Cisco Jabber for Windows, Cisco Jabber for Mac, and Cisco UC IntegrationTM for Microsoft Lync all
use the Client Services Framework as a base building block for the client application. Cisco Unified
Client Services Framework is a software application that combines a number of services into an
integrated client. An underlying framework is provided for integration of Unified Communications
services, including audio, video, web collaboration, visual voicemail, and so forth, into a presence and
instant messaging application.
These Cisco Jabber client applications reside on top of the Clients Services Framework, which provides
a simplified client interface and an abstraction layer that allows access to the following underlying
communications services:
SIP-based call control for voice and video softphone clients from Unified CM
Deskphone call control and "Click to Dial" services from Unified CM's CTI interface
Voice and video media termination for softphone clients
Instant messaging and presence services using XMPP, from either the Cisco IM and Presence
Service or Cisco WebEx. Cisco WebEx Meeting Center also offers hosted collaboration services
such as online meetings and events
Scheduled audio, video and web conferencing services
Desktop sharing using either, video desktop sharing (BFCP) or WebEx desktop sharing
Visual voicemail services from Cisco Unity Connection using IMAP
Contact management using:
Unified CM User Data Service (UDS) as a contact source (LDAP directory
synchronization supported)
Directory access using Microsoft Active Directory or supported LDAP directories as
a contact source
WebEx Messenger service
Client Services Framework cache and contact list
Microsoft Office Integration, which provides user availability status and messaging capabilities
directly through the user interface of Microsoft Office applications such as Microsoft Outlook.
Client Services Framework Services
Cisco Jabber for Windows, Cisco Jabber for Mac, and Cisco UC IntegrationTM
for Microsoft Lync all use the Client Services Framework as a base building block
for the client application.
39 www.flane.com.au
The ability to communicate and abstract services and APIs,, allows the Client Services Framework to
coordinate the management of protocols to these services and APIs, handle event notifications, and
control the low-level connection logic for local system resources.
Client Services Framework
Services (Cont.)
Call Control
Softphone Mode
Deskphone Control Mode
Audio and Video Media
Instant Messaging and Presence Services Cisco IM and Presence
Cisco IM and Presence
Audio, Video and Web Conferencing Services
Cisco Unified MeetingPlace
WebEx Meeting Center
40 www.flane.com.au
Cisco Unified Client Services Framework can operate in one of two modes for call control:
Softphone Mode — Using audio and video on a computer
The Client Services Framework in softphone mode is directly registered to Unified CM as
a SIP endpoint for audio and video call control functionality, and it is configured on
Unified CM as device type Client Services Framework.
Deskphone Control Mode — Using a Cisco IP Phone for audio (and video, if supported)
The Client Services Framework in deskphone control mode does not register with Unified
CM using SIP, but instead uses CTI/JTAPI to initiate, monitor, and terminate calls,
monitor line state, and provide call history, while controlling a Cisco Unified IP Phone.
The Cisco CallManager Cisco IP Phone (CCMCIP) service on Unified CM is used by the
Client Services Framework to retrieve a list of devices associated with each user. This list
of devices is used by a client in deskphone mode to choose which Cisco IP Phone it
wishes to control.
A number of standard audio and video codecs for use in low bandwidth or high fidelity
deployments are supported with the Client Services Framework. Audio codecs include G.729a,
G.711, and G.722.1, while video codecs include H.264 AVC (Advanced Video Coding) with
support for H.264 baseline profile levels 1 through 3.1. Video formats supported include QCIF,
CIF, VGA, and 720p HD at a rate of up to 30 frames per second.
The Client Services Framework always attempts to transmit and receive high definition video;
however, there are a number of throttling factors that need to be considered when deploying
video. These throttling considerations include the capability of the device communicating with,
the local processing capability of the PC, administrative or user settings, local camera
capabilities, and any call admission control policies in place.
There are a number of references the Client Services Framework can use to determine the video
frame rate for a call. The processing power and CPU used by the client play an important role in
determining the video frame rate used. Another decision point is based on the Windows
Experience Index (WEI) for the personal computer being used (see
http://technet.microsoft.com/en-us/library/cc507870.aspx). The minimum values for encoding
and decoding high definition video require a processor WEI encode value of 5.9 and a bandwidth
requirement of 1 Mbps for 720p at 15 frames per second or 2 Mbps for 720p at 30 frames per
second.
Client Services Framework
Services (Cont.)
Contact Management:
Cisco UCM User database via the User Data Service (UDS)
LDAP directory integration

UDS
Contacts can also be stored and retrieved locally using

either of the following:
Client Services Framework Cache LDAP
Local address books and contact lists

The Client Services Framework uses reverse number lookup to
map an incoming telephone number to a contact, in addition to
photo retrieval.
41 www.flane.com.au
The Client Services Framework can handle the management of contacts through a number of sources,
including the following:
Cisco Unified CM User database via the User Data Service (UDS)
LDAP directory integration
Contacts can also be stored and retrieved locally using either of the following:
Client Services Framework Cache
Local address books and contact lists
The Client Services Framework uses reverse number lookup to map an incoming telephone number to a
contact, in addition to photo retrieval. The Client Services Framework contact management allows for up
to five search bases to be defined for LDAP queries.
UDS provides clients with a contact search service on Cisco Unified Communications Manager. You can
synchronize contact data into the Cisco Unified CM User database from Microsoft Active Directory or
other LDAP directory sources. Clients can then automatically retrieve that contact data directly from
Unified CM using the UDS REST interface.
The Client Services Framework maintains a local cache of contact information derived from
previous directory queries and contacts already listed, as well as the local address book or contact
list. If a contact for a call already exists in the cache, the Client Services Framework does not
search the directory. If a contact does not exist in the cache, the Client Services Framework
performs a directory search.
Dial Plan Considerations
Use the directory for searching, resolving, and adding contacts. The number that
is associated with those contacts must be in a form that the client can recognize,
resolve, and dial.
Cisco UCM Dial plan:
E164 Numbering Plan
Private Numbering Plan

Outbound calls can be translated by translation patterns that allow the
number being dialed (for example, +18005551212) to be presented to the
endpoint as the private number (5551212 in this example).
Inbound calls can be translated by means of directory lookup rules. This

allows an incoming number of 5551212 to be presented for reverse number
lookup caller identification as +18005551212.
42 www.flane.com.au
Dial plan and number normalization considerations must be taken into account when deploying
the Client Services Framework as part of any Unified Communications endpoint strategy. The
Client Services Framework, as part of a Unified Communications collaboration client, will
typically use the directory for searching, resolving, and adding contacts. The number that is
associated with those contacts must be in a form that the client can recognize, resolve, and dial.
Deployments may vary, depending on the configuration of the directory and Unified CM. In the
case where the directory contains E.164 numbering (for example, +18005551212) for business,
mobile, and home telephone numbers and Unified CM also contains an E.164 dial plan, the need
for additional dial rules is minimized because every lookup, resolution, and dialed event results in
an E.164 formatted dial string.
If a deployment of Unified CM has implemented a private dial plan (for example, 5551212), then
translation of the E.164 number to a private directory number needs to occur on Unified CM.
Outbound calls can be translated by Unified CM translation patterns that allow the number being
dialed (for example, +18005551212) to be presented to the endpoint as the private number
(5551212 in this example). Inbound calls can be translated by means of directory lookup rules.
This allows an incoming number of 5551212 to be presented for reverse number lookup caller
identification as +18005551212.
Private numbering plan deployments may arise, where the dial plan used for your company and
the telephone number information stored in the LDAP directory may require the configuration of
translation patterns and directory lookup rules in Cisco Unified Communications Manager to
manage number format differences. Directory lookup rules define how to reformat the inbound
call ID to be used as a directory lookup key. Translation patterns define how to transform a phone
number retrieved from the LDAP directory for outbound dialing.
CSF Dial Plan Components
Translation Patterns
Application Dialling Rules
Directory Lookup Rules
Client Transformation
Directory Lookup Rules Application Dial Rules

43 www.flane.com.au
Translation patterns are used by Unified CM to manipulate the dialed digits before a call is
routed, and they are strictly handled by Unified CM. Translation patterns are the recommended
method for manipulating dialed numbers. For additional guidelines on translation pattern usage
and dial plan management,
Application Dialing Rules

Application dialing rules can be used as an alternative to translation patterns to manipulate
numbers that are dialed. Application dialing rules can automatically strip numbers from, or add
numbers to, phone numbers that the user dials. Application dial rules are configured in Unified
CM and are downloaded through TFTP to the client from Unified CM. Translation patterns are
the recommended method for manipulating dialed numbers.

Directory lookup rules transform caller identification numbers into numbers that can be looked up
in the directory. A directory lookup rule specifies which numbers to transform based on the initial
digits and the length of the number. Directory lookup rules are configured in Unified CM and are
downloaded through TFTP to the client from Unified CM.
Client Transformation
Before a call is placed through contact information, the client application removes everything
from the phone number to be dialed, except for letters and digits. The application transforms the
letters to digits and applies the dialing rules. The letter-to-digit mapping is locale-specific and
corresponds to the letters found on a standard telephone keypad for that locale. For example, for a
US English locale, 1-800-4UCSRND transforms to 18004827763. Users cannot view or modify
the client transformed numbers before the application places the call.
Deploying Client Services
Framework
Use the Bulk Administration Tool for the Client Services Framework deployment.
Capacity Planning for Client Services Framework

TFTP
CTI
CCMCIP: Used to gather information about the devices associated with a
user.
IMAP: When configured for voicemail, the Client Services Framework
updates and retrieves voicemail through an IMAP connection to the mailstore.
LDAP: Client login and authentication, contact profile information, and incoming caller
identification.
UDS
46 www.flane.com.au
Cisco Unified Client Services Framework operates as either a SIP endpoint registered to Unified
CM or as a deskphone controller of a Cisco Unified IP Phone using a CTI connection to Unified
CM. When planning a deployment using the Client Services Framework, Cisco partners and
employees can use the Cisco Unified Communications Sizing Tool (available at
http://tools.cisco.com/cucst) to assist in the appropriate sizing of SIP registered endpoints and
CTI controlled devices. The following additional items must be considered for a Client Services
Framework deployment:
TFTP — When configured in softphone mode, a Client Services Framework device
configuration file is downloaded through TFTP to the client for Unified CM call control
configuration information. In addition, any application dial rules or directory lookup rules
are also downloaded through TFTP to Client Services Framework devices.
CTI — When configured in deskphone mode, the Client Services Framework establishes
a CTI connection to Unified CM upon login and registration to allow for control of the IP
phone. Unified CM supports up to 40,000 CTI connections. If you have a large number of
clients operating in deskphone mode, make sure that you evenly distribute those CTI
connections across all Unified CM subscribers running the CTIManager service. This can
be achieved by creating multiple CTI Gateway profiles, each with a different pair of
CTIManager addresses, and distributing the CTI Gateway profile assignments across all
clients using deskphone mode.
CCMCIP — The Client Services Framework uses the Cisco CallManager Cisco IP Phone
(CCMCIP) service to gather information about the devices associated with a user, and it
uses this information to provide a list of IP phones available for control by the client in
deskphone control mode. The Client Services Framework in softphone mode uses the
CCMCIP service to discover its device name for registration with Unified CM.
IMAP — When configured for voicemail, the Client Services Framework updates and
retrieves voicemail through an IMAP connection to the mailstore.
LDAP — Client login and authentication, contact profile information, and incoming
caller identification are all handled through a query to the LDAP directory, unless stored
in the local Client Services Framework cache.
UDS — The UDS service can be used by clients to search for contacts in the Unified CM User
database. Like LDAP directory searches, UDS contact searches take place if the requested contact
cannot be found in the local Client Services Framework cache.
Summary
CSF allows desktop application users to access a variety of communication and

collaboration services as provided by back-end collaboration application servers
such as Cisco Unified Communications Manager (Unified CM), Cisco Unity
Connection, Cisco WebEx, and Lightweight Directory Access Protocol (LDAP)-
compliant directories.
CSF Framework is a device type in Cisco Unified CM that enables phone

registration and communication for Cisco Unified Communications Integration for
Cisco WebEx Connect and Cisco Jabber desktop applications, and it operates in
either softphone mode or deskphone mode to control a Cisco Unified IP Phone.
45 www.flane.com.au
Module 2
Module Outlines
Deploying Cisco Jabber for Windows
Install and Configure Cisco Jabber for Windows
Designing Cisco IM and Presence
Integrating Cisco Unified CM and Cisco Unified IM and Presence
Set Up Cisco Jabber On-Premises Deployments with Cisco UCM Version
9.x
Cisco Unified IM and Presence Multi-Node deployments
Instant Messaging Compliance ,Logging and Chat Rooms
2-2 Designing and Implementing Cisco Jabber Cisco Jabber for Windows
Lesson 1
Deploying Cisoc Jabber for

Winodws
Cisco Jabber Deployment Options
Additional Services WebEx

UC Manager IM & Presence Directory Service IM & Presence Service
Call Control
Cisco Unity Connection
WebEx Meeting
On Premise Deployment Model Cloud Deployment Model

• Admin from UC Manager (9.x) • Admin in Cloud
• IM & Presence from IM&Presence Server • IM & Presence from cloud
• Contact search from cloud
www.flane.com.au
Cisco Jabber for Windows can be deployed on-premises or on-demand, offering IT departments
the flexibility to choose the model that best suits their business. When the application is deployed
on-demand, IT administrators can push client upgrades automatically to users.
On-Premises Deployments
Cisco UCM provides user and device configuration capabilities.
Cisco IM and Presence provides instant messaging and presence services.
Microsoft Active Directory or another supported LDAP directory provides contact
You can deploy the client in the following modes:
Full UC and Cisco Jabber for Everyone (IM Only)
Phone Mode
www.flane.com.au
An on-premises deployment is one in which you set up, manage, and maintain all services on
your corporate network.
Product Modes
Full UC and Cisco Jabber for Everyone (IM Only)
The default product mode is one in which the user's primary authentication is to a presence
server. At a minimum, users have instant messaging and presence capabilities.
Both full UC and Cisco Jabber for Everyone deployments use the default product mode. To
deploy full UC, you enable instant messaging and presence capabilities. You then provision users
with devices for audio and video in addition to voicemail and conferencing capabilities. To
deploy Cisco Jabber for Everyone, you enable instant messaging and presence capabilities. You
can optionally provision users with desk phone devices that they can control with the client.
Phone Mode
In phone mode, the user's primary authentication is to Cisco Unified Communications Manager.
To deploy phone mode, you provision users with devices for audio and video capabilities. You
can also provision users with additional services such as voicemail.
Cisco Jabber for Windows does not currently support meetings integration in phone mode. You
cannot provision users with conferencing functionality if you deploy the client in phone mode.
Full UC and Cisco Jabber for Everyone
(IM Only)
The default product mode.
User's primary authentication

is to a presence server.
www.flane.com.au
The following are the services available in an on-premises deployment:

Presence
Users can publish their availability and subscribe to other users' availability through
Cisco Unified Presence.
Instant Messaging
Users send and receive instant messages through Cisco Unified Presence.
Audio Calls
Users place audio calls through desk phone devices or on their computers through Cisco
Unified Communications Manager.
Video
Users share their screens and place video calls through Cisco Unified Communications
Manager.
Voicemail
Users send and receive voice messages through Cisco Unity Connection.
Conferencing
Integrate with one of the following:
Cisco WebEx Meeting Center
Provides hosted meeting capabilities.
Cisco WebEx Meetings Server
Provides on-premises meeting capabilities.
Full UC and Cisco Jabber for
Everyone (IM Only) (pre 9)
CUCM Node
Client uses on premise services Users, Contacts
Licensing Cisco Unified
Directory Service
Client configuration on CUCM & Cisco Presence
Unified Presence Server
Instant Messaging and presence

provided by CUP
Contact source: Active directory
Supported with CUCM 7.1(4) thru 8.6 (1)
Aligns with CUPC model
WebEx Meeting Cisco Unity

Center Connection
Roadmap
www.flane.com.au
Full UC and Cisco Jabber for
Everyone (IM Only) (9.x +)
CUCM Node
New Deployment Model Users, Contacts Cisco Unified IM
Licensing and Presence
Client uses on premise services
Client configuration on CUCM (CUP

Profile replaced with Service Profiles
on CUCM)
Instant Messaging and presence

provided by Unified IM & Presence IMAP
Contact source is based on CUCM

User Data Service (synced from AD) WebEx Meeting Cisco Unity
Center Connection
www.flane.com.au
The following are the services available in an on-premises deployment:

Presence
Users can publish their availability and subscribe to other users' availability through
Cisco Unified Communications IM and Presence.
Instant Messaging
Users send and receive instant messages through Cisco Unified Communications IM
and Presence.
Audio Calls
Video
Manager.
Voicemail
Conferencing
Integrate with one of the following:
Cisco WebEx Meeting Center
Provides hosted meeting capabilities.
Cisco WebEx Meetings Server
Provides on-premises meeting capabilities.
Deployment Summary Matrix
Features Cloud Model On Prem (UC 7/8) On Prem (UC 9)
Cisco Unified CM and Cisco

Primary User Admin OrgAdmin Cisco Unified CM
IM and Presence Server
Cisco Collaboration Cisco IM and Presence Cisco Unified CM

IM & Presence
Cloud Server 8.x IM & Presence
Primary Contact Cisco Collaboration Active Directory or
Active Directory
Source Cloud UDS
Office Integration Office 2007/2010 Office 2007/2010 Office 2007/2010
Voice/Video Call
Cisco Unified CM Cisco Unified CM Cisco Unified CM
control
Video desktop share Cisco Unified CM Cisco Unified CM Cisco Unified CM
WebEx desktop Cisco Collaboration
-- --
share Cloud
Cisco Collaboration
WebEx Meetings In the roadmap In the roadmap
Cloud
Outlook Calendar/ Connect Cloud/
In the roadmap In the roadmap
WebEx Meetings MS Outlook
Voicemail Unity Connection Unity Connection Unity Connection
www.flane.com.au
This table is a quick summary for Cisco Jabber for desktop different deployment options.
Phone Mode
User's primary authentication is to

Cisco Unified Communications
Manager.
Cisco Jabber for Windows does not

currently support meetings
integration in phone mode.
www.flane.com.au
The following are the services available in a phone mode deployment:

Audio Calls
Users place audio calls through desk phone devices or on their computers through
Cisco Unified Communications Manager.
Video
Users share their screens and place video calls through Cisco Unified
Communications Manager.
Voicemail
Deployments – Services Connections
By default, Cisco Jabber for Windows connects to the presence
server to authenticate users and retrieve service profiles.
The client can connect to the presence server in the following

ways:
Connection Settings.
Bootstrap File.
Presence Server Discovery.
www.flane.com.au
By default, Cisco Jabber for Windows connects to the presence server to authenticate users and
retrieve service profiles. The client can connect to the presence server in the following ways:
Users enter the presence server address in the Connection Settings window when they
start Cisco Jabber for Windows.
You specify the presence server address during installation. Cisco Jabber for Windows
can then get the presence server address from a bootstrap file when it starts.
The client automatically discovers the presence server.
Deployments – Connection Settings
1. Users set the presence server address in the Connection

Settings window.
2. Cisco Jabber for Windows can then connect to the presence

server to authenticate users.
3. Cisco Jabber for Windows retrieve service profiles.
www.flane.com.au
Connection Settings
Users set the presence server address in the Connection Settings window. Cisco Jabber for
Windows can then connect to the presence server to authenticate users and retrieve service
profiles.
Cisco Jabber for Windows retrieves two different configuration files from the TFTP server:
Client configuration files that you create.
Device configuration files that reside on the Cisco Unified Communications Manager
TFTP service when you provision users with devices.
To minimize effort, you should host your client configuration files on the Cisco Unified
Communications Manager TFTP service. You then have only one TFTP server address for all
configuration files and can specify that address as required.
You can, however, host your client configuration on a different TFTP server to the one that
contains the device configuration. In this case, you have two different TFTP server addresses, one
address for the TFTP server that hosts device configuration and another address for the TFTP
server that hosts client configuration files.
Default Deployments
This section describes how you should handle two different TFTP server addresses in
deployments that have a presence server.
You should do the following:
1. Specify the address of the TFTP server that hosts the client configuration on the presence
server.
2. During installation, specify the address of the Cisco Unified Communications Manager
TFTP service with the TFTP argument.
When the client starts for the first time, it:
1. Retrieves the address of the Cisco Unified Communications Manager TFTP service from
the bootstrap file.
2. Gets device configuration from the Cisco Unified Communications Manager TFTP
service.
3. Connects to the presence server.
4. Retrieves the address of the TFTP service that hosts the client configuration from the
presence server.
5. Gets client configuration from the TFTP server
Deployments – Bootstrap File
1. Specify the presence server address during
installation with the following argument:
ADDRESS.
2. Cisco Jabber for Windows gets the presence

server address from the bootstrap file when it
starts.
3. It can then connect to the presence server to

authenticate users and retrieve service profiles.
www.flane.com.au
Bootstrap File
You can specify the presence server address during installation with the following argument:
ADDRESS.
The installation program then saves the presence server address to a bootstrap file. Cisco Jabber
for Windows gets the presence server address from the bootstrap file when it starts. It can then
connect to the presence server to authenticate users and retrieve service profiles.
Deployments – Presence Server Discovery
Cisco Jabber for Windows can automatically discover either Cisco IM and
Presence or Cisco Unified Communications IM and Presence if you do not
specify the presence server address during installation.
The following is an example SRV record:

_cuplogin._tcp.domain SRV 0 1 8443 cup_server.domain
www.flane.com.au
Presence Server Discovery

Cisco Jabber for Windows can automatically discover either Cisco Unified Presence or Cisco
Unified Communications IM and Presence if you do not specify the presence server address
during installation.
When the client launches for the first time, it retrieves the presence server type from the
bootstrap file.
The bootstrap file contains the settings you specify during installation.
You set the presence server type as the value of the TYPE argument during installation.
In on-premises deployments, the value must be CUP.
To discover the presence server, the client must first determine the domain. It attempts to
retrieve the domain from the following locations, in order of priority:
1. Environment variable: USERDNSDOMAIN
2. Registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
Domain
3. Registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
DhcpDomain
After it finds the domain, the client gets the presence server address from the Domain Name
Server (DNS).
When the client gets the presence server address, it connects to the presence server and then
caches the address of the presence server.
If a redirect occurs to another server in the cluster, the client caches the address of the presence
server to which it connects, not the address of the server before the redirect.
DNS SRV Records
Cisco Jabber for Windows retrieves the _cuplogin._tcp SRV record from the Domain Name
Server (DNS) to lookup either Cisco Unified Presence or Cisco Unified Communications IM
and Presence.
Cisco Jabber for Windows launch
sequence
1. Retrieve the presence server type from jabber-bootstrap.properties in the
installation directory.
2. Authenticate with the presence server.
3. Retrieve profile details and connect to available services.
4. The client connects to available services after it retrieves the service profiles.
The client connects to the conferencing service.
The client connects to the voicemail service.
If the profile contains settings for Cisco Unified Communications Manager,

the client does the following:
Retrieves the device list for the user.
Retrieves the device configuration from the TFTP server.
Registers with Cisco Unified Communications Manager. www.flane.com.au
The client connects to available services after it retrieves the service profiles.
If the profile contains conferencing settings, the client connects to the conferencing
service.
If the profile contains voicemail settings, the client connects to the voicemail service.
If the profile contains settings for Cisco Unified Communications Manager, the client
does the following:
Retrieves the device list for the user.
Retrieves the device configuration from the TFTP server.
Registers with Cisco Unified Communications Manager.
Phone Deployments – Services
Connections
The client can connect to Cisco Unified Communications Manager in the following
ways:
Connection Settings
Bootstrap Files
Connection Settings Bootstrap Files

www.flane.com.au
If you deploy the client in phone mode, it connects to Cisco Unified Communications Manager
to authenticate users and retrieve configuration from the TFTP service. The client can connect
to Cisco Unified Communications Manager in the following ways:
Users enter the TFTP server address in the Connection Settings window when they
start Cisco Jabber for Windows.
You specify the TFTP server address during installation. Cisco Jabber for Windows can
then get the TFTP server address from a bootstrap file when it starts.
Phone Mode Deployments

This section describes how you should handle two different TFTP server addresses in phone mode
deployments.
You should do the following:
1. During installation, specify the address of the TFTP server that hosts the client configuration with
the TFTP argument.
2. Specify the address of the TFTP server that hosts the device configuration in your client
configuration file with the following parameter: TftpServer1.
3. Host the client configuration file on the TFTP server.
When the client starts for the first time, it:
1. Retrieves the address of the TFTP server from the bootstrap file.
2. Gets client configuration from the TFTP server.
3. Retrieves the address of the Cisco Unified Communications Manager TFTP service from the
client configuration.
4. Gets device configuration from the Cisco Unified Communications Manager TFTP
service.
Cloud-Based Deployment
Client Connects to Webex cloud for service
Configuration information provided from

OrgAdmin tool
Instant Messaging and presence service cloud

based
Contact source / directory service is cloud based
Aligns with Webex Connect model
www.flane.com.au
The following are the services available in a cloud-based deployment:

Contact Source
The Cisco WebEx Messenger service provides contact resolution.
Presence
The Cisco WebEx Messenger service lets users can publish their availability and
subscribe to other users' availability.
Instant Messaging
The Cisco WebEx Messenger service lets users send and receive instant messages.
Conferencing
Cisco WebEx Meeting Center provides hosted meeting capabilities.
Hybrid Cloud-Based
A hybrid deployment is one in which the cloud-base services hosted on Cisco
WebEx Connect are combined with the following components of an on-
premises deployment :
Cisco Unified Communications Manager provides user and device services.
Cisco Unity Connection provides voicemail services.
www.flane.com.au
The following are the services available in a hybrid cloud-based deployment:

Contact Source
The Cisco WebEx Messenger service provides contact resolution.
Presence
The Cisco WebEx Messenger service lets users can publish their availability and
subscribe to other users' availability.
Instant Messaging
The Cisco WebEx Messenger service lets users send and receive instant messages.
Conferencing
Cisco WebEx Meeting Center provides hosted meeting capabilities.
Audio Calls
Video
Manager.
Voicemail
Cloud-Based Deployment – Services
Connections
Connection Settings Bootstrap File
• Users set Cisco WebEx as the value of the • Specify WebEx as value of the TYPE
Server type property in the Connection argument during installation.
Settings window. • The installation program then saves that
value to a bootstrap file.
• Cisco Jabber for Windows gets the value
from the bootstrap file when it starts.
www.flane.com.au
Connection Settings
Users set Cisco WebEx as the value of the Server type property in the Connection Settings
window. CiscoJabber for Windows can then connect to the Cisco WebEx Messenger service to
authenticate users and retrieve configuration and services.
Bootstrap File
You specify WebEx as value of the TYPE argument during installation.
The installation program then saves that value to a bootstrap file. Cisco Jabber for Windows
gets the value from the bootstrap file when it starts. It can then connect to the Cisco WebEx
Messenger service to authenticate users and retrieve configuration and services.
Configure Directory Integration with On-
Premises Servers
When you set up an on-premises deployment, you should configure Cisco Unified
Communications Manager to do both of the following:
Synchronize with the directory server.
Authenticate with the directory server.
By default Cisco Jabber for Windows automatically discovers the directory

service and connects to a Global Catalog in the domain.
www.flane.com.au
Directory Service in On-Premises Deployments

Cisco Jabber for Windows searches the directory to add contacts and to resolve contacts and
phone numbers.
To successfully deploy Cisco Jabber for Windows in an on-premises deployment, you should
understand the directory infrastructure of the environment into which you plan to install the
client. You can then choose a contact source that is most suited to that environment.
This section explains the different contact sources you can choose and what, if any,
configuration you must perform to deploy Cisco Jabber for Windows with each contact source.
Configure Directory Integration with On-Premises Servers

When you set up an on-premises deployment, you should configure Cisco Unified
Communications Manager to do both of the following:
Synchronizing with the directory server replicates contact data from your directory to Cisco
Enabling authentication with the directory server lets Cisco Unified Communications Manager
proxy authentication from the client to the directory server. In this way, users authenticate with
the directory server, not with Cisco Unified Communications Manager or a presence server.
Contact Sources
You can use either of the following as the contact source for an
on-premises deployment:
Enhanced Directory Integration
Enhanced Directory Integration (EDI) is an LDAP-based contact source.
Cisco Unified Communications Manager User Data Service

Cisco Unified Communications Manager User Data Service (UDS) is a
contact source on Cisco Unified Communications Manager.
www.flane.com.au
Contact Sources
You can use either of the following as the contact source for an on-premises deployment
Enhanced Directory Integration (EDI) is an LDAP-based contact source.
Cisco Unified Communications Manager User Data Service
Cisco Unified Communications Manager User Data Service (UDS) is a contact source on Cisco
Enhanced Directory Integration (EDI)
Cisco Jabber for Windows by default uses auto-discovery for directory access.
Clients connect to a Global Catalog server in the current domain (Windows selects exact
GC); If workstation isn’t domain member, custom configuration can be used.
Client uses encrypted authentication to directory based on current logged on user

(workstation)
EDI can be administratively configured for alternative LDAP / domain environments
Active
Directory
DNS 2. Client uses ASDI to
connect to directory
1. Workstation discovered 2. Authenticated using existing

DC/GC using DNS SRV domain authentication
www.flane.com.au

EDI uses native Microsoft Windows APIs to retrieve contact data from the directory service.
The following are the default settings for on-premises deployments with EDI:
Cisco Jabber for Windows integrates with Active Directory as the contact source.
Cisco Jabber for Windows automatically discovers and connects to a Global Catalog.
Enhanced Directory Integration (EDI) (Cont.)
Connection Credentials:
By default, the client uses MS Windows usernames and passwords to connect to the directory
service.
You can pecify a connection username and password to access a directory service other than EDI
or to use a set of common credentials for all users.
Domain Name Retrieval:

Cisco Jabber for Windows retrieves the fully qualified DNS domain from the USERDNSDOMAIN
environment variable on the client workstation.
After Cisco Jabber for Windows gets the DNS domain, it can locate the Domain Name Server and
retrieve SRV records.
Cisco Jabber for Windows can automatically discover the directory server if:
The workstation on which you install Cisco Jabber for Windows is on the Windows domain.
Cisco Jabber for Windows can retrieve the address of the directory server from a DNS SRV record.
Global Catalog: _gc._msdcs._tcp.domain.com
Domain Controller LDAP-based directory servers: _ldap._msdcs._tcp.domain.com
www.flane.com.au
Connection Credentials
By default, the client uses Microsoft Windows usernames and passwords to connect to the
directory service.
You can specify a connection username and password to access a directory service other than
EDI or to use a set of common credentials for all users.
The UseWindowsCredentials parameter specifies if you use Microsoft Windows credentials to
connect to your directory.
Set credentials with the following parameters:
ConnectionUsername
ConnectionPassword
Domain Name Retrieval
Cisco Jabber for Windows retrieves the fully qualified DNS domain from the
USERDNSDOMAIN environment variable on the client workstation.
After Cisco Jabber for Windows gets the DNS domain, it can locate the Domain Name Server
and retrieve SRV records.
In some instances, the value of the USERDNSDOMAIN environment variable does not resolve
to the DNS domain that corresponds to the domain of the entire forest. For example, when an
organization uses a sub-domain or resource domain. In this case, the USERDNSDOMAIN
environment variable resolves to a child domain, not the parent domain. As a result, Cisco
Jabber for Windows cannot access information for all users in the organization.
Cisco Jabber for Windows can automatically discover and connect to the directory server if:
The workstation on which you install Cisco Jabber for Windows is on the Windows
domain.
Cisco Jabber for Windows can retrieve the address of the directory server from a DNS
SRV record.
Enhanced Directory Integration (EDI)
(Cont.)
Attributes on the Directory Server
sAMAccountName
telephoneNumber
Additionally, ensure you index the following attributes for secondary number
queries:
otherTelephone
mobile
homePhone
msRTCSIP-PrimaryUserAddress
www.flane.com.au
You must index attributes on your directory server so that Cisco Jabber for Windows can
resolve contacts.
If you use the default attribute mappings, ensure the following attributes are indexed:
sAMAccountName
telephoneNumber
Additionally, ensure you index the following attributes for secondary number queries:
otherTelephone
mobile
homePhone
By default secondary number queries are enabled in Cisco Jabber for Windows. You can disable
secondary number queries with the DisableSecondaryNumberLookups parameter.
msRTCSIP-PrimaryUserAddress
You should index msRTCSIP-PrimaryUserAddress for intradomain federation only.
Because the client connects to a Global Catalog server by default, you must ensure that all
attributes reside on your Global Catalog server. You can replicate attributes to a Global Catalog
server using an appropriate tool such as the Microsoft Active Directory Schema snap-in.
Replicating attributes to your Global Catalog server generates traffic between Active Directory
servers in the domain. For this reason, you should replicate attributes to your Global Catalog
server at a time when network traffic can handle extra load.
If you do not want to replicate attributes to a Global Catalog server, you can configure Cisco
Jabber for Windows to connect to a Domain Controller. However, the client queries single
domains only when it connects to a Domain Controller.
EDI - Contact Photo Retrieval Methods
URI substitution
Cisco Jabber for Windows dynamically builds a URL to contact photos with a directory
attribute and a URL template.
<Directory>
<DirectoryServerType>EDI</DirectoryServerType>
<BusinessPhone>aNonDefaultTelephoneNumberAttribute</BusinessPhone>
<PhotoUriSubstitutionEnabled>true</PhotoUriSubstitutionEnabled>
<PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSubstitutionToken>
<PhotoUriWithToken>http://staffphoto.example.com/sAMAccountName.jpg</PhotoUriWit
hToken>
</Directory>
www.flane.com.au
Cisco Jabber for Windows retrieves and displays contact photos with the following methods:
URI substitution
Cisco Jabber for Windows dynamically builds a URL to contact photos with a directory
attribute and a URL template.
To use this method, set the following values in your configuration file:
1. Specify true as the value of the PhotoUriSubstitutionEnabled parameter.
2. Specify a directory attribute to use as a dynamic token as the value of the
PhotoUriSubstitutionToken parameter; for example,
<PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSu
bstitutionToken>
3. Specify the URL and the dynamic token as the value of the PhotoUriWithToken
parameter; for example,
<PhotoUriWithToken>http://staffphoto.example.com/sAMA
ccountName.jpg</PhotoUriWithToken>
With the example values in the preceding steps, the sAMAccountName attribute might resolve
to msmith in your directory. Cisco Jabber for Windows then takes this value and replaces the
token to build the following URL: http://staffphoto.example.com/msmith.jpg.
EDI - Contact Photo Retrieval Methods (Cont.)
Binary objects
Cisco Jabber for Windows retrieves the binary data for the photo from your
database.
<PhotoSource>jpegPhoto</PhotoSource>
PhotoURL attribute
Cisco Jabber for Windows retrieves a URL from a directory attribute.

<PhotoSource>photoUri</PhotoSource>
www.flane.com.au
Binary objects
Cisco Jabber for Windows retrieves the binary data for the photo from your database.
To use this method to retrieve contact photos, specify the attribute that contains the binary data
as the value of the PhotoSource parameter in the configuration; for example,
<PhotoSource>jpegPhoto</PhotoSource>
PhotoURL attribute
Cisco Jabber for Windows retrieves a URL from a directory attribute.
To use this method to retrieve contact photos, specify the attribute that contains the photo URL
as the value of the PhotoSource parameter in the configuration; for example,
<PhotoSource>photoUri</PhotoSource>
Cisco Unified Communications Manager User
Data Service
UDS is a REST interface on Cisco Unified

Communications Manager that provides contact
resolution.
You can synchronize contact data into Cisco UCM

from a directory server.
www.flane.com.au
UDS is a REST interface on Cisco Unified Communications Manager that provides contact
resolution. You synchronize contact data into Cisco Unified Communications Manager from a
directory server. Cisco Jabber for Windows then automatically retrieves that contact data directly
from UDS.
A known issue in UDS exists on versions of Cisco Unified Communications Manager lower than
8.6.2.
This known issue prevents successful contact resolution. As a result, Cisco Jabber for Windows
supports UDS on Cisco Unified Communications Manager version 8.6.2 or later.
Enable Integration with UDS
1. Create your directory source in Cisco Unified Communications Manager.
2. Synchronize the contact data to Cisco Unified Communications Manager.
3. Provision users with CCMCIP profiles on Cisco Unified Communications IM and

Presence.
www.flane.com.au
Enable Integration with UDS

To enable integration with UDS, perform the following steps:
Procedure
Step 1 Create your directory source in Cisco Unified Communications Manager.
Step 2 Synchronize the contact data to Cisco Unified Communications Manager.
After the synchronization occurs, your contact data resides in Cisco Unified Communications
Manager.
Step 3 Provision users with CCMCIP profiles on Cisco Unified Presence or Cisco Unified
Communications IM and Presence.
The client requires a CCMCIP profile that contains the primary Cisco Unified Communications
Manager server address. The client uses the CCMCIP profile to locate Cisco Unified
Communications Manager and resolve contacts with UDS.
Enable Integration with UDS (Cont.)
4. Specify UDS as the value of the DirectoryServerType parameter in your

configuration file.
<Directory>
<DirectoryServerType>UDS</DirectoryServerType>
</Directory>
5. Configure the client to retrieve contact photos with UDS.

<PhotoUriWithToken>http://server_name.domain/%%uid%%.jpg</PhotoUriWithToken>
www.flane.com.au
Step 4 Specify UDS as the value of the DirectoryServerType parameter in your configuration
file.
The following is an example configuration where UDS is the directory server type:
<Directory>
</Directory>
Step 5 Configure the client to retrieve contact photos with UDS.
The following is an example configuration for contact photo retrieval:
<PhotoUriWithToken>http://server_name.domain/%%uid%%.jpg</P
hotoUriWithToken>
Authentication Options
Jabber provide options to integrate authentication in existing authentication realms.
User accounts can also be imported/sync from organization directory into Unified CM
or WebEx Connect user database
Cloud
CUCM Local On Premises Authentication
Authentication (CUCM IM & Presence)
Cisco Collaboration
Cloud
LDAP Authentication SSO Authentication

(via Active Directory) (SAML 2.0 Compliant or WS federation 1.0)
OrgAdmin must be provisioned for SSO
www.flane.com.au
Summary
Cisco Jabber for Windows deployments models:

On-Premises (Full UC, Phone mode)
Cloud Based
Hybrid Cloud Based
Cisco Jabber for Windows start up sequence
Cisco Jabber for Windows Directory integrations:

EDI
UDS
32 www.flane.com.au
Lesson 2
Install and Configure Cisco

Jabber for Winodws
Plan for Installation - Hardware
Requirements
Installed RAM
1.87 GB RAM on Microsoft Windows XP 32 bit with Service Pack 3
2 GB RAM on Microsoft Windows 7
Free Disk Space

256 MB
CPU Speed and Type

Mobile AMD Sempron Processor 3600+ 2 GHz
Intel Core2 CPU T7400 @ 2. 16 GHz
GPU
Directx 9 on Microsoft Windows XP 32 bit with Service Pack 3
Directx 11 on Microsoft Windows 7
www.flane.com.au
Hardware Requirements
Installed RAM
• 1.87 GB RAM on Microsoft Windows XP 32 bit with Service Pack 3
• 2 GB RAM on Microsoft Windows 7
Free Physical Memory
• 128 MB
Free Disk Space
• 256 MB
CPU Speed and Type
• Mobile AMD Sempron Processor 3600+ 2 GHz
• Intel Core2 CPU T7400 @ 2. 16 GHz
GPU
• Directx 9 on Microsoft Windows XP 32 bit with Service Pack 3
• Directx 11 on Microsoft Windows 7
I/O Ports
• USB 2.0 for USB camera and audio devices.
Plan for Installation - Software
Requirements
Operating Systems Microsoft Windows 7 32 bit
Microsoft Windows 7 64 bit
Microsoft Windows Vista 32 bit
Microsoft Windows XP 32 bit with Service Pack 3
On-Premises Servers Cisco Unified Communications Manager version 7.1(4) or later

Cisco IM and Presence version 8.0.3 or later
Cisco Unity Connection version 8.5 or later
Cisco WebEx Meetings Server version 1.1 or later
Cloud-Based Servers Cisco WebEx Messenger service

Cisco WebEx Administration Tool, minimum supported version is 7.5
Cisco WebEx Meeting Center, minimum supported versions are as follows:
Version T26L with Service Pack EP 20
Version T27L with Service Pack 9
Cisco WebEx Meetings (WebEx 11)
www.flane.com.au
Operating Systems
You can install Cisco Jabber for Windows on the following operating systems:
Microsoft Windows XP 32 bit with Service Pack 3
On-Premises Servers
Cisco Jabber for Windows supports the following on-premises servers:
Cisco Unified Communications Manager version 7.1(4) or later
Cisco Unified Presence version 8.0.3 or later
Cisco Unity Connection version 8.5 or later
Cisco WebEx Meetings Server version 1.1 or later
Cisco Jabber for Windows supports the following features with Cisco Unified
Survivable Remote Site Telephony version 8.5:
Basic call functionality
Ability to hold and resume calls
Cloud-Based Servers
Cisco Jabber for Windows supports integration with the following hosted servers:
Cisco WebEx Messenger service
Cisco WebEx Administration Tool, minimum supported version is 7.5
Cisco WebEx Meeting Center, minimum supported versions are as follows:
Version T26L with Service Pack EP 20
Version T27L with Service Pack 9
Cisco WebEx Meetings (WebEx 11)
Requirements (Cont.)
Directory Servers Active Directory for Windows Server 2003 R2
Active Directory Domain Services for Windows Server 2008 R2
UDS is supported on Cisco Unified Communications Manager version 8.6.2 or
later.
OpenLDAP
Active Directory Lightweight Directory Service (AD LDS) or Active Directory
Application Mode (ADAM)
Microsoft Internet Microsoft Internet Explorer 7 or later
Explorer
Microsoft Office Microsoft Office 2007 32 bit

Microsoft Office 2010 32 bit
Microsoft Exchange 2007
www.flane.com.au
Directory Servers
You can use the following directory servers with Cisco Jabber for Windows:
Active Directory for Windows Server 2003 R2
Active Directory Domain Services for Windows Server 2008 R2
Cisco Unified Communications Manager User Data Service UDS is supported on
Cisco Unified Communications Manager version 8.6.2 or later.
OpenLDAP
Active Directory Lightweight Directory Service (AD LDS) or Active Directory
Application Mode (ADAM)
Restriction:
Directory integration with OpenLDAP, AD LDS, or ADAM requires you to define specific
parameters in a Cisco Jabber for Windows configuration file. See LDAP Directory Servers for
more information.
Microsoft Internet Explorer

Cisco Jabber for Windows requires Microsoft Internet Explorer 7 or later. Cisco Jabber for
Windows uses the Internet Explorer rendering engine to display HTML content.
Attention:
Cisco Jabber for Windows requires Internet Explorer active scripting to render instant messages.
See the following Microsoft documentation for instructions to enable active scripting: http://
windows.microsoft.com/en-US/windows/help/genuine/ie-active-script
Microsoft Office
Cisco Jabber for Windows supports integration with the following software:
Local Contacts in Microsoft Outlook

Cisco Jabber for Windows lets users search for and add local contacts in Microsoft Outlook.
To search for local contacts in Microsoft Outlook with the client, users must have profiles set in
Microsoft Outlook. In addition, users must do the following:
1. Select File > Options.
2. Select the Integration tab.
3. Select either None or Microsoft Outlook.
To add local Microsoft Outlook contacts to contact lists in the client, local contacts must have
instant message addresses in Microsoft Outlook.
To show contact photos in the client interface, local contacts in Microsoft Outlook must have
instant message addresses.
To communicate with local contacts in Microsoft Outlook using the client, local contacts must
have the relevant details. To send instant messages to contacts, local contacts must have an instant
message address. To call contacts in Microsoft Outlook, local contacts must have phone numbers.
Calendar Integration Microsoft Outlook 2007 32 bit
Microsoft Outlook 2010 32 bit
IBM Lotus Notes 8.5.1 32 bit
Google Calendar
Virtual Environments Citrix XenDesktop 5.0
Citrix XenDesktop 5.5
Citrix XenApp 5.0 Feature Pack 3 Enterprise Edition for Windows Server 2008
Service Pack 2 64 bit, published desktop
Citrix XenApp 6.0 Enterprise Edition for Windows 2008 R2 64 bit, published
desktop
desktop
VMWare View Connection Manager 4.6.1.640196 with
VMWare Agent 5.0
VMWare Client 4.6.1
VMWare View Connection Manager 5.1.0704644 with
VMWare Agent 5.1.0704644
VMWare Client 5.1.0704644
www.flane.com.au
Calendar Integration
You can use the following client applications for calendar integration:
Google Calendar
Virtual Environments
You can deploy Cisco Jabber for Windows in virtual environments using the following software:
Citrix XenApp 5.0 Feature Pack 3 Enterprise Edition for Windows Server 2008
Service Pack 2 64 bit, published desktop
desktop
desktop
VMWare View Connection Manager 4.6.1.640196 with
o VMWare Agent 5.0
o VMWare Client 4.6.1
VMWare View Connection Manager 5.1.0704644 with
o VMWare Agent 5.1.0704644
o VMWare Client 5.1.0704644
Supported Functionality
Cisco Jabber for Windows supports the following functionality in virtual environments:
Instant messaging and presence with other Cisco Jabber clients Cisco Jabber for
Windows does not support instant messaging and presence with other applications such
as Microsoft Outlook.
Desk phone control.
Supported Codecs
Supported Audio Codecs Supported Video Codecs

G.722.1 H.264/AVC
G.722.1 32k
G.722.1 24k
G.711
G.711 A-law
G.711 u-law
G.729a
www.flane.com.au
Supported Codecs
Supported Audio Codecs
g.722.1
g.722.1 32k
g.722.1 24k
o g.722.1 is supported on Cisco Unified Communications Manager 8.6.1 or
later.
g.711
o g.711 A-law
o g.711 u-law
g.729a
Supported Video Codecs
H.264/AVC
Bandwidth Requirements
Bit Rates for Audio
Codec RTP payload in kilobits Actual bitrate Notes

(kbits) per second (kbits per second)
G.722.1 24/32 54/62 High quality
compressed
G.711 64 80 Standard
uncompressed
G.729a 8 38 Low quality
compressed
www.flane.com.au
This table describes bit rates for audio.
Bandwidth Requirements (Cont.)
Bit Rates for Video
Resolution Pixels Measured bit rate (kbits

per second) with g.711
audio
w144p 256 x 144 156
w288p 512 x 288 320
This is the default size of the video
rendering window for Cisco Jabber
for Windows
w448p 768 x 448 570
w576p 1024 x 576 890
720p 1280 x 720 1300
www.flane.com.au
This table describes bit rates for video with g.711 audio.
Bandwidth Requirements (Cont.)
Video Rate Adaptation
Video rate adaptation dynamically increases or decreases video bit rate

throughput to handle real-time variations on available IP path bandwidth.
Cisco Jabber for Windows users should expect video calls to begin at lower
resolution and scale upwards to higher resolution over a short period of time
Cisco Jabber for Windows saves history so that subsequent video calls
should begin at the optimal resolution.
www.flane.com.au
Video Rate Adaptation

Cisco Jabber for Windows uses video rate adaptation to negotiate optimum video quality. Video
rate adaptation dynamically increases or decreases video bit rate throughput to handle real-time
variations on available IP path bandwidth.
Cisco Jabber for Windows users should expect video calls to begin at lower resolution and scale
upwards to higher resolution over a short period of time. Cisco Jabber for Windows saves history
so that subsequent video calls should begin at the optimal resolution.
Cisco Media Services Interface
Cisco Media Services Interface provides a Microsoft Windows service that works with Cisco
Prime Collaboration Manager and Cisco Medianet-enabled routers to ensure that Cisco Jabber for
Windows can send audio media and video media on your network with minimum latency or
packet loss.
Before Cisco Jabber for Windows sends audio media or video media, it checks for Cisco Media
Services Interface.
If the service exists on the computer, Cisco Jabber for Windows provides flow information to
Cisco Media Services Interface. The service then signals the network so that routers classify
the flow and provide priority to the Cisco Jabber for Windows traffic.
If the service does not exist, Cisco Jabber for Windows does not use it and sends audio media
and video media as normal.
You must install Cisco Media Services Interface separately and ensure your network is enabled
for Cisco Medianet. You must also install Cisco Prime Collaboration Manager and routers
enabled for Cisco Medianet.
Install Cisco Jabber for Windows
Installation Options:
Use the Command Line
Run the MSI Manually
Create a Custom Installer
Deploy with Group Policy
www.flane.com.au
Installation Options
Cisco Jabber for Windows provides an MSI installation package. You can use this installation
package in the following ways:
Use the Command Line
Specify arguments in a command line window to set installation properties.
Choose this option if you plan to install multiple instances.
Run the MSI Manually
Run the MSI manually on the file system of the client workstation and then specify
connection properties when you start the client.
Choose this option if you plan to install a single instance for testing or evaluation
purposes.
Create a Custom Installer
Open the default installation package, specify the required installation properties, and
then save a custom installation package.
Choose this option if you plan to distribute an installation package with the same
installation properties.
Deploy with Group Policy
Install the client on multiple computers in the same domain.
Configure Cisco Jabber for Windows
The client retrieves configuration settings from XML files that reside on your
TFTP server.
Configure Cisco Jabber for Windows if:

The client workstation is not on the Windows domain.
You connect to one of the following as the contact source (Domain Controller ,LDAP
directory and UDS)
You need to configure attribute mappings.
You plan to set up intradomain federation.
You plan to deploy custom content such as:
Custom embedded tabs
Automatic updates
Problem reporting
You plan to set policies for your users.
www.flane.com.au
Configuration Overview
The client retrieves configuration settings from XML files that reside on your TFTP server.
Understand when you should create a custom configuration and learn about the different types of
configuration files you can create.
When to Configure Cisco Jabber for Windows
In most environments, Cisco Jabber for Windows does not require any configuration to connect to
the contact source or other services. You should create a configuration file for Cisco Jabber for
Windows only if the default configuration does not suit your environment or you require custom
configuration.
You should configure Cisco Jabber for Windows if:
The client workstation is not on the Windows domain.
You connect to one of the following as the contact source:
Domain Controller
LDAP directory server such as OpenLDAP or AD LDS
UDS
You need to configure attribute mappings.
You plan to set up intradomain federation.
You plan to deploy custom content such as:
Custom embedded tabs
Automatic updates
Problem reporting
You plan to set policies for your users.
Configuration Files
Global Configuration Files jabber-config.xml

Cisco Jabber for Windows downloads the global configuration file from your TFTP
server during the login sequence.
Group Configuration Files

Subsets of Cisco Jabber for Windows users.
Takes priority over global configuration files.
Cisco Jabber for Windows retrieves group configuration files after users sign in to their
phone account in the client for the first time.
Cisco Jabber for Windows then prompts the users to sign out.
During the second login sequence, Cisco Jabber for Windows downloads the group
configuration file from your TFTP server.
www.flane.com.au
Global Configuration Files

Global configuration files apply to all Cisco Jabber for Windows users. Cisco Jabber for
Windows downloads the global configuration file from your TFTP server during the login
sequence.
The default name for the global configuration file is jabber-config.xml.
Group Configuration Files
Group configuration files apply to subsets of Cisco Jabber for Windows users. Group
configuration files take priority over global configuration files.
Cisco Jabber for Windows retrieves group configuration files after users sign in to their phone
account in the client for the first time. Cisco Jabber for Windows then prompts the users to sign
out. During the second login sequence, Cisco Jabber for Windows downloads the group
configuration file from your TFTP server.
Cisco Jabber for Windows loads group configuration files as follows:
Users are signed in and use software phones for calls
1. Cisco Jabber for Windows notifies the users about the change to their configuration
settings.
2. Users sign out.
3. Users sign in and then Cisco Jabber for Windows loads the group configuration settings.
Users are signed in and use desk phones for calls
1. Users sign out.
2. Users sign in and then Cisco Jabber for Windows notifies the users about the change to
their configuration settings.
3. Users sign out.
4. Users sign in and then Cisco Jabber for Windows loads the group configuration settings.
If users select the option to use software phones for calls before they sign out, Cisco
Jabber for Windows notifies the users to sign out and then sign in again to load the group
configuration settings.
Group Configuration File Names
You specify the name of the group configuration files in the Cisco Support Field on the CSF
device configuration in Cisco Unified Communications Manager.
If you remove the name of the group configuration file in the CSF device configuration on Cisco
Unified Communications Manager, Cisco Jabber for Windows detects the change, prompts the
users to sign out, and loads the global configuration file. You can remove the name of the group
configuration file in the CSF device configuration by deleting the entire
configurationFile=group_configuration_file_name.xml string or by deleting the group
configuration filename from the string.
If users have desk phone devices only, use the following command line argument to specify
unique names configuration files for different groups:
TFTP_FILE_NAME
Create Global Configurations
Custom configuration files in on-premises and hybrid cloud-based deployments.

1. Create a file named jabber-config.xml with any text editor.
2. Define the required configuration parameters in jabber-config.xml.
3. Host the group configuration file on your TFTP server.
Software Updates > TFTP File Management
www.flane.com.au

Configure the client for all users in your deployment.
Procedure
Step 1 Create a file named jabber-config.xml with any text editor.
Use lowercase letters in the filename.
Use utf-8 encoding.
Step 2 Define the required configuration parameters in jabber-config.xml.
If the structure of your configuration file is not valid, Cisco Jabber for Windows cannot read the
values you set. Review the XML samples in this chapter for more information.
Step 3 Host the group configuration file on your TFTP server.
Create Group Configurations
1. Create an XML group configuration file with any text editor. For example,
jabber-groupa-config.xml.
2. Define the required configuration parameters in the group configuration file.
3. Specify the name of the group configuration file in Cisco UCM:

Device > Phone:
4. Host the group configuration file on your TFTP server.
www.flane.com.au
Create Group Configurations

Apply different client configurations to different sets of users.
If you provision users with CSF devices, you specify the group configuration file names in the
Cisco Support Field field on the device configuration.
If users do not have CSF devices, set a unique configuration file name for each group during
installation with the TFTP_FILE_NAME argument.
Procedure
Step 1 Create an XML group configuration file with any text editor.
The group configuration file can have any appropriate name; for example, jabber-groupa-
config.xml.
Use lowercase letters in the filename.
Use utf-8 encoding.
Step 2 Define the required configuration parameters in the group configuration file.
If the structure of your configuration file is not valid, Cisco Jabber for Windows cannot read the
values you set. Review the XML samples in this chapter for more information.
Step 3 Specify the name of the group configuration file.
a. Open the Cisco Unified CM Administration interface.
b. Select Device > Phone.
c. Find and select the appropriate CSF device to which the group configuration applies.
The Phone Configuration window opens.
d. Navigate to Product Specific Configuration Layout > Desktop Client Settings.
e. Enter configurationfile=group_configuration_file_name.xml in the Cisco Support
Field field. For example, enter the following: configurationfile=groupa-
config.xml
Use a semicolon to delimit multiple entries. Do not add more than one group
configuration file. The client uses only the first group configuration in the Cisco
Support Field field.
If you host the group configuration file on your TFTP server in a location other than
the default directory, you must specify the path and the filename; for example,
configurationfile=/customFolder/groupa-config.xml.
f. Select Save.
Step 4 Host the group configuration file on your TFTP server.
Configuration File Structure
<?xml version="1.0" encoding="utf-8"?>
XML <config version="1.0">
Declaration <Client> Root Element
<parameter_name>value</parameter_name>
</Client>
<Directory>
</Directory>
<Options>
</Options>
<Presence>
Group <parameter_name>value</parameter_name>
</Presence>
Elements <Policies>
</Policies>
<Phone>
</Phone>
<Voicemail>
</Voicemail>
</config>
www.flane.com.au
You create Cisco Jabber for Windows configuration files in XML format. The XML
configuration files contain the following elements:
XML Declaration
Your configuration file must conform to XML format standards. The first element in your
configuration file must be a declaration as in the following example:
Root Element
The root element contains all group elements. The root element must also contain a version
attribute as in the following example:
<config version="1.0">
</config>
Group Elements
Group elements contain the configuration parameters and values that you specify.
Client Configuration Parameters
Parameter Description
ProductMode Specifies the Cisco Jabber for Windows product mode.
PrtLogServerUrl Specifies the custom script for submitting problem reports.
UpdateUrl Specifies the URL to the automatic updates XML definition
file on your HTTP server. Cisco Jabber for Windows uses
this URL to retrieve the update XML file from your HTTP
server.
jabber-plugin-config Contains plug-in configuration elements.
You can define custom embedded tabs to display HTML
content in Cisco Jabber for Windows.
Forgot_Password_URL Specifies the URL of your web page for users to reset or
retrieve forgotten passwords.
In hybrid cloud-based deployments, you should use the Cisco
WebEx Administration Tool to direct users to the web page
to reset or retrieve forgotten passwords.
<Client>
<PrtLogServerUrl>http://server_name.domain.com/prt_script.php</PrtLogServerUrl>
<UpdateUrl>http://server_name.domain.com/update.xml</UpdateUrl>
<Forgot_Password_URL>http://server_name.domain.com/password.html</Forgot_Password_URL>
www.flane.com.au
This table describes the parameters you can specify within the Client element.
Directory Configuration Parameters
1. Domain Controller Connection
<Directory>
<ConnectionType>1</ConnectionType>
</Directory>
2. Manual Server Connection

<Directory>
<PrimaryServerName>primary-server-name.domain.com</PrimaryServerName>
<ServerPort1>1234</ServerPort1>
<SecondaryServerName>secondary-server-name.domain.com</SecondaryServerName>
<ServerPort2>5678</ServerPort2>
</Directory>
3. UDS Integration
<Directory>
<PhotoUriWithToken>http://server-name/%%uid%%.jpg</PhotoUriWithToken>
</Directory>
www.flane.com.au
Domain Controller Connection

To connect to a Domain Controller, set the following parameters:
Parameter Value
Parameter Value
DirectoryServerType EDI
ConnectionType 1
Manual Server Connection

To configure a manual connection to a directory server, set the following parameters:
Parameter Value
DirectoryServerType EDI
PrimaryServerName FQDN
IP address
ServerPort1 Port number
SecondaryServerName FQDN
IP address
ServerPort2 Port number
UDS Integration
To integrate with UDS, set the following parameters:
Parameter Value
DirectoryServerType UDS
PhotoUriWithToken Contact photo URL
Options Configuration Parameters
Set_Status_Away_On_Inactive Specifies if the availability status changes to Away when users are
inactive.
Set_Status_Inactive_Timeout Sets the amount of time, in minutes, before the availability status
changes to Away if users are inactive.
Set_Status_Away_On_Lock_OS Specifies if the availability status changes to Away when users lock
their operating systems.
StartCallWithVideo Specifies how calls start when users place calls. Calls can start with
audio only or audio and video.
Start_Client_On_Start_OS Specifies if the client starts automatically when the operating
system starts.
AllowUserCustomTabs Specifies if users can create their own custom embedded tabs.
ShowContactPictures Specifies if contact pictures display in the contact list.
ShowOfflineContacts Specifies if offline contacts display in the contact list.
DockedWindowVisible Specifies if the docked window displays when the client starts.
DockedWindowPosition Sets the position of the docked window on the user's screen.
www.flane.com.au
Options Parameters
Options parameters let you modify the default values for certain settings in the Options window
in the client.
Users can also specify their own values in the Options window and override the defaults that you
set in your configuration file.
Phone Configuration Parameters
TftpServer1 Specifies the address of the primary Cisco Unified Communications Manager TFTP
service where device configuration files reside.
TftpServer2 Specifies the address of the secondary Cisco Unified Communications Manager
TFTP service.
CtiServer1 Specifies the address of the primary CTI server.
You should specify a CTI server address in the client configuration if users have
desk phone devices.
CtiServer2 Specifies the address of the secondary CTI server.
CcmcipServer1 Specifies the address of the primary CCMCIP server.
This parameter is required only if the address of your CCMCIP server is not the
same as the TFTP server address. If the address of the CCMCIP server is the same
as the TFTP server address, the client can use the TFTP server address to connect
to the CCMCIP server.
CcmcipServer2 Specifies the address of the secondary CCMCIP server.
www.flane.com.au
Phone Parameters
This table describes the parameters you can specify within the Phone element:
On-premises Policies Configuration
Parameters
Screen_Capture_Enabled Specifies if users can take screen captures.
File_Transfer_Enabled Specifies if users can transfer files to each other.
Disallowed_File_Transfer_Types Restricts users from transferring specific file types.
www.flane.com.au
On-Premises Policies
This table describes the parameters you can specify within the Policies element in on-premises.
Note: You can disable file transfers and screen captures on Cisco Unified Communications IM
and Presence with the Enable file transfer parameter.
If you disable the setting on the server, you must also disable file transfers and screen captures in
the client configuration.deployments.
Common Policies Configuration
Parameters
EnableVideo Enables or disables video capabilities.
InitialPhoneSelection Sets the phone type for users when the client starts for the
first time. Users can change their phone type after the initial start.
The client then saves the user preference and uses it for
subsequent starts.
UserDefinedRemoteDestinations Lets users add, edit, and delete remote destinations through the
client interface.
enableLocalAddressBookSearch Lets users search for and add local Microsoft Outlook contacts to
their contact lists.
EnableAccessoriesManager Enables the accessory manager API in the client. This API lets
accessory vendors create plugins to enable call management
functionality for devices such as headsets.
ForceFontSmoothing Specifies if the client applies anti-aliasing to smooth text.
www.flane.com.au
Common Policies
This table describes the parameters you can specify within the Policies element in both on-
premises deployments and hybrid cloud-based deployments.
Cisco WebEx Policies

In hybrid cloud-based deployments, you can set policies for the client through the Cisco WebEx
Administration Tool.
Service Credentials Parameters
You can specify service credentials parameters in your configuration so that
users do not need to authenticate with certain services.
VoiceMailService_UseCredentialsFrom Specifies that the client uses the phone service
credentials to access voicemail services.
Ensure the user's phone service credentials

match their voicemail service credentials. If you
set this configuration, users cannot specify
voicemail service credentials in the client
interface.
This parameter is not set by default.

<config version="1.0">
<Voicemail>
<VoicemailService_UseCredentialsFrom>phone</VoicemailService_UseCredentialsFrom>
</Voicemail>
</config>
www.flane.com.au
Service Credentials Parameters

You can specify service credentials parameters in your configuration so that users do not need to
authenticate with certain services.
Voicemail Service Credentials
You can specify the following parameter to configure voicemail service credentials within the
Voicemail element
Custom Embedded Tabs
Custom Embedded Tab Definitions
Custom embedded tabs display HTML content in the client interface using the
Microsoft Internet Explorer rendering engine.
<Client>
<jabber-plugin-config>
<browser-plugin>
<page refresh="" preload="">
<tooltip>Cisco WebEx</tooltip>
<icon></icon>
<url>http://www.webex.com/</url>
</page>
</browser-plugin>
</jabber-plugin-config>
</Client>
www.flane.com.au
Custom Embedded Tabs

Custom embedded tabs display HTML content in the client interface using the Microsoft Internet
Explorer rendering engine.
User Custom Tabs
Users can create their own custom embedded tabs through the client user interface.
You must enable users to create custom embedded tabs. Set true as the value for the
AllowUserCustomTabs parameter in your configuration file as follows:
<Options>
<AllowUserCustomTabs>true</AllowUserCustomTabs>
</Options>
Develop with Cisco Jabber Web SDK
Customers can also build and deploy presence and IM-enabled applications
using the Jabber Web Software Development Kit (SDK).
Enables you to integrate Cisco UCM capabilities in web applications.
To integrate IM capabilities in a web application, you use the Cisco AJAX XMPP
Library (CAXL).
CAXL is a client-side JavaScript library that runs in a web browser and sends and
receives XMPP messages as HTTP POSTs.
www.flane.com.au
The Cisco AJAX XMPP Library (CAXL) is an API that provides a jump start for developers
writing Extensible Messaging and Presence Protocol (XMPP)-enabled web applications.
CAXL is ideal for companies that are looking to leverage the Cisco WebEx Collaboration Cloud
and integrate presence and messaging into their own custom web-based applications. With the
CAXL, developers can:
Embed a customer support portal into a company website
Add instant messaging capabilities to a gaming application
Add presence information and messaging capability to custom applications
The Cisco AJAX XMPP Library provides a foundation for developing web-based
applications that use the XMPP protocol. For detailed information on the XMPP standard,
please visit http://xmpp.org The AJAX library is a JavaScript XMPP client library that is
used for instant messaging integration, presence, and roster services from the Cisco WebEx
Collaboration Cloud. CAXL includes the following components:
jQuery: An open-source library for searching, traversing, and manipulating the browser's
Document Object Model (DOM)
CAXL Core: A high-level API for messaging and presence
CAXL UI: HTML UI components built on top of the CAXL Core API click to enlarge
The library can be used purely as an API or as a web UI, or both. The core CAXL API does not
require the CAXL UI. The internals of the library use jQuery for low-level JavaScript tasks, but
on the library does not depend on any JavaScript UI framework for the UI components. The Cisco
AJAX XMPP library is an object-oriented, client-side library that communicates to a BOSH
server component. BOSH (Bidirectional-streams Over Synchronous HTTP) technology is used as
an HTTP binding for XMPP communications and is useful in situations where a device or client
is unable to maintain a long-lived TCP connection to an XMPP server (for example, as in a web
browser).
Summary
Cisco Jabber for Windows installation requirements.
Cisco Jabber for Windows bandwidth requirements
Cisco Jabber for Windows configuration file structure and parameters
Global and Group configuration files
Deploying Cisco Jabber Web SDK
59 www.flane.com.au
Lesson 3
Designing Cisco IM and

Presence
Cisco IM and Presence Components
Cisco IM and Presence Service
Cisco Unified Communications Manager (Unified CM)
Cisco Jabber
Cisco Unified MeetingPlace or MeetingPlace Express
Cisco Unity or Unity Connection
Cisco Unified Videoconferencing or Cisco Unified MeetingPlace Express VT
Lightweight Directory Access Protocol (LDAP) Server v3.0
Cisco Unified IP Phones
Third-party presence server
Third-party XMPP clients
Third-party applications
www.flane.com.au
Cisco IM and Presence encompasses the following components:

Cisco IM and Presence Service
Cisco Unified Communications Manager (Unified CM)
Cisco Jabber
Cisco Unified MeetingPlace or MeetingPlace Express
Cisco Unity or Unity Connection
Cisco Unified Videoconferencing or Cisco Unified MeetingPlace Express VT
Lightweight Directory Access Protocol (LDAP) Server v3.0
Cisco Unified IP Phones
Third-party presence server
Third-party XMPP clients
Third-party applications
Cisco IM and Presence Architecture
www.flane.com.au
Cisco IM and Presence Interfaces
Cisco IM and Presence Platforms

Cisco Unified Communications Mode
Deployment Model Platform Model Number of Users
Supported
Single Node MCS-7816 1000
(or UCS B series / C series
equivalent)
(or UCS B series / C series
equivalent)
www.flane.com.au
The Cisco IM and Presence Service use the same underlying appliance model and hardware used
by Unified CM as well as Unified CM on the Cisco Unified Computing System (UCS) platform,
including a similar administration interface.
Cisco Unified Communications Mode
Supported
Multi-Node Cluster (6 nodes) MCS-7816 3000
(or UCS B series / C series equivalent)
www.flane.com.au
Cisco IM and Presence Service Platforms and Number of Users Supported

Jabber for Everyone (IM–Only User) Mode
Supported
www.flane.com.au
Cisco IM and Presence Service Platforms and Number of Users Supported
Cisco Unified IM and Presence Licensing
The IM and Presence Service does not require a server license or software
version license.
You must assign the IM and Presence Service to each IM and Presence Service
user.
You can assign IM and Presence on a per user basis, regardless of the number
of clients you associate with each user.
IM and Presence capabilities are included within both User Connect Licensing
(UCL) and Cisco Unified Workspace Licensing (CUWL).
www.flane.com.au
The IM and Presence Service does not require a server license or software version license.
However, you must assign the IM and Presence Service to each IM and Presence Service user.
You can assign IM and Presence on a per user basis, regardless of the number of clients you
associate with each user. When you assign IM and Presence to a user, this enables the user to
send and receive IMs and also to send and receive presence updates. If the user is not enabled for
IM and Presence, no presence updates are allowed for that user.
You can enable a user for IM and Presence in the End User Configuration window in Cisco
Unified Communications Manager. See the Cisco Unified Communications Manager
Administration Guide for more information.
IM and Presence capabilities are included within both User Connect Licensing (UCL) and Cisco
Unified Workspace Licensing (CUWL).
Cisco IM and Presence Cluster
Cisco IM and Presence consists of up to six servers, including one designated as a
publisher.
Utilize the same architectural concepts as the Unified CM publisher and subscriber.
The Cisco IM and Presence publisher utilizes and builds upon the database used by the
Cisco Unified Communications Manager publisher:
Sharing the user and device information
Supports only a single Cisco Unified Communications Manager cluster
All users of Cisco IM and Presence must be defined within the same Cisco Unified
Communications Manager cluster
Within a Cisco IM and Presence cluster, individual servers can be grouped to form a
subcluster, and the subcluster can have at most two servers associated with it.
www.flane.com.au
A Cisco IM and Presence cluster consists of up to six servers, including one designated as a
publisher, which utilize the same architectural concepts as the Unified CM publisher and
subscriber. Within a Cisco IM and Presence cluster, individual servers can be grouped to form a
subcluster, and the subcluster can have at most two servers associated with it.
High Availability Deployment Options
Basic Deployment of Cisco IM and Presence
High Availability Deployment of Cisco IM and Presence
www.flane.com.au
A highly available Cisco IM and Presence cluster requires two servers per subcluster. This allows
for users to fail-over between the servers within the subcluster; however, the total number of
users supported and the time to failover vary based on which features are enabled, the average
size of contact lists, and the rate of traffic placed on the servers. Once a Cisco IM and Presence
subcluster is configured for two servers, it always operates as highly available. High availability
can be deployed using an Active/Standby model or an Active/Active model, and these modes are
controlled by the Sync Agent service parameter User Assignment Mode. By default all users are
balanced across all servers in the cluster, and Cisco recommends leaving this parameter set to its
default value.Presence cluster.
High Availability Deployment Options (Cont.)
Mixed Deployment of Cisco IM and Presence
www.flane.com.au
The Cisco IM and Presence cluster can also have mixed subclusters, where one subcluster is
configured with two servers while other subclusters contain a single server.
Cisco IM and Presence Database
Synchronization with Cisco Unified CM
Intracluster traffic participates at a very low level between Cisco IM and Presence and
Cisco UCM, and between the Cisco IM and Presence publisher and subscriber.
Both clusters share a common hosts file and have a strong trust relationship using
IPTables.
At the level of the database and services, the clusters are separate and distinct, and each
Cisco IM and Presence and Cisco UCM cluster requires separate administration.
Publisher
Sharing
Information
Cisco UCM
Cisco IM and Cluster
Presence
Cluster
User and Devices

Subscriber
www.flane.com.au
The Cisco IM and Presence Service utilizes and builds upon the database used by the Unified CM
publisher by sharing the user and device information. A Cisco IM and Presence cluster supports
only a single Unified CM cluster; therefore, a separate IM and Presence cluster is required for
each Unified CM cluster.
Intracluster traffic participates at a very low level between Cisco IM and Presence and Unified
CM and between the Cisco IM and Presence publisher and subscriber servers. Both clusters share
a common hosts file and have a strong trust relationship using IPTables. At the level of the
database and services, the clusters are separate and distinct, and each Cisco IM and Presence
Service and Unified CM cluster requires separate administration. There is currently no Transport
Layer Security (TLS) or IPSec utilization for intracluster traffic.
The Cisco IM and Presence Service interface with external systems sends SIP and XMPP traffic
over UDP, TCP, or TLS. TLS mutual authentication requires the import and export of certificates
between Cisco IM and Presence Service and the external system. TLS server authentication
(Cisco IM and Presence Service presenting its TLS certificate to the client device for verification)
validates the end user via digest authentication.
Cisco IM and Presence Publisher
Communication
The Cisco IM and Presence publisher communicates directly with the Cisco UCM publisher
via the AXL API using the SOAP interface.
All Cisco IM and Presence users are configured in the Cisco UCM End User configuration.
During the synchronization, Cisco IM and Presence populates these users in its database
from the Cisco UCM database.
Cisco IM and Presence does not provide end-user configuration from its administration
interface.
Sync User and

Device Data
AXL/SOAP
Publisher Publisher
www.flane.com.au
The Cisco IM and Presence publisher communicates directly with the Unified CM publisher via
the AVVID XML Layer Application Program Interface (AXL API) using the Simple Object
Access Protocol (SOAP) interface. When first configured, the Cisco IM and Presence publisher
performs an initial synchronization of the entire Unified CM user and device database. All Cisco
IM and Presence users are configured in the Unified CM End User configuration. During the
synchronization, Cisco IM and Presence populates these users in its database from the Unified
CM database and does not provide end-user configuration from its administration interface.
The initial Cisco IM and Presence database synchronization from Unified CM might take a while,
depending on the amount of information in the database as well as the load that is currently on the
system. Subsequent database synchronizations from Unified CM to Cisco IM and Presence are
performed in real time when any new user or device information is added to Unified CM.
Cisco IM and Presence Redundancy
If one Cisco IM and Presence server fails, the users associated with that failed server will
automatically fail over to the other Cisco IM and Presence server.
Load balancing allows for the processing power to be scaled beyond the capacity of a
single server to support a larger number of users.
The Cisco IM and Presence cluster consists of up to six servers, which can be configured
into multiple subclusters, with a maximum of three subclusters for high availability.
A subcluster contains a maximum of two servers and allows for users associated with one
server of the subcluster to use the other server in the subcluster automatically if a failover
event occurs. Cisco IM and Presence does not provide failover between subclusters.
www.flane.com.au
The Cisco IM and Presence cluster consists of up to six servers, which can be configured into
multiple subclusters, with a maximum of three subclusters for high availability. A subcluster
contains a maximum of two servers and allows for users associated with one server of the
subcluster to use the other server in the subcluster automatically if a failover event occurs. Cisco
IM and Presence does not provide failover between subclusters.
When deploying a Cisco IM and Presence cluster for high availability, you must take into
consideration the maximum number of users per server to avoid oversubscribing any one server
within the subcluster in the event of a failover. When deploying a Cisco IM and Presence cluster,
use equivalent hardware for all servers within the cluster.
Cisco Unified Communications Manager
Deployment Options
Applications
Cisco Unified
Communications
Manager
Cisco Unified Applications
Cluster
Communications
Manager
Cluster PSTN
IP WAN Branch
Headquarters
Supported IP telephony deployment models:
Single-site deployment
Multisite WAN with centralized call processing
Multisite WAN with distributed call processing
Clustering over the IP WAN

www.flane.com.au
Supported Cisco Unified CM provides a choice of the following deployment models:

Single site
Multisite WAN with centralized call processing
Multisite WAN with distributed call processing
Clustering over the WAN
Supported CUCM Deployment Models
Cisco UCM Deployment Model Cisco IM and Presence Support
Single-site X
Multisite WAN with centralized call processing X
Multisite WAN with distributed call processing X
Clustering over the WAN X
Both the Cisco IM and Presence publisher and subscriber must be

co-located with the Cisco UCM publisher.
www.flane.com.au
Cisco IM and Presence Deployment Models
(Cont.)
Cisco IM and Presence is supported with all the Unified CM deployment models.
However, Cisco recommends co-locating the Cisco IM and Presence publisher

with the Unified CM publisher due to the initial user database synchronization.
All Cisco IM and Presence servers should be co-located within the Cisco IM and
Presence cluster, with the following exceptions:
Geographic datacenter redundancy
Clustering over the WAN
www.flane.com.au
Cisco IM and Presence is supported with all the Unified CM deployment models. However, Cisco
recommends co-locating the Cisco IM and Presence publisher with the Unified CM publisher due
to the initial user database synchronization. All Cisco IM and Presence Services should be co-
located within the Cisco IM and Presence cluster, with the exception of geographic datacenter
redundancy and clustering over the WAN.
Cisco IM and Presence Deployment
Supported Cisco IM and Presence Deployment Models:

Single Cluster
Multi-Cluster
Cluster Over WAN
Federated
Instant Messaging Only
www.flane.com.au
Cisco IM and Presence can be deployed in any of the following configurations:

Single-Cluster Deployment
Multi-Cluster Deployment
Clustering Over the WAN
Federated Deployment
Instant Messaging Only Deployment
Single-Cluster Deployment
1. SIP connection handles all the presence information exchange.

2. CTI-QBE connection handles all the CTI communication for users on Cisco IM and Presence to control
phones on Cisco UCM.
3. The AXL/SOAP interface handles the database synchronization from Cisco UCM to populate the Cisco
IM and Presence database.
4. The LDAP interface is used for LDAP authentication of Cisco Unified Personal Communicator users
during login.
www.flane.com.au
This figure represents the communication protocols between Cisco IM and Presence, the LDAP
server, and Cisco Unified Communications Manager for basic functionality.
For complete information on Cisco IM and Presence administration and configuration, refer to the
Cisco IM and Presence installation, administration, and configuration guides, available at
http://www.cisco.com/en/US/products/ps6837/tsd_products_support_series_home.html
Interactions Between Cisco IM and Presence
Components – SIP
The SIP connection between Cisco IM and Presence and Cisco UCM handles all the
presence information exchange.
Cisco UCM configuration requires:
The Cisco IM and Presence publisher and subscriber to be added as application

servers on Cisco UCM
A SIP trunk pointing to Cisco Unified Presence
Cisco IM and Presence configuration requires:
A Cisco UCM Presence Gateway for presence information exchange with Cisco UCM
Presence Gateway: server_fqdn:5070
Cisco UCM 6.x provides the ability to further streamline communications and reduce
bandwidth utilization:
SIP PUBLISH Trunk, which allows for the PUBLISH method (rather than
SUBSCRIBE/NOTIFY) to be configured
www.flane.com.au
The SIP connection between the Cisco IM and Presence Service and Unified CM handles all the
phone state presence information exchange.
a. Unified CM configuration requires the Cisco IM and Presence Services to be added
as application servers on Unified CM and also requires a SIP trunk pointing to the
Cisco IM and Presence Service. The address configured on the SIP trunk could be a
Domain Name System (DNS) server (SRV) fully qualified domain name (FQDN)
that resolves to the Cisco IM and Presence Services, or it could simply be an IP
address of an individual Cisco IM and Presence Service. The Cisco IM and Presence
Service handles the configuration of the Cisco Unified Communications Manager
application server entry automatically through AXL/SOAP once the administrator
adds a node in the system topology page through Cisco IM and Presence
administration.
b. Configuration of Cisco IM and Presence occurs through the Unified CM Presence
Gateway for presence information exchange with Unified CM. The following
information is configured:
Presence Gateway: server_fqdn:5070
Components – CTI-BQE
The CTI-QBE connection handles all the CTI communication for users on Cisco
IM and Presence to control phones via Cisco UCM when:
Cisco Jabber is using Desk Phone mode to do Click-to-Call
Microsoft Office Communicator is doing Click-to-Call through Microsoft Live

Communications Server 2005 or Office Communications Server 2007
Cisco UCM configuration requires:
User to be associated with a CTI Enabled Group
Primary extension assigned to that user must be enabled for CTI control
The CTI Manager Service must be activated
www.flane.com.au
The Computer Telephony Integration Quick Buffer Encoding (CTI-QBE) connection between
Cisco IM and Presence and Unified CM is the protocol used by presence-enabled users in Cisco
IM and Presence to control their associated phones registered to Unified CM. This CTI
communication occurs when Cisco Jabber is using Desk Phone mode to do Click to Call or when
Microsoft Office Communicator is doing Click to Call through Microsoft Live Communications
Server 2005 or Office Communications Server 2007 or Microsoft Lync.
a. Unified CM configuration requires the user to be associated with a CTI Enabled Group,
and the primary extension assigned to that user must be enabled for CTI control
(checkbox on the Directory Number page). The CTI Manager Service must also be
activated on each of the Unified CM subscribers used for communication with the Cisco
IM and Presence publisher and subscriber. Integration with Microsoft Live
Communications Server 2005 or Office Communications Server 2007 or Microsoft Lync
requires that you configure an Application User, with CTI Enabled Group and Role, on
Unified CM.
b. Cisco IM and Presence CTI configuration (CTI Server and Profile) for use with Cisco
Jabber is automatically created during the database synchronization with Unified CM. All
Cisco Jabber CTI communication occurs directly with Unified CM and not through the
Cisco IM and Presence Service.
Cisco IM and Presence CTI configuration (Desktop Control Gateway) for use with Microsoft
Live Communications Server 2005 or Office Communications Server 2007 or Microsoft Lync
requires you to set the Desktop Control Gateway address (Cisco Unified Communications
Manager Address) and a provider, which is the application user configured previously in Unified
CM. Up to eight Cisco Unified Communications Manager Addresses can be provisioned for
increased scalability. Only IP addresses can be used for Desktop Control Gateway configuration
in the Cisco IM and Presence Service. Administrators should ensure that any configuration and
assignment of Cisco Unified Communications Manager addresses is evenly distributed for the
purpose of load balancing.
Components – AXL/SOAP and LDAP
The AXL/SOAP interface handles the database synchronization from Cisco UCM to
populate the Cisco IM and Presence database.
The LDAP interface is used for LDAP authentication of Cisco Jabber users during
login.
Cisco UCM is responsible for all synchronization of user information directly from
corporate LDAP server:
Then Cisco IM and Presence synchronizes all the user information from Cisco UCM.
Cisco IM and
LDAP CUCM Presence
LDAP Sync
enabled AXL/SOAP
User information User information
CUCM = Cisco UCM
www.flane.com.au
The AXL/SOAP interface handles the database synchronization from Unified CM to populate the
Cisco IM and Presence database.
a. No additional configuration is required on Unified CM.
b. Cisco IM and Presence security configuration requires you to set a user and password for
the Unified CM AXL account in the AXL configuration.
The Sync Agent Service Parameter, User Assignment, set to balanced by default, will load-
balance all users equally across all servers within the Cisco IM and Presence cluster. The
administrator can also manually assign users to a particular server in the Cisco IM and Presence
cluster by changing the User Assignment service parameter to None.
Components – AXL/SOAP and LDAP (Cont.)
If a Cisco Jabber user logs into Cisco IM and Presence and LDAP authentication is
enabled:
Cisco IM and Presence will go directly to LDAP for the Cisco Jabber user
authentication using the Bind operation.
After Cisco Jabber is authenticated, Cisco IM and Presence forwards the information to
Cisco Jabber to continue login.
When using Microsoft AD, point to a Domain Controller:
To improve the response time, promote the Domain Controller to a Global Catalog
server.
DC/GC Cisco IM and
LDAP CUCM Presence
Without LDAP
Auth. enabled Login
LDAP Auth. Cisco Jabber
www.flane.com.au
The LDAP interface is used for LDAP authentication of Cisco Jabber users during login. For
more information regarding LDAP synchronization and authentication.
Unified CM is responsible for all user entries via manual configuration or synchronization
directly from LDAP, and Cisco IM and Presence then synchronizes all the user information from
Unified CM. If a Cisco Jabber user logs into the Cisco IM and Presence Service and LDAP
authentication is enabled on Unified CM, Cisco IM and Presence will go directly to LDAP for the
Cisco Jabber user authentication using the Bind operation. Once Cisco Jabber is authenticated,
Cisco IM and Presence forwards the information to Cisco Jabber to continue login.
When using Microsoft Active Directory, consider the choice of parameters carefully.
Performance of Cisco IM and Presence might be unacceptable when a large Active Directory
implementation exists and the configuration uses a Domain Controller. To improve the response
time of Active Directory, it might be necessary to promote the Domain Controller to a Global
Catalog and configure the LDAP port as 3268.
Extends presence and instant messaging capability and functionality.
Configure peer relationships for communication between clusters within the same
domain.
To create a fully meshed presence topology:
Each Cisco IM and Presence cluster requires a separate peer relationship.
The address configured in this intercluster peer could be a DNS SRV FQDN
or an IP address.
The interface between each Cisco IM and Presence cluster is twofold:
AXL/SOAP interface
SIP or XMPP interface
www.flane.com.au
The deployment topology in previous sections is for a single Cisco IM and Presence cluster
communicating with a single Unified CM cluster. Presence and instant messaging functionality is
limited by having communications within a single cluster only. Therefore, to extend presence and
instant messaging capability and functionality, these standalone clusters can be configured for
peer relationships for communication between clusters within the same domain. This
functionality provides the ability for users in one cluster to communicate and subscribe to the
presence of users in a different cluster within the same domain.
To create a fully meshed presence topology, each Cisco IM and Presence cluster requires a
separate peer relationship for each of the other Cisco IM and Presence clusters within the same
domain. The address configured in this intercluster peer could be a DNS SRV FQDN that
resolves to the remote Cisco IM and Presence cluster servers, or it could also simply be the IP
address of the Cisco IM and Presence cluster servers.
Multi-Cluster Deployment (Cont.)
AXL/SOAP interface handles the synchronization of user information for home
cluster association, but it is not a full user synchronization.
SIP or XMPP interface handles the subscription and notification traffic, and it
rewrites the host portion of the URI before forwarding, if the user is detected to be
on a remote Cisco IM and Presence cluster within the same domain.
The traffic generated between Cisco IM and Presence clusters is directly

proportional to the characteristics of the presence user profile.
www.flane.com.au
The interface between each Cisco IM and Presence cluster is two-fold, an AXL/SOAP interface
and a signaling protocol interface (SIP or XMPP). The AXL/SOAP interface handles the
synchronization of user information for home cluster association, but it is not a full user
synchronization. The signalling protocol interface (SIP or XMPP) handles the subscription and
notification traffic, and it rewrites the host portion of the URI before forwarding if the user is
detected to be on a remote Cisco IM and Presence cluster within the same domain.
When Cisco IM and Presence is deployed in a multi-cluster environment, a presence user profile
should be determined. The presence user profile helps determine the scale and performance of a
multi-cluster presence deployment and the number of users that can be supported. The presence
user profile helps establish the number of contacts (or buddies) a typical user has, as well as
whether those contacts are mostly local cluster users or users of remote clusters.
The traffic generated between Cisco IM and Presence clusters is directly proportional to the
characteristics of the presence user profile. For example, assume presence user profile A has 30
contacts with 20% of the users on a local Cisco IM and Presence cluster and 80% of the users on
a remote Cisco IM and Presence cluster, while presence user profile B has 30 contacts with 50%
of the users on a local Cisco IM and Presence cluster and 50% of the users on a remote Cisco IM
and Presence cluster. In this case, presence user profile B will provide for slightly better network
performance and less bandwidth utilization due to a smaller amount of remote cluster traffic.
This allows for geographic redundancy of a subcluster and high availability for the
users between the nodes across the sites.
Geographic datacenter redundancy and remote failover
A Cisco IM and Presence cluster can be deployed between two sites with a single
subcluster topology, where one server of the subcluster is in one geographic site
and the other server of the subcluster is in another site.
Any remaining subclusters (nodes within those subclusters) must remain co-
located with the Cisco IM and Presence publisher.
This deployment must have a minimum bandwidth of 5 Mbps, a maximum latency

of 80 ms round-trip time (RTT), and TCP method event routing.
www.flane.com.au

A Cisco IM and Presence cluster can be deployed with one of the nodes of a subcluster deployed
across the Wide Area Network (WAN). This allows for geographic redundancy of a subcluster
and high availability for the users between the nodes across the sites. The following guidelines
must be used when planning for a Cisco IM and Presence deployment with clustering over the
WAN.
Geographic datacenter redundancy and remote failover
A Cisco IM and Presence cluster can be deployed between two sites with a single
subcluster topology, where one server of the subcluster is in one geographic site and the
other server of the subcluster is in another site. This deployment must have a minimum
bandwidth of 5 Mbps, a maximum latency of 80 ms round-trip time (RTT), and TCP
method event routing.
Clustering Over the WAN (Cont.)
A scalable highly available capacity for a Cisco IM and Presence cluster is up to

three subclusters; therefore, a scalable highly available remote failover topology
would consist of the following two sites:
Site A: Subcluster 1 node A, subcluster 2 node A, and subcluster 3 node A
Site B: Subcluster 1 node B, subcluster 2 node B, and subcluster 3 node B
Local Failover : A Cisco IM and Presence cluster deployment between two sites
may also contain a subcluster topology per site (single node or dual node for high
availability).
www.flane.com.au
High availability and scale

Cisco IM and Presence high availability allows for users on one node within a subcluster
to automatically fail-over to the other node within the subcluster. With a Cisco IM and
Presence subcluster containing a maximum of two nodes, remote failover is essentially
between two sites, one site for each node. A scalable highly available capacity for a Cisco
IM and Presence cluster is up to three subclusters; therefore, a scalable highly available
remote failover topology would consist of the following two sites:
– Site A: Subcluster 1 node A, subcluster 2 node A, and subcluster 3 node A
– Site B: Subcluster 1 node B, subcluster 2 node B, and subcluster 3 node B
This deployment must have a minimum bandwidth of 5 Mbps per subcluster, a maximum
latency of 80 ms round-trip time (RTT), and TCP method event routing. Each new
subcluster added to the deployment requires an additional 5 Mbps of dedicated bandwidth
to handle the database and state replication.
Local Failover
A Cisco IM and Presence cluster deployment between two sites may also contain a
subcluster topology per site (single node or dual node for high availability), where one
subcluster is in one geographic site and the other subcluster is in another geographic site.
This topology allows for the users to remain at their local site (highly available or not)
without the requirement or need to fail-over to a different site or location. This
deployment must have a minimum bandwidth of 5 Mbps dedicated bandwidth between
each subcluster in the respective sites, a maximum latency of 80 ms round-trip time
(RTT), and TCP method event routing.
Clustering Over the WAN (Cont.)
Cisco recommends 25% or fewer remote contacts for a client in environments

where the bandwidth is low (10 Mbps or less), and at all times the maximum
round-trip latency must be 80 ms or less.
Persistent Chat and Compliance logging considerations When Cisco IM and

Presence is enabled for persistent chat, message archiving, or compliance
logging and a sublcuster is split across a WAN, the external database server(s)
must reside on the same side of the WAN as the Cisco IM and Presence servers
that use them.
With the ability to support multiple database instances on a single server and the
requirement for an external database server to reside on the same side of the
WAN, if a Cisco IM and Presence cluster is split across a WAN, then two external
database servers will be required.
www.flane.com.au
Bandwidth and latency considerations

With a Cisco IM and Presence cluster that has a topology of nodes split across a WAN,
the number of contacts within a user's client can impact the bandwidth needs and criteria
for the deployment.
The traffic generated within and between Cisco IM and Presence clusters is directly
proportional to the characteristics of the presence user profile, and thus the amount of
bandwidth required for deployment. Cisco recommends 25% or fewer remote contacts for
a client in environments where the bandwidth is low (10 Mbps or less), and at all times
the maximum round-trip latency must be 80 ms or less.
Persistent Chat and Compliance logging considerations
When Cisco IM and Presence is enabled for persistent chat, message archiving, or
compliance logging and a sublcuster is split across a WAN, the external database
server(s) must reside on the same side of the WAN as the Cisco IM and Presence
Services that use them. With the ability to support multiple database instances on a single
server and the requirement for an external database server to reside on the same side of
the WAN, if a Cisco IM and Presence cluster is split across a WAN, then two external
database servers will be required.
WAN Bandwidth requirements
At a minimum, you must dedicate five megabits per second of bandwidth
for each Cisco IM and Presence subcluster, with no more than an eighty
millisecond round-trip latency.
If there are more than 10, 000 users spread across the WAN, 10
megabits of bandwidth is required.
These bandwidth recommendations apply to both intracluster and

intercluster WAN deployments. Any bandwidth less than this
recommendation can adversely impact performance.
Each Cisco IM and Presence subcluster that you add to your Clustering
over WAN deployment requires an additional (dedicated) five megabits
per second bandwidth.
www.flane.com.au
Federation Deployment
Use Case : Inter-Domain federation supports both IM and Presence federation between
different enterprises.
Provides inter-working between Cisco Jabber where Cisco IM and Presence is
deployed in in two DIFFERENT domains
This includes support of users of both clients on a client buddy list, sending/receiving IM,
and sending/receiving status updates
Supports another Cisco IM and Presence Server ,AOL, OCS, Google Talk, IBM Sametime
and Connect, WebEx Connect
www.flane.com.au
Cisco IM and Presence allows for business-to-business communications by enabling inter-domain

federation, which provides the ability to share presence and instant messaging communications
between different domains. Inter-domain federation requires two explicit DNS domains to be
configured, as well as a security appliance (Cisco Adaptive Security Appliance) in the DMZ to
terminate federated connections with the enterprise. If all the federated domains are within the
same trust boundary, where a deployment has all components within a single datacenter, then the
use of the Adaptive Security Appliance is not required.
Cisco IM and Presence XMPP Federation
(Inter-Domain)
www.flane.com.au
The Adaptive Security Appliance (ASA) in the DMZ is used as a demarcation into the enterprise.
XMPP traffic is passed through, whereas SIP traffic is inspected. All federated incoming and
outgoing traffic is routed through the Cisco IM and Presence Service that is enabled as a
federation node, and is routed internally to the appropriate server in the cluster where the user
resides. For multi-cluster deployments, intercluster peers propagate the traffic to the appropriate
home cluster within the domain. Multiple nodes can be enabled as federation nodes within large
enterprise deployments, where each request is routed based on a round-robin implementation of
the data returned from the DNS SRV lookup.
Cisco IM and Presence SIP Federation
(Inter-Domain)
www.flane.com.au
Cisco IM and Presence inter-domain federation with Microsoft Lync Server, Office
Communications Server (OCS), and Live Communications Server (LCS) provides basic presence
(available, away, busy, offline) and point-to-point instant messaging.
Rich presence capability (On the Phone, In a Meeting, On Vacation, and so forth), as well as
advanced instant messaging features, are not supported. Cisco IM and Presence inter-domain
federation with AOL allows federation with users of AOL public communities (aim.com,
aol.com), with users of domains hosted by AOL, and with users of a far-end enterprise that
federates with AOL (that is, AOL is being used as a clearing house).
Note A SIP federation (inter-domain to AOL) on Cisco IM and Presence must be configured for
each domain of the AOL network, which can consist of both hosted networks and public
communities. Each unique hosted domain must be configured; however, only a single aol.com
public community needs to be configured because the AOL network allows a user to be addressed
as user@aol.com or user@aim.com
The inter-domain federation configuration also allows for a specific federation between Cisco IM
and Presence and Microsoft Lync Server or Microsoft Office Communications Server (OCS).
Cisco IM and Presence provides inter-domain federation with Microsoft Lync Server, Microsoft
Office Communications Server (OCS), or Live Communications Server (LCS) to provide basic
presence (available, away, busy, offline) and point-to-point instant messaging. Rich presence
capability (On the Phone, In a Meeting, On Vacation, and so forth), as well as advanced instant
messaging features, are not supported.
Instant Messaging Only Deployment
Provides full presence and instant messaging support
Instant messaging only users on Cisco IM and Presence are still provisioned from
Unified CM through the AXL/SOAP interface by means of LDAP synchronization
or manual provisioning.
www.flane.com.au
A Cisco IM and Presence cluster (or clusters) can be deployed to provide enterprise-class
presence and instant messaging in an environment where Unified CM is not deployed for call
control for specific users. A deployment of IM and Presence only is also referred to as Jabber for
Everyone. Unified CM is still required to establish user accounts entered either manually or
through LDAP synchronization. A Cisco IM and Presence instant messaging only deployment
synchronizes user information from Unified CM in the same way as is done with a full Unified
Communications deployment. If Unified CM is not deployed or if the existing deployed Unified
CM will not be used for instant messaging only, a Cisco MCS 7816 Media Convergence Server
with preloaded Unified CM software is provided as an option.
For existing Cisco IM and Presence deployments where a Unified CM cluster is already
deployed, users can also be added for use with the instant messaging only mode. This allows for a
mix of full Unified Communications users in addition to instant messaging only users, in
accordance with the end-user license agreement.
Summary
Cisco IM and Presence solution components and architecture.
Platform and License requirements for Cisco IM and Presence
Cisco IM and Presence high availability options
Cisco IM and Presence Deployment options:
Single Cluster
Multi-Cluster
Cluster Over WAN
Federated
Instant Messaging Only
92 www.flane.com.au
Lesson 4
Integrating Cisoc Unified

CM and Cisco Unified IM
and Presence
Configuration Checklist
Complete these tasks from the Cisco Unified Communications Manager
Administration window:
Configure service parameters
Configure Cisco IM and Presence as an application server
Configure the SIP trunk security profile
Configure SIP trunks for each Cisco IM and Presence server
Add an application user with the standard AXL access role enabled
Verify that the required services are running
www.flane.com.au
Configure the Service Parameters and
Application Server
Set the CUP PUBLISH Trunk parameter
Navigate to the CallManager Service Parameters
Used to send PUBLISH messages
Configure the Application Server

You no longer have to manually add the IM and Presence Service as an Application
Server on Cisco Unified Communications Manager:
www.flane.com.au
You only configure one SIP trunk between a Cisco Unified Communications Manager cluster and
a Cisco Unified IM and Presence cluster. After you configure the SIP trunk, you must assign that
SIP trunk as the CUP PUBLISH trunk on Cisco Unified Communications Manager by selecting
Cisco Unified Communications Manager Administration > System > Service Parameters.
If DNS SRV is an option in your network, and you want availability messaging to be shared
equally among all the servers used for availability information exchange, you must configure the
SIP trunk for the Cisco Unified Presence server with a DNS SRV record of the Cisco Unified
Presence publisher and subscriber servers. You must also configure the Presence Gateway on the
Cisco Unified Presence server with a DNS SRV record of the Cisco Unified Communications
Manager subscriber nodes.
Configure the SIP Trunk Security Profile
Navigate to System > Security Profile > SIP Trunk Profile
www.flane.com.au
Configuring the SIP Trunk Security Profile for Cisco Unified Presence
Procedure
Step 1 Select Cisco Unified Communications Manager Administration > System >
Security > SIP Trunk Security Profile.
Step 2 Select Find.
Step 3 Select Non Secure SIP Trunk Profile.
Step 4 Verify that the setting for Device Security Mode is Non Secure.
Step 5 Verify that the setting for Incoming Transport Type is TCP+UDP.
Step 6 Verify that the setting for Outgoing Transport Type is TCP.
Step 7 Check to enable these items:

Accept Presence Subscription
Accept Out-of-Dialog REFER
Accept Unsolicited Notification
Configure SIP Trunks for Each Cisco IM and
Presence Server
Navigate to Device > Trunk and add a new SIP trunk
Add a new SIP trunk.
Enter the Cisco IM and

Presence address.
www.flane.com.au
You only configure one SIP trunk between a Cisco Unified Communications Manager cluster and
an IM and Presence cluster. After you configure the SIP trunk, you must assign that SIP trunk as
the IM and Presence Publish Trunk on Cisco Unified Communications Manager by selecting
Cisco Unified Communications Manager Administration > System > Service Parameters.
If DNS SRV is an option in your network, and you want availability messaging to be shared
equally among all the servers used for availability information exchange, you must configure the
SIP trunk for the IM and Presence server with a DNS SRV record of the IM and Presence
publisher and subscriber servers. You must also configure the Presence Gateway on the IM and
Presence server with a DNS SRV record of the Cisco Unified Communications Manager
subscriber nodes.
Add an Application User with the Standard
AXL Access Role
If the CCMAdministrator is not used as the AXL user, create a new
application user with AXL access rights
Navigate to User Management > Application User
Add a new Application User AXLuserCUPS
www.flane.com.au
The AXL/SOAP interface handles the database synchronization from Cisco Unified
Communications Manager and populates the Cisco Unified IM and Presence database. To
activate the database synchronization, you must start the Sync Agent service on Cisco Unified IM
and Presence. By default the Sync Agent load balances all users equally across all nodes within
the Cisco Unified IM and Presence cluster. You also have the option to manually assign users to a
particular node in the Cisco Unified IM and Presence cluster. For guidelines on the recommended
synchronization intervals when executing database synchronization with Cisco Unified
Communications Manager, for single and dual-node Cisco Unified IM and Presence, see the
Cisco Unified IM and Presence SRND document.
Add an Application User with the Standard
AXL Access Role (Cont.)
Navigate to User Management > User Group
Add a new user group group_AXLaccess
Add the Application User AXLuserCUPS to the group
Assign Standard AXL API Access role to the new group
www.flane.com.au
Add an Application User with the Standard AXL Access Role Enabled
Consider this step as optional. During Cisco Unified IM and Presence installation, you must enter
an AXL UserID and AXL User password for an application user who has AXL API access
enabled.
You can use the CCMAdministrator application user, which has the Standard AXL API Access
role enabled by default, or you can follow this step to create a new application user.
Verify that the Required Services Are Running
Activate the required services on Cisco Unified Communications Manager
Cisco CallManager
Cisco TFTP (if you are deploying Cisco Unified Personal Communicator
softphone)
Cisco CTIManager (if you are deploying Cisco Unified Personal

Communicator in desk phone control mode)
Cisco AXL Web Service (for data synchronization between IM and

Presence and Cisco Unified Communications Manager)
www.flane.com.au
Make sure that the following services are running:

Cisco CallManager
Cisco TFTP (if you are deploying Cisco Unified Personal Communicator softphone)
Cisco CTIManager (if you are deploying Cisco Unified Personal Communicator in desk
phone control mode)
Cisco AXL Web Service (for data synchronization between IM and Presence and Cisco
Unified Communications Manager)
Cisco IM and Presence Navigation and Menus
Cisco IM and Presence navigation is similar to Cisco Unified

Communications Manager
Cisco IM and Presence Administration menus
www.flane.com.au
Cisco IM and Presence Configuration
Checklist
Configuration tasks for Cisco IM and Presence to integrate with

Cisco Unified Communications Manager are:
Add an optional Cisco IM and Presence subscriber
Configure the Presence gateway
Configure an incoming and privacy access control list
Verify Cisco IM and Presence settings and configure a SIP publish trunk
Configure Presence Settings
www.flane.com.au
Configuration tasks for Cisco Unified IM and Presence to integrate with Cisco Unified
Communications Manager are:
Add an optional Cisco Unified Presence subscriber
Configure the Presence gateway
Enable Cisco Unified Personal Communicator Release 8.x Mandatory and Optional XCP
Services
Configure an incoming and privacy access control list
Verify Cisco Unified Presence settings and configure a SIP publish trunk
Configure Presence Settings
Build a Cisco IM and Presence Cluster
This task has to be completed before the installation of the second Cisco IM
and Presence server.
From the Cisco IM and Presence Administration window, navigate to

System > Cluster Topology > Add Node
www.flane.com.au
Add an Optional Secondary Cisco Unified IM and Presence Node
Step 1 Choose System > Cluster Topology > Add New Node.
The Server Configuration window displays.
Step 2 For Host Name/IP Address, enter the hostname or IP address of the subscrib
Step 3 Click Save.
Presence Gateway
Configure the Cisco IM and Presence gateways
Navigate to Presence > Gateways > Communications Manager
Select the Presence Gateway Type CUCM or Exchange
CUCM = Cisco Unified Communications Manager
www.flane.com.au
Presence Gateway Configuration Option

You must configure Cisco Unified Communications Manager as a Presence Gateway on Cisco
Unified IM and Presence to enable the SIP connection that handles the availability information
exchange between Cisco Unified Communications Manager and Cisco Unified IM and Presence.
The Cisco Unified IM and Presence server sends SIP subscribe messages to Cisco Unified
Communications Manager over a SIP trunk which allows the Cisco Unified IM and Presence
server to receive availability information (for example, phone on/off hook status). When
configuring the Presence Gateway, specify the FQDN (Fully Qualified Domain Name) or the IP
address of the associated Cisco Unified Communications Manager server. Depending on your
network this value can be one of the following:
The FQDN address of the Cisco Unified Communications Manager publisher
A DNS SRV FQDN that resolves to the Cisco Unified Communications Manager
subscriber nodes
The IP address of the Cisco Unified Communications Manager publisher If DNS
SRV is an option in your network, configure the following:
1. Configure the Presence Gateway on the Cisco Unified IM and Presence server
with a DNS SRV FQDN of the Cisco Unified Communications Manager
subscriber nodes (equally weighted). This will enable Cisco Unified IM and
Presence to share availability messages equally among all the servers used for
availability information exchange.
2. On Cisco Unified Communications Manager, configure the SIP trunk for the
Cisco Unified IM and Presence server with a DNS SRV FQDN of the Cisco
Unified IM and Presence publisher and subscriber.
If DNS SRV is not an option in your network, and you are using the IP address of the associated
Cisco Unified Communications Manager server, you cannot share presence messaging traffic
equally across multiple subscriber nodes because the IP address points to a single subscriber
node.
Configure an Incoming Access Control List
Navigate to System > Security > Incoming ACL
Enter the Address Pattern of the associated server:
Default is to deny all incoming requests
An access control list can also be configured for outgoing addresses

(privacy access control list )
Enter ALL in the Address

Pattern Field to allow all
incoming requests.
www.flane.com.au
In the Incoming Access Control List (ACL), you can configure patterns that control which
incoming hosts and domains can access Cisco Unified Presence without authentication. Cisco
Unified IM and Presence accepts a range of IP address patterns in addition to fully qualified
names of incoming hosts or domains.
Configuring Cisco IM and Presence Settings
Navigate to Presence > Settings
Enable Availability Sharing
Enable SIP Publish on Cisco Unified Communications Manager
If not visible, check if

CUP PUBLISH Trunk
parameter on Cisco
Unified
Communications
Manager is set.
www.flane.com.au
Availability sharing is turned on by default on IM and Presence.
Configure Messaging Settings
Navigate to Messaging > Settings
Enable Instant Messaging
www.flane.com.au
By default IM and Presence stores (locally) any instant messages that are sent to a user when they
are offline, and IM and Presence delivers these instant messages to the user the next time they
sign in to the client application. You can turn off (suppress) this feature so IM and Presence does
not store offline instant messages.
For example, in large deployments, this feature could require significant message storage, so you
may want to suppress offline instant messages to increase performance.
Summary
Configuring Cisco UCM to integrate with Cisco IM and Presence:
Configuring SIP Trunk Security Profile
Configuring SIP Trunk
Configuring AXL communication
Initialize Cisco Unified IM and Presence:
Configure Subcluster
Configure Presence Gateway
Configuring ACL
Configure Message Settings
108 www.flane.com.au
Lesson 5
Set Up Cisco Jabber On-

Premises Deployments with
Cisco UCM Version 9.x
Product Mode Requirements
Full UC
Users have instant messaging and presence as their base functionality.
Provision users with devices for audio and video in addition to voicemail and
conferencing capabilities.
www.flane.com.au
Product Mode Requirements

Full UC
The primary authentication for users is to Cisco Unified Presence.
Users have instant messaging and presence as their base functionality. You can then provision
users with devices for audio and video in addition to voicemail and conferencing capabilities.
Product Mode Requirements (Cont.)
Cisco Jabber for Everyone (IM Only)

Users have instant messaging and presence capabilities. You can optionally
provision users with desk phone devices that they can control with the client.
To set up a deployment with instant messaging and presence capabilities

only, complete the following tasks:
1. Activate and start essential services.
2. Configure directory integration.
3. Create a service profile.
4. Set up instant messaging and presence.
www.flane.com.au
Cisco Jabber for Everyone (IM Only)

The primary authentication for users is to Cisco Unified Presence.
Users have only instant messaging and presence capabilities. You can optionally provision users
with desk phone devices that they can control with the client.
To set up a deployment with instant messaging and presence capabilities only, complete the
following tasks in this lesson:
1. Activate and start essential services.
2. Configure directory integration.
3. Set up instant messaging and presence.
Product Mode Requirements (Cont.)
Phone Mode
Users have devices for audio and video as their base functionality.
To deploy the client in phone mode, complete the following tasks:
1. Configure directory integration for Cisco Unified Communications

Manager.
2. Create a service profile.
3. Set up audio and video capabilities.
4. Provision users with additional capabilities as required.
www.flane.com.au
Phone Mode
The primary authentication for users is to Cisco Unified Communications Manager.
Users have devices for audio and video as their base functionality.
To deploy the client in phone mode, complete the following tasks in this lesson:
1. Configure directory integration for Cisco Unified Communications Manager.
2. Set up audio and video capabilities.
3. Provision users with additional capabilities as required.
Activate and Start Essential Services
Cisco UP XCP Text Conference Manager: for group

chat and persistent chat rooms.
Cisco UP XCP Web Connection Manager: to manage

connections for web-based client applications, that
connect to Cisco IM and Presence using HTTP.
Cisco UP XCP SIP Federation Connection Manager:

to support federation services with third-party
applications that use SIP.
Cisco UP XCP XMPP Federation Connection

Manager: to support federation services with third-
party applications that use XMPP.
www.flane.com.au
Turn on the following services:

Cisco UP XCP Connection Manager - Turn on this service if you are integrating XMPP
clients (such as Cisco Unified Personal Communicator), or XMPP-based API clients, on
Cisco Unified Presence
Cisco UP XCP Authentication Service - Turn on this service if you are integrating XMPP
clients (such as Cisco Unified Personal Communicator), or XMPP-based API clients, , or
XMPP-based API clients, on Cisco Unified Presence.
Cisco UP XCP Web Connection Manager - Optionally, turn on this service if you are
integrating XMPP clients (such as Cisco Unified Personal Communicator), or XMPP-based
API clients, on Cisco Unified Presence.
Activate and Start Essential Services (Cont.)
Cisco UP XCP Counter Aggregator: if you want system

administrators to be able to view statistical data on
XMPP components.
Cisco UP XCP Message Archiver : for automatic

archiving of all instant messages.
Cisco UP XCP Directory Service: if you want to

enable third-party XMPP client applications to do
LDAP searches.
www.flane.com.au
Cisco UP XCP Text Conference Manager, for group chat and persistent chat rooms. If
you have a mixture of Cisco Unified Personal Communicator Release 8.x and Release 7.x
users, then the Cisco UP XCP Text Conference Manager service must be running for
them to communicate with one another.
Cisco UP XCP SIP Federation Connection Manager, to support federation services with
third-party applications that use SIP.
Cisco UP XCP XMPP Federation Connection Manager, to support federation services
with third-party applications that use XMPP.
Cisco UP XCP Counter Aggregator, if you want system administrators to be able to view
statistical data on XMPP components.
Cisco UP XCP Message Archiver, for automatic archiving of all instant messages.
Cisco UP XCP Directory Service, if you want to enable third-party XMPP client
applications to do LDAP searches.
User Configuration Architecture
The client can then retrieve settings for available services from the
service profile.
Voicemail
Conferencing
UC Service
User
Profile
Directory
CTI
www.flane.com.au
You create a service profile that contains the configuration settings for the services you add on
Cisco Unified Communications Manager. You add the service profile to the end user
configuration for your users. The client can then retrieve settings for available services from the
service profile.
Directory Integration
LDAP Integrations satisfy a number of different requirements:

User provisioning: You can provision users automatically from the LDAP
directory into the Cisco Unified Communications Manager database.
User authentication: You can authenticate users using the LDAP directory
credentials.
User lookup: You can enable LDAP directory lookups to allow Cisco Unified
Personal Communicator client users, or third-party XMPP clients, to search
for and add contacts from the LDAP directory.
www.flane.com.au
You can configure a corporate LDAP directory in this integration to satisfy a number of different
requirements:
User provisioning:
You can provision users automatically from the LDAP directory into the Cisco Unified
Communications Manager database. Cisco Unified Communications Manager synchronizes
with the LDAP directory content so you avoid having to add, remove, or modify user
information manually each time a change occurs in the LDAP directory.
User authentication:
You can authenticate users using the LDAP directory credentials. Cisco Unified Presence
synchronizes all the user information from Cisco Unified Communications Manager to
provide authentication for users of the Cisco Unified Personal Communicator client and
Cisco Unified Presence user interface.
User lookup:
You can enable LDAP directory lookups to allow Cisco Unified Personal Communicator
client users, or third-party XMPP clients, to search for and add contacts from the LDAP
directory.
Configure Directory Integration
When you set up an on-premises deployment, you should do both

of the following:
www.flane.com.au
As the scope of the LDAP integration is dependent on customer requirements and it can vary
between companies, there are a number of potential LDAP integration scenarios:
1. You integrate Cisco Unified Communications Manager and Cisco Unified Personal
Communicator with an LDAP directory. We strongly recommend this configuration.
2. You integrate Cisco Unified Communications Manager with an LDAP directory, but you
do not integrate Cisco Unified Personal Communicator. We do not recommend this
configuration because it will impact Cisco Unified Personal Communicator functionality
and you will experience performance issues.
3. You integrate Cisco Unified Personal Communicator with an LDAP directory, but you do
not integrate Cisco Unified Communications Manager. We do not recommend this
configuration because you will have to manually configure all your users on Cisco
Unified Communications Manager at initial installation, and each time a change is made
on the LDAP directory.
Configure Directory Integration (Cont.)
Enable Synchronization
In Cisco UCM Administration: System > LDAP > LDAP System
www.flane.com.au
LDAP synchronization uses the Cisco Directory Synchronization (DirSync) tool on Cisco Unified
Communications Manager to synchronize information (either manually or periodically) from a
corporate LDAP directory.
When you enable the DirSync service, Cisco Unified Communications Manager automatically
provisions users from the corporate directory. Cisco Unified Communications Manager still uses
its local database, but disables its facility to allow you to create user accounts. You use the LDAP
directory interface to create and manage user accounts.
Perform Synchronization
System > LDAP > LDAP Directory.
www.flane.com.au
LDAP synchronization does not apply to application users on Cisco Unified Communications
Manager. You must manually provision application users in the Cisco Unified CM
Administration interface.
Authenticate with the Directory Server
In Cisco UCM Administration: System > LDAP > LDAP Authentication
www.flane.com.au
The LDAP authentication feature enables Cisco Unified Communications Manager to

authenticate user passwords against the corporate LDAP directory.
Set Up Instant Messaging and Presence
Add an Instant Messaging and Presence Service
In Cisco Unified CM Administration > User Management > User

Settings > UC Service.
www.flane.com.au
Instant messaging and presence capabilities let users send and receive instant messages as well as
publish and view availability status.
Procedure
Step 1 Open the Cisco Unified CM IM and Presence Administration interface.
Step 2 Select Messaging > Settings.
Step 3 Select the following options:
Enable instant messaging
Allow clients to log instant message history
Step 4 Select other messaging settings as appropriate.
Step 5 Select Save.
Set Up Voicemail – Voicemail Server
Setting up voicemail enables users to receive voice mail messages and redirect
incoming audio calls to the voicemail service.
Add a Voicemail Service
In Cisco Unified CM Administration > User Management > User Settings

> UC Service.
www.flane.com.au
Setting up voicemail enables users to receive voice mail messages and redirect incoming audio
calls to the voicemail service. As part of the task of setting up voicemail, you can also configure a
mailstore to enable visual voicemail in the client.
You must complete some specific steps to configure Cisco Unity Connection so that Cisco Jabber
can access voicemail services. You should refer to the Cisco Unity Connection documentation for
instructions on general tasks such as creating users, passwords, and provisioning users with
voicemail access.
Set Up Voicemail – Mailstore server
Provides users with visual voicemail capabilities.
In Cisco Unified CM Administration > User Management >

User Settings > UC Service.
www.flane.com.au
The mailstore service provides users with visual voicemail capabilities.
Set Up Conferencing - On-Premises
On-Premises Conferencing (Cisco WebEx Meetings Server)
In Cisco Unified CM Administration > User Management >

User Settings > UC Service.
www.flane.com.au
Conferencing capabilities enable users to create and attend meetings. Review the different types
of conferencing deployments you can configure. Learn how to set up authentication and enable
communication between the conferencing service and the client.
Set Up On-Premises Conferencing
Cisco WebEx Meetings Server provides on-premises meeting and conferencing services for the
client.
Cisco WebEx Meetings Server Installation and Configuration
The first step in setting up integration between Cisco WebEx Meetings Server and the client is to
install and configure Cisco WebEx Meetings Server. You should refer to the Cisco WebEx
Meetings Server product documentation for installation and configuration procedures.
You cannot currently integrate Cisco Jabber with Cisco WebEx Meetings Server sites that you
configure for single sign on (SSO).
Provide Conferencing Credentials
Choose one of the following methods to provide conferencing credentials to the client:
Users individually specify their credentials in the Options window.
You specify a credentials source on Cisco Unified Communications Manager when you
apply the conferencing service to the service profile.
Specify Conferencing Credentials in the Client
Users can specify their credentials in the Meetings tab on the Options window. To open the
Options window, select File > Options.
Set Up Conferencing - Cloud-Based
Cloud-Based Conferencing (Cisco WebEx Meeting Center)
Integration with Cisco WebEx Meeting Center:
Cloud-based integration:
Cisco WebEx Meeting Center provides the following services to the
client:
Data such as participant chat and roster lists.
Audio and video capabilities.
Hybrid cloud-based integration
Cisco WebEx Meeting Center provides data such as participant chat and
roster lists.
A conferencing bridge provides audio and video capabilities.
www.flane.com.au
Cisco WebEx Meeting Center provides cloud-based meeting and conferencing services for the
client.
Integration with Cisco WebEx Meeting Center
As of this release, there are two types of Cisco WebEx Meeting Center integration for on-
premises deployments:
Cloud-based integration
Hybrid cloud-based integration
Cloud-Based Integration
Cloud-based integration refers to an environment in which Cisco WebEx Meeting Center
provides the following
services to the client:
Data such as participant chat and roster lists.
Audio and video capabilities.
Hybrid Cloud-Based Integration
Hybrid cloud-based integration refers to an environment in which:
Cisco WebEx Meeting Center provides data such as participant chat and roster lists.
A conferencing bridge provides audio and video capabilities.
Authentication with Cisco WebEx Meeting Center
Cisco Jabber supports the following types of authentication with Cisco WebEx Meeting Center:
Direct Authentication
The client can pass user credentials directly to Cisco WebEx Meeting Center.
To enable direct authentication, complete the following steps:
1. Create user accounts for Cisco WebEx Meeting Center using the Cisco WebEx
Administration Tool.
Cisco WebEx Meeting Center must validate user credentials in a direct authentication
scenario. The user accounts hold the credentials so that Cisco WebEx Meeting Center can
validate them when the client attempts to authenticate.
2. Provide Cisco WebEx Meeting Center user credentials to the client.
Authentication with an Identity Provider

The client can redirect authentication from Cisco WebEx Meeting Center to an identity provider.
To enable authentication with an identity provider, complete the following steps:
1. Set up your identity provider as appropriate.
When users attempt to authenticate with Cisco WebEx Meeting Center, the client
redirects that authentication to your identity provider. Your identity provider then
validates the credentials and passes an authentication token back to the client. The client
then passes that token to Cisco WebEx Meeting Center to complete the authentication
process.
2. Provide Cisco WebEx Meeting Center user credentials to the client.
Provide Conferencing Credentials
Choose one of the following methods to provide conferencing credentials to the client:
Users individually specify their credentials in the Options window.
You specify a credentials source on Cisco Unified Communications Manager when you
apply the conferencing service to the service profile. See the topic in this section that
describes how to add the conferencing server to the service profile for instructions.
Specify Conferencing Credentials in the Client
Users can specify their credentials in the Meetings tab on the Options window.
To open the Options window, select File > Options.
Set Up Conferencing
In Cisco Unified CM Administration > User Management > User Settings >
UC Service.
www.flane.com.au
Configure Service Profiles
In Cisco Unified CM Administration > User Management > User Settings >
Service Profile.
Voice Mail
Service
Credential
Source
MailStore
Conferencing
Service
Credential Source
www.flane.com.au
You create a service profile that contains the configuration settings for the services you add on
Cisco Unified Communications Manager. You add the service profile to the end user
configuration for your users. The client can then retrieve settings for available services from the
service profile.
Configure Service Profiles (Cont.)
Enable UDS
Cisco IM and
Presence Service
www.flane.com.au
Configure Users
Through Cisco Unified CM administration screens, configure UC Services for

clients
UC Services that can be defined:
Voice Mail, Visual Voice Mail, Conferencing, Directory, IM and

Presence, CTI
UC Service Profiles assigned to users licensing for the feature handled at the
user level
www.flane.com.au
To configure users, you enable instant messaging and presence and add a service profile to the
users.
Configure Users Individually
Enable instant messaging and presence and add your service profile to individual users.
Procedure
Step 1 Open the Cisco Unified CM Administration interface.
Step 2 Select User Management > End User.
The Find and List Users window opens.
Step 3 Specify the appropriate filters in the Find User where field and then select Find to
retrieve a list of users.
Step 4 Select the appropriate username from the list.
The End User Configuration window opens.
Step 5 Locate the Service Settings section and do the following:
a) Select Enable User for Unified CU IM and Presence.
b) Select your service profile from the UC Service Profile drop-down list.
Step 6 Select Save.
Configure Users in Bulk
Enable instant messaging and presence and add your service profile to multiple users.
Procedure
Step 2 Select Bulk Administration > Users > Update Users > Query.
The Find and List Users To Update window opens.
Step 4 Select Next.
The Update Users Configuration window opens.
Step 5 Select both of the Enable User for Unified CU IM and Presence check boxes.
There are two check boxes for Enable User for Unified CU IM and Presence. To
disable instant messaging and presence, you select one check box. To enable instant
messaging and presence, you select both check boxes.
Step 6 Select the UC Service Profile check box and then select your service profile from the
drop-down list.
Step 7 In the Job Information section, specify if you want to run the job immediately or at a
later time.
Step 8 Select Submit.
Architecture for Voice/Video Calling
Desk phone control

Cisco Jabber for windows registers to Cisco
Unified CM using CTI.
Jabber allows the select of device
Supports Extension Mobility
Soft phone
Cisco Jabber registers to Cisco Unified CM as
a Client Services Framework device (CSF)
using SIP.
www.flane.com.au
Cisco Unified Client Services Framework

Cisco Unified Client Services Framework (CSF) is a software application that provides an
underlying framework for integration of Unified Communications services, including audio,
video, web collaboration, visual voicemail, and so forth, into a software-based desktop
application. The Cisco Unified Client Services Framework allows desktop application users to
access a variety of communication and collaboration services as provided by back-end
collaboration application servers such as Cisco Unified Communications Manager (Unified CM),
Cisco Unity Connection, Cisco WebEx, and Lightweight Directory Access Protocol (LDAP)-
compliant directories. The Cisco Unified Client Services Framework is a device type in Cisco
Unified CM that enables phone registration and communication for Cisco Unified
Communications Integration for Cisco WebEx Connect and Cisco Jabber desktop applications,
and it operates in either softphone mode or deskphone mode to control a Cisco Unified IP Phone.
Softphone Mode of Operation
For the Cisco WebEx Connect and Cisco Jabber desktop applications to operate in softphone
mode, a Cisco Unified Client Services Framework device must be configured in Cisco Unified
CM. The Cisco Unified Client Services Framework will then enable the Cisco Jabber and Cisco
Unified Communications Integration for Cisco WebEx Connect applications to operate as a SIP-
based single-line Cisco Unified IP Phone and will support the full registration and redundancy
mechanisms of a Cisco Unified IP Phone.
Deskphone Control Mode of Operation
When the Cisco Jabber or Cisco WebEx Connect desktop application operates in deskphone
control mode, the application uses CTI/JTAPI to control an associated Cisco Unified IP Phone.
The Unified Client Services Framework uses the Cisco CallManager Cisco IP Phone Services
(CCMCIP) service from Unified CM to provide a listing of valid Cisco Unified IP Phones to
control.
The following design considerations should be taken into account when deploying Cisco Jabber
and other desktop applications that use the Cisco Unified Client Services Framework:
The administrator must determine how to install, deploy, and configure the Unified
Client Services Framework desktop applications in their organization. Cisco recommends
using a well-known installation package such as Altris to install the desktop application,
and use Group Policies to configure the user registry settings for the required components
such as TFTP, CTI Manager, CCMCIP, and LDAP server IP addresses and other
pertinent information.
The user ID and password configuration of the Cisco Unified Client Services Framework
desktop application user must match the user ID and password of the user stored in the
LDAP server to allow for seamless integration of the Unified Communications and back-
end directory components.
The directory number configuration on Cisco Unified CM and the telephoneNumber
attribute in LDAP should be configured with a full E.164 number. A private enterprise
dial plan can be used, but it might involve the need to use application dial rules and
directory lookup rules.
The deskphone mode for control of a Cisco Unified IP Phone uses CTI; therefore, when
sizing a Unified CM deployment, you must also account for other applications that
require CTI usage. For more information on CTI system sizing.
Desktop Share Options
Video desktop Share (BFCP)

Standards based desktop sharing
Interoperates with Telepresence endpoints
Requires UC Manager 8.6
Requires active voice call
Available in both Cloud and on Premise Mode
WebEx Ad-hoc Desktop Share

Only available in Cloud Mode
Two way sharing
Supports Annotation
www.flane.com.au
Jabber for Windows supports desktop sharing using either WebEx Desktop Share or Video
Desktop Share (using BFCP).
Video desktop sharing (BFCP)
Cisco Jabber for Windows provides desktop sharing capabilities for users. You can configure
Cisco Unified Communications Manager 8.6.1 and later to enable video desktop sharing. To
configure Cisco Unified Communications Manager for video desktop sharing, you apply a COP
file to Cisco Unified Communications Manager and enable video desktop sharing on the SIP
profiles of CSF devices.
In a hybrid cloud-based deployment, Cisco WebEx Connect provides instant messaging
capabilities and Cisco Unified Communications Manager provides audio and video
communication capabilities. However, both Cisco WebEx Connect and Cisco Unified
Communications Manager provide desktop sharing functionality.
If you configure video desktop sharing in a hybrid cloud-based deployment, Cisco WebEx
Connect provides desktop sharing functionality if users initiate desktop sharing sessions in instant
messaging conversations. If users initiate desktop sharing sessions during an audio or video
conversation, they use the video desktop sharing capabilities on Cisco Unified Communications
Manager.
Attention
As of this release, Cisco Jabber for Windows supports video desktop sharing in software
phone mode only. Video desktop sharing is not available in desk phone mode.
Migration of your video desktop sharing configuration is not possible. If you configure
video desktop sharing on Cisco Unified Communications Manager 8.6.1 and then
upgrade to Cisco Unified Communications Manager 8.6.2, you must configure video
desktop sharing on 8.6.2.
WebEx Ad-hoc Desktop Share
The Cisco Jabber application provides for smooth escalation to desktop sharing or Cisco's
market-leading collaboration solution, Cisco WebEx® conferencing. You can instantly share
documents and expand chats and conversations to multiparty voice, video, and web conferencing.
Supported WebEx Options:
Cisco WebEx Meeting Center T26L SP 20
Cisco WebEx Meeting Center T27L SP 9
Desktop Sharing (Cont.)
On Cisco UCM version 9.0(1) and higher, BFCP presentation sharing is

automatically enabled.
You can enable video desktop sharing only on software phone devices.
You cannot enable video desktop sharing on desk phone devices.
In hybrid cloud-based deployments, both Cisco WebEx and Cisco UCM provide
desktop sharing functionality.
If users initiate desktop sharing sessions during an instant messaging

session, Cisco WebEx provides desktop sharing capabilities.
If users initiate desktop sharing sessions during an audio or video

conversation, Cisco UCM provides desktop sharing capabilities.
www.flane.com.au
Binary Floor Control Protocol (BFCP) provides video desktop sharing capabilities for CSF
devices. Cisco Unified Communications Manager handles the BFCP packets that users transmit
when using video desktop sharing capabilities. On Cisco Unified Communications Manager
version 9.0(1) and higher, BFCP presentation sharing is automatically enabled. For this reason,
you do not need to perform any steps to enable video desktop sharing on CSF devices.
Restrictions:
Cisco Unified Communications Manager supports BFCP presentation sharing on version
8.6(1) and higher only. You cannot enable BFCP, or provision users with video desktop
sharing capabilities, on versions lower than 8.6(1).
You can enable video desktop sharing only on software phone devices. You cannot
enable video desktop sharing on desk phone devices.
In hybrid cloud-based deployments, both Cisco WebEx and Cisco Unified
Communications Manager provide desktop sharing functionality.
If users initiate desktop sharing sessions during an instant messaging session, Cisco
WebEx provides desktop sharing capabilities.
If users initiate desktop sharing sessions during an audio or video conversation, Cisco
Unified Communications Manager provides desktop sharing capabilities.
Desktop Sharing Summary
Video Desktop
UC Manager WebEx Desktop
Deployment Model Share (requires UC
Version Share
manager 8.6+)
< 8.6
Cloud Model
8.6 +
< 8.6
On Premise Model
8.6 +
www.flane.com.au
Set Up Audio and Video Capabilities

Softphone
Create Software Phone Devices
Software phones let users send and receive audio and video through
their computers.
You should use the CSFusername format for CSF device names.
www.flane.com.au
You should use the CSFusername format for CSF device names. For example, you create a CSF
device for a user named Tanya Adams, whose username is tadams. In this case, you should
specify CSFtadams as the device name.
Associate End Users with a Line Appearance
Navigate to Device > Phone and select the directory number

Click Associate End
Users.
Select the user and

click Add Selected.
Verify the association

and click Save.
www.flane.com.au
Desk Phone
Users can control desk phones on their computers to place audio calls.
In Cisco Unified CM Administration Interface > Device > Phone
Select Allow Control of Device from CTI.
Select Enabled from the Video Capabilities drop-down list.
www.flane.com.au
Users can control desk phones on their computers to place audio calls.
Procedure
Step 2 Select Device > Phone.
The Find and List Phones window opens.
Step 3 Select Add New.
Step 4 Select the appropriate device from the Phone Type drop-down list and then select Next.
Step 5 Complete the following steps in the Device Information section:
a) Enter a meaningful description in the Description field.
The client displays device descriptions to users. If users have multiple devices of the
same model, the descriptions help users tell the difference between multiple devices.
b) Select Allow Control of Device from CTI.
If you do not select Allow Control of Device from CTI, users cannot control the desk
phone.
Step 6 Complete the following steps to enable desk phone video capabilities:
a) Locate the Product Specific Configuration Layout section.
b) Select Enabled from the Video Capabilities drop-down list.
If possible, you should enable desk phone video capabilities on the device configuration.
However, certain phone models do not include the Video Capabilities drop-down list at
the device configuration level. In this case, you should open the Common Phone
Profile Configuration window and then select Enabled from the Video Calling drop-
down list.
Step 7 Specify all other configuration settings on the Phone Configuration window as
appropriate.
Step 8 Select Save.
An message displays to inform you if the device is added successfully. The Association
Information section becomes available on the Phone Configuration window.
Associate End Users with a Line Appearance
Navigate to Device > Phone and select the directory number

Click Associate End
Users.
Select the user and

click Add Selected.
Verify the association

and click Save.
www.flane.com.au
Desk Phone (Cont.)
Enable Video Rate Adaptation
Negotiate optimum video quality. Video rate adaptation dynamically increases or
decreases video quality based on network conditions.
To use video rate adaptation, you must enable Real-Time Transport Control Protocol
(RTCP) on Cisco Unified Communications Manager.
RTCP is enabled on software phone devices by default. However, you must enable
RTCP on desk phone devices.
www.flane.com.au
Enable Video Rate Adaptation

Cisco Jabber uses video rate adaptation to negotiate optimum video quality. Video rate adaptation
dynamically increases or decreases video quality based on network conditions.
To use video rate adaptation, you must enable Real-Time Transport Control Protocol (RTCP) on
Cisco Unified Communications Manager.
RTCP is enabled on software phone devices by default. However, you must enable RTCP on desk
phone devices.
Desk Phone (Cont.)
Add a CTI Service
The CTI service lets users control devices.

> UC Service.
Apply CTI Service

> Service Profile.
www.flane.com.au
Add a CTI Service

The CTI service lets users control devices.
Procedure
Step 2 Select User Management > User Settings > UC Service.
The Find and List UC Services window opens.
The UC Service Configuration window opens.
Step 4 In the Add a UC Service section, select CTI from the UC Service Type drop-down list.
Step 5 Select Next.
Step 6 Provide details for the instant messaging and presence service as follows:
a) Specify a name for the service in the Name field.
The name you specify displays when you add services to profiles. Ensure the name you
specify is unique, meaningful, and easy to identify.
b) Specify an optional description in the Description field.
c) Specify the CTI service address in the Host Name/IP Address field.
d) Specify the port number for the CTI service in the Port field.
Step 7 Select Save.
Apply CTI Service
After you add a CTI service on Cisco Unified Communications Manager, you must apply it to a
service profile so that the client can retrieve the settings.
Procedure
Step 2 Select User Management > User Settings > Service Profile.
The Find and List Service Profiles window opens.
Step 3 Find and select your service profile.
The Service Profile Configuration window opens.
Step 4 In the CTI Profile section, select up to three services from the following drop-down lists:
Primary
Secondary
Tertiary
Step 5 Select Save.
Extend and Connect
Users control calls on devices such as public switched telephone network
(PSTN) phones and private branch exchange (PBX) devices.
Create CTI Remote Devices

CTI remote devices let users control calls on devices other than software phone devices or desk
phone devices
such as Cisco IP phones.
Extend and Connect Capabilities
Cisco Unified Communications Manager Extend and Connect capabilities let users control calls
on devices such as public switched telephone network (PSTN) phones and private branch
exchange (PBX) devices.
Cisco recommends that you use extend and connect capabilities with Cisco Unified
Communications Manager 9.1(1) and higher only.
Extend and Connect (Cont.)
Provisioning CTI Remote Devices
Dedicated Device: To provision CTI remote devices as dedicated

devices, you should add remote destinations through the Cisco Unified
CM Administration interface.
Alternative Device you should not add remote destinations. Users can
add, edit, and delete remote destinations through the client interface.
www.flane.com.au
Provisioning CTI Remote Devices

Dedicated Device
You can provision users with dedicated CTI remote devices. For example, each user has a PSTN
phone at their workstation. You want to allow the users to make calls with their PSTN phones
using the client.
You do not plan to provision users with software phone devices or desk phone devices.
To provision CTI remote devices as dedicated devices, you should add remote destinations
through the Cisco Unified CM Administration interface. This ensures that users can
automatically control their phones and place calls when they start the client.
Alternative Device
You can provision CTI remote devices so that users can specify an alternative phone number to
their software phone device or desk phone device. For example, each user can work remotely
from home.
In this case, users can specify their home phone numbers as remote destinations. This allows the
users to control home phones with the client.
If you plan to provision CTI remote devices as an alternative device, you should not add remote
destinations. Users can add, edit, and delete remote destinations through the client interface.
Enable Users to Modify Remote Destinations
When a user logs in, the client retrieves the user's device list from Cisco Unified Communications
Manager. If that device list contains a software phone device or desk phone device, the client
automatically lets users add, edit, and delete remote destinations through the client interface.
If that device list contains only a CTI remote device, the client does not let users add, edit, and
delete remote destinations. You must enable users to add, edit, and delete remote destinations in
the client configuration.
Using CTI Remote Devices with the Client
If a user is signed in to the client and sets a remote device as active, that device
rings when the user receives incoming calls. Additionally, the client routes outgoing
calls to the active device when the user is signed in.
If a user is not signed in to the client, and that user receives an incoming call to the
directory number, all devices set as remote destinations ring.
www.flane.com.au
Using CTI Remote Devices with the Client

If a user is signed in to the client and sets a remote device as active, that device rings when the
user receives incoming calls. Additionally, the client routes outgoing calls to the active device
when the user is signed in.
If a user is not signed in to the client, and that user receives an incoming call to the directory
number, all devices set as remote destinations ring.
Limitations and Known Issues
This section describes limitations and known issues that currently exist for Cisco Unified
Communications Manager extend and connect capabilities.
You can create only one remote destination per user. Do not add two or more remote
destinations for a user.
Two or more users cannot use the same remote destination.
Users cannot use the same remote destination for multiple devices.
You cannot provision extend and connect capabilities for devices that you configure as
endpoints on the Cisco Unified Communications Manager cluster.
Incoming calls incorrectly ring on remote devices if the following occurs:
1. A user adds a number for a remote destination.
Cisco Unified Communications Manager routes incoming calls to that remote
destination. The user can control the call session with the client.
2. The user changes their phone. For example, the user selects their software phone.
Cisco Unified Communications Manager routes incoming calls to the user's
software phone. However, if the user does not answer incoming calls on the
software phone within 4 or 5 seconds, the user's remote destination also rings.
To resolve this issue, users must delete numbers for remote destinations when
they change their phones.
Enable User Mobility
User Management > End User.
www.flane.com.au
Enable User Mobility

You must enable user mobility to provision CTI remote devices. If you do not enable mobility for
users, you cannot assign those users as owners of CTI remote devices.
CTI remote devices are virtual devices that monitor and have call control over
a user's remote destination.
www.flane.com.au

CTI remote devices are virtual devices that monitor and have call control over a user's remote
destination.
Procedure
Step 2 Select Device > Phone.
The Find and List Phones window opens.
Step 4 Select CTI Remote Device from the Phone Type drop-down list and then select Next.
Step 5 Select the appropriate user ID from the Owner User ID drop-down list.
Only users for whom you enable mobility are available from the Owner User ID drop-
down list.
Cisco Unified Communications Manager populates the Device Name field with
the user ID and a CTRID prefix; for example, CTRIDusername
The Rerouting Calling Search Space ensures that users can send and
receive calls from the CTI remote device.
www.flane.com.au
Cisco Unified Communications Manager populates the Device Name field with the user ID and a
CTRID prefix; for example, CTRIDusername
Step 6 Edit the default value in the Device Name field, if appropriate.
Step 7 Ensure you select an appropriate option from the Rerouting Calling Search Space drop-
down list in the
Protocol Specific Information section.
The Rerouting Calling Search Space drop-down list defines the calling search space for
re-routing and ensures that users can send and receive calls from the CTI remote device.
Step 8 Specify all other configuration settings on the Phone Configuration window as
appropriate.
Step 9 Select Save.
The fields to associate directory numbers and add remote destinations become available
on the Phone Configuration window.
Add a Directory Number to the Device
Associate end users with the directory number
Click Associate End

Users.
Select the user and

click Add Selected.
www.flane.com.au
You must add directory numbers to devices in Cisco Unified Communications Manager. This
topic provides instructions on adding directory numbers using the Device > Phone menu option
after you create your device.
Under this menu option, only the configuration settings that apply to the phone model or CTI
route point display. See the Cisco Unified Communications Manager documentation for more
information about different options to configure directory numbers.
Add a Remote Destination
Remote destinations represent the CTI controllable devices that are available to
If you plan to provision users with CTI remote devices along with software phone
devices and desk phone devices, you should not add a remote destination
through the Cisco Unified CM Administration interface.
Users can enter remote destinations through the client interface.
You must specify JabberRD in the Name field. The client uses only the
JabberRD remote destination.
www.flane.com.au
Add a Remote Destination

Remote destinations represent the CTI controllable devices that are available to users.
You should add a remote destination through the Cisco Unified CM Administration interface if
you plan to
provision users with dedicated CTI remote devices. This task ensures that users can automatically
control their phones and place calls when they start the client.
If you plan to provision users with CTI remote devices along with software phone devices and
desk phone devices, you should not add a remote destination through the Cisco Unified CM
Users can enter remote destinations through the client interface.
Note
You should create only one remote destination per user. Do not add two or more remote
destinations for a user.
Cisco Unified Communications Manager does not verify if it can route remote
destinations that you add through the Cisco Unified CM Administration interface. For
this reason, you must ensure that Cisco Unified Communications Manager can route the
remote destinations you add.
Cisco Unified Communications Manager automatically applies application dial rules to
all remote destination numbers for CTI remote devices.
Associate a Device to a User
Navigate to User Management > End User
Add the Primary Extension
Associate a device with the user
Physical Phone
Soft phone (CSF)
Remote CTI Device
www.flane.com.au
When you associate a user with a device, you provision that device to the user.
Procedure
Step 2 Select User Management > End User.
The Find and List Users window opens.
Step 4 Select the appropriate user from the list.
Step 5 Locate the Device Information section.
Step 6 Select Device Association.
The User Device Association window opens.
Step 7 Select the devices to which you want to associate the user.
Step 8 Select Save Selected/Changes.
Assign End Users to User Group
Navigate to User Management > User Group
Assign the user to the group Standard CTI Enabled and Standard CCM End User
Group
Select the User group
Standard CTI Enabled.
Select the users and

click Add Selected.
Add End Users to

the CTI group.
www.flane.com.au
Step 9 Select User Management > End User and return to the Find and List Users window.
Step 10 Find and select the same user from the list.
Step 11 Locate the Permissions Information section.
Step 12 Select Add to Access Control Group.
The Find and List Access Control Groups dialog box opens.
Step 13 Select the access control groups to which you want to assign the user.
At a minimum you should assign the user to the following access control groups:
Standard CCM End Users
Standard CTI Enabled
If you are provisioning users with secure phone capabilities, do not assign the users to the
Standard CTI Secure Connection group.
Remember
Certain phone models require additional control groups, as follows:
Cisco Unified IP Phone 9900 or 8900 series, select Standard CTI Allow
Control of Phones supporting Connected Xfer and conf.
Cisco Unified IP Phone 6900 series, select Standard CTI Allow Control of
Phones supporting Rollover Mode.
Step 14 Select Add Selected.
The Find and List Access Control Groups window closes.
Step 15 Select Save on the End User Configuration window.
Specify Your TFTP Server Address
Specify Your TFTP Server on Cisco Unified Communications IM and

Presence
In Cisco Unified CM IM and Presence Administration interface. Select

Application > Legacy Clients > Settings.
www.flane.com.au
Specify Your TFTP Server Address

The client gets device configuration from the TFTP server. For this reason, you must specify your
TFTP server address when you provision users with devices.
Specify Your TFTP Server Address (Cont.)
Specify TFTP Servers in Phone Mode
Users enter the TFTP server address in the Connection Settings window
when they start the client.
You specify the TFTP server address during installation with the TFTP
argument.
Specify TFTP Servers with the Cisco WebEx Administration Tool
Specify your TFTP server address with the Cisco WebEx Administration Tool.
www.flane.com.au
Specify Your TFTP Server on Cisco Unified Communications IM and Presence

Complete the steps to specify the address of your TFTP server on Cisco Unified Communications
IM and Presence.
Specify TFTP Servers in Phone Mode
If you deploy the client in phone mode you can provide the address of the TFTP server as
follows:
Users enter the TFTP server address in the Connection Settings window when they start
the client.
You specify the TFTP server address during installation with the TFTP argument.
Create a CCMCIP Profile
The client gets device lists for users from the CCMCIP server.
In Cisco Unified CM IM and Presence Administration interface.
Select Application > Legacy Clients > CCMCIP Profile.
www.flane.com.au
The client gets device lists for users from the CCMCIP server.
Application Dialing and Directory Lookup
Rules
Cisco IM and Presence then queries Cisco Unified Communications Manager to
obtain these dialing rules for the Cisco Unified Personal Communicator.
Application dialing rules are used to manipulate numbers that are dialed from
Cisco Jabber.
Directory lookup rules transform caller identification numbers into numbers that
can be looked up in the directory from Cisco Unified Personal Communicator.
www.flane.com.au
You configure dial plan mapping to ensure that dialing rules on Cisco Unified Communications
Manager match dialing rules on your directory.
Application Dial Rules
Application dial rules automatically add or remove digits in phone numbers that users dial.
Application dialing rules manipulate numbers that users dial from the client.
For example, you can configure a dial rule that automatically adds the digit 9 to the start of a 7
digit phone number to provide access to outside lines.
Directory Lookup Dial Rules
Directory lookup dial rules transform caller ID numbers into numbers that the client can lookup
in the directory.
Each directory lookup rule you define specifies which numbers to transform based on the initial
digits and the length of the number.
For example, you can create a directory lookup rule that automatically removes the area code and
two digit prefix digits from 10 digit telephone numbers. An example of this type of rule is to
transform 4089023139 into 23139.
Summary
Cisco Jabber product modes configuration requriements
Activating Cisco IM and Presence essential services
Configuring Cisco Jabber services
Cisco IM and presence
CTI
Voice Mail
Conferencing Services
Configuring Cisco Jabber for voice and video calling:
Deskphone mode
Softphone mode
Extend and Connect (Remote CTI Device) mode
Configure Desktop sharing
Lesson 6
Jabber for Everyone

Jabber for Everyone Overview
A new offer which is being made available to Cisco customers from mid-year
2012 onwards.
Presence and instant messaging (IM) available at zero cost.
Provides the complete flexibility of Jabber's Bring Your Own Device (BYOD)
capabilities for presence and IM.
The full range of Cisco Jabber clients deployable on Windows, MAC, iPad,
iPhone, BlackBerry, Android1, as well as Cisco Cius, are supported.
Customers can also build and deploy presence and IM-enabled applications
using the Jabber Web Software Development Kit (SDK).
Leverage Cisco Jabber clients to control their IP desk phone to initiate and
manage calls.
www.flane.com.au
“Jabber for Everyone” is a new offer which is being made available to Cisco customers from mid-
year 2012 onwards. The offer makes Cisco Jabber presence and instant messaging (IM) available
at zero cost for an end-user license to all employees of Cisco customers who have deployed Cisco
Unified Communications Manager for all or even part of their organization.
The “Jabber for Everyone” offer provides the complete flexibility of Jabber's Bring Your Own
Device (BYOD) capabilities for presence and IM. The full range of Cisco Jabber clients
deployable on Windows, MAC, iPad, iPhone, BlackBerry, and Android1 are supported.
Customers can also build and deploy presence and IM-enabled applications using the Jabber Web
Software Development Kit (SDK).
As part of the offer, employees who are existing Cisco IP Telephony users can leverage Cisco
Jabber clients to control their IP desk phone to initiate and manage calls. In addition, employees
who are existing Cisco Unity Connection users can leverage Cisco Jabber clients for visual
voicemail. Customers who are fully licensed for Cisco Collaboration can easily expand beyond
the “Jabber for Everyone” IM and Presence offer to leverage Jabber's complete Unified
Communications capabilities, including WebEx Meetings, and standards-based voice and HD
video (using Cisco's Precision Video Engine PVE technology) across desktop and mobile
devices.
“Jabber for Everyone” Solution
supported features
Core IM and Presence
Advanced IM
Rich UC Presence
Deskphone Control
Visual Voicemail
You must configure Core IM and Presence as the first step to utilize basic
features of IM and presence and as a prerequisite to further enable Rich UC
Presence, any of the Advanced IM or Deskphone Control features.
www.flane.com.au
The “Jabber for Everyone” offer enables a broad range of Cisco Jabber features as follows:
Core IM and Presence—This is the baseline offering. It provides standard IM features
such as One-to-One and Group Chat IM. It also provides a range of presence states
(“Available,” “Away,” “Offline,” “Do Not Disturb,” and custom status). Core IM and
Presence also enables Multi-Device which allows a user to log in to multiple Cisco
Jabber devices in parallel (such as Cisco Jabber for Windows and Cisco Jabber IM for
iPhone), send and receive IMs to multiple devices simultaneously and set presence state
from any device. See Table 1 for details of supported features.
Advanced IM—If you want to add other advanced IM features such as Federation,
Compliance and High Availability, you can incorporate them into your deployment with
additional configuration.
Rich UC Presence—If you want to integrate additional sources of presence including
the telephony state of Cisco IP phone-enabled users (“On a call”) or meeting status from
Microsoft Exchange (“In a Meeting”) with the presence features that are available with
Core IM and Presence, you can do so with additional configuration. See Table 1 for
details.
Desk Phone Control—Along with IM and presence capabilities, the “Jabber for
Everyone” offer allows users who are configured for Cisco IP Telephony to also use their
Cisco Jabber client to control their Cisco IP phone to make and answer calls (through
Computer Telephony Integration (CTI)).
Visual Voicemail—If you have Cisco Unity Connection deployed, you can add the
ability to view, play, sort and delete voicemail messages from Cisco Jabber with
additional configuration.
You must configure Core IM and Presence as the first step to utilize basic features of IM and
presence and as a prerequisite to further enable Rich UC Presence, any of the Advanced IM,
Desk Phone Control or Visual Voicemail features, if you wish to do so. You can flexibly select
which features of Rich UC Presence and Advanced IM you wish to enable. In general, these
optional features do not have to be configured or enabled in any particular sequence.
Supported Cisco Jabber features
Feature Jabber for Jabber for Jabber for Jabber for Jabber for Jabber
Windows Mac BlackBerry iPhone iPad Web SDK
Core IM and Presence Features
Presence X X X X X X
Instant X X X X X X
messaging
Multi-device X X X X X X
Group chat X X X X X X
File transfer X X
Emoticons X X X X X X
Contact X X X X X
search
www.flane.com.au
This matrix lists the features that the “Jabber for Everyone” offer supports for each client.
Supported Cisco Jabber features (Cont.)

Microsoft X
Office
Integration,
Office 2007,
20102
Offline X X X X
messages
Client X X
history
Localization X X X X X X
www.flane.com.au
Advanced IM Features
Interdomain X X X X X X
federation
Partitioned X X X X X X
intradomain
federation
with
Microsoft
(LCS, OCS)
Start/join X X X X X
WebEx
meetings
Visual X X
Voicemail
www.flane.com.au

Rich UC Presence Features
Cisco X X X X X X
Telephony
Presence
Integration
(“On a call”)
“In a X X X X X X
meeting”
status via
Exchange
calendar
integration
www.flane.com.au
Deskphone Control
Desktop X X
Phone
Control
Visual Voicemail
Visual X X
Voicemail
www.flane.com.au
The following features are not included in the “Jabber for Everyone” offer:
Audio
Video
Desktop sharing
\Options for phone configuration
Jabber for Everyone architecture
www.flane.com.au
Jabber for Everyone Architecture

“Jabber for Everyone” is an IM and Presence solution that consists of the following components:
Server software—Provides IM, presence, and directory services to the client application
Client application—Renders IM and presence functionality to users
“Jabber for Everyone” comprises the following server components:
Cisco Unified Communications Manager (Unified CM)—Provides user configuration,
device
configuration, licensing and directory integration services.
IM and Presence Service—Provides instant messaging and presence capabilities.
External directory source—Provides contact search and retrieval services. For directory
requirements for specific clients, see the appropriate client documentation.
“Jabber for Everyone” supports the following Cisco Jabber clients, as release available:
Cisco Jabber for Mac
Cisco Jabber IM for Android
Cisco Jabber IM for BlackBerry
Cisco Jabber Web SDK
License requirements
Licenses are available to Cisco Unified Communications Manager customers at

no additional license cost.
Ordering options are available for existing User Connect Licensing (UCL) and
Cisco Unified Workspace Licensing (CUWL) customers as follows:
Unified CM UCL customers can order “Jabber for Everyone” to provide IM to users that
are not Unified CM users.
CUWL customers can order “Jabber for Everyone” to provide IM to users that are not
Unified CM users.
www.flane.com.au
License Requirements
With the “Jabber for Everyone” offer, Jabber IM client applications and IM and Presence Service
(on-premises) licenses are available to Cisco Unified Communications Manager customers at no
additional license cost.
Ordering options are available for existing User Connect Licensing (UCL) and Cisco Unified
Workspace Licensing (CUWL) customers as follows:
Unified CM UCL customers can order “Jabber for Everyone” to provide IM to users that
are not Unified CM users.
CUWL customers can order “Jabber for Everyone” to provide IM to users that are not
Unified CM users.
From Cisco Unified Communications Manager Release 9.0(1) onwards, IM and Presence is an
integrated service, therefore all Unified CM users have access to IM as part of the core user
licensing.
Jabber for Everyone deployment workflow
There are three deployment scenarios for “Jabber for Everyone”:
www.flane.com.au
Core IM and Presence represents the baseline offering for the “Jabber for Everyone” solution.
You can extend your deployment by incorporating any of the following additional, optional
feature sets:
Advanced IM
Rich UC Presence
Desk Phone Control
Visual Voicemail
Each deployment scenario assumes that Unified CM is installed.
Core IM and Presence deployment
The following are the high-level tasks that you must complete to enable core IM
and presence features in your network:
1. Set up users on Unified CM.
2. Install IM and Presence Service.
3. Verify essential services on Unified CM and IM and Presence Service.
4. Specify capabilities assignments for end users on Unified CM.
5. Create an LDAP profile on IM and Presence Service.
6. Install Cisco Jabber.
You can deploy “Jabber for Everyone” in a mixed cluster where you provision
some users with only instant messaging and availability and other users with
instant messaging and availability along with audio capabilities.
www.flane.com.au
The following are the high-level tasks that you must complete to enable core IM and presence
features in your network:
1. Set up users on Unified CM.
2. Install IM and Presence Service.
3. Verify essential services on Unified CM and IM and Presence Service.
4. Specify capabilities assignments for end users on Unified CM.
5. Create an LDAP profile on IM and Presence Service.
6. Install Cisco Jabber.
You can deploy “Jabber for Everyone” in a mixed cluster where you provision some users with
only instant messaging and availability and other users with instant messaging and availability
along with audio capabilities.
You should create separate service profiles for users that have only instant messaging and
availability capabilities. If the service profile contains a CTI or CCMCIP profile, the client
attempts to retrieve device lists for users from Cisco Unified Communications Manager. If no
device lists exist for users, the client continually requests device lists from the server. As a result,
the server consumes additional CPU resources.
Advanced IM deployment
“Jabber for Everyone” supports optional advanced IM and presence features that
extend your baseline deployment:
Federation
IM Compliance
High Availability
Intercluster Peering
Rich presence with Microsoft Exchange
www.flane.com.au
“Jabber for Everyone” supports optional advanced IM and presence features that extend your
baseline deployment:
Federation
IM Compliance
High Availability
Intercluster Peering
Rich UC Presence deployment
The following are the high-level tasks that you must complete if you want to
deploy rich presence for Cisco IP phone users in your network:
1. Configure the SIP Publish trunk.
2. Configure a Presence gateway for Unified CM.
3. Associate line appearances to IM and presence enabled users.
www.flane.com.au
Rich UC Presence Deployment

You can optionally expand your “Jabber for Everyone” deployment to include Telephone
Presence (“On a call”) for Cisco IP phone users and Meeting Status (“In a Meeting”) through
integration with Microsoft Exchange.
Telephony Presence Integration
The following are the high-level tasks that you must complete if you want to deploy rich presence
for Cisco IP phone users in your network:
1. Configure the SIP Publish trunk.
2. Configure a Presence gateway for Unified CM.
3. Associate line appearances to IM and presence enabled users.
Summary
Cisco Jabber product modes configuration requriements
Activating Cisco IM and Presence essential services
Configuring Cisco Jabber services
Cisco IM and presence
CTI
Voice Mail
Conferencing Services
Configuring Cisco Jabber for voice and video calling:
Deskphone mode
Softphone mode
Extend and Connect (Remote CTI Device) mode
Configure Desktop sharing
Lesson 7
Cisco Unified IM and

Presence Multi-Node
deployments
Cisco Unified IM and Presence Multi-Node
Deployment Overview
You must manually turn on High Availability in a subcluster.
If the node detects that any critical service is not running for a configurable
outage period (90 seconds is the default value), it instructs the peer node to
initiate a failover.
Automatically moves all user to the backup node.
Instant Message and Availability services from that node can failover to the
second node in the subcluster
In IM and Presence Release 9.0(1) and later, manual recovery is not required.
When the network issue is resolved, auto-recovery occurs without administrator

intervention.
www.flane.com.au
The IM and Presence Service supports High Availability deployments. Cisco recommends that
you configure your IM and Presence deployments as High Availability deployments.
Although mixed mode deployments are permitted, for example High Availability subclusters and
non High Availability subclusters in a single deployment, we do not recommend this
configuration.
You must manually turn on High Availability in a subcluster. You can achieve a High
Availability deployment by configuring the Balanced Mode (Redundant High Availability) or the
Active/Standby Redundant High Availability deployment models, and turning on High
Availability in your deployment.
Cisco Unified IM and Presence Multi-Node
Deployment - Fallback
IM and Presence supports automatic fallback to the primary node after a failover.
Automatic fallback is the process of moving users back to the primary node after
a failover without manual intervention.
You can enable automatic fallback with the Enable Automatic Fallback service
parameter on the Cisco Unified CM IM and Presence Administration interface.
Automatic fallback occurs in the following scenarios:

A critical service on Node A fails
Node A is rebooted
Node A loses communications with Node B
If failover occurs for a reason other than one of the three scenarios listed here,
you must recover the node manually. If you do not want to wait 10 minutes before
the automatic fallback, you can perform a manual fallback to the primary node.
www.flane.com.au
IM and Presence supports automatic fallback to the primary node after a failover. Automatic
fallback is the process of moving users back to the primary node after a failover without manual
intervention. You can enable automatic fallback with the Enable Automatic Fallback service
parameter on the Cisco Unified CM IM and Presence Administration interface.
Automatic fallback occurs in the following scenarios:
A critical service on Node A fails—A critical service (for example, the Presence Engine)
fails on Node A. Automatic failover occurs and all users are moved to Node B. Node A is
in a state called "Failed Over with Critical Services Not Running." When the critical
service recovers, the node state changes to "Failed Over." When this occurs Node B
tracks the health of Node A for 30 minutes. If no heartbeat is missed in this timeframe
and the state of each node remains unchanged, automatic fallback occurs.
Node A is rebooted—Automatic failover occurs and all users are moved to Node B.
When Node A returns to a healthy state and remains in that state for 30 minutes
automatic fallback will occur.
Node A loses communications with Node B—Automatic failover occurs and all users
are moved to Node B. When communications are re-established and remain unchanged
for 30 minutes automatic fallback will occur. If failover occurs for a reason other than
one of the three scenarios listed here, you must recover the node manually. If you do not
want to wait 10 minutes before the automatic fallback, you can perform a manual
fallback to the primary node.
High Availability for Cisco Jabber (XMPP
Failover)
1. When the server recovery manager

determines that a service is no longer
communicating, a failover user move
operation from server 1A to server 1B is
initiated. User123 is moved from home
server 1A and is now homed to server 1B.
2. Cisco Jabber determines connectivity with

server 1A is lost through time-out,
connection loss, or XMPP protocol update,
and it initiates a new connection to server
1B.
www.flane.com.au
All users in the Cisco IM and Presence cluster must be assigned to a server prior to any exchange
of information. By default, Cisco IM and Presence allows for automatic user assignment that is
equally balanced across all servers in the cluster. If desired, the administrator can control where
users are assigned by setting the User Assignment Mode Sync Agent service parameter to None
instead of the default balanced. If this parameter is set to None, user assignment is done from the
System > Topology menu.
Cisco Jabber clients can be provisioned with a basic deployment, a highly available deployment
for automatic redundancy, and an IM and presence only deployment. In a Cisco IM and Presence
two-server subcluster, users associated with one server are known by the other server in the
subcluster, thus allowing for automatic failover when service communication with the configured
server is interrupted. Cisco Jabber client high availability is supported only within a Cisco IM and
Presence subcluster.
As illustrated in the figure, the server recovery manager monitors the various services on Cisco
IM and Presence to determine if a service has failed and then to initiate an XMPP failover event.
The following sequence of events occurs during an XMPP failover:
1. When the server recovery manager determines that a service is no longer communicating,
a failover user move operation from server 1A to server 1B is initiated. User123 is moved
from home server 1A and is now homed to server 1B.
2. The Cisco Jabber client determines that connectivity with server 1A is lost through time-
out, connection loss, or XMPP protocol update, and it initiates a new connection to server
1B.
Cisco UP Server Recovery Manager (SRM)
Manages the failover between nodes in a subcluster.
After you turn on High Availability in a subcluster, the Cisco UP SRM on each node
establishes heartbeat connections with the peer node, and begins to monitor the
critical processes.
The SRM is responsible for the user move operations after it detects that failover has
occurred.
It is the SRM on the peer node, not on the failed node, that performs the user move
operation.
On failover, the SRM will move users that are signed in first, and then move users that
are not signed in. If you initiate a fallback, users that are not signed in are moved first,
and then users that are signed in.
www.flane.com.au
The Cisco Server Recovery Manager (SRM) on IM and Presence manages the failover between
nodes in a subcluster. The Cisco Server Recovery Manager manages all state changes in a node;
state changes are either automatic or initiated by the administrator (manual).
After you turn on High Availability in a subcluster, the Cisco Server Recovery Manager on each
node establishes heartbeat connections with the peer node, and begins to monitor the critical
processes.
The SRM is responsible for the user move operations after it detects that failover has occurred. It
is the SRM on the peer node, not on the failed node, that performs the user move operation. For
example, if node A fails, the SRM on node B performs the user move operation. The SRM
throttles the number of users moved to the peer node, it moves the users in batches or iterations.
You can configure the number of users that the SRM moves per iteration (the default value is 25).
On failover, the SRM will move users that are signed in first, and then move users that are not
signed in. Note that if you initiate a fallback or if an automatic fallback occurs, users that are not
signed in are moved first, and then users that are signed in.
If the SRM is not turned on, it does not monitor any critical processes, nor does it monitor the
heartbeat connections with the peer node.
Cisco UP Replication Watcher Service
Monitors IDS replication state on Cisco Unified Presence.
Delays the startup of Other Cisco Unified IM and Presence feature

services until IDS replication is successfully established.
www.flane.com.au
The Cisco Replication Watcher monitors IDS replication state on the IM and Presence Service.
Other IM and Presence services are dependent on the Cisco Replication Watcher service. These
dependent services use the Cisco Replication Watcher service to delay startup until such time as
IDS replication is in a stable state.
On the subscriber nodes, the Cisco Replication Watcher service delays the startup of feature
services until IDS replication is successfully established. The Cisco Replication Watcher service
only delays the startup of feature services on the problem subscriber node in a cluster, it will not
delay the startup of feature services on all subscriber nodes due to one problem node. For
example, if IDS replication is successfully established on node1 and node2, but not on node3, the
Cisco Replication Watcher service allows feature services to start on node1 and node2, but delays
feature service startup on node3.
The Cisco Replication Watcher service behaves differently on the publisher node. It only delays
the startup of feature services until a timeout expires. When the timeout expires, it allows all
feature services to start on the publisher node even if IDS replication is not successfully
established.
The Cisco Replication Watcher service generates an alarm when it delays feature service startup
on a node. It then generates a notification when IDS replication is successfully established on that
node.
The Cisco Replication Watcher service impacts both a fresh multi-node installation, and a
software upgrade procedure. Both will only complete when the publisher and subscriber nodes
are running the same IM and Presence release, and IDS replication is successfully established on
the subscriber nodes.
Subclusters
A subcluster is a single Cisco Unified IM and Presence server, or a pair of Cisco

Unified IM and Presence servers, where each node has an independent
database and set of users operating with a shared availability database that is
able to support common users.
By default, allows for automatic user assignment that is equally balanced across
all servers in the cluster.
The administrator can control where users are assigned.
www.flane.com.au
The multi-node feature introduces the concept of a subcluster. A subcluster is a single IM and
Presence server, or a pair of IM and Presence servers, where each node has an independent
database and set of users operating with a shared availability database that is able to support
common users.
In a single-node deployment within a subcluster, there is no High Availability failover protection
for users assigned to the node. In a dual-node deployment within a subcluster, if you turn on High
Availability in the subcluster, users have failover protection; each node acts as a backup for the
other node allowing clients to fail over in case of outages of components or nodes. When you turn
on High Availability in a subcluster, all users in the subcluster have redundancy and full failover
capabilities.
User Assignment Mode
Balanced: Cisco Unified IM and Presencedivides all users equally across all nodes in
all subclusters.
Active/Standby: Cisco Unified IM and Presenceassigns all users only to the first node
of a subcluster. If there is only a single node in the subcluster, Cisco Unified IM and
Presenceuses this node for assignment regardless of the location of the node within
the subcluster.
None: you must manually assign your users to nodes in system topology
management GUI.
www.flane.com.au
To allow users to receive the availability and Instant Messaging (IM) services on IM and
Presence, you must assign users to nodes, and subclusters, in your IM and Presence deployment.
You can manually or automatically assign users in a IM and Presence deployment. You manage
user assignment using the User Assignment Mode parameter on the Sync Agent on IM and
Presence.
Balanced mode (default) assigns users equally to each node in the subcluster and attempts to
balance the total number of users equally across each node. Active-Standby mode assigns all
users to the first node of the subcluster, leaving the secondary server as a backup. None mode
results in no assignment of the users to the nodes in the cluster by the sync agent. The default
mode is Balanced.
If you select manual user assignment, you must manually assign your users to nodes, and
subclusters, using the System Topology interface in the Cisco Unified CM IM and Presence
Administration.
Balanced User Assignment Redundant
High Availability Deployment
Supports up to fifteen thousand users per cluster.
Using the balanced mode High Availability deployment option in a redundant mode,
as compared to a non-redundant mode, only half the number of users are assigned to
each node. However, if one node fails, the other node will handle the full load of the
additional 50% of users in the subcluster, even at peak traffic.
In order to support this failover protection, you must turn on High Availability in each of
the subclusters in your deployment.
www.flane.com.au
You can achieve a balanced mode High Availability deployment by evenly balancing users across
all nodes in the subcluster, but only using up to 35% of the CPU of each IM and Presence server.
The balanced mode High Availability deployment option in a redundant mode supports up to
fifteen thousand users per cluster. For example, if you have six IM and Presence nodes in your
deployment, and fifteen thousand users, you assign 2.5 thousand users to each IM and Presence
node.
When you use the balanced mode High Availability deployment option in a redundant mode, as
compared to a non-redundant mode, only half the number of users are assigned to each node.
However, if one node fails, the other node will handle the full load of the additional 50% of users
in the subcluster, even at peak traffic.
In order to support this failover protection, you must turn on High Availability in each of the
subclusters in your deployment.
Active/Standby User Assignment
Redundant High Availability Deployment
Assign all your users to the active Cisco Unified IM and Presence node, and none to
the backup node.
When you turn on High Availability in the subcluster, the backup node can handle all
traffic from the active node if the active node fails.
www.flane.com.au
For this deployment model, assign all your users to the primary IM and Presence node, and none
to the backup node. When you turn on High Availability in the subcluster, the backup node can
handle all traffic from the primary node if the primary node fails.
Automatic Failover Detection
Cisco Unified IM and Presence uses these methods to automatically detect if a

node fails:
Peer Heartbeat
Monitor Critical Services :
These are the list of critical services that the node monitors:
Cisco DB
Cisco UP Presence Engine
Cisco UP XCP Router
Cisco UP Message Archiver
Cisco UP SIP Proxy
Cisco UP XCP SIP Federation Connection Manager
www.flane.com.au
IM and Presence uses these methods to automatically detect if a node fails:

Peer Heartbeat - In a subcluster, each node sends heartbeat intervals to the other node to
check if the node is up and running. If a node detects a loss of heartbeat in the peer node,
the node initiates a failover. You can configure the heartbeat interval and the heartbeat
timeout from the Service Parameters page on Cisco Unified CM IM and Presence
Monitor Critical Services - Each node monitors a list of critical services. If the node
detects that any critical service is not running for a configurable outage period (ninety
seconds is the default value), it instructs the peer node to initiate a failover. You can
configure this critical service delay from the Service Parameters page on Cisco Unified
CM IM and Presence Administration interface. These are the list of critical services that
the node monitors:
Cisco DB (internal IDS database)
Cisco Presence Engine (if you activate this service)
Cisco XCP Router
Cisco Message Archiver (if you integrate IM and Presence with a third-party off-
board database, and you activate this service)
Cisco SIP Proxy (if you configure SIP federation or you enable Partitioned
Intradomain Federation and you activate this service)
Cisco XCP SIP Federation Connection Manager (if you configure SIP federation,
or enable Partitioned Intradomain Federation, and you activate this service)
Cisco Presence Datastore
Cisco Route Datastore (if you configure SIP federation or you enable Partitioned
Intradomain Federation and you activate this service)
You can view the critical services that IM and Presence monitors for failover on the node details
screen on the Cluster Topology interface. The critical services that IM and Presence monitors are
marked in the “Monitored” column in the services list.
Note
IM and Presence only detects a failover if a critical service is not running for the duration
of the outage period. It does not detect a failover in the case where one or more critical
services are not running during the outage period, but not for the duration of the outage
period, for example, a rolling outage. In this case, IM and Presence generates alarms
indicating that services are starting and stopping, and you can perform a manual failover
on IM and Presence.
If you manually stop a critical service, and the service is stopped for longer than the
permitted outage period, failover will occur.
Prior to Release 8.6, if IM and Presence detects the situation where both nodes in the subcluster
think they own the same user, both nodes go into a failed state, and you need to perform a manual
recovery from the Cluster Topology interface. In IM and Presence Release 9.0(1) and later,
manual recovery is not required.
When the network issue is resolved, auto-recovery occurs without administrator intervention.
If manual recovery is required for another reason, you may experience IDS replication delays.
To check the status of the IDS replication on a node either:
Use this CLI command:
utils dbreplication runtimestate
Use the Cisco Unified IM and Presence Reporting Tool. The “IM and Presence Database
Status” report displays a detailed status of the cluster.
Server-side failback
Cisco Unified IM and Presence provides server-side failback, which uses the
same throttle mechanism as server failover.
This feature detects when a failed Cisco Unified IM and Presence server in a
High Availability deployment comes back in service.
It then sends terminating notify messages to Cisco Jabber clients that are failed
over to initiate failback to their home node.
www.flane.com.au
Manual Failover and Fallback From the
Cluster Topology interface
You can perform the following procedures:
Initiate a manual failover for a subcluster.
Initiate a manual fallback from the Cluster Topology interface, where the
Cisco UP Server Recovery Manager restarts critical services on the active
node and moves users back to the active node.
Perform a manual recovery for a subcluster (when both nodes in the

subcluster are in a failed state).
www.flane.com.au
You can perform a manual failover to the backup node in the subcluster using the Cluster
Topology interface.
When you initiate a manual failover, the Cisco Server Recovery Manager stops the critical
services on that node, and moves all users to the backup node.
The Cisco Server Recovery Manager stops the following critical services on the node:
Cisco SIP Proxy
Cisco Presence Engine
Cisco XCP Router (this causes all XCP processes to stop)
Cisco Client Profile Agent
The Cisco Server Recovery Manager then move all users to the backup node
Restriction You can only initiate a failover for a node that is in “Normal” state.
Cluster-Wide Routing Information on Cisco
Unified IM and Presence
To allow the nodes in a cluster to route messages to each other, you must
configure the routing communication type.
MDNS is the default mechanism for establishing the XCP route fabric on Cisco
Unified Presence; the network automatically establishes router-to-router
connections between all Cisco Unified IM and Presencenodes in a cluster.
A requirement for MDNS routing is that all nodes in the cluster are in the same
multicast domain.
When multicast DNS is disabled in the network, you can select router-to-router
communication for your deployment. In this case, Cisco Unified IM and Presence
dynamically configures all router-to-router connections between nodes in a
cluster.
www.flane.com.au
MDNS is the default mechanism for establishing the XCP route fabric on IM and Presence; the
network automatically establishes router-to-router connections between all IM and Presence
nodes in a cluster. A requirement for MDNS routing is that all nodes in the cluster are in the same
multicast domain. We recommend MDNS routing because it can seamlessly support new XCP
routers joining the XCP route fabric.
If you select MDNS as the routing communication, you must have multicast DNS enabled in your
network. In some networks multicast is enabled by default, or enabled in a certain area of the
network, for example, in an area that contains the nodes that form the cluster. In these networks,
you do not need to perform any additional configuration in your network to use MDNS routing.
When multicast DNS is disabled in the network, MDNS packets cannot reach the other nodes in a
cluster. If multicast DNS is disabled in your network, you must perform a configuration change to
your network equipment to use MDNS routing.
Alternatively, you can select router-to-router communication for your deployment. In this case,
IM and Presence dynamically configures all router-to-router connections between nodes in a
cluster. Select this routing configuration type if all the nodes in your cluster are not in the same
multicast domain. Note that when you select router-to-router communication:
Your deployment will incur the additional performance overhead while IM and Presence
establishes the XCP route fabric.
You do not need to restart the Cisco XCP Router on all nodes in your deployment when
you add a new node.
If you delete or remove a node, you must restart the Cisco XCP Router on all nodes in
your deployment.
Cluster-Wide Routing Information on Cisco
Unified IM and Presence(Cont.)
Multicast DNS (MDNS)- Select Multicast DNS communication if the
nodes in your cluster are in the same multicast domain. Multicast DNS
communication is enabled by default on Cisco Unified Presence.
Router to Router - Select Router-to-Router communication if the nodes in

your cluster are not in the same multicast domain.
www.flane.com.au
Multicast DNS (MDNS)- Select Multicast DNS communication if the nodes in your cluster
are in the same multicast domain. Multicast DNS communication is enabled by default on IM
and Presence.
Router to Router - Select Router-to-Router communication if the nodes in your cluster are
not in the same multicast domain.
How To Configure High Availability Cisco
Unified IM and Presence Deployments
Turning On or Off High Availability for a Subcluster
Configuring the Advanced Service Parameters for the Server Recovery

Manager
Performing a Manual Failover to Backup Node
Performing a Manual Fallback to Active Node
www.flane.com.au
High Availability IM and Presence deployments configuration

Turn on or off High Availability for subcluster.
Configure advanced service parameters for Server Recovery Manager.
Perform manual failover to backup node.
Perform manual fallback to primary node.
Perform manual recovery of subcluster.
Summary
Cisco IM and Presence Multi-node deployment overview
Cisco Jabber failover and failback
Cisco UP SRM and Replication watcher services
Cisco IM and Presence User assignment modes:
Balanced
Active/Standby
Automatic Failover detection
Lesson 8
Instant Messaging
Compliance ,
Logging and Chat Rooms
EIM, Persistent Chat and Message
Compliance
Enterprise instant messaging (EIM) features of the Jabber Extensible
Communications Platform (XCP)
Multi-device user experience (SIP to XMPP)
Text conferencing (or multiuser chat)
Ad hoc group chat
Persistent group chat
www.flane.com.au
Many industries require that instant messages adhere to the same regulatory compliance
guidelines as are all other business records. To comply with these regulations, your system must
log and archive all business records, and the archived records must be retrievable.
The Cisco Unified Communications Manager IM and Presence Service provides support for
instant messaging (IM) compliance by collecting data for the following IM activities in single
cluster, intercluster, or federated network configurations:
Point-to-point messages.
Group chat - This includes ad-hoc, or temporary chat messages, and permanent chat
messages.
Cisco IM and Presence incorporates the supported enterprise instant messaging features of the
Jabber Extensible Communications Platform (XCP), while allowing for some modifications to
enhance support for multi-device user experience. Cisco IM and Presence changes the Jabber
XCP instant messaging routing architecture to allow for initial instant messages to be routed to all
of the user's non-negative priority logged-in devices, rather than routing to the highest priority
device as is done with existing Jabber XCP installations. Backward compatibility support for
point-to-point instant messaging between Cisco IM and Presence SIP clients and XMPP clients is
provided by an IM gateway.
Text conferencing, sometimes referred to as multi-user chat, is defined as ad-hoc group chat and
persistent group chat and is supported as part of the Jabber XCP feature set. In addition, offline
instant messaging (storing instant messages for users who are currently offline) is also supported
as part of the Jabber XCP feature set. Cisco IM and Presence handles storage for each of these
instant messaging features in different locations. Offline instant messaging is stored locally in the
Cisco IM and Presence IDS database. Ad-hoc group chat is stored locally in memory on Cisco IM
and Presence. Persistent group chat requires an external database to store chat rooms and
conversations. The only external database supported is PostgreSQL (see
http://www.postgresql.org/).
Cisco IM and Presence uses the basic interfaces of the external database and does not provide any
administration, interface hooks, or configuration of the database. Cisco requires a separate
database instance for each server in the cluster when Cisco IM and Presence is deployed with
persistent group chat.
Message Compliance Overview
What is message compliance?

Message compliance describes archiving , auditing and logging of
instant messages (IMs)
External message compliance servers can perform security tasks for

IMs:
Spam over IM (SPIM)
Virus scans file transfer with chat clients
Enterprise may have a requirement by law for message compliance
In some countries a works council needs to be involved when using

message compliance technologies
www.flane.com.au
Instant messaging is very popular in consumer sector. However, it has yet to be used widely in
the commercial sector as e-mail is currently used. The major drawback has been the
vulnerabilities associated with IM technology. These vulnerabilities have created several security
issues. The security issues have made organizations think before exploiting IM technology. This
paper provides an overview of IM technology. It discusses vulnerabilities of IM and related
security issues. This paper also provides an insight in to the considerations an enterprise should
give during the implementation of IM technology and related products.
Message Compliance Options
Cisco Unified IM and Presence supports two message compliance

options
www.flane.com.au
PostgreSQL Database Integration for Message
Compliance
One PostgreSQL database instance is required per Cluster
www.flane.com.au
As part of the Jabber XCP architecture, Cisco IM and Presence contains a Message Archiver
component that allows for logging of text conferencing, federated, and intercluster messages into
an external database as part of a non-blocking native compliance. Cisco IM and Presence native
compliance and message archival requires a PostgreSQL database instance per cluster. The same
database can be shared with multiple clusters; however, a large number of users in a multi-cluster
deployment might require multiple database servers.
Packet Flow for Message Compliance with a
PostgreSQL Database
User A wants to send an IM to User B with Cisco Jabber:
Cisco Unified IM and Presence receives the IM (1) forwards the message to User B
(2)
A copy of the IM is forwarded (3) from Cisco Unified IM and Presence to the
PostgreSQL database
The message is stored in clear test in PostgreSQL database
If the PostgreSQL database is not available the users can still send IMs bit message
compliances does not work
www.flane.com.au
IM compliance provides logging of all compliance related data to an external database. All IM
traffic passes through the IM and Presence Server (via the Message Archiver component) and is
simultaneously logged to the external database. Each IM log contains the sender and recipient
information, the timestamp, and the message body.
For ad-hoc group chat messages, by default IM and Presence logs multiple copies of the same
message to the external database, one copy for each recipient. This identifies what users in the ad-
hoc group chat received the message.
Depending on the XMPP client you deploy, you may also notice this behavior:
IM and Presence may log an incoming message to the external database twice. This
occurs because some XMPP clients do not support the ability to learn the full JID, or
address, of the other party in the conversation. Consequently the XMPP client forks the
message to all active clients for the user (all clients that the user is currently signed into),
and IM and Presence then logs all forked messages to the external database.
IM and Presence may log the first message in a chat to the external database twice. This
occurs until the XMPP client learns the full JID, or address, of the other party in the
conversation.
If IM and Presence loses its connection to the external database, it continues to send and deliver
IMs to users, and users can still create (ad-hoc) chat rooms. However with no connection to the
external database, IM and Presence does not log any of these IMs so it does not support
permanent group chat. IM and Presence raises an alarm if the connection to the external database
is lost.
Third-Party Compliance Server Integration
One Third-Party compliance server is required per server
www.flane.com.au
A blocking third-party compliance solution, which not only allows logging of messages but also
applies policy to message delivery and message content, is provided through a third-party
compliance server solution. Cisco IM and Presence third-party compliance requires a compliance
server for each server in the cluster.
As an alternative to IM compliance, you can integrate IM and Presence with a third-party
compliance server.
With this solution, IM and Presence only delivers messages to users after it successfully logs the
message to a third-party compliance server. If the compliance server is unavailable, IM and
Presence does not deliver the message to the recipient.
Third-party IM compliance requires these components:
IM and Presence Service Release 9.0(1) - IM and Presence uses the Event Broker
component to send messages to the third-party compliance server.
Third-party compliance server - You require a third-party compliance server for each
node in the cluster.
IM Client - Supported clients include Cisco clients such as Cisco Jabber, third-party
XMPP clients, and other third-party clients used in federated networks.
The IM and Presence Service does not provide a secure TLS/SSL connection between IM and
Presence and the third-party compliance server.
To use the third-party compliance solution you must configure a third-party compliance server for
each node in the cluster. IM and Presence passes all messages that are sent to or from any users
associated with a node to the designated third-party compliance server for that node. The third-
party compliance server applies any relevant policy or filtering to the message, and then passes
the message back to IM and Presence. IM and Presence delivers the message to the recipient.
Note that you may potentially experience performance delays in your network because of the
volume of messages that pass between IM and Presence and the third-party compliance server. If
IM and Presence loses its connection to the third-party server, all IM traffic stops.
Packet Flow for Message Compliance with a
Third-Party Server
User A wants to send an IM to User B with Cisco Jabber:
Cisco Unified IM and Presence receives the IM (1) and forwards the message to the
third-party compliance server.
The third-party compliance server performs logging , auditing ,policing and other
configured features and sends back the IM (3).
Cisco Unified IM and Presence forwards (4) the IM to User B.
If the third-party compliance server database is not available no IM can be sent.
www.flane.com.au
Persistent Group Chat Feature Overview
A persistent group chat has these characteristics:
Use File > new Chartroom to create a new

room:
Created room is visible in the contact list
Can be rejoined
Old messages are still displayed
Messages stored in a PostgreSQL database.
Requires one database instance per cluster

node
www.flane.com.au
Checklist for installation of the PostgreSQL
Database
1. Install the database software
2. Create the database instance for:
Message compliance
Persistent chat
3. Edit the configuration file of the PostgreSQL server to allow connections
www.flane.com.au
Step 1: Install the PostgreSQL Server

Software
www.flane.com.au
Software (Cont.)
www.flane.com.au

Software (Cont.)
www.flane.com.au
Step 2a: Create the Database Instances for
Message Compliance
Open the SQL Shell from the Windows Start menu:
Use UTF8 encoding when non ASCII characters otherwise choose SQL ,
ASCII as the encoding type.
Message complaince requires one database instance per Cisco Unified IM

and Presence cluster
www.flane.com.au
Procedure
Step 1 Enter these commands to sign in to the database server as a Postgres user:
>su - postgres
>psql
Step 2 Create a new database user. The example below creates a new database user called
“tcuser”:
#CREATE ROLE tcuser LOGIN CREATEDB;
Step 3 Create the database.
If your database will contain ASCII characters only, create the database with SQL_ASCII
encoding. If your database will contain non-ASCII characters, create the database with UTF8
encoding.
The example below creates an SQL_ASCII database called “tcmadb”.
#CREATE DATABASE tcmadb WITH OWNER tcuser ENCODING
'SQL_ASCII';
Step 4 Configure user access to the database. Edit the <install_dir>/data/pg_hba.conf file to allow
the Postgres user and the new ‘tcuser’ user to access the database.
Step 5 Enter these commands to define passwords for the Postgres and 'tcuser' users:
#ALTER ROLE postgres WITH PASSWORD 'mypassword';
#ALTER ROLE tcuser WITH PASSWORD 'mypassword';
Note You are required to enter a password for the database user when you configure an external
database entry on IM and Presence.
Step 6 If you are running PostgreSQL version 8.3.7 or a later 8.3.x release, change the permission
of the ‘tcuser’ to superuser to allow this user access to the database. Enter this command:
#ALTER ROLE tcuser WITH SUPERUSER;
Step 7 Configure the connections to the database from remote hosts. Edit the listen_addresses
parameter in the <install_dir>/data/postgresql.conf file. For example:
listen_addresses = '*'
Step 8 If you are running PostgreSQL version 9.1.1, you must set the following values in the
postgresql.conf file:
escape_string_warning = off
standard_conforming_strings = off
Step 9 Stop and restart the PostgreSQL service, for example:
/etc/rc.d/init.d/postgresql-8.3 stop
/etc/rc.d/init.d/postgresql-8.3 start
Note The commands to stop and start the PostgreSQL servicemay vary between PostgreSQL
releases.
Step 10 Enter these commands to sign in to the new database as the Postgres user and enable
PL/pgSQL:
>psql tcmadb -U postgres
#CREATE FUNCTION plpgsql_call_handler () RETURNS
LANGUAGE_HANDLER AS '$libdir/plpgsql'
LANGUAGE C;
#CREATE TRUSTED PROCEDURAL LANGUAGE plpgsql HANDLER
plpgsql_call_handler;
Step 2b: Create the Database Instances for
Persistent Group Chat
Create a database instance for every Cisco Unified IM and Presence node in the
cluster:
One database instance is for one node in the Cisoc Unified IM and Presence
cluster
www.flane.com.au
Step 2b: Create the Database Instances for

Persistent Group Chat
Open the pg_hba.conf file in the root of the data directory during
the installation
www.flane.com.au
By default, the Postgresql database listens on port 5432. If you want to change this port, you must
edit the PGPORT environment variable in /etc/rc.d/init.d/postgresql with the new port number.
Checklist for Database Integration in Cisco
1. Add the external databases in Cisco Unified IM and Presence
2. Enable message compliance and persistent chat
3. Start the necessary services in the Cisco Unified Serviceability
4. Verify database connectivity Gather message compliance data
www.flane.com.au
Step 1: Add the external databases in Cisco

www.flane.com.au
Step 2a: Enable Persistent Group Chat
www.flane.com.au
When you configure an external database entry on IM and Presence, you assign the external
database to a node, or nodes, in your cluster as follows:
For the Compliance feature, you require at least one external database per cluster.
Depending on your deployment requirements, you can also configure a separate external
database per node.
For the Permanent Group Chat feature, you require a unique external database per node.
Configure and assign a unique external database for each node in your cluster.
If you deploy both the Permanent Group Chat and Compliance features on an IM and
Presence node, you can assign the same external database to both features.
Step 2a: Enable Message Comliance
www.flane.com.au
Procedure
Step 1 Select Cisco Unified CM IM and Presence Administration > Messaging >
Compliance.
Step 2 Select Message Archiver from the Compliance Server Selection.
Step 3 (Optional) Select Enable Outbound Message Logging.
Turning on this option can degrade IM performance. Because all inbound messages are
already logged, do not enable this setting unless you are using IM compliance in
intercluster or federated networks.
Step 4 For each node, assign a database from the External Database option.
If you are using one external database for your cluster, assign all nodes to the same
external database. If you are using more than one external database for your cluster,
assign the nodes to the external databases based on your capacity requirements.
Step 5 Click Save.
Step 6 Start the Cisco Message Archiver service (if this service is not already started).
Step 7 Restart the Cisco XCP Router.
Step 3: Start the necessary services
www.flane.com.au
The Cisco XCP Message Archiver service must be running for the compliance feature to operate
correctly on IM and Presence.
Procedure
Step 1 Select Cisco Unified IM and Presence Serviceability > Tools > Service Activation.
Step 2 Select the server from the Server list box.
Step 3 Click Go.
Step 4 Select the radio button next to the Cisco XCP Message Archiver service in the IM and
Presence Services section.
Step 5 Select Save.
Step 4: Verify Database Connection
Go to Messaging > External Server Setup > External Databases and Select a
database instance:
Both tests of the External Database Troubleshooter for all database instances
should now be successful.
Ensure that all created external database instances are mapped to message
compliance or persistent group chat.
www.flane.com.au
Step 5: Obtain Message Compliance Data
www.flane.com.au
(Cont.)
www.flane.com.au

(Cont.)
All chat messages are archived in this table:
www.flane.com.au
PostgreSQL Database Tables
TC_ROOMS Table
Information for group chat rooms.
TC_USERS Table
Roles and affiliations, alternate names, and other data associated with
group chat room users.
TC_MESSAGES Table
Messages that are sent in group chat rooms.
TC_TIMELOG Table
The time that users enter and exit specific group chat rooms.
TC_MSGARCHIVE Table
Stores messages and associated information for group chat rooms.
JM Table
Stores conversations and associated information for the Message Archiver
component.
www.flane.com.au
By default, IM and Presence generates 27 tables in the PostgreSQL database but at present it only
uses the tables described in this lesson.
Summary
What is Message Compliance ?
PostgreSQL database integration
Third-Party Compliance server integration
Installing PostgreSQL for Message Compliance and Persistent Chat Rooms
Module 3
Cisco Jabber for Mobile
Module Outlines
Designing Cisco Jabber for Mobile Solution
Provisioning Cisco Jabber for Mobile
Lesson 1
Designing Cisco Jabber for

Mobile Solution
BYOD Smart Solution
Providing a work-your-way solution for diverse users with multiple devices,

anytime, anywhere
The Mobile Experience - Your Way
BYOD Smart Solution Delivers End-to-End Value
Unified Policy to Secure Data on Any Device
Uncompromised Experience
Simplified Operations and Management
www.flane.com.au
The Cisco BYOD Smart Solution provides a comprehensive approach to effectively design,
manage, and control the access of a bring-your-own-device (BYOD) network. Cisco BYOD
enhances user experiences and productivity.
This complete solution starts with Cisco design guides and professional services that lead you
from planning and design to day-to-day operations. This BYOD solution also provides the
necessary infrastructure, including:
• Access points
• Controllers
• Security
• Network management
This infrastructure supports a highly secure, high-performing network that is accessible to a wide
range of devices.
Cisco Jabber Product Portfolio
All-in-one UC Application Collaborate from Any Workspace

Presence & IM PC, Mac, tablet, smart phone
Voice, Video, voice messaging On-premises and Cloud
Desktop sharing, conferencing Integration with Microsoft Office
www.flane.com.au
Collaborate Across Multiple Devices with Cisco Jabber Be more productive wherever you are, on
whatever device you choose, with Cisco Jabber. Find the right people, see how they're available,
and collaborate the way you want to work. Use Cisco Jabber to access presence information,
instant messaging, voice, video, desktop sharing, and conferencing. Even integrate with Cisco
TelePresence from mobile devices.
Cisco Jabber can give your employees the collaboration tools they need to see, hear, or work
together - on any device, at any time.
Key Features & Capabilities on Mobile
Devices
Mobile Voice & Video Access Corporate Directory Access
Place voice/video calls through Cisco Quickly find information about
call control platforms: Cisco Unified CM, coworkers or other employees
Cisco VCS, Cisco Jabber Video Service Cisco Mobile Connect (SNR)
Rich Presence & IM Simultaneous ring on all phones &
devices
Know the presence state of contacts to
Desk & Mobile Hand-off
instantly initiate a conversation in most
effective way Seamless transition of ongoing
calls to mobile phone from desk
Escalation to Web Meetings phone/client and vice versa
Quickly find information about
coworkers or other employees
Business Visual Voicemail
Single voice mailbox across multiple
phone numbers
www.flane.com.au
Interoperability:
Cisco Jabber uses the industry-standard Extensible Messaging and Presence Protocol (XMPP) for
presence and IM. With Jabber's interoperability, employees from one company can interact with
employees at other companies using applications from Google, IBM. Microsoft and AOL.
Further increasing user acceptance and adoption, Cisco Jabber provides integration with
Microsoft Office productivity applications so users can see a colleague's availability status, and
quickly escalate communications to an instant message, phone call or conference from within the
application.
Mobility Capabilities
Mobile users will enjoy a variety of communication capabilities including presence, IM, voice
over WiFi, and visual voicemail.
Using Jabber technology, a business user can use a single work line for their desk phone, wireless
device and desktop computer -- and can make and receive enterprise calls on the device over a
Wi-Fi connection. This adds to the existing capability available over a cellular network.
Video Capabilities
Standards-based H.264, high-definition (HD) resolution enables users to interoperate in HD with
Cisco TelePresence and other industry video solutions.
Users also benefit from multiparty, continuous presence video so one can simultaneously see
multiple video users during group or team communications sessions.
These integrated video capabilities are scheduled to be available in the second half of 2011.
Voice Dialing
Allows users to dial a number by speaking a name in the corporate directory. If Voice Dialing is
available on your network, Cisco Jabber users can always dial the Voice Dialing pilot number to
access that feature as they would from any phone.
You can simplify voice dialing by doing either of the following: You can automatically add the
Voice Dialing pilot number to the Favorites list in Cisco Jabber. You can enable gesture-
activated voice dialing.
Features of Cisco Jabber for iPhone allow you to:
Place and receive VoIP calls from a corporate phone number through Unified CM using
your mobile device while Cisco Jabber is running and connected to the network.
Receive calls at the standard mobile phone number when Cisco Jabber is not running or
not connected to the corporate network
Have multiple VoIP calls (call waiting, add new call, swap between active calls)
Use many of the standard in-call features that Unified CM provides, including hold,
transfer, and conference
Connect automatically to the VPN if the corporate Wi-Fi network is not directly available
Transfer an active Cisco Jabber VoIP call from your device to your desk phone and vice
versa
Transfer an active Cisco Jabber VoIP call to your mobile network
Dial numbers by raising the iPhone to the ear and speaking the name of the person to call
Search the corporate directory
Access voicemail through a visual list
Run the application in the background, and automatically register to Unified CM when
available, and remain ready to receive calls to the work phone number
Transfer services from the Unified CM to another Unified CM or a router with Cisco
Unified Survivable Remote Site Telephony (SRST).
Open an IM session with Cisco Jabber contacts
Use a Bluetooth headset on supported iPhone devices
With Cisco Jabber for Android, you can do the following:
Place and receive VoIP calls from your corporate phone number through Cisco Unified
Communications Manager using your mobile device, while Cisco Jabber is running and
connected to the corporate network.
Securely connect to your corporate network from any remote location, using Wi-Fi or
mobile data networks.
Use the native Android phone application to place work calls from the Keypad, Logs,
Favorites, or Contacts tab.
Have up to two VoIP calls (call waiting, add new call, swap between active calls).
Use many of the standard in-call features that Cisco Unified Communications Manager
provides, including hold, transfer, and conference.
Transfer an active Cisco Jabber VoIP call to your mobile network.
Transfer an active Cisco Jabber VoIP call from your device to your desk phone.
Search the corporate directory.
See a message indicator for new voice messages that are left at the office phone number.
Access voicemail from the home screen; or from the status bar if a new message exists.
Receive calls to your work phone number while Cisco Jabber for Android runs in the
background. Cisco Jabber for Android automatically registers to Cisco Unified
Communications Manager when available.
Network Connectivity:
WLAN and VPN
WLAN Infrastructure
Deploy a finely tuned, QoS-enabled, and highly available WLAN

network.
VPN Infrastructure
Deploy a high-bandwidth and secure VPN infrastructure that adheres

to the enterprise's security requirements and policies
VPN connection types:

Cisco IOS VPN or Cisco Adaptive Security Appliance (ASA) to Cisco
AnyConnect also leveraging the Cisco ASA
www.flane.com.au
Cisco mobility clients are typically deployed on dual-mode phones, which contain two physical
interfaces or radios that enable the device to connect to both mobile voice and data carrier
networks by means of traditional cellular or mobile network technologies and to connect to
wireless local area networks (WLANs) using IEEE 802.11 standards. Cisco mobility clients and
devices enable on-premises data and voice connectivity through wireless local area networks
(WLANs) using IEEE 802.11 standards. In addition, these clients and devices provide remote
data and voice connectivity to the enterprise through public or private WLANs or over the mobile
data network. For devices with provider cellular voice radios, voice connectivity may also be
enabled through the mobile voice network and PSTN.
Because Cisco Jabber mobile clients and Cisco Cius are often attached to a WLAN, all of the
WLAN deployment considerations that were mentioned previously for wireless endpoints apply
to mobile clients and devices, including WLAN RF design and verification by site survey,
interference identification and mitigation, security methods for authenticating endpoints and
encrypting traffic, channel cell call capacity, and avoiding Bluetooth when deploying in the 2.4
GHz band.
Mobile client devices can utilize the IP telephony infrastructure for enterprise VoIP calling even
when not connected to the enterprise, provided they have a secure connection back to the
enterprise in order to register the client with Unified CM. Remote secure connectivity for these
devices requires the use of a VPN solution such as Cisco AnyConnect mobile client or the Cisco
Jabber secure connect feature in order to secure the client connection over the Internet.
Voice quality and user experience for remotely attached dual-mode client devices will vary
depending on the nature of the Internet-based network connection. Cisco cannot guarantee
acceptable voice quality nor successful connectivity for these types of client connections. Care
should be taken when relying on these types of connections for business-critical communications.
In the case of unreliable or low-bandwidth Internet connections, users should be advised to make
calls over the mobile voice network if connectivity is available rather than relying on the
enterprise telephony infrastructure.
Solution Backend Cisco
UC Components
www.flane.com.au
Supported UC Backend Components
Cisco Cisco Cisco Cisco

Jabber for Jabber for Jabber for Jabber IM
iPad iPhone Android for iPhone
Cisco Unified CM √ √ √ ×
Voice/Video Cisco VCS √ × × ×
Cisco Jabber Video
Service* √ × × ×
Cisco Unified
Presence √ × × √
Presence/IM
Cisco WebEx
Connect Service** √ × × √
* On-demand service
** On-demand service; supports peer to peer (P2P) voice/video

www.flane.com.au
Cisco Jabber™ for iPad is a unified communications client application that provides presence,
instant messaging (IM), voice, voice messaging, and video calling capabilities on the Apple iPad .
Conferencing and screen-sharing capabilities are delivered with an escalation to the Cisco
WebEx® for iPad application. This integrated collaboration experience is designed to take
advantage of the form factor of the iPad; it works with both a premises- and a cloud-based
collaboration architecture. This application supports the following important functions:
Integrated voice, high-quality video, IM, presence, and visual voicemail functions
Flexibility of configuration for different communications infrastructure and
combinations of:
– Voice and video: Cisco Unified Communications Manager
– Video: Cisco TelePresence® Video Communication Server (VCS) or Cisco
Jabber Video for TelePresence
– Peer-to-peer voice and video: Cisco WebEx Connect® service
– Presence and IM: Cisco WebEx Connect service or Cisco Unified Presence.
Cisco Jabber® for iPhone lets you place, receive, and manage calls over your corporate Wi-Fi
network. Cisco Jabber for iPhone also supports calls over any Wi-Fi hotspot using a VPN,
allowing you to take further advantage of your corporate telephony infrastructure whenever you
have access to a high-quality wireless network connection. You will benefit from the cost savings
from not using your wireless minutes, the capability to use your work phone number when
placing calls from your Apple iPhone, and the stronger in-building network coverage from a
wireless network.
Platform Support and Compatibility for Cisco Jabber 8.6 for iPhone:
Telephony integration
Cisco Unified Communications Manager 7.1.5, 8.0.3, 8.5, and 8.6 (refer
to release notes for exact versions)
Cisco Unified Communications Manager Express 8.6 and 8.8
Visual voicemail
Cisco Unity Connection 7.0, 7.1, 8.0, 8.5, and 8.6
Cisco Unity Express 8.6
Voice dialing
Cisco Unity Connection 7.0, 7.1, 8.0, 8.5, and 8.6
Cisco Unified SRST
Cisco Unified SRST 8.6
With Cisco Jabber for Android you can turn your Android device into a full-featured Cisco
Unified IP Phone. You can place, receive, and manage calls whether using your corporate Wi-Fi
network, other Wi-Fi networks, or a mobile data network. Cisco Jabber for Android features a
secure connection capability to your corporate network so that you remain transparently and
automatically connected no matter where you choose to work. You will also benefit from the cost
savings from not using your wireless voice minutes, the ability to use your work phone number
when placing calls from your Android smartphone or tablet, and the stronger network coverage
from a Wi-Fi network.
Platform Support and Compatibility for Cisco Jabber for Android:
Telephony integration
Cisco Unified Communications Manager 7.1.5, 8.0.3, 8.5, and 8.6 (refer to
release notes for exact versions)
Voicemail (optional)
Cisco Unity® Connection 7.1, 8.0, 8.5, and 8.6
Lightweight Directory Access Protocol (LDAP) integration (optional)
Microsoft Active Directory
OpenLDAP
2003 and 2008
Secure connect feature (optional)
Cisco ASA 5500 Series Adaptive Security Appliances
Cisco ASA 8.0 and above
Cisco ASA 8.4 and above for certificate distribution using Simple Certificate
Enrollment Protocol (SCEP)
Cisco Jabber® IM for iPhone delivers instant messaging (IM) and presence to your Apple iPhone.
Access your desktop IM contact list (Figure 1) and take action with features such as click
to IM, click to call, click to email, and click to text from a person's profile.
Start or join an instant Cisco WebEx® meeting from an IM conversation.
Search for colleagues in your corporate directory .
Maintain security using Secure Sockets Layer (SSL) encryption and by connecting your
IPhone directly to the Cisco IM infrastructure - Cisco Unified Presence or Cisco WebEx
Connect.
Supported features
Jabber for Jabber for Jabber for
iPad iPhone Android
VoIP over
3G/4G × × ×
Wi-Fi √ √ √
Video Calling (including TelePresence interoperability)
√ × ×
Hand-off
VoIP to Mobile network N/A √ √
Mobile network to VoIP N/A × ×
Mid-call Control (Hold, Resume, Transfer, Add Calls) √ √ √
Voicemail
Visual Voicemail (Requires Unity Connection)
√ √ ×
Call Voicemail √ √ √
www.flane.com.au
Transfer active VoIP call to the mobile network

Users can transfer an active VoIP call from Cisco Jabber to their mobile phone number on the
mobile network. This is useful when a user on a call leaves the Wi-Fi network (for example,
leaving the building to walk out to the car), or if there are voice quality issues over the Wi-Fi
network.
This Cisco Jabber feature is called Use Mobile Network.
There are several ways to implement this feature. You can also disable it.
Handoff DN
The iPhone calls Unified CM using the mobile network. This method requires a Direct
Inward Dial (DID) number.
The service provider must deliver the DID digits exactly as configured. Alternately, for
Cisco IOS gateways with H.323 or SIP communication to Unified CM, you can use Cisco
IOS to manipulate the inbound called-party number at the gateway, presenting the digits
to Unified CM exactly as configured on the handoff number.
If you select this implementation method and it fails, the system automatically tries the
Mobility Softkey and Call Park methods, in order.
This method will not work for iPod Touch or iPad devices.
Mobility Softkey
Unified CM calls the phone number of the iPhone PSTN mobile service provider.
If you select this implementation method and it fails, the system automatically tries the
Call Park method.
Call Park
Cisco Jabber attempts this method only if attempts to use other methods fail . In the Call
Park method, the iPhone makes a mobile-network call to a Call Park number to retrieve
the call. This method requires a DID number.
This method does not work for iPod Touch or iPad devices.
None of the above
Disable this feature if you do not want to make it available to users.
Enterprise Voicemail Services
Many mobile clients and devices are also capable of accessing enterprise voicemail services.
Most clients are capable of receiving enterprise message waiting indication whenever an unread
voicemail is in the user's enterprise voicemail box and the mobile device is attached to the
enterprise network.
Further, mobile clients can be used to retrieve enterprise voicemail messages. Typically enterprise
voicemail messages are retrieved when the user dials the voicemail system number and navigates
to their voicemail box after providing required credentials. However, some mobile clients provide
the ability to retrieve voicemail messages from the voicemail box by downloading and displaying
a list of all messages in the voicemail box and then by selecting individual messages to be
downloaded to the mobile device for listening. This is sometimes referred to as visual voicemail.
Both the mobile client and the enterprise voicemail system must be capable of providing and
receiving message waiting indication (MWI), voicemail message information, and downloads of
the messages over the network. Cisco Unity Connection supports visual voicemail through IMAP,
and it can provide MWI and voicemail lists and downloads, but only if the mobile client also
supports this functionality.
Cisco Jabber Handoff
There are two methods of handoff, depending on the Transfer to

Mobile Network setting:
Mobility Softkey Method
Supported with all Cisco Jabber dual-mode clients.
Handoff Number Method

Supported only with Cisco Jabber for iPhone clients.
www.flane.com.au

To properly deploy Cisco dual-mode clients such as Cisco Jabber, it is important to understand
the nature of handoff operations within the client. The handoff method used by the Cisco Jabber
dual-mode client depends on the Transfer to Mobile Network setting on the Cisco Dual-Mode
for iPhone or Cisco Dual-Mode for Android device configuration page.
There are two methods of handoff, depending on the Transfer to Mobile Network setting:
Mobility Softkey Method of Hand-Out
With this method the Transfer to Mobile Network setting should be set to Use Mobility
Softkey (user receives call). In this type of handoff, the Unified CM system generates a
call over the PSTN to the user's mobile number. This hand-out method is supported with
all Cisco Jabber dual-mode clients.
Handoff Number Method of Hand-Out.
With this method the Transfer to Mobile Network setting should be set to Use
HandoffDN Feature (user places call). In this type of handoff, the mobile client
generates a call over the mobile voice network to the handoff number configured within
the Unified CM system. This hand-out method is supported only with Cisco Jabber for
iPhone clients.
Mobility Softkey Method of Hand-Out
1. Existing call between the mobile client
device associated to the enterprise
WLAN and registered to Unified CM,
and a phone on the PSTN network
2. User selects Mobile Network button
from the in-call menu.
3. Unified CM generates a call to the
configured mobility identity number.
4. The user can now move out of the
enterprise and away from WLAN
network coverage.
5. Once the inbound call on the cellular
interface is answered, the RTP stream
that was traversing the WLAN is
redirected to the PSTN gateway.
www.flane.com.au
The operation depicted in the figure is of an active call on an iPhone or Android dual-mode
device within the enterprise being moved manually from the WLAN interface to the mobile voice
network or cellular interface of the device through the enterprise PSTN gateway. As shown, there
is an existing call between the mobile client device associated to the enterprise WLAN and
registered to Unified CM, and a phone on the PSTN network (step 1). Because this is a manual
process, the user must select the Use Mobile Network button from the in-call menu within the
Cisco Jabber client, which signals to Unified CM the intention to hand-out the call (step 2). Next
Unified CM generates a call to the configured mobility identity number corresponding to this
mobile device through the enterprise PSTN gateway (step 3). This call to the mobility identity is
made to the mobile voice network or cellular interface of the iPhone or Android device. The user
can now move out of the enterprise and away from WLAN network coverage (step 4). In the
meantime, the inbound call from Unified CM is received at the mobile voice network interface,
and the user must answer the call manually to complete the hand-out.
Once the inbound call on the cellular interface is answered, the RTP stream that was traversing
the WLAN is redirected to the PSTN gateway, and the call continues uninterrupted between the
mobile client device and the original PSTN phone, with the call anchored in the enterprise
gateway (step 5).
Handoff Number Method
1. Existing call between the mobile client
device associated to the enterprise
WLAN and registered to Unified CM, and
a phone on the PSTN network
2. user selects the Use Mobile Network
button from the in-call menu.
3. Cisco Jabber client automatically
generates a call through the cellular
interface over the mobile voice network to
the configured Handoff Number within the
Unified CM system
4. User can now move out of the enterprise
and away from WLAN network coverage.
5. The meantime, the inbound call from the
Cisco Jabber client is received by Unified
CM.
www.flane.com.au
Handoff Number Method of Hand-Out

an active call on an iPhone dual-mode phone within the enterprise is moved manually from the
WLAN interface to the mobile voice network or cellular interface of the device through the
enterprise PSTN gateway. However, in this case the Handoff Number method of hand-out is
used.
Note The Handoff Number method of hand-out is supported only with Cisco Jabber for iPhone
As shown in the figure, there is an existing call between the iPhone dual-mode device associated
to the enterprise WLAN and registered to Unified CM, and a phone on the PSTN network (step
1). Because this is a manual process, the user must select the Use Mobile Network button from
the in-call menu within the Cisco Jabber dual-mode client, which signals to Unified CM the
intention to hand-out the call (step 2). Next the Cisco Jabber client automatically generates a call
through the cellular interface over the mobile voice network to the configured Handoff Number
within the Unified CM system (step 3). The user can now move out of the enterprise and away
from WLAN network coverage (step 4). In the meantime, the inbound call from the Cisco Jabber
client is received by Unified CM. Assuming the inbound calling number matches the user's
configured mobility identity, the RTP stream that was traversing the WLAN is redirected to the
PSTN gateway, and the call continues uninterrupted between the Cisco Jabber mobile client and
the original PSTN phone, with the call anchored in the enterprise gateway (step 5).
Interactions Between Cisco Jabber and
Cisco Unified Mobility
Cisco Jabber mobile clients can be integrated with Cisco Unified
Mobility to leverage Cisco Mobile Connect, mid-call DTMF
features, two-stage dialing, and single enterprise voicemail box
mobile voicemail avoidance.
Requires the iPhone or Android dual-mode mobile phone number

to be configured within Unified CM as a mobility identity
associated with the Cisco Dual-Mode for iPhone or Cisco Dual-
Mode for Android device.
www.flane.com.au
Interactions Between Cisco Jabber and Cisco Unified Mobility

The Cisco Jabber mobile clients can be integrated with Cisco Unified Mobility to leverage Cisco
Mobile Connect, mid-call DTMF features, two-stage dialing, and single enterprise voicemail box
mobile voicemail avoidance.
Integration with Unified Mobility requires the iPhone or Android dual-mode mobile phone
number to be configured within Unified CM as a mobility identity associated with the Cisco
Dual-Mode for iPhone or Cisco Dual-Mode for Android device. Once the mobile number is
configured as a mobility identity within the system, Mobile Connect can be leveraged so that
incoming calls to the user's enterprise number will be extended to the iPhone or Android dual-
mode device through the mobile voice network as long as the iPhone or Android dual-mode
device is not connected to the enterprise and not registered to Unified CM. In situations where the
dual-mode device is connected to the enterprise and registered to Unified CM, an inbound call to
the enterprise number will not be extended to the mobile voice network interface of the device.
When the iPhone or Android dual-mode device is connected to the enterprise, only the WLAN or
mobile data interface of the device will receive the inbound call. This prevents unnecessary
consumption of enterprise PSTN gateway resources.
Interactions Between Cisco Jabber and
Cisco Unified Mobility (Cont.)
Leveraged so that incoming calls to the user's enterprise number
will be extended to the iPhone or Android dual-mode device
through the mobile voice network as long as the iPhone or Android
dual-mode device is not connected to the enterprise and not
registered to Unified CM.
In situations where the dual-mode device is connected to the

enterprise and registered to Unified CM, an inbound call to the
enterprise number will not be extended to the mobile voice
network interface of the device.
www.flane.com.au
When not connected to the enterprise and not registered to Unified CM, the iPhone or Android
dual-mode device can invoke mid-call features by means of DTMF and perform desk phone
pickup for any enterprise anchored call. The dual-mode device can also leverage Mobile Voice
Access and Enterprise Feature Access two-stage dialing features when making outbound calls to
route these calls through the enterprise and anchor them in the enterprise PSTN gateway.
In addition to configuring a mobility identity for the iPhone or Android dual-mode device, you
can configure additional mobile phone numbers or off-system phone numbers as remote
destinations and associate them to the Cisco Dual-Mode for iPhone or Cisco Dual-Mode for
Android device within Unified CM. When associating the mobility identity and additional remote
destinations to the dual-mode device, you do not have to configure a remote destination profile.
Cisco Jabber for iPhone Desk Phone
Integration
Enables the user to move an active or held call from the user's desk phone to the
iPhone device.
Relies on CTI monitoring of the primary line of the user's desk phone as well as
the call park feature.
Whenever an active or held call is sensed by the Cisco Jabber client, it prompts
the user as to whether they want to transfer the call to the dual-mode device.
If the user indicates they wish to transfer the call, the desk phone automatically
parks the call and the mobile client automatically retrieves the call from the park
number.
www.flane.com.au
Cisco Jabber for iPhone Desk Phone Integration

The Cisco Jabber for iPhone mobile client enables the user to move an active or held call from the
user's desk phone to the iPhone device. This feature relies on CTI monitoring of the primary line
of the user's desk phone as well as the call park feature. The functionality provided by desk phone
integration relies on active CTI monitoring of the primary line of the user's desk phone.
Whenever an active or held call is sensed by the Cisco Jabber client, it prompts the user as to
whether they want to transfer the call to the dual-mode device. If the user indicates they wish to
transfer the call, the desk phone automatically parks the call and the mobile client automatically
retrieves the call from the park number.
To enable desk phone integration, ensure that the user's end-user account is assigned to a CTI-
enabled user group and that the user's desk phone is enabled to allow CTI control. In addition, the
CTI Control Username field on the Cisco Dual-Mode for iPhone device must be configured with
the user's end-user account userID.
Cisco Jabber for Android Desk Phone
Integration
enables the user to move an active call from the Android
device to the IP desk phone sharing a line with the mobile client device.
invoked by placing the active call on hold through the Cisco Jabber client.
When the call is placed on hold, the call
can be resumed at either the shared-line IP desk phone or on the Cisco Jabber
client
www.flane.com.au
Cisco Jabber for Android Desk Phone Integration

The Cisco Jabber for Android dual-mode client enables the user to move an active call from the
Android device to the IP desk phone sharing a line with the mobile client device. This feature is
invoked by placing the active call on hold through the Cisco Jabber client. When the call is placed
on hold, the call can be resumed at either the shared-line IP desk phone or on the Cisco Jabber
client.
WLAN Design Considerations for Cisco
Jabber Mobile Clients
Whenever possible, ensure that Cisco Jabber mobile clients roam on the WLAN
only at Layer 2 so that the same IP address can be used on the WLAN interface
of the device. In Layer 3 roaming scenarios where subnet boundaries are crossed
due to device IP address changes, calls will be dropped.
Deploy Cisco Jabber mobile clients on WLAN networks where the same SSID is
used across all APs. Roaming between APs is much slower if SSIDs are
different.
Ensure all APs in the WLAN broadcast their SSID(s).
Whenever possible, deploy Cisco Jabber mobile clients on the 5 GHz WLAN
band (802.11a/n).
www.flane.com.au
Design Considerations for Cisco Mobile Clients and Devices

Observe the following design recommendations when deploying Cisco mobile clients and
devices:
Dual-mode mobile devices must be capable of dual transfer mode (DTM) in order to be
connected simultaneously to both the mobile voice and data network and the WLAN
network so that the device is reachable and able to make and receive calls on both the
cellular radio and WLAN interface of the device. In some cases, proper dual-mode client
operation might not be possible if mobile voice and data networks do not support dual-
connected devices.
WLAN APs should be deployed with a minimum cell overlap of 20%. This overlap
ensures that a mobile device can successfully roam from one AP to the next as the device
moves around within a location, while still maintaining voice and data network
connectivity.
WLAN APs should be deployed with cell power level boundaries (or channel cell radius)
of -67 dBm in order to minimize packet loss. Furthermore, the same-channel cell
boundary separation should be approximately 19 dBm. A same-channel cell separation of
19 dBm is critical for ensuring that APs or clients do not cause co-channel interference to
other devices associated to the same channel, which would likely result in poor voice and
video quality.
Whenever possible rely on the 5 GHz WLAN band (802.11a/n) for connecting mobile
clients and devices capable of generating voice and video traffic. 5 GHz WLANs provide
better throughput and less interference for voice and video calls.
The enterprise wired and wireless LAN should be deployed and configured to support the
necessary end-to-end QoS classes of service, including priority queuing for voice media
and dedicated video and signaling bandwidth, to ensure the quality of client application
voice and video calls and the appropriate behavior of all features. While most clients
mark traffic appropriately at Layer 3 based on Cisco QoS recommendations, appropriate
Layer 2 WLAN UP marking is dependent on the client device and vendor
implementation. For this reason, Layer 2 marking is not consistent across platforms and
as such cannot be relied upon.
Because mobile devices are similar to desktop computers and can generate a large variety
of data and real-time traffic, these devices are typically considered untrusted. For this
reason, the network should be configured to re-mark all traffic from these client devices
based on port number and/or protocol. Likewise, rate limiting and policing on ingress to
the network is recommended.
Cisco recommends using only an enterprise-class voice and video optimized WLAN
network for connecting mobile devices and clients. While most mobile client devices are
capable of attaching to public or private WLAN access points or hot spots for connecting
back to the enterprise through the Internet for call control and other Unified
Communications services, Cisco cannot guarantee voice and video quality for these types
of connections.
When deploying Cisco collaboration mobile clients and devices on a Cisco Bring Your
Own Device (BYOD) infrastructure, administrators should consider a network
attachment method that does not require user intervention and which maximizes
utilization of the IP telephony infrastructure.
Further, for remote connectivity scenarios, all relevant ports must be opened in the
corporate firewall in order for Cisco mobile clients and devices to be able to access
collaboration services.
If corporate policy dictates that the BYOD infrastructure must remotely wipe or factory-
reset lost or stolen mobile devices, employees using personal mobile devices should be
aware of the policy and should regularly back up personal data.
The Unified Mobility Mobile Connect feature will not extend incoming calls to the dual-
mode device's configured mobility identity if the dual-mode device is inside the
enterprise and registered to Unified CM. This is by design in order to reduce utilization of
enterprise PSTN resources.
Because the dual-mode device registers to Unified CM, the system knows whether the
device is reachable inside the enterprise; and if it is, there is no reason to extend the call
to the PSTN in order to ring the dual-mode device's cellular voice radio. Only when the
dual-mode device is unregistered will Mobile Connect extend incoming calls to the user's
enterprise number out to the mobility identity number on the PSTN.
When you deploy mobile devices, Cisco recommends normalizing required dialing
strings so that users are able to maintain their dialing habits, whether the mobile device is
connected to the enterprise or not. Because dialing on the mobile network is typically
done using full E.164 (with or without a preceding '+') and mobile phone contacts are
typically stored with full E.164 numbers, Cisco recommends configuring the enterprise
dial plan to accommodate full E.164 or full E.164 with preceding '+' for mobile client
devices. By configuring the enterprise dial plan in this manner, you can provide the best
possible end-user dialing experience so that users do not have to be aware of whether the
device is registered to Unified CM.
Cisco recommends that dual-mode phone users rely exclusively on the mobile voice
network for making emergency calls and determining device and user location. This is
because mobile provider networks typically provide much more reliable location
indication than WLAN networks. To ensure that dual-mode phones rely exclusively on
the mobile voice network for emergency and location services, configure the Emergency
Numbers field of the dual-mode devices within Unified CM with emergency numbers
such 911, 999, and 112 in order to force these calls over the mobile voice network. Dual-
mode phone users should be advised to make all emergency calls over the mobile voice
network rather than the enterprise network. Although making emergency calls over
corporate WLANs or mobile data networks is not recommended, mobile devices that do
not have cellular voice radios are capable of making calls only through these data
interfaces. Mobile devices that do not have cellular voice radios should not be relied upon
for making emergency calls.
When deploying Cisco Jabber for iPhone with desk phone integration, the end-user
account for the Cisco Jabber user must be enabled for CTI. In addition, call park should
be configured at a system level so that the desk phone can auto-park the call and the
Cisco Jabber client can retrieve it whenever a call is moved from the desk phone to the
Cisco Jabber client. CTI overhead of this feature should be considered when sizing the
overall Unified CM system.
When deploying Cisco Jabber for iPhone or Android mobile clients, configure the
WLAN network to accommodate the following deployment guidelines:
• Minimize roaming of Cisco Jabber for iPhone and Android mobile devices at
Layer 3 on the WLAN. Layer 3 roaming, where a device IP address changes,
will result in longer roam times and dropped voice packets and could even
result in dropped calls.
• Configure the same SSID across all APs utilized by the Cisco Jabber mobile
client devices within the WLAN to ensure the fastest AP-to-AP roaming.
• Configure all enterprise WLAN APs to broadcast their SSIDs in order to
prevent mid-call prompts to join other APs within the WLAN infrastructure,
which could result in interrupted calls.
Provide sufficient wireless voice and video call capacity on the enterprise wireless
network for Cisco mobile clients and devices by deploying the appropriate number of
wireless APs to handle the desired call capacity based on mobility-enabled user BHCA
rates. Each 802.11g/n (2.4 GHz) or 802.11a/n (5 GHz) channel cell can support a
maximum of 27 simultaneous voice-only calls with 24 Mbps or higher data rates. Each
802.11g/n (2.4 GHz) or 802.11a/n (5 GHz) channel cell can support a maximum of 8
simultaneous video calls assuming 720p video resolution at up to 1 Mbps bit rate. For 2.4
GHz WLAN deployments, Bluetooth must be disabled to achieve this capacity. Actual
call capacity could be lower depending on the RF environment, wireless endpoint type,
and WLAN infrastructure.
Characteristics of Video on Mobile Devices
Requires low end-to-end latency to prevent users’ perceived disturbing delay in the
realtime interaction
Very sensitive to both delay and jitter due to a small playback buffer
Throughput is not a large issue since data rate is typically low (around1 Mbps)
Reasonably high sensitivity to packet loss due to significant compression and

possible UDP-based transmission
Product Codec
Cisco Jabber for iPhone Voice: G.711, G729a
Cisco Jabber for Android Voice: G.711µ, G.729a/b
Cisco Jabber for iPad Voice: G.711, G.722.1
Video: H.264
www.flane.com.au
Cisco Jabber for iPad Overview
Cisco Jabber for iPad is a Unified Communications application that provides

instant messaging (IM), video and voice calling, corporate directory search,
availability, and voicemail. The underlying technologies include
Cisco WebEx Messenger
Cisco Unified Presence
Cisco TelePresence Video Communication Server
Cisco Jabber Video for TelePresence (formerly known as the free Jabber
Video service)
Cisco WebEx TelePresence (formerly known as the paid Jabber Video

service)
www.flane.com.au
Cisco Jabber for iPad is a mobile client for the Apple iPad, and it provides voice and video
calling capabilities as well as enterprise visual voicemail and directory access. The Cisco Jabber
for iPad client also provides XMPP-based IM and presence when integrated to on-premises Cisco
IM and Presence services or cloud-based collaboration services such as Cisco WebEx Messenger.
Once the client application is downloaded from the Apple Application Store and installed on the
iPad device, it can connect to the enterprise network and register to Unified CM or Cisco
TelePresence Video Communication Server (VCS) as a SIP enterprise endpoint. To provide
registration and call control services to the Cisco Jabber iPad client, the device must be
configured within Unified CM or VCS. When registering to Unified CM call control services, the
client device is configured as a Cisco Jabber for Tablet device type. When registering to VCS
call control services, the client device is configured and provisioned using the jabbertablet
provisioning template and Cisco TelePresence Management Suite (TMS).
Next, the client device must be configured to access the enterprise WLAN for connectivity based
on the enterprise WLAN infrastructure and security policies. Alternatively the device can be
connected to the enterprise network through the mobile data network (if the device supports
mobile provider data and if mobile data services are enabled) or over non-enterprise WLANs.
Once the client device has been configured to access the enterprise network, when the Cisco
Jabber for iPad client is launched, it will register the device to Unified CM or VCS for voice and
video call control services.
The Cisco Jabber for iPad client is supported on the Apple iOS iPad 2 or the new iPad (third
generation). WLAN interfaces of Apple iPad devices support 802.11a, 802.11b, 802.11g, and
802.11n.
Cisco UC Components Requirements
www.flane.com.au
Cisco Jabber for iPad System

Requirements
Component System Requirements
Apple iPad iPad 2, new iPad (iPad 3), and Apple iOS 5.1.1
or later
Cisco Unified Communications Manager Voice: 7.1.5
Voice and video: 8.03, 8.5.1, 8.6.2, and 9.0
Cisco Unified Presence 8.0, 8.5, 8.6.2, and 9.0
Cisco TelePresence Video Communication 6.0 or later
Server
Cisco TelePresence Management Suite 13.1 or later
(Cisco TMS)
Cisco WebEx Messenger 7.6
Cisco Jabber Video for TelePresence 1.0 or later
Cisco Unity® Connection 8.5, 8.6, and 9.0
www.flane.com.au
Cisco Jabber for iPad System Requirements
Cisco Jabber for iPad System
Component System Requirements
Cisco Unified Survivable Remote Site 8.6 and 9.0 (voice only)
Telephony (Cisco Unified SRST)
Corporate Directory Microsoft AD 2008 and OpenLDAP v3
(optional) Cisco AnyConnect® 2.5 or later
Cisco Adaptive Security Appliance (ASA) Cisco ASA 8.4 or later
Cisco Adaptive Security Device Manager
(ASDM) 6.4 or later
www.flane.com.au
Cisco Jabber Deployment Models
On-premises solutions include the following:
Cisco Unified Communications Manager (Cisco UCM) for enterprise voice

and video
Cisco TelePresence Video Communication Server (Cisco VCS) for Cisco

TelePresence video
Cisco Unified Presence for IM and Presence
Cloud solutions include the following:
Cisco WebEx Messenger (also known as WebEx Connect) service for IM and
Presence, and peer-to-peer (P2P) voice and video
Cisco Jabber Video™ for TelePresence
www.flane.com.au
Cisco offers a variety of back-end services for voice and video call control and IM and presence
either in the cloud or on-premises, or a combination of both.
On-premises solutions include the following:
Cisco Unified Communications Manager (Cisco UCM) for enterprise voice and video
Cisco TelePresence Video Communication Server (Cisco VCS) for Cisco TelePresence
video.
Cisco Unified Presence for IM and Presence
Cloud solutions include the following:
Cisco WebEx Messenger (also known as WebEx Connect) service for IM and Presence,
and peer-to-peer (P2P) voice and video
Cisco Jabber Video™ for TelePresence
Backend Services
Many deployment options & combinations to meet customer needs
Understanding what customer has and needs is key

Voice + Video +
Voice + Video Only Presence/IM Only
Presence/IM
Features Features
Features
Unified CM + Unified
Unified CM Unified Presence (IM Only)
Presence
Unified CM + WebEx
Cisco VCS WebEx Connect (IM Only)
Connect
VCS + WebEx Connect Jabber Video*
Jabber Video* + WebEx
Connect
www.flane.com.au
Cisco Jabber for iPad enables various deployment options for on-premises and cloud back-end
services for unified communications and collaborations, with flexibility to support different
combinations of functions based on your requirements. The Cisco Jabber for iPad Administration
Guide provides details of administration and provisioning steps for the back-end services,
including the following deployment scenarios:
Instant messaging and presence only
Cisco Unified Presence (on-premises)
Cisco WebEx Messenger service (cloud)
Voice and video call control only
Cisco Unified Communications Manager (on-premises)
Cisco TelePresence Video Communication Server (on-premises)
Cisco Jabber Video for TelePresence (cloud)
Instant messaging, presence, voice, and video
Cisco Unified Presence + Cisco Unified Communications Manager
Cisco WebEx Messenger service + Cisco Unified Communications Manager
Cisco WebEx Messenger service + Cisco TelePresence Video Communication
Server
Cisco WebEx Messenger service + Cisco Jabber Video for TelePresence
Corporate Directory
Microsoft Active Directory 2008
Open Lightweight Directory Access Protocol (OpenLDAP) Version 3
Unified messaging
Cisco Unity® Connection
VPN
Cisco Adaptive Security Appliance (ASA)
Jabber for iPad Architecture
www.flane.com.au
Not all the services and functions are required for deploying Cisco Jabber for iPad, so during the
design and deployment timeframe you should consider a combination of functions such as IM,
call control, and secure remote. From a user perspective, as a minimum you need to decide to set
up individual accounts or company-provided accounts for IM and voice and video call-control
services for Cisco Jabber for iPad users before the deployment.
Cisco Jabber VCS/TMS Deployment
Cisco TelePresence VCS

Control Cisco TelePresence MCU
Cisco TelePresence
VCS Expressway
Private Network Internet
Voice and Video Calling Voice and Video Calling
Cisco TelePresence
Management Suite
www.flane.com.au
How Does Communication Work at Sign-in?

After signing in to Cisco Jabber for iPad, users specify the internal and external VCS server
addresses. The application first attempts to subscribe to the internal address. In such situations as
the iPad device being connected to non-corporate Wi-Fi, the application then tries to subscribe to
the external address.
If the internal VCS server address is a DNS address that translates to more than one IP address,
the application attempts to connect to all these IP numbers before trying the external VCS server
address. If the DNS server contains SRV records, the application adheres to the priority and
weight of the IP addresses; otherwise they are tried in a random order.
Typically, the VCS or the TMS Agent challenges the first subscription message. The application
answers this challenge by sending another SUBSCRIBE message with the authentication
information.
After the subscription has been authenticated, the TMS Agent sends provisioning information to
the application. The application registers to the VCS according to the provisioning information
for SIP Server URI or Public SIP Server URI in the TMS. If this provisioning information is
identical to the internal and external VCS server addresses users specify upon signing in (Cisco
recommends that they are identical.), the application registers to the same VCS it subscribes to.
As long as the application is registered, the VCS knows to forward messages to the application.
After initial registration, the application continues to send registration messages to the VCS
according to the Standard registration refresh maximum (seconds) setting in the VCS server.
The application sends the messages after 75% of the specified time interval has elapsed.
Cisco Jabber in On-Premises Deployment
www.flane.com.au
Cisco Jabber in Hybrid Deployment
www.flane.com.au
Wi-Fi Network Connectivity
Site survey required prior to adding VoWLAN devices
Even with existing VoWLAN devices already deployed, each Cisco Jabber type
should be tested prior to production rollout
You can use the following tools and applications to verify coverage, quality, and
configuration:
Cisco Prime™ Network Control System (NCS) for Unified Wireless LAN Management
Cisco Wireless Control System (WCS) for Unified Wireless LAN Management
Cisco Wireless LAN Solution Engine (WLSE) for Autonomous Wireless LAN
Management
Cisco Spectrum Expert® Wi-Fi
Cisco Spectrum Expert AirMagnet
www.flane.com.au
Apple iPad is a mobile device that requires wireless network connectivity by using Wi-Fi or
mobile wireless data services. Although a mobile wireless network provided by mobile wireless
carriers is capable of delivering IM, presence status, voice, video capabilities, and other
communication capabilities to Cisco Jabber for iPad, this document focuses on important
deployment concepts and expectations for Cisco Jabber for iPad in an enterprise wireless LAN
(WLAN) environment.
Apple iPad Wi-Fi Specifications
Apple iPad 2 and the new iPad (iPad 3) support 2.4- and 5-GHz 802.11a/b/g/n Wi-Fi with Wi-Fi
Multimedia (WMM) capability. Details about WLAN data rates, modulation schemes, RF
characteristics, antenna, and other specifications are available at the Apple website and at the
Federal Communications Commission (FCC) website.
Site Survey
A site survey is strongly recommended before you deploy Cisco Jabber for iPad in a production
environment. Because Cisco Jabber for iPad requires a low end-to-end latency and packet-loss
rate to prevent delay in real-time communications, you must have a well-designed and -planned
wireless network. During the site survey, you must analyze and validate RF spectrum, coverage,
data rates, capacity, signal levels, noise, roaming, interference, and locations of access points to
ensure a high-quality WLAN for real-time communications.
You can use the following tools and applications to verify coverage, quality, and configuration:
Cisco Prime™ Network Control System (NCS) for Unified Wireless LAN Management:
http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps11682/ps11686/ps11688/
data_sheet_c78-650051.html.
Cisco Wireless Control System (WCS) for Unified Wireless LAN Management:
http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_dat
a_sheet0900aecd802570d0.html.
Cisco Wireless LAN Solution Engine (WLSE) for Autonomous Wireless LAN
Management:
http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6380/ps6563/ps3915/ps6839/pr
oduct_data_sheet0900aecd80410b92.html.
Cisco Spectrum Expert® Wi-Fi:
http://www.cisco.com/en/US/prod/collateral/wireless/ps9391/ps9393/product_data_sheet
0900aecd807033c3.html.
Cisco Spectrum Expert AirMagnet (Survey, Wi-Fi Analyzer, VoWi-Fi Analyzer, and
Spectrum Analyzer): http://www.airmagnet.com.
WLAN Considerations for Cisco Jabber for
iPad Deployment
Band selection
IEEE 802.11n on 5 GHz, which also operates on the 2.4-GHz band, is

recommended
Apple iPad 2 and the new iPad (iPad 3) support 2.4- and 5-GHz
802.11a/b/g/Wi-Fi with Wi-Fi Multimedia (WMM)
Overlapping channel:
Overlapping channels causes unacceptable and degraded signal quality and
throughput, and users could have a bad overall experience when using real-time
communication applications such as Jabber for iPad.
Coverage area
www.flane.com.au
WLAN Considerations for Cisco Jabber for iPad Deployment

You have many wireless standards and technologies options; the intent of this document is not to
provide a comparison of each option but to provide a list of recommendations and considerations
for a successful deployment of Cisco Jabber for iPad for real-time communications.
After a site-survey analysis, administrators should have a clear view of how their WLAN is
implemented. It is essential for administrators to improve and correct any existing deficiency,
including identifying and eliminating sources of interference in the WLAN, before deploying
Cisco Jabber for iPad. Implementation involves making decisions about the following parameters:
Band selection: The 2.4-GHz frequency band used by 802.11b, 802.11g, and 802.11n is
shared with other unlicensed devices, including Bluetooth devices, cordless phones, etc.,
and these devices generally increase noises and interference and result in air-time
congestion. On the other hand, the 5-GHz band is less crowded compared to the 2.4-GHz
band. IEEE 802.11n on 5 GHz, which also operates on the 2.4-GHz band, is
recommended; it provides a faster speed and data rate with the latest wireless
technologies.
Overlapping channel: Whether you use the 2.4- or 5-GHz band, the band is divided into
channels, similar to the way radio and TV broadcast bands are divided. For example, the
2.4-GHz band is divided into 13 channels (Japan has a 14th channel for 802.11g only),
each 5 MHz apart.
Overlapping channels causes unacceptable and degraded signal quality and throughput, and users
could have a bad overall experience when using real-time communication applications such as
Jabber for iPad. Therefore, it is essential that you allocate nonoverlapping channels when
designing a WLAN network. In the United States, the channels 1, 6, and 11 are the only
nonoverlapping channels available when 802.11b/g used. In 802.11a and 802.11n at 5 GHz, on
the other hand, there is a larger range of band frequency and more nonoverlapping channels to
allocate. We recommend at least one channel of separation for adjacent access points in the 5-
GHz band.
In 802.11n, two adjacent 20-MHz channels can be bounded into a 40-MHz channel, doubling the
amount of available bandwidth and increased throughput. In the 2.4-GHz frequency band, only
one bounded channel is available, either channels 1 and 6 or 6 and 11. Because only three
nonoverlapping channels in the 2.4-GHz band are available, channel bonding in the 2.4-GHz
band is not recommended. However, because there are more nonoverlapping channels in the 5-
GHz frequency band, you can consider channel bonding configuration and design in the 5-GHz
band.
iPad Deployment (Cont.)
Coverage area
Includes office area, conference rooms, cafeterias, etc. Capacity, data rate, and
transmit power configurations affect the coverage-area design.
In general, faster data rates translate to smaller cells, meaning an access point that
operates in 5-GHz frequency covers less footage than an access point in 2.4-GHz
frequency.
www.flane.com.au
Coverage area:
The coverage area typically includes office area, conference rooms, cafeterias, etc. Capacity, data
rate, and transmit power configurations affect the coverage-area design. In general, faster data
rates translate to smaller cells, meaning an access point that operates in 5-GHz frequency covers
less footage than an access point in 2.4-GHz frequency. Similar to data rates, if the transmit
power settings in an access point are higher, the coverage area of a cell is larger.
The general rule for supporting real-time communications is smaller cells and more cells in a
coverage area. Figure 5 shows a comparison of larger and less cells vs. smaller and more cells in
a coverage area. However, the numbers of access points that are deployed in a coverage area
depend on the numbers of wireless devices in the area, how those devices are used, and other
factors such as budgets (more access points cost more money) and lobbies and conference rooms
(a lobby may need less coverage, whereas a conference room may need more, etc.).
Channel cell capacity and density
Cisco Jabber for iPad delivers real-time voice and video. It supports up to 448p at 30
fps, and the suggested bandwidth allocation per call is 768 kbps end-to-end, which
includes the transmission over the air from and to the iPad.
These voice and video call-capacity values are highly dependent upon the RF
environment, the configured or supported video resolution and bit rates, and the
underlying WLAN system features.
www.flane.com.au
Channel cell capacity and density:

The coverage area of an antenna is the collision domain of the access point. Cisco Jabber for iPad
delivers real-time voice and video. It supports up to 448p at 30 fps, and the suggested bandwidth
allocation per call is 768 kbps end-to-end, which includes the transmission over the air from and
to the iPad. Therefore, it is important to check the specifications of your access points and
wireless infrastructure to carefully calculate the number of calls an access point can support. Pay
special attention to the high-density area where Cisco Jabber for iPad will be used, such as
conference rooms, to avoid bandwidth exhaustion.
Because there are more channels in the 5-GHz frequency band, using co-location of access points
on nonoverlapping channels increases per-channel cell capacity on a floor.
These voice and video call-capacity values are highly dependent upon the RF environment, the
configured or supported video resolution and bit rates, and the underlying WLAN system
features. Actual capacities for a particular deployment could be less. Coverage area, channel cell
capacity, and density are the main factors for a successful WLAN deployment.
When deploying wireless devices within the enterprise WLAN, it is important to consider the call
capacity of the WLAN infrastructure. Oversubscription of the enterprise WLAN infrastructure in
terms of number of devices or number of active calls results in dropped wireless connections,
poor voice and video quality, and delayed or failed call setup. The chances of oversubscribing a
deployment of voice and video over WLAN (VVoWLAN) are greatly minimized by deploying
sufficient numbers of access points to handle required call capacities. Access-point call capacities
are based on the number of simultaneous voice and video bidirectional streams that can be
supported in a single channel cell area. When deploying Cisco Jabber for iPad, the following
WLAN call capacities apply:
Maximum of 27 simultaneous voice-over-WLAN (VoWLAN) bidirectional streams per
802.11g/n (2.4 GHz) with Bluetooth disabled or 802.11 a/n (5 GHz) channel cell and 24
Mbps or higher data rates.
Assuming a video resolution of 448p and a video bit rate of up to 1 Mbps, a maximum of
eight simultaneous VVoWLAN bidirectional streams per 802.11 g/n (2.4 GHz) with
Bluetooth disabled or 802.11 a/n (5 GHz) channel cell.
WLAN QoS support:
Wi-Fi Multimedia (WMM), also known as Wireless Multimedia Extensions (WME), is a
subset of the 2005 IEEE 802.11e specification, which provides basic QoS and a power-
saving mechanism to the IEEE 802.11 network.
Roaming:
The iPad is a mobile device that allows you to move around without losing connectivity
by roaming from one access point to another.
www.flane.com.au
WLAN QoS support:

Wi-Fi Multimedia (WMM), also known as Wireless Multimedia Extensions (WME), is a subset
of the 2005 IEEE 802.11e specification, which provides basic QoS and a power-saving
mechanism to the IEEE 802.11 network. WMM prioritizes traffic in four categories: voice, video,
best effort, and background. Applications such as Jabber for iPad can request QoS level support
over Wi-Fi. Without QoS, all applications running on different devices have equal opportunity to
transmit data, and it may result a slow transmission for voice and video data.
WMM provides differentiated services by tagging the Layer 3 and Layer 2 protocol layer bit
fields, and gives real-time communication applications a priority preference over other traffic.
You should configure WMM policy in the wireless infrastructure wherever possible.
Roaming:
The iPad is a mobile device that allows you to move around without losing connectivity by
roaming from one access point to another. Roaming is the process of a client moving an
established Wi-Fi network association among access points within the same Service Set
Identification (SSID). Without a well-planned and well-designed wireless network, roaming can
cause dropped calls or long delays for mobile users.
The goal of roaming for any wireless client is to minimize the time required to transition between
access points to avoid disruptions of the client applications. Fast roaming and session caching
mechanisms can be used to eliminate some of the unnecessary authentication steps. However, the
algorithm to decide when to roam and how to roam is implemented by the clients. Because Apple
iPad does not support Cisco Compatible Extensions or the IEEE 802.11r specification for fast
secure roaming, users may experience delay during the process of roaming.
Opportunistic Key Caching (OKC), also known as Proactive Key Caching, is also used to
minimize latency and overhead in the authentication process during a roaming process. iPad does
not support OKC; however, it supports Pairwise Master Key ID (PMKID) or “sticky key
caching” for roaming, meaning the client remembers or “sticks” the PMKID with its initial
associated and authenticated access point or Basic Service Set Identification (BSSID), not to
another access point. Therefore, during the roaming process, the client may disconnect until it
completes the authentication process again with a new PMKID. If you are in a call using Jabber
for iPad, your call may be disrupted by a long delay or may even be disconnected during
roaming.
In addition, calls may be dropped or experience long delays during roaming in the following
scenarios:
When an IP address assigned to your iPad changes
When you roam from one WLAN to another
When you roam within a WLAN that does not broadcast SSID
Recommended Wi-Fi Deployment Settings
Factor Recommendations
RF bands 5 GHz
Signal level -67 dBm with 20-30% overlap of the cell edge on
nonadjacent channels
Channel usage < 50%
Noise < -92 dBm
Packet loss < 1%
Jitter < 100 ms
Retries < 20%
www.flane.com.au
Bandwidth Management and QOS
Cisco Jabber for iPad supports G.711 and G.722 for audio and H.264 for video,
and for video calls, up to 448p at 30 fps. We recommend that the minimum
bandwidth allocated per call should be >768 kbps.
Cisco Jabber for iPad uses video rate adaptation to negotiate optimal video
quality based on your network conditions.
Upload Speed Audio Audio + Interactive

Video (Main Video)
125 kbps At bandwidth threshold for G.711 Insufficient bandwidth
Sufficient bandwidth for G.722.1 for video
384 kbps Sufficient bandwidth for any audio w288p (512x288) at 30
codec fps
1000 kbps Sufficient bandwidth for any audio 448p (576x448) at 30 fps
codec
www.flane.com.au
When deploying Cisco Jabber for iPad, it is important that the network infrastructure support
necessary QoS classes of service, including priority queuing for voice media and dedicated video
and signaling bandwidth, to ensure the quality of Cisco Jabber voice and video calls. It is critical
to minimize the end-to-end latency to avoid delay, packet loss, and jitter for real-time
communications.
Cisco Jabber for iPad supports G.711 and G.722 for audio and H.264 for video, and for video
calls, up to 448p at 30 fps. We recommend that the minimum bandwidth allocated per call should
be >768 kbps.
Cisco Jabber for iPad uses video rate adaptation to negotiate optimal video quality based on your
network conditions. Video rate adaptation dynamically scales video quality when video
transmission begins.
Cisco Jabber VPN Requirements
Account Is VPN required for remote access?
Cisco WebEx Messenger No. You can use it over any Wi-Fi or 3G
connection.
Cisco Unified Presence Yes. Connect on Demand VPN applicable.
Cisco Unified Communications Yes. Connect on Demand VPN applicable.

Manager
Cisco TelePresence Video No, if you are using Cisco TelePresence Video
Communication Server Communication Server (VCS) Expressway.
Yes, if you are not using Cisco VCS Expressway.
Connect on Demand VPN not applicable.
Cisco Jabber Video for TelePresence No. You can use it over any Wi-Fi connection.
www.flane.com.au
Cisco Jabber VPN Requirements (Cont.)
Administrators should also consider the following configurations for a more

integrated user experience with Jabber for iPad and AnyConnect:
Enable Certificate Authentication, so end users do not need to enter VPN credentials
manually.
Properly configure split tunneling, to ensure only the traffic destined for Cisco UCM
goes into the encrypted tunnel.
www.flane.com.au
AnyConnect VPN Features Overview
VPN on-demand, which is available for iOS and allows the AnyConnect tunnel to
be established whenever a particular destination is contacted (that is, Cisco
UCM).
Split Include, which allows you to configure specific traffic to be sent through the
encrypted tunnel; for example, using Split Include, Cisco UCM voice traffic could
be sent through the encrypted tunnel, and Safari browser data would not.
AnyConnect also has a built-in diagnostics and reporting tool and statistics
reporting to help troubleshoot VPN problems.
The Apple iOS On-Demand VPN feature requires certificate-only authentication.

For non-certificate authentication options, the end user has to manually initiate
the AnyConnect VPN connection as needed.
www.flane.com.au
The Cisco AnyConnect® Secure Mobility Client is the industry-leading multiservice client that
provides an intelligent and optimized connection while helping ensure a secure session. The
Cisco Jabber™ client enables collaboration across a multitude of devices, including laptops,
smartphones, and tablets. The Jabber client also provides rich unified communications
capabilities such as voice and video, instant messaging (IM), presence, visual voicemail, web
conferencing, desk phone integration, and more. To meet the needs of an increasingly mobile
workforce, the Jabber client requires secure access to the unified communications (UC) servers.
This deployment guide discusses the various AnyConnect features1 used to secure and improve
the user experience with Jabber, offering configuration steps and best practices.
The target audience includes security and collaboration engineers and anyone seeking an
understanding of what it takes to implement the Jabber and AnyConnect solution. Some prior
knowledge of Cisco AnyConnect, ASA, Jabber, and Unified Communications Manager is
helpful, though not required. After reading this document, the reader should have a good
understanding of the components involved in the solution and will be well equipped to review
other detailed collateral.
Cisco ASA 5500 Series SSL/IPsec VPN Edition
The Cisco® ASA 5500 Series SSL/IPsec VPN Edition offers flexible VPN technologies for any
connectivity scenario, with scalability up to 10,000 concurrent users per gateway. It provides
easy-to-manage, full-tunnel network access through SSL, Datagram Transport Layer Security
(DTLS), IP Security (IPsec) VPN client technologies, advanced clientless SSL VPN capabilities,
and network-aware site-to-site VPN connectivity, enabling highly secure connections across
public networks to mobile users, remote sites, contractors, and business partners.
Cisco AnyConnect Secure Mobility Client
The Cisco AnyConnect Secure Mobility Client provides a highly secure connectivity experience
across a broad set of PCs, tablets, and smartphone-based mobile devices, such as the Apple
iPhone and Android. As mobile workers roam to different locations, an always-on intelligent
VPN enables the AnyConnect Secure Mobility Client to automatically select the most optimal
network access point and adapt its tunneling protocol to the most efficient method, including the
DTLS protocol for latency-sensitive traffic such as voice over IP (VoIP) traffic or TCP-based
application access.
Cisco Jabber for iPad contains the Connect on Demand VPN feature. The Connect on Demand
VPN feature enables the Cisco Jabber for iPad application to automatically establish VPN
connections when needed without additional actions by end users. The Connect on Demand VPN
feature requires a user to download and install the Cisco AnyConnect Secure Mobility Client
from the App Store.
Cisco AnyConnect Secure Mobility Client must be configured with certificate authentication to
provide the Connect on Demand VPN feature to Cisco Jabber for iPad.
There is no configuration in Cisco Jabber for iPad other than turning the Connect on Demand
VPN feature on or off. This feature is turned on by default after Cisco Jabber for iPad is installed.
Cisco AnyConnect and Jabber
VPN Initiation on iOS

1. The remote end user launches the Jabber client.
2. The Jabber client triggers the iOS On-Demand VPN feature, and the AnyConnect
client establishes an SSL VPN connection with the ASA VPN gateway, using
certificate-based authentication. www.flane.com.au
VPN Initiation on iOS

1. The remote end user launches the Jabber client.
2. The Jabber client triggers the iOS On-Demand VPN feature, and the AnyConnect client
establishes an SSL VPN connection with the ASA VPN gateway, using certificate-based
authentication.
Note: The Apple iOS On-Demand VPN feature requires certificate-only authentication. For non-
certificate authentication options, the end user has to manually initiate the AnyConnect VPN
connection as needed.
VPN Initiation on Windows, Mac OS X, and Android*
1. As soon as the end user connects to noncorporate Wi-Fi or 3G cellular networks, the
Trusted Network Detection feature of the AnyConnect VPN client initiates an SSL VPN
connection.
2. The AnyConnect client establishes an SSL VPN connection with the ASA VPN gateway,
using certificate-based authentication.
Note: The Trusted Network Detection feature is currently not available with the Android
ICS (generic) version of AnyConnect. Hence, the end user has to manually initiate the
VPN connection as needed. For support for other Android devices, please see the release
notes.7
Connection Flow After Establishing VPN on All Devices
3. The Jabber client will connect to Cisco Unified Communications appliances to provide
unified communications services over the VPN connection.
4. The Jabber client is then ready to place or receive voice or video calls, etc.
Cisco Jabber Secure Connect Feature
Overview
A built-in feature of Cisco Jabber
No separate security application needs to start
Secures traffic & workloads for Cisco Jabber

Just for Cisco Jabber, not the entire device
Enterprise-grade encryption and authentication

Leverages Cisco ASA security solutions
Seamless user experience as part of Cisco Jabber

Cisco Jabber controls secure connect in the background
Reuse the same Cisco AnyConnect licenses

No need to buy additional licenses
Already part of Cisco Jabber client as a feature
www.flane.com.au
Cisco Jabber secure connect enables users who are away from the office Wi-Fi network to easily
remain connected to corporate resources. When deployed together with the Cisco ASA 5500
Series Adaptive Security Appliance, the end user connectivity experience is secure, transparent,
and friendly to today's proliferation of individually purchased mobile devices. When needed, the
Cisco Jabber application - rather than the entire device or platform - initiates a secure Secure
Sockets Layer (SSL) connection and validates the user credentials (whether authentication,
authorization, and accounting [AAA] or digital certificates). Also, when the user returns to the
office network, the Cisco Jabber application detects that the SSL tunnel is no longer required and
breaks the tunnel down. Only application traffic from the Cisco Jabber application will traverse
the enterprise, and other applications will not access corporate networks.
Cisco Jabber Secure Connect Feature
New Way of Securing with Cisco Jabber
Figure 3-9
www.flane.com.au
When accessing the enterprise from a carrier network or noncorporate Wi-Fi network, the Cisco
Jabber secure connect feature authenticates using either x.509 digital certificates or usernames
and passwords (RADIUS). The Cisco Jabber secure connect feature then establishes a secure SSL
connection to the enterprise and allows access to the resources. When the user returns to the
office and is able to access the corporate Wi-Fi network, the Cisco Jabber secure connect feature
detects this state and automatically disables the SSL tunnel. If, however, a call is in progress, the
application waits until the call is completed, so as not to interrupt the call.
We recommend deploying the Cisco Jabber application with secure connect using certificate-
based authentication. The next preferred method is password-based authentication using AAA on
RADIUS servers.
Cisco Secure Connect Feature
System Admin Perspective Comparison
Feature Jabber secure connect AnyConnect Secure Mobility Client
Combined Jabber + security app –
Installation and Handled through ASA, separate
easier setup for new hires &
Administration setup from Jabber app
vendors
Client setup and Provisioned with Jabber app (i.e..
Provisioned through ASA
management TFTP)
Comparable security, encryption, Comparable security, encryption,
Common infrastructure
authentication types authentication types
Requires AnyConnect Essentials or Requires AnyConnect Essentials or
Licensing
Premium Premium, and AnyConnect Mobile
Branch access Not yet available on ISR routers ISR routers
D-TLS and SSL for tunneling. D-TLS and SSL for tunneling.
Protocols
Multiple authentication types Multiple authentication types
www.flane.com.au
Cisco Secure Connect Feature

End User Perspective Comparison
AnyConnect Secure Mobility
Feature Jabber secure connect
Client
Sweet spot: use case Personal device, enterprise apps Corporate managed device for
description get access to enterprise resources business use
Device choice Personal or Corporate device Corporate device
Security control Jabber app controls the tunnel Always on, user controlled
Enterprise traffic Personal apps and traffic don’t All device traffic traverses
traverse through enterprise through enterprise
Application experience Jabber app and interface combined Separate apps and interface for
with secure connect Jabber and security
Local resource access Access local network resources like Spilttunnel policy for network
printers access generally not allowed
Voice calls VOIP friendly D-TLS
Trusted Network Detection Via Jabber app Within AnyConnect
Roaming Roaming friendly and fast reconnects (i.e. IP address caching)
www.flane.com.au
Summary
Cisco Jabber for mobile supports WLAN and VPN connectivity.
Cisco Jabber for iPad has flexible deployment options using Cisco Unified CM or
VCS.
Cisco Jabber user administration depends on the deployment option
Cisco Secure Connect is embedded feature in Cisco Jabber for mobile to secures
the connection to the premises.
Another option is to use Anyconnect client with Cisco Jabber for mobile.
www.flane.com.au
Lesson 2
Provisoing Cisoc Jabber for

Mobile
Provisioning for Users
Cisco Jabber for iPhone Cisco Jabber for iPad
Cisco Jabber for iPad Cisco Jabber IM for iPhone

www.flane.com.au
User provisioning depends on the deployment model :

For TelePresence Video Communications Server (Video Deployment):
Cisco TelePresence Management Suite (TMS) need to be synchronized with
corporate directory server via LDAP and the VCS will synchronize with TMS
through its TMS Agent
For Cisco Unified CM and Cisco Unified IM and Presence (Voice/Video/IM and
Presence Deployment):
Cisco Unified CM need to be synchronized with the corporate directory .Cisco
Unified IM and Presence will pick users enabled for presence from the Cisco Unified
CM and the user can be authenticated against LDAP password or local to the Cisco
Unified CM
For WebEx Connect (IM/Presence Only deployment):
If your Cisco WebEx organization is enabled with directory integration, users cannot
edit the directory information in their profiles. Users need to contact the Organization
Administrator for updates to their profiles.
If your Cisco WebEx organization is enabled with directory integration, you can
deactivate users manually in case a user's account needs to be deactivated immediately.
Single sign-on also permits companies to use their on-premise single sign-on system to
simplify the management of Cisco WebEx Administration. With single sign-on, users
securely sign in to the application using their corporate sign in credentials. The user's sign
in credentials are not sent to Cisco WebEx, protecting the user's corporate sign in
information.
As a single sign-on configuration option, user accounts can be automatically created the
first time a user signs in. Single sign-on also prevents users from accessing Cisco WebEx
application if their corporate sign in account has been deactivated.
The Cisco WebEx application supports single sign-on systems based on the industry
standard Security Assertion Markup Language (SAML) protocol.
Provisioning for Devices in Unified CM
Jabber for iPad Jabber for Jabber for
iPhone Android
Phone Type in Product Type Cisco Jabber for Cisco Dual Mode Cisco Dual Mode
CUCM Tablet for for
(CSF based) iPhone (Dual Android (Dual
Mode Mode
Phone based) Phone based)
Device Protocol SIP SIP SIP
CUCM Version requiring COP File Up to 9.0(1) Up to 8.0(2) Up to 8.6(x)
Device name in CUCM TAB<userID> TCT<userID> BOT<userID>

e.g. TABBJONES e.g. TCTBJONES e.g. BOTBJONES
Devices are not required for Jabber IM for iPhone (cross functional with Jabber
for iPhone)
www.flane.com.au
To make Cisco Jabber available as a device in Unified CM, you must install a device-
specific Cisco Options Package (COP) file on all your Unified CM servers.
Device Name for Cisco Jabber for iPad:
Represents only one device. If a user has Jabber for iPad on multiple devices, set
up each device with a different device name.
Must start with TAB, followed by up to 15 uppercased or numeric characters.
Example: TABJOHND.
Can contain dot (.), dash (–), or underscore (_).
Device Name for Cisco Jabber for iPhone:
Can represent only one device. If a single user has Cisco Jabber on multiple
devices (for example, an iPhone and an iPad), configure separate Cisco Dual
Mode for iPhone devices for each in Unified CM.
Must start with TCT
Must be uppercase
Can contain up to 15 characters total
Can include only A to Z, 0 to 9, dot (.), dash (-), or underscore (_)
Device Name for Cisco Jabber for Android:
Must start with BOT
Must be uppercase
Can contain up to 15 characters
Can include only the following characters: A to Z, 0 to 9, dash (-), or underscore
(_)
We recommend that the device name include the username of the user so it is
easily remembered
Step 1: Create SIP Profile
In Cisco Unified CM Administration. Select Device > Device Settings > SIP
Profile
Set the following values to 660:

Timer Register Expires
Timer Keep Alive Expires
Timer Subscribe Expires
www.flane.com.au
Create a dedicated SIP Profile that allows Cisco Jabber to stay connected to Unified CM while
Cisco Jabber is running in the background.
Procedure
Step 1 In Unified CM, select Device > Device Settings > SIP Profile.
Step 2 Create a new SIP profile, such as “iPhone SIP profile,”or copy an existing SIP profile.
Step 3 In the new SIP profile, set the following values:
Timer Register Delta to 60
Timer Register Expires to 660
Timer Keep Alive Expires to 660
Timer Subscribe Expires to 660
Timer Subscribe Delta to 15
Step 4 Select Save.
Step 2: Add User Device
In Cisco Unified CM Administration , Select Device > Phone
Choose the configured iPhone SIP Profile
www.flane.com.au
Procedure
Step 1 Sign in to the Unified CM Administration portal.
Step 2 Select Device > Phone, and click Add New to add a new phone device with Cisco Dual
Mode for iPhone as the Phone Type.
Step 3 Enter the required settings for your devices. If you require additional information about
any option on the device configuration window, see the online help in Unified CM.
Step 4 Select Save.
Step 5 Select Apply Config.
Step 6 Select [Line n] - Add a new DN.
Step 7 Enter the directory number of this device.
This can be a new DN; a desk phone with the same DN is not required.
Step 8 If this device is a standalone device (not sharing a DN with a desk phone), configure these
settings to forward calls when Cisco Jabber is not running and connected to the network, so
callers do not receive an error message:
a) Forward Unregistered Internal
b) Forward Unregistered External
For more information about these settings, see the online help in Unified CM for the Forward All
and other
settings on the same window.
Step 9 Set the No Answer Ring Duration (seconds) to 24 seconds to allow time for Cisco Jabber
to ring before calls go to voicemail.
Note If Cisco Jabber for iPhone users have a PIN on the device, you may need to
increase the No Answer
Ring Duration (seconds) setting to ensure that they have enough time to enter the PIN
and answer the call before the call goes to voicemail.
If you increase the No Answer Ring Duration (seconds) setting, see related cautions for this
setting in the
online help in Unified CM.
Step 10 In the Multiple Call/Call Waiting Settings on Device device name section, in the Busy
Trigger field, ensure that the value is set to 2 or greater.
Step 11 Configure other settings as appropriate for your environment. Cisco Jabber does not
require specific values.
Step 12 Select Save.
Step 13 Navigate to the End User window for the user.
Step 14 Associate the Cisco Dual Mode for iPhone device that you just created for this user.
Depending on your release of Unified CM, the device should now appear in the Controlled
Devices box in
the Device Information or Device Associations section.
Step 15 If this user has a desk phone, select the desk phone as the Primary User Device.
Step 16 If the device is a standalone device that runs without an associated desk phone, you may
need to enter other information that is standard for all devices in your system.
Step 2: Add User Device (Cont.)
Configure the Product Specific Configuration Parameters:
Select User Management > End User
www.flane.com.au
Step 3: Prepare Automatic Setup Link
Simplify the setup process for your users by allowing them to automatically enter
settings into Cisco Jabber by tapping a link in an email message.
Transfers the information from the Product Specific Configuration Layout section
on the Phone Configuration page in Unified CM to the settings in the Cisco
Jabber application on the iPhone
Use the following format:

tctprov://connect?tu=username&td=Cisco Dual Mode for iPhone device
ID&ts=TFTP server IP address&tt=Secondary TFTP server IP address
Example:
tctprov://connect?tu=jsmith&td=TCTJSMITH&ts=192.0.2.41&tt=192.0.2.42
www.flane.com.au
Prepare Automatic Setup Link (Optional)

Simplify the setup process for your users by allowing them to automatically enter settings into
Cisco Jabber by tapping a link in an email message, instead of manually entering settings into
Cisco Jabber.
This link transfers the information from the Product Specific Configuration Layout section on the
Phone Configuration page in Unified CM to the settings in the Cisco Jabber application on the
iPhone. At first launch, Cisco Jabber prompts users for any required passwords.
You can include the following information in the URL:
tu—username
• td—device id
• ts—TFTP server
• tt—Secondary, or backup TFTP server
Cisco Jabber for iPhone Features Setup
Enable Active Call Transfer Between Cisco Jabber and Desk Phone
Add Mobile Connect and Mobile Identity
Transfer Active VoIP Call to the Mobile Network
Set Up Voice Dialing
Set Up Visual Voicemail on Unified CM
Specify Directory Search Settings
Set Up SRST Failover
Set Up Extension Mobility to Allow Users to Sign In and Out
Set Up Cisco AnyConnect
www.flane.com.au
Enable Active Call Transfer Between Cisco
Jabber and Desk Phone
Set up Call Park for the system , Call Routing > Call Park
www.flane.com.au
Make sure the desk phone (Primary DN) for the user is fully set up and can make and receive
internal and external calls and set up Call Park for the system.
Jabber and Desk Phone (Cont.)
In the End User configuration page
1. Associate the desk phone to the user
2. Ensure that the Allow Control of Device from CTI check box is checked.
3. Select the primary extension for the desk phone you want to associate with the
mobile device.
4. In the Permissions Information section, add Standard CTI Enabled to the User
Groups list.
www.flane.com.au
Procedure
Step 2 Choose User Management > End User.
Step 3 Search for the user you want to associate with a desk phone.
Step 4 Select the user ID to open the User Information page.
a) In the Device Information section, select Device Association and search for the desk
phone you want to associate with the mobile device.
b) Select the device you want to associate with the mobile device, and select Save
Selected/Changes.
c) Navigate back to the End User page.
d) Ensure that the Allow Control of Device from CTI check box is checked.
e) Select the primary extension for the desk phone you want to associate with the mobile
device.
f) In the Permissions Information section, add Standard CTI Enabled to the User
Groups list.
For 8900 and 9900 series phones, also add Standard CTI Allow Control of Phones
supporting Connected Xfer and conf.
g) Note the user ID of this user for use later in this procedure.
h) Select Save.
Jabber and Desk Phone (Cont.)
In the Phone configuration page assign Owner User ID to the desk phone and
the Dual mode iPhone
In the Desk Phone configuration page:
In the Dual mode iPhone Configuration page:
www.flane.com.au
Step 5 Choose Device > Phone and locate the desk phone you want to associate with the mobile
device.
a) Verify that the value for Owner User ID is the correct end user.
b) Ensure that the Allow Control of Device from CTI check box is checked.
If this option does not appear in the Device Information section of the Phone
Configuration window,
the phone does not support this feature.
c) Select Save.
Step 6 Navigate to the Cisco Dual Mode Device for iPhone page.
a) Verify that the value for Owner User ID is the correct end user.
b) In the Product Specific Layout Configuration section, for CTI Control Username,
enter the user ID
from the End User page.
c) Select Save.
Step 7 Navigate to the Directory Number Information page and verify that:
The Allow Control of Device from CTI check box is checked
The Associated Devices box displays the desk phone and the mobile device
Step 8 Restart the mobile device and the desk phone.
Added in Phone Configuration page
Required for hand-off from VoIP to cellular network
Enable/disables Mobile Connect
To assign mobile phone number
Specifies time of the day
www.flane.com.au
Mobile Connect, formerly known as Single Number Reach (SNR), allows the native mobile
phone number to ring when someone calls the work number if:
Cisco Jabber is not available.
After Cisco Jabber becomes available again and connects to the corporate network, the
Unified CM returns to placing VoIP calls rather than using Mobile Connect.
The user selects the Always Use DVO Jabber calling option.
The user selects the Automatically select Jabber calling option and the user is outside of
the Wi-Fi network.
To set up Mobile Connect, perform the following procedures:
1. Enable Mobile Connect
2. Specify one or more remote phone numbers to which Mobile Connect connects using one
or both of the following procedures:
(Preferred) To specify the GSM number of the mobile device
(Optional) To specify alternate phone numbers, see Add Remote Destination
(Optional)
Alternate numbers can be any type of phone number, such as home phone numbers, conference
room numbers, desk phone numbers, or a GSM number for a second mobile device.
Add Mobility Identity
Use this procedure to add a Mobility Identity to specify the GSM number of the mobile device as
the destination number. This destination number is used by features such as Dial via Office or
Mobile Connect.
You can specify only one number when you add a mobility identity. If you want to specify an
alternate number such as a second GSM number for a mobile device, you can set up a remote
destination. The Mobility Identity configuration characteristics are identical to those of the
Remote Destination configuration.
Procedure
Step 2 Navigate to the device page for the Cisco Dual Mode mobile device settings.
Step 3 In the Associated Mobility Identity section, select Add a New Mobility Identity.
Step 4 Enter the mobile phone number as the Destination Number.
This number must be routable to an outbound gateway. Generally, the number is the full E.164
number.
If you enable the Dial via Office - Reverse feature for a user, you must enter a destination number
for the user's mobility identity.
If you enable Dial via Office - Reverse and leave the destination number empty in the mobility
identity:
Note
The phone service cannot connect if the user selects the Automatically select Jabber
calling
option while using a 3G network and VPN.
The phone service cannot connect if the user selects the Always use DVO Jabber calling
option
on any type of network.
The logs do not indicate why the phone service cannot connect.
When using Dial via Office - Reverse, the system does not automatically push updated
destination
numbers for the user's mobility identity to the client after you already entered a
destination number.
To work around this issue, ask the user to do one of the following:
In the Cisco Jabber for iPhone Settings, manually update the phone number in the
DVO Callback
Number field.
In the Cisco Jabber for iPhone Settings, delete the current number in the DVO
Callback Number
field, and then exit and restart Cisco Jabber for iPhone
Step 5 Enter the initial values for call timers.
These values ensure that calls are not routed to the mobile service provider voicemail before they
ring in the client on the mobile device.
Setting Suggested Initial Value
Answer Too Soon Timer 3000
Answer Too Late Timer 20000
Delay Before Ringing Timer 0
Step 6 Check the Enable Mobile Connect check box.
Step 7 If you are setting up the Dial via Office feature, in the Mobility Profile drop-down list,
select one of the following options.
Leave blank Choose this option if you want users to use the Enterprise Feature
Access
Number (EFAN).
Mobility Profile Choose the Mobility Profile that you just created if you want
users to use a Mobility Profile instead of an EFAN.
Step 8 Set up the schedule for routing calls to the mobile number.
Step 9 Select Save.
(Cont.)
You have to enable Mobility in the User Configuration page before
configuring your Dual mode phone for mobility
Select a Rerouting Calling Search Space that includes the partition that
applies to the mobile phone number.
www.flane.com.au
Enable Mobile Connect

Use the following procedure to enable mobile connect for an end user.
Procedure
Step 2 Search for and delete any existing Remote Destination or Mobility Identity that is already
set up with the mobile phone number.
Step 3 Navigate to the End User page for the user.
a) In the Mobility Information section, check the Enable Mobility check box.
b) On Unified CM Release 9.0 and earlier, specify the Primary User Device.
c) Select Save.
a) Enter the following information:
Softkey Template
Choose a softkey template that includes the Mobility button.
Mobility User ID Select the user.
Owner User ID Select the user. The value must match the Mobility User ID.
Rerouting Calling Search Space. Choose a Rerouting Calling Search Space that includes
both of the following:
The partition of the desk phone extension of the user. This requirement is used by
the system to provide the Dial via Office feature, not for routing calls.
A route to the mobile phone number. The route to the mobile phone number (that
is, the Gateway/Trunk partition) must have a higher preference than the partitions
of the enterprise extension that is associated with the device.
Note that Cisco Jabber allows users to specify a callback number for Dial via Office-Reverse
calls that is different from the mobile phone number of the device, and the Rerouting Calling
Search Space controls which callback numbers are reachable.
If the user sets up the DVO Callback Number with an alternate number, ensure that you set up the
trunk Calling Search Space (CSS) to route to destination of the alternate phone number.
b) Select Save.
Transfer Active VoIP Call to the Mobile
Network
Useful when a user on a call leaves the Wi-Fi network (for example, leaving the
building to walk out to the car), or if there are voice quality issues over the Wi-Fi
network.
Hand Off Methods:
Handoff DN :
The iPhone calls Unified CM using the See Set Up Handoff DN mobile
network.
This method requires a Direct Inward Dial (DID) number.
If it fails, the system automatically tries the Mobility Softkey and Call Park
methods, in order.
This method will not work for iPod Touch or iPad devices.
www.flane.com.au
Transfer Active VoIP Call to the Mobile Network

Users can transfer an active VoIP call from Cisco Jabber to their mobile phone number on the
mobile network.
This feature is useful when a user on a call leaves the Wi-Fi network (for example, leaving the
building to
walk out to the car), or if there are voice quality issues over the Wi-Fi network. This Cisco Jabber
feature is called Use Mobile Network.
There are two ways to implement this feature. You can also disable it.
Handoff DN
The iPhone calls Unified CM using the mobile network.
This method requires a Direct Inward Dial (DID) number.
The service provider must deliver the DID digits exactly as configured. Alternately, for Cisco IOS
gateways with H.323 or SIP communication to Unified CM, you can use Cisco IOS to manipulate
the inbound called-party number at the gateway, presenting the digits to Unified CM exactly as
configured on the handoff DN.
If you select this implementation method and it fails, the system automatically tries the Mobility
Softkey.
This method will not work for iPod Touch devices.
Network (Cont.)
Mobility Softkey:
Unified CM calls the phone number of the iPhone PSTN mobile service
provider.
If it fails, the system automatically tries the Call Park method.
Call Park:
Cisco Jabber attempts this method only if attempts to use other methods
fail.
In the Call Park method, the iPhone makes a mobile-network call to a Call
Park number to retrieve the call.
This method requires a DID number.
www.flane.com.au
Mobility Softkey
Unified CM calls the phone number of the
iPhone PSTN mobile service provider.
Call Park
Cisco Jabber attempts this method only if attempts to use other methods fail.
In the Call Park method, the iPhone makes a mobile-network call to a Call Park number to
retrieve the call.
This method requires a DID number.
Set up Call Park for the system. See the Call Park chapter in the Unified CM Features and
Services Guide at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html
.
Set the Call Park number in Call Routing > Call Park to be an E.164 (DID) number.
Cisco recommends changing the value in the Park Monitoring Forward No Retrieve Timer to
60 seconds if more immediate ring-back to the parker phone is required.
o Note: Cisco Jabber uses the "Park Monitoring Reversion Timer" in combination with
the " Park Monitoring Forward No Retrieve Timer." This timer is used even if no
forward target is configured. The "Call Park Reversion Timer" is not used for this
product .
The parked call is forwarded to a forwarding number, if one is set up. If no forwarding
number is set up, the call returns to the parker.
Network - Set Up Handoff DN
Call Routing > Mobility > Handoff Configuration
The service provider must deliver the DID digits exactly as configured.
You cannot use translation patterns or other similar manipulations within Unified
CM to match the inbound DID digits to the configured Handoff DN.
This partition should be present in the Remote

Destination inbound Calling Search Space (CSS), which
points to either the Inbound CSS of the Gateway or
Trunk, or the Remote Destination CSS.
Match Caller ID with Mobile Identity
www.flane.com.au
Procedure
Step 1 Sign in to Unified CM Administration portal.
Step 2 Select Call Routing > Mobility > Handoff Configuration.
Step 3 Enter the Handoff Number for the Direct Inward Dial (DID) number that the device uses
to hand off a VoIP call to the mobile network
The service provider must deliver the DID digits exactly as configured. Alternately, for Cisco IOS
gateways with H.323 or SIP communication to Unified CM, you can use Cisco IOS to manipulate
the inbound called-party number at the gateway, presenting the digits to Unified CM exactly as
configured on the handoff number.
Note
You cannot use translation patterns or other similar manipulations within Unified CM to match
the
inbound DID digits to the configured Handoff DN.
Step 4 Select the Route Partition for the handoff DID.
This partition should be present in the Remote Destination inbound Calling Search Space (CSS),
which points to either the Inbound CSS of the Gateway or Trunk, or the Remote Destination CSS.
This feature does not use the remaining options on this page.
Step 5 Select Save.
Match Caller ID with Mobility Identity
To ensure that only authorized phones can initiate outbound calls, calls must originate from a
phone that is set up in the system. To do this, the system attempts to match the caller ID of the
requesting phone number with an existing Mobility Identity. By default, when a device initiates
the Handoff feature, the caller ID that is passed from the gateway to Unified CM must exactly
match the Mobility Identity number that you entered for that device.
However, your system may be set up such that these numbers do not match exactly. For example,
Mobility
Identity numbers may include a country code while caller ID does not. If so, you must set up the
system to recognize a partial match.
Be sure to account for situations in which the same phone number may exist in different area
codes or in different countries. Also, be aware that service providers can identify calls with a
variable number of digits, which may affect partial matching. For example, local calls may be
identified using seven digits (such as 555 0123) while out-of-area calls may be identified using
ten digits (such as 408 555 0199).
Network - Set Up Handoff DN
In the Cisco Dual Mode for iPhone Device page.
Do not assign this method for iPad and iPod Touch devices. Use the Mobility
Softkey method instead.
www.flane.com.au
Procedure
Step 1 In the Unified CM, select Use Handoff DN Feature for the Transfer to Mobile Network
option on the Cisco Dual Mode for iPhone Device page.
Do not assign this method for iPod Touch devices. Use the Mobility Softkey method instead.
Step 2 On the iOS device, tap Settings > Phone > Show My Caller ID to verify that Caller ID is
on.
Step 3 Test this feature.
Network – Mobility Softkey
In Device > Device Settings > Softkey Template
Assign the Softkey template to the Dual mode iPhone Template
www.flane.com.au
Enable Active Call Transfer from VoIP to Mobile Network

Procedure
Step 1 For system-level settings, check that the Mobility softkey appears when the phone is in the
connected and on-hook call states.
a) In Device > Device Settings > Softkey Template, select the softkey template that you
selected when you configured the device for Mobile Connect.
b) In the Related Links list box at the upper right, choose Configure Softkey Layout
and select Go.
c) Select Connected state and verify that the Mobility key is in the list of selected
softkeys, and then do the
same for the On Hook state.
Step 2 For the per-user and per-device settings in Unified CM, ensure that you set up a device
Mobility Identity and Mobile Connect for the mobile device.
After the transfer feature is working, users can enable and disable Mobile Connect at their
convenience without affecting the feature.
If the device is an iPod Touch, you can configure a Mobility Identity using an alternate phone
number such
as the mobile phone of the user.
a) Select the Owner User ID on the Cisco Dual Mode for iPhone device page.
b) In the Product Specific Configuration Layout section, for the Transfer to Mobile
Network option, choose Use Mobility Softkey.
Step 3 Navigate to the device page, Device > Phone, and search for the TCT device.
Step 4 In the User Locale field, choose English, United States.
Network – Mobility Softkey (Cont.)
For the per-user and per-device settings in Unified CM, ensure that you set up a
device Mobile Identity and Mobile Connect for the mobile device.
In the Product Specific Configuration Layout section, for the Transfer to Mobile
Network option, choose Use Mobility Softkey.
www.flane.com.au
Set Up Dial Via Office
Allows users to initiate Cisco Jabber outgoing calls with their work number using the voice
plan for the device.
There are two types of Dial via Office calls:
Dial via Office-Reverse (DVO-R)
Dial via Office-Forward (DVO-F)
DVO-R works as follows:
1. User initiates a Dial via Office-Reverse call.
2. The client notifies Unified CM to call the mobile phone number.
3. Unified CM calls and connects to the mobile phone number.
4. Unified CM calls and connects to the number that the user dialed.
5. Unified CM connects the two segments.
6. The user and the called party continue as with an ordinary call.
www.flane.com.au
The Dial via Office (DVO) feature allows users to initiate Cisco Jabber outgoing calls with their
work number using the voice plan for the device.
There are two types of Dial via Office calls: Dial via Office-Reverse (DVO-R) and Dial via
Office-Forward (DVO-F). Cisco Jabber supports Dial via Office-Reverse (DVO-R) calls. DVO-R
works as follows:
1. User initiates a Dial via Office-Reverse call.
2. The client notifies Unified CM to call the mobile phone number.
3. Unified CM calls and connects to the mobile phone number.
4. Unified CM calls and connects to the number that the user dialed.
5. Unified CM connects the two segments.
6. The user and the called party continue as with an ordinary call.
Set Up Dial Via Office (Cont.)
The DVO-R feature requires:
Cisco Jabber for iPhone client, Release 9.1(1) and later.
Unified CM 9.1(1a), which is targeted to release at the end of February, 2013.
The following table describes the calling methods used for incoming and outgoing calls. The
calling method (Internet, Mobile Connect, DVO-R, or native cellular call) varies depending
on the selected Jabber Calling Options and the network connection.
www.flane.com.au
The DVO-R feature requires:

Cisco Jabber for iPhone client, Release 9.1(1) and later.
Unified CM 9.1(1a), which is targeted to release at the end of February, 2013.
Incoming calls use either Mobile Connect or the Internet, depending on which Jabber Calling
Options the user sets on the client. Dial via Office does not require Mobile Connect to work.
However, we recommend that you enable Mobile Connect to allow the native mobile number to
ring when someone calls the work number. From the Unified CM user pages, users can enable
and disable Mobile Connect, and adjust Mobile Connect behavior using settings (for example, the
time of day routing and Delay Before Ringing Timer settings).
Set Up Dial Via Office (Cont.)
To set up Dial via Office-Reverse (DVO-R), you must do the following:
1. Set up the Unified CM to support DVO-R.
2. Enable DVO on each Cisco Dual Mode for iPhone device.
Voicemail avoidance is a feature that prevents calls from being answered by the
mobile service provider voice mail.
The Dial via Office feature is not supported with the Extension Mobility feature.
www.flane.com.au
To set up Dial via Office-Reverse (DVO-R), you must do the following:

1. Set up the Unified CM to support DVO-R.
2. Enable DVO on each Cisco Dual Mode for iPhone device.
Set Up Unified CM to Support DVO-R
To set up Unified CM to support DVO-R, perform the following procedures:
1. Complete one or both of the following procedures.
Set Up Enterprise Feature Access Number
Set Up Mobility Profile
2. Verify Device COP File Version
3. If necessary, create application dial rules to allow the system to route calls to the Mobile
Identity phone number to the outbound gateway. Ensure that the format of the Mobile
Identity phone number matches the application dial rules.
Set Up Enterprise Feature Access Number
Use this procedure to set up an Enterprise Feature Access Number for all Cisco Jabber calls that
are made using Dial via Office-Reverse.
The Enterprise Feature Access Number is the number that Cisco Unified Communications
Manager uses to call the mobile phone and the dialed number unless a different number is set up
in Mobility Profile for this purpose.
Before You Begin
Reserve a Direct Inward Dial (DID) number to use as the Enterprise Feature Access Number
(EFAN).
This procedure is optional if you already set up a mobility profile.
Determine the required format for this number. The exact value you choose depends on the
phone number that the gateway passes (for example, 7 digits or 10 digits). The Enterprise
Feature Access Number must be a routable number.
Procedure
Step 2 Choose Call Routing > Mobility > Enterprise Feature Access Number Configuration.
Step 4 In the Number field, enter the Enterprise Feature Access number.
Enter a DID number that is unique in the system.
To support dialing internationally, you can prepend this number with \+.
Step 5 From the Route Partition drop-down list, choose the partition of the DID that is required
for enterprise feature access.
This partition is set under System > Service Parameters, in the Clusterwide Parameters
(System - Mobility) section, in the Inbound Calling Search Space for Remote Destination
setting. This setting points either to the Inbound Calling Search Space of the Gateway or Trunk,
or to the Calling Search Space assigned on the Phone Configuration screen for the device.
If the user sets up the DVO Callback Number with an alternate number, ensure that you set up the
trunk Calling Search Space (CSS) to route to destination of the alternate phone number.
Step 6 In the Description field, enter a description of the Mobility Enterprise Feature Access
number.
Step 7 (Optional) Check the Default Enterprise Feature Access Number check box if you want
to make this Enterprise Feature Access number the default for this system.
Step 8 Select Save.
Set Up Mobility Profile

Use this procedure to set up a mobility profile for Cisco Jabber devices. This procedure is
optional if you already set up an Enterprise Feature Access Number.
Mobility profiles allow you to set up the Dial via Office-Reverse settings for a mobile client.
After you set up a mobility profile, you can assign it to a user or to a group of users, such as the
users in a region or location.
Procedure
Step 2 Choose Call Routing > Mobility > Mobility Profile.
Step 3 In the Mobility Profile Information section, in the Name field, enter a descriptive name
for the mobility profile.
Step 4 In the Dial via Office-Reverse Callback section, in the Callback Caller ID field, enter
the caller ID for the callback call that the client receives from Unified CM.
Step 5 Click Save.
Verify Device COP File Version
Use the following procedure to verify that you are using the correct device COP file for this
release of Cisco Jabber.
Procedure
Step 2 Choose Device > Phone.
Step 3 Click Add New.
Step 4 From the Phone Type drop-down list, choose Cisco Dual Mode for iPhone.
Step 5 Click Next.
Step 6 Scroll down to the Product Specific Configuration Layout section, and verify that you can
see the Dial via Office drop-down list.
If you can see the Dial via Office drop-down list, the COP file is already installed on your system.
Set Up Dial Via Office for Each Device
Use the following procedures to set up Dial via Office - Reverse for each Cisco Jabber device.
1. Add a Mobility Identity for each user.
2. Enable Dial via Office on each device.
3. If you enabled Mobile Connect, verify that Mobile Connect works. If you dial the desk
phone extension, the phone number that is specified in the associated Mobile Identity
should ring.
Add Mobility Identity

Use this procedure to add a Mobility Identity to specify the GSM number of the mobile device as
the destination number. This destination number is used by features such as Dial via Office or
Mobile Connect.
You can specify only one number when you add a mobility identity. If you want to specify an
alternate number such as a second GSM number for a mobile device, you can set up a remote
destination. The Mobility Identity configuration characteristics are identical to those of the
Remote Destination configuration.
Procedure
Step 3 In the Associated Mobility Identity section, select Add a New Mobility Identity.
Step 4 Enter the mobile phone number as the Destination Number.
This number must be routable to an outbound gateway. Generally, the number is the full E.164
number.
If you enable the Dial via Office - Reverse feature for a user, you must enter a destination number
for the user's mobility identity.
If you enable Dial via Office - Reverse and leave the destination number empty in the mobility
identity:
Note
The phone service cannot connect if the user selects the Automatically select Jabber calling
option while using a 3G network and VPN.
The phone service cannot connect if the user selects the Always use DVO Jabber calling
option on any type of network.
The logs do not indicate why the phone service cannot connect.
When using Dial via Office - Reverse, the system does not automatically push updated
destination numbers for the user's mobility identity to the client after you already entered a
destination number.
To work around this issue, ask the user to do one of the following:
In the Cisco Jabber for iPhone Settings, manually update the phone number in the DVO
Callback Number field.
In the Cisco Jabber for iPhone Settings, delete the current number in the DVO Callback
Number field, and then exit and restart Cisco Jabber for iPhone
Step 5 Enter the initial values for call timers.
These values ensure that calls are not routed to the mobile service provider voicemail before they
ring in the client on the mobile device.
Answer Too Soon Timer 3000
Answer Too Late Timer 20000
Delay Before Ringing Timer 0
Step 6 Check the Enable Mobile Connect check box.
Step 7 If you are setting up the Dial via Office feature, in the Mobility Profile drop-down list,
select one of the following options.
Leave blank
Choose this option if you want users to use the Enterprise Feature Access
Number (EFAN).
Mobility Profile
Choose the Mobility Profile that you just created if you want users to use a
Mobility Profile instead of an EFAN.
Step 8 Set up the schedule for routing calls to the mobile number.
Step 9 Select Save.
Enable Dial Via Office on Each Device

Use this procedure to enable Dial via Office on each device.
Procedure
Step 2 Navigate to the device page for the user.
Step 3 In the Device Information section, check the Enable Cisco Unified Mobile
Communicator check box.
Step 4 On the device page for the user, in the Product Specific Configuration Layout section, set
the Dial via Office drop-down list to Enabled.
DVO-R is supported only on Unified CM Release 9.1 and later. Cisco plans to release a service
update (SU) in the near future to support Cisco Jabber with DVO-R on Unified CM 8.6. If you
enable this setting on an unsupported release of Unified CM, the end user sees the DVO calling
options and can attempt to make DVO-R calls, but the calls cannot connect.
Step 5 Select Save.
Step 6 Select Apply Config.
Set Up Voicemail Avoidance

Voicemail avoidance is a feature that prevents calls from being answered by the mobile service
provider voice mail. This feature is useful if a user receives a Mobile Connect call from the
enterprise on the mobile device.
It is also useful when an incoming DVO-R call is placed to the mobile device.
You can set up Voicemail Avoidance in one of two ways:
Timer-controlled: (Default) With this method, you set timers on the Unified CM to
determine if the call is answered by the mobile user or mobile service provider voicemail.
User-controlled: With this method, you set the Unified CM to require that a user presses
any key on the keypad of the device to generate a DTMF tone before the call can proceed.
If you deploy DVO-R, Cisco recommends that you also set user-controlled Voicemail Avoidance.
If you set user-controlled Voicemail Avoidance, this feature applies to both DVO-R and Mobile
Connect calls.
Set Up Voice Dialing
Voice Dialing allows users to dial a number by speaking a name in the corporate
directory.
If Voice Dialing is available on your network, Cisco Jabber users can always dial
the Voice Dialing pilot number to access that feature as they would from any
phone.
Voice dialing must be set up and working on your network and configured in
Cisco Unity Connection.
www.flane.com.au
Voice Dialing allows users to dial a number by speaking a name in the corporate directory. If
Voice Dialing is available on your network, Cisco Jabber users can always dial the Voice Dialing
pilot number to access that feature as they do from any phone.
You can simplify voice dialing by enabling either of the following settings:
Enable Voice Dialing Motion
Add Voice Dialing to Favorites
Set Up Visual Voicemail on Unified CM
Verify that IMAP is enabled:
Consult your voicemail administrator if you have questions about

the values for the settings in this section.
www.flane.com.au
Specify Directory Search Settings
In the Product Specific Configuration Layout section, enter the iPhone country
code.
This information helps determine Caller ID.
LDAP field mappings identify the attributes in your directory that hold the
information to be searched and displayed for directory searches.
www.flane.com.au
Before You Begin

Make sure the telephoneNumber attribute in Active Directory (or its equivalent, if you
use a different attribute) is indexed.
Identify attributes in your corporate directory schema that are different from, or additional
to, the defaults in the following table. You must map changed attributes later in this
procedure.
In Active Directory:
Phone numbers must be unformatted.
Global Catalog must be enabled.
You must identify all the Active Directory attributes that Jabber must access, and then
replicate these attributes to all Global Catalog servers. Otherwise, Jabber cannot access
the attribute information on the default port.
Cisco Jabber for iPhone determines which type of directory server you use by checking whether
the defaultNamingContext is defined. If the defaultNamingContext is defined, the app determines
that you are using Active Directory. If this value is not defined, the app determines that the
system is using another LDAP server.
Set Up SRST Failover
1. Set up the required SRST information on the Unified CM.
2. Set up the failover device:

SRST failover to a Unified CME.
On Unified CME, you must configure the following parameters:

registrar server expires max 1200 min 660
sip-ua
timers connection aging 12
www.flane.com.au
Survivable Remote Site Telephony (SRST) allows you to transfer services from the Unified CM
to another Unified CM, a Unified CM Express (Unified CME), or a router running SRST.
Set Up Extension Mobility to Allow Users to
Sign In and Out
The Sign In feature using Extension Mobility is disabled by default in Cisco

Jabber.
To enable it, select Enabled in the “Sign In Feature” drop-down list.
When using Extension Mobility, choose Disabled for Allow End User
Configuration Editing.
www.flane.com.au
Set up and activate the Cisco Extension Mobility Service to allow users to sign in and out of
Cisco Jabber on devices.
Before You Begin
The Sign In feature using Extension Mobility is disabled by default in Cisco Jabber. To
enable it, select Enabled in the “Sign In Feature” drop-down list. For more information
about setting up Extension Mobility, see
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_6_1/ccmfeat/fsem.htm
l.
Note
External number masks are not displayed while Extension Mobility is enabled if the
mask is not also configured for the Extension Mobility device profile.
Extension Mobility is functional only if a single profile is listed in the Controlled
Profiles field.
If you set up Extension Mobility as an Enterprise Subscription service, all Cisco Jabber
users are required to sign in and out of Cisco Jabber while Extension Mobility is enabled.
When using Extension Mobility, choose Disabled for Allow End User Configuration
Editing.
After Extension Mobility is set up, Cisco Jabber is functional only if the user is signed in.
The Cisco AnyConnect Secure Mobility Client provides a highly secure

connectivity experience across a broad set of PCs, tablets, and smartphone-
based mobile devices, such as the Apple iPhone and Android.
To support the Cisco AnyConnect Secure Mobility Client, you must set up your
system using the following procedures.
1. Install and set up the Cisco Adaptive Security Appliance (ASA).
2. Set up the ASA to support Cisco AnyConnect.
a. Provision Application Profiles
b. Automate VPN Connection
c. Set Up Certificate-Based Authentication
d. Set ASA Session Parameters
e. Set Up Tunnel Policies
3. Set up the Unified CM for AnyConnect.

www.flane.com.au
Cisco AnyConnect Secure Mobility Client is a VPN application that allows Cisco Jabber to
securely connect to your corporate network from a remote location using Wi-Fi or mobile data
networks.
To support the Cisco AnyConnect Secure Mobility Client, you must set up your system using the
following procedures.
1. Install and set up the Cisco Adaptive Security Appliance (ASA).
2. Set up the ASA to support Cisco AnyConnect.
Perform the following procedures in order:
a. Provision Application Profiles
b. Automate VPN Connection
c. Set Up Certificate-Based Authentication
d. Set ASA Session Parameters
e. Set Up Tunnel Policies,
3. Set up the Unified CM for AnyConnect
Provision Application Profiles
The configuration profile for the Cisco AnyConnect client includes VPN policy
information such as the company ASA VPN gateways, the connection protocol
(IPSec or SSL), and on-demand policies.
Provision application profiles methods:

Provision VPN Profiles on ASA (Recommended):
VPN profile is automatically downloaded to the Cisco AnyConnect client after the
client establishes the VPN connection for the first time.
On the ASDM, choose Configuration > Remote Access VPN > Network (Client)
Access > AnyConnect Client Profile
www.flane.com.au
Provision Application Profiles

After users download the Cisco AnyConnect client to their device, the ASA must provision a
configuration profile to the application.
The configuration profile for the Cisco AnyConnect client includes VPN policy information such
as the company ASA VPN gateways, the connection protocol (IPSec or SSL), and on-demand
policies.
You can provision application profiles for Cisco Jabber for iPhone in one of the following ways:
Provision VPN Profiles on ASA
Provision iOS Devices Using Apple Configuration Profile and iPCU
Provision iOS Devices Using Apple Configuration Profile and MDM
Provision VPN Profiles on ASA
Cisco recommends that you use the profile editor on the ASA Device Manager (ASDM) to define
the VPN profile for the Cisco AnyConnect client.
When you use this method, the VPN profile is automatically downloaded to the Cisco
AnyConnect client after the client establishes the VPN connection for the first time. You can use
this method for all devices and OS types, and you can manage the VPN profile centrally on the
ASA.
Provision Application Profiles (Cont.)
Apple configuration profiles are XML files that contain information such as device
security policies, VPN configuration information, and Wi-Fi, mail, and calendar
settings.
www.flane.com.au

Use the following procedure to provision iOS devices using an Apple configuration profile that
you create with the iPhone Configuration Utility (iPCU). Apple configuration profiles are XML
files that contain information such as device security policies, VPN configuration information,
and Wi-Fi, mail, and calendar settings.
Use the following procedure to provision iOS devices using an Apple configuration profile that
you create with third-party Mobile Device Management (MDM) software. Apple configuration
profiles are XML files that contain information such as device security policies, VPN
configuration information, and Wi-Fi, mail,and calendar settings.
Automate VPN Connection
Set up the system to allow Cisco AnyConnect Secure Mobility Client to
automatically establish a VPN connection in the background.
Set Up Connect On-Demand VPN
When the user is inside the corporate Wi-Fi network, Cisco Jabber can reach
the Cisco UC infrastructure directly.
When the user leaves the corporate Wi-Fi network, Cisco AnyConnect
automatically detects if it is connected to a domain that you specify in the
AnyConnect client profile.
If so, the application initiates the VPN to ensure connectivity to the UC

infrastructure.
All applications on the device including Cisco Jabber can take advantage of
this feature.
www.flane.com.au
Automate VPN Connection

When users open Cisco Jabber from outside the corporate Wi-Fi network, Cisco Jabber needs a
VPN connection to access the Cisco UC application servers. You can set up the system to allow
Cisco AnyConnect Secure Mobility Client to automatically establish a VPN connection in the
background, which helps ensure a seamless user experience.
Set Up Connect On-Demand VPN
The Apple iOS Connect On Demand feature enhances the user experience by automating the
VPN connection based on the user's domain.
When the user is inside the corporate Wi-Fi network, Cisco Jabber can reach the Cisco UC
infrastructure directly. When the user leaves the corporate Wi-Fi network, Cisco AnyConnect
automatically detects if it is connected to a domain that you specify in the AnyConnect client
profile. If so, the application initiates the VPN to ensure connectivity to the UC infrastructure. All
applications on the device including Cisco Jabber can take advantage of this feature.
Note Connect On Demand supports only certificate-authenticated connections.
Automate VPN Connection (Cont.)
The following options are available with this feature:
Always Connect
Connect If Needed
Never Connect
When Cisco Jabber opens, it initiates a DNS query to

the URL (for example, ccm-sjc-111.cisco.com).
If this URL matches the On-Demand domain list entry

that you defined in this procedure (for example,
cisco.com),
Cisco Jabber indirectly initiates the AnyConnect VPN

connection.
www.flane.com.au
The following options are available with this feature:

Always Connect: Apple iOS always attempts to initiate a VPN connection for domains in
this list.
Connect If Needed: Apple iOS attempts to initiate a VPN connection to the domains in the
list only if it cannot resolve the address using DNS.
Never Connect: Apple iOS never attempts to initiate a VPN connection to domains in this
list.
Automate VPN Connection (Cont.)
1. Use the ASDM profile editor, iPCU, or MDM software to open the AnyConnect
client profile.
2. In the AnyConnect client profile, under the Connect if Needed section, enter your
list of on-demand domains.
Cisco recommends using Cisco AnyConnect Secure Mobility Client for Apple iOS
for iPhones running iOS 5.1.1. Requirements for the Cisco AnyConnect VPN
solution are as follows:
Cisco Adaptive Security Appliance Release 8.4 or later
Cisco AnyConnect Secure Mobility Client Release 2.5 or later
In Unified CM, set up the On-Demand VPN URL field in the Cisco Jabber device
settings.
www.flane.com.au
Set Up Certificate-Based Authentication
Cisco AnyConnect client supports many authentication methods including
Microsoft Active Directory/LDAP password, RADIUS-based one-time tokens, and
certificates.
Client certificate authentication provides the most seamless experience.
ASA supports certificates issued by various standard Certificate Authority

(CA) servers such as Cisco IOS
CA, Microsoft Windows 2003, Windows 2008 R2, Entrust, VeriSign, and RSA
Keon.
www.flane.com.au

The Cisco AnyConnect client supports many authentication methods including Microsoft Active
Directory/LDAP password, RADIUS-based one-time tokens, and certificates. Of these methods,
client certificate authentication provides the most seamless experience.
Set Up ASA for Certificate-Based Authentication
ASA supports certificates issued by various standard Certificate Authority (CA) servers such as
Cisco IOS CA, Microsoft Windows 2003, Windows 2008 R2, Entrust, VeriSign, and RSA Keon.
(Cont.)
Distribute Client Certificates
You can issue certificates to Cisco Jabber for iPhone devices using one of
the following methods:
SCEP
Mobileconfig file
www.flane.com.au
Distribute Client Certificates

You can issue certificates to Cisco Jabber for iPhone devices using one of the following methods:
SCEP
Mobileconfig file
Distribute Client Certificate Using SCEP
1. The first time a remote user opens Cisco AnyConnect, the application
authenticates the user with either Active Directory credentials or a one-time
token password.
2. After the client establishes the VPN, the ASA provides a client profile that
includes the SCEP request.
3. The Cisco AnyConnect client sends a certificate request and the Certificate
Authority (CA) automatically accepts or denies the request.
4. If the CA accepts the request:

a. The certificate is installed in the native certificate store on the device.
b. Cisco AnyConnect uses the certificate for authentication, and no longer prompts the
user for a password when establishing subsequent VPN connections.
www.flane.com.au
Distribute Client Certificate Using SCEP

ASA supports Simple Certificate Enrollment Protocol (SCEP) to simplify certificate distribution.
The ASA can use SCEP to securely issue and renew a certificate that is used for client
authentication. The following is a general overview of this process.
1. The first time a remote user opens Cisco AnyConnect, the application authenticates the
user with either Active Directory credentials or a one-time token password.
2. After the client establishes the VPN, the ASA provides a client profile that includes the
SCEP request.
3. The Cisco AnyConnect client sends a certificate request and the Certificate Authority
(CA) automatically accepts or denies the request.
4. If the CA accepts the request:
a. The certificate is installed in the native certificate store on the device.
b. Cisco AnyConnect uses the certificate for authentication, and no longer prompts the
user for a password when establishing subsequent VPN connections.
Distribute Client Certificate Using Mobileconfig File
1. Use the iPCU software to create a mobileconfig file and include the certificate
(.pfx) file.
2. Forward the mobileconfig file to the user.

When the user opens the file, the file installs the certificates to the device.
3. Use the Cisco ISE native supplicant provisioning process to distribute user
certificates.
4. Use the Enterprise MDM software to provision and publish certificates to

registered devices.
www.flane.com.au
Distribute Client Certificate Using Mobileconfig File

Use this procedure to create an iPhone mobile configuration file that includes a certificate. You
can use this file to distribute the certificate to users.
Set Up Tunnel Policies
Full-Tunnel Policy
This is the default tunnel policy. Use this policy if you want the most secure option for
Cisco Jabber and Cisco AnyConnect deployments.
All the traffic from all the applications on the device is sent over the VPN tunnel to the
ASA gateway.
Optionally, you can enable the Local LAN Access feature to enable local printing and
local network drive mapping.
www.flane.com.au
Set Up Tunnel Policies

Use the following procedure to set up a tunnel policy that specifies how you want to direct traffic
in the VPN tunnel.
To set up tunnel policies, you must first determine which type of tunnel policy you want to use.
Tunnel policies include the following:
Full-Tunnel Policy
This is the default tunnel policy. Use this policy if you want the most secure option for Cisco
Jabber and Cisco AnyConnect deployments. In case of Full-Tunnel, all the traffic from all the
applications on the device is sent over the VPN tunnel to the ASA gateway. Optionally, you can
enable the Local LAN Access feature to enable local printing and local network drive mapping.
Split-Tunnel Policy
Use this policy if you want to direct only Cisco Jabber-specific traffic from your phone to the
corporate network. This policy directs traffic based on destination subnets. You can specify which
traffic goes over VPN (encrypted) and which traffic goes in the clear (unencrypted).
An associated feature, Split-DNS, defines which DNS traffic to resolve over the VPN tunnel and
which DNS traffic to handle with the endpoint DNS resolver.
Set Up Tunnel Policies (Cont.)
Split-Tunnel Policy
Use this policy if you want to direct only Cisco Jabber-specific traffic from your phone to
the corporate network.
This policy directs traffic based on destination subnets.
You must include the IP subnets of the Cisco Unified CM Cluster, Directory Server, and
TFTP Server.
Cisco Jabber needs peer-to-peer media connections with any IP phone or computer
phone on the corporate Wi-Fi network. Therefore, Cisco recommends that you include
the corporate network IP address range in the Split-Include policy.
Split-Include Policy with Network ACL

Use this policy if you want to:
• Limit the traffic that is sent over the VPN tunnel due to bandwidth concerns.
• Restrict the VPN session to the Cisco Jabber application.

www.flane.com.au
Limit the traffic that is sent over the VPN tunnel due to bandwidth concerns.
Restrict the VPN session to the Cisco Jabber application.
www.flane.com.au

Use this policy if you want to:
Limit the traffic that is sent over the VPN tunnel due to bandwidth concerns.
Restrict the VPN session to the Cisco Jabber application.
You can use the Split-Include policy on the ASA to specify which traffic goes inside the VPN
tunnel based on the destination IP address of the traffic.
You must include the IP subnets of the Cisco Unified CM Cluster, Directory Server, and TFTP
Server. Cisco Jabber needs peer-to-peer media connections with any IP phone or computer phone
on the corporate Wi-Fi network. Therefore, Cisco recommends that you include the corporate
network IP address range in the Split-Include policy. This configuration may not be appropriate
for all deployments (for example, if the IP space of your company is not contiguous because of
acquisitions and other events).
This policy directs all internal traffic into the tunnel, but can prevent cloud-based services such as
Facebook and YouTube from entering the tunnel.
Split-Exclude Policy
Prevent any known traffic from using the VPN tunnel. For example, an organization
concerned about bandwidth could add the destination subnets for NetFlix, Hulu,
YouTube, and others to their split-exclude list
www.flane.com.au
Cisco Jabber
Provisioning Cisco
Jabber for iPad
89 www.flane.com.au
Client Sign-In and Auto-Discovery
Users enter their email address (username@example.com), the client queries the
DNS SRV records corresponding to the domain portion of the supplied email
address (example.com in this instance).
It expects responses from the DNS server that allow it to complete the
configuration task and provide the user with service.
DNS records consist of a series of entries that match a server name to a single IP
address in a networked environment.
DNS SRV records differ in that they match a service with a server, or set of
servers, in a networked environment.
www.flane.com.au

The client queries the Domain Name Server (DNS) when it is launched for the first time. After
users enter their email address (username@example.com), the client queries the DNS SRV
records corresponding to the domain portion of the supplied email address (example.com in this
instance). It expects responses from the DNS server that allow it to complete the configuration
task and provide the user with service. The administrator creates a new DNS SRV record for each
type of service the enterprise has implemented. The client supports the following services:
Instant Messaging and Presence
Cisco Unified Communications Manager Instant Messaging and Presence (formerly
known as Cisco Unified Presence)
Cisco WebEx Messenger (formerly known as Cisco WebEx Connect)
Unified Communications
Cisco Telepresence Video Communication Server
Cisco Jabber Video for Telepresence
Cisco WebEx TelePresence
When both Instant Messaging and Presence and Unified Communications services are deployed
(such as Cisco WebEx Messenger and Cisco Unified Communications Manager), the client uses
the Unified Communications server as configured in the Instant Messaging and Presence service
(Cisco WebEx Messenger or Cisco Unified Presence), rather than any Unified Communication
server supplied using the DNS SRVrecord.
(Cont.)
The client queries the network for all possible services corresponding to the
domain portion of the user-supplied email address. It then attempts to connect
based on the services it discovers through the DNS SRV record results. If there is
more than one service found, the client connects to the service in this order:
1. Cisco WebEx Messenger
2. Cisco Unified Presence
3. Cisco Unified Communications Manager
4. Cisco TelePresence Video Communication Server
5. Cisco Jabber Video for Telepresence
6. Cisco WebEx TelePresence
www.flane.com.au
DNS SRV Record

A DNS SRV record provides information on the services available in a specific domain to a
client. The client then chooses a server and uses it to connect to the deployed service or server.
This section provides information on the form and format of DNS SRV records. See RFC 2782
for additional technical information about DNS SRV records.
The client queries the network for all possible services corresponding to the domain portion of the
user-supplied email address. It then attempts to connect based on the services it discovers through
the DNS SRV record results. If there is more than one service found, the client connects to the
service in this order:
1. Cisco WebEx Messenger
2. Cisco Unified Presence
3. Cisco Unified Communications Manager
4. Cisco TelePresence Video Communication Server
5. Cisco Jabber Video for Telepresence
6. Cisco WebEx TelePresence
Set Up DNS SRV Records
DNS records consist of a series of entries that match a server name to a single IP address in a
networked environment. DNS SRV records differ in that they match a service with a server, or set
of servers, in a networked environment. In doing this, DNS SRV allows a client to only have to
know what type of service it is looking for instead of the actual server. This aids deployment,
server management, and service failover because most networked environments have multiple,
load balanced servers attending to the needs of a particular service.
When multiple servers are configured for a single service, the client tries the next server if it is
unable to connect to the first entry. In the case of an authentication failure for a given service, the
client stops attempting to connect to that service and display an error message.
The following lists the DNS SRV record types for the client.
Cisco WebEx Messenger _xmpp-client._tcp
Cisco Unified Presence _cuplogin._tcp
Cisco Unified Communications Manager CCMCIP _cisco-phone-
http._tcp
Cisco TelePresence Video Communication Server _sip._tcp.internal
(Internal)
Cisco TelePresence Video Communication Server _sip._tcp.external
(External)
Cisco Jabber Video for TelePresence _ciscowtp._tcp
Cisco WebEx TelePresence _ciscowtp._tcp
Set Up Centralized TFTP Server
Set up a centralized TFTP server if there are multiple Cisco Unified Communications Manager
clusters in the same corporate domain. You must also add a DNS SRV record so this server can
be discovered. The following is an example of what such a record might look like. The items in
the record appear in the following order:
SRV Record
Priority
Weight
Port
A Record
cisco-phone-tftp._tcp.example.com 0 0 69 cftp.example.com
Cisco Unified Communications Manager TFTP _cisco-phone-tftp._tcp
New Phone Type for Tablet Devices in Unified
CM
New Phone Type: Cisco Jabber for Tablet
New Device Security Profile: Cisco Jabber for Tablet – Standard SIP Non-Secure
Profile
www.flane.com.au
Cisco Unified Presence (Pre-UC9.0)

TFTP Servers
CNF configuration file
Application Dial Rules
Application Profiles
Define application servers
Assigned to users
www.flane.com.au
Cisco Unified Presence (UC9.0 or Later)
Application Profiles will be no longer
configured on Unified Presence but be
migrated to Unified CM
‘Service Profile’ gets assigned to users
Each ‘UC Service’ to define a UC application
Node licensing for Presence and IM won’t

exist but the service will be licensed from
Unified CM
www.flane.com.au
WebEx Connect Org Admin
www.webex.com/go/connectadmin (Common URL for all customers)
Request the following when ordering:
“CUCI” UC integration
WebEx Meetings integration
Customer “Administrator” receives a Welcome

email with instructions to set password and login
Provision users
Set policies*/groups (most enabled by default)
Configure CUCI (OrgAdmin and UC Manager)
Set up Federation
Customize welcome email (optional)
*Not all policies that apply to the desktop clients

apply to mobile devices
www.flane.com.au
The Cisco WebEx Messenger Administration Tool allows you to specify settings for instant
messaging (IM), availability, and integration with Cisco Unified Communications Manager. To
learn how to use this tool, see the Cisco WebEx Messenger Administration Guide at
http://www.webex.com/webexconnect/orgadmin/help/ index.htm.
Cisco recommends that you perform the tasks in this order. This is a list of high-level tasks that
may not include every aspect of your setup.
If a user already has both Cisco WebEx Messenger and Cisco Unified Communications Manager
set up in the desktop application, the settings automatically take effect in Cisco Jabber for iPad.
Centralized Administration
User • Account creation and management
• Set up, features, services, basic security,

Configuration
integrations, federation
• Define and apply policies (features / services)

Policy Editor
for individuals, groups or organization wide
Group • Control features by groups
Report • Generate usage/user reports
www.flane.com.au
Procedure
Step 1 Specify organization information. Go to
http://www.webex.com/webexconnect/orgadmin/help/index.htm?toc.htm?17382.htm.
Step 2 Create and provision users. Go to
http://www.webex.com/webexconnect/orgadmin/help/index.htm?toc.htm?cs_user.htm .
Step 3 Set up IM and availability.Go to
Step 4 Set up telephony services.
Go to http://www.webex.com/webexconnect/orgadmin/help/index.htm?toc.htm?18648.htm.
Note
Cisco recommends deploying Cisco Unified Communications Manager with a Fully Qualifed
Domain Name (FQDN) when setting up telephony services. If you deploy Cisco Unified
Communications Manager with an IP address when setting up telephony services, extra
configuration is required to enable the Connect on Demand VPN feature. Refer to the appropriate
Cisco Unified Communications Manager documentation for information on using a FQDN.
Step 5 Set up voicemail. Go to
http://www.webex.com/webexconnect/orgadmin/help/index.htm?toc.htm?cs_visual_voicemail.ht
m.
Note
If voicemail parameters are configured in both the Cisco WebEx Messenger Administration Tool
and the Product Specific Configuration on Cisco Unified Communications Manager, Cisco Jabber
for iPad will use the configuration in Cisco Unified Communications Manager and ignore the
voicemail settings in Cisco WebEx Messenger Administration Tool.
Step 6 Set up meetings.Go to
Cisco VCS & TMS
Step 1:
Administrator creates new users import, or
sync from Active Directory
Step 2:
Configures policies and assign device
templates
Step 3:
Users receive automated email that
includes username and password
Users switch on new endpoints
Users enter user name and password and

are ready to make video calls
www.flane.com.au
TMS Setup for Provisioning

To deploy VCS on Cisco Jabber for iPad, provision the user devices with appropriate settings.
You add and manage desired settings in TMS. The data is then transferred to the VCS, from
which it is distributed to the devices through the Provisioning Server running on the VCS.
Perform these two required procedures to set up TMS for provisioning.
Defining Device Address Pattern
Device address patterns are templates that TMS Provisioning Extension (TMSPE) uses to create
addresses for provisioned devices. Assign device address patterns so that TMSPE can connect
users to their devices. To specify a device address pattern for Cisco Jabber for iPad, set the
attribute {device.model} to jabbertablet.
Optionally, add an alias conversion from jabbertablet to jabber to simplify naming.
VCS Setup
Review this topic if you use the registration Allow List or search rules. In order for the user
devices to work with the VCS, the devices must first register with the VCS. The suffix in the
registration URIs for Cisco Jabber for iPad users is .jabbertablet or .jabber. For example, a user's
URI may be in this format with the new suffixes: userName.jabbertablet@DomainName or
userName.jabber@DomainName. Because of the URI suffix additions, you may need to make
these changes:
Update the registration Allow List (VCS configuration > Registration > Allow List) to
allow the new URI suffixes.
Example: If you have deployed both VCS and VCSE (VCS Expressway) and used the
Allow List to control registration from external locations, add the new suffixes to the
Allow List.
Update or create search rules to include the new URI suffixes. In creating search rules,
specify a pattern string that resembles the format
.+\.(jabbertablet|jabber).*@%localdomains%.*.
Example: If you have multiple VCS clusters (zones) within your organization, you may have to
update the rules that control call routing between the VCS and VCSE zones.
Cisco VCS & TMS – Creating Users
www.flane.com.au
Cisco VCS & TMS – Creating Device Template
www.flane.com.au
Setting Up Provisioning Template and Assigning It to Users

Cisco Jabber for iPad requires a specific template—an XML file containing all the possible
settings supported by the application. After you download the template and upload it in TMS, you
can then set up the template and assign it to groups of users.
Where to find the latest
FCS version ?
Cisco Jabber is a free download
End users can download directly in Apple App store or Google

Play
www.flane.com.au

Installation Steps
www.flane.com.au
Jabber for iPad Client Deployment
After launching the Jabber for iPad application for the first time, you need to
choose to sign in by using the
Individual Accounts
Cisco WebEx Messenger or Cisco Jabber Video for TelePresence account

information is required.
Company-Provided Accounts.
www.flane.com.au
Jabber Client Deployment
Individual Account
Individual Account Instructions to Download Cisco Jabber for iPad

Use either WebEx Jabber Video for TelePresence Username and password
Messenger or Jabber Video
for TelePresence account WebEx Messenger
www.flane.com.au
Individual Accounts
If you select Individual Accounts, Cisco WebEx Messenger or Cisco Jabber Video for
TelePresence account information is required. We recommend that you use a WebEx Messenger
account for IM and presence, and Jabber Video for TelePresence for voice and video calling.
Company-Provided Account
www.flane.com.au
Similar to setting up Individual Accounts, we recommended that you set up an IM and Presence
account first before a Video and Voice Calling account, unless no IM and Presence account is
available. If you select a Cisco Unified Presence account, then Cisco UCM is your only valid
option for video and voice calling. On the other hand, if a Cisco WebEx Messenger account is
configured, then you can select one of three options, including Cisco UCM, Cisco VCS, and
Cisco Jabber Video for TelePresence, for video and voice calling. See Figure 9 for Company-
Provided Account Settings.
During a deployment, administrators should provide an instruction to end-users on what features
are available and how to configure Jabber for iPad.
Company-Provided Account (Cont.)
Company-Provided Instructions to Download Cisco Jabber for iPad
Account
Voice and video calling Cisco UCM Username
Password
(TFTP) server address
Cisco Unified
Communications Manager IP
phone server address
(optional)
Cisco VCS Username
Password
Internal server address
External server address
SIP domain address
Jabber Video for TelePresence Username and password
www.flane.com.au

Company-Provided Account (Cont.)
Company- Instructions to Download Cisco Jabber for

Provided Account iPad
IM WebEx Messenger WebEx Messenger
username and
password
Cisco Unified Username

Presence Password
Server address
www.flane.com.au
Cisco Jabber for iPad Installation Steps
Select Account to Select the deployment model

Create Basic Account
go to the next Cisco Instant Messaging – Video and
for Cisco Jabber menu for Voice Calling set up will follow if
deployment enabled
Video Service
models
Cisco Video and Voice Calling -choose
here to set up standalone models
www.flane.com.au

(Cont.)
www.flane.com.au
(Cont.)
Unified Communications Manager Video Communication Server
Standalone: Voice/Video Only Standalone: Voice/Video Only

Cisco Unified Communications Video Communication Server
Manager Username
Username Password
Password Server Addresses (Internal/External)
Server Addresses Domain
www.flane.com.au
Cisco Jabber for iPad AnyConnect VPN
Administrators should also consider the following configurations for a more

integrated user experience with Jabber for iPad and AnyConnect:
Enable Certificate Authentication, so end users do not need to enter VPN

credentials manually.
Properly configure split tunneling, to ensure only the traffic destined for Cisco
UCM goes into the encrypted tunnel.
www.flane.com.au
AnyConnect VPN
The Cisco Jabber for iPad application requires Cisco Unified Communications back-end services
either in the cloud or on-premises. If one or all back-end services are deployed on-premises, then
an established secure VPN connection is required for the Cisco Jabber for iPad clients that are
outside of corporate network to communicate with those back-end services behind a firewall over
public Wi-Fi or mobile wireless networks. We strongly recommend that you deploy Cisco
AnyConnect Secure Mobility Client alongside Cisco Jabber for iPad2.
Cisco AnyConnect client on iPad provides a full VPN tunnel for Cisco Jabber and other
applications that need secure access to the enterprise network from outside the corporate firewall.
AnyConnect is a VPN client that provides secure connect features, including:
VPN on-demand3, which is available for iOS and allows the AnyConnect tunnel to be
established whenever a particular destination is contacted (that is, Cisco UCM).
Split Include, which allows you to configure specific traffic to be sent through the
encrypted tunnel; for example, using Split Include, Cisco UCM voice traffic could be sent
through the encrypted tunnel, and Safari browser data would not.
AnyConnect also has a built-in diagnostics and reporting tool and statistics reporting to
help troubleshoot VPN problems.
The following services do not require AnyConnect VPN for remote access:
Cisco Jabber Video for TelePresence Service.
Cisco WebEx Messenger Service.
Cisco WebEx Meetings.
Cisco TelePresence Video Communication Server (TelePresence VCS Expressway is
required).
Summary
You can add Cisco Jabber for iPhone to Cisco UCM as Dual mode iPhone
Configuring Cisco Jabber for iPhone features:
Mobility Features
Voice Dialing
Visual Voicemail
AnyConnect
Cisco Jabber for iPad On-Premises Configuration:
Cisco UCM and Cisco Unified IM and Presence
Cisco VCS and TMS
Cisco Jabber for iPad Cloud Configuration
www.flane.com.au

Student Guide PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Student Guide PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Designing and

Fast Lane APAC

Cisco Collaboration Overview ....................................................................................................... 1-3

Cisco Jabber Portfolio...................................................................................................................1-11

Cisco Unified Client Services Framework Architecture...............................................................1-35

Cisco Jabber For Windows............................................................................................................ 2-1

Deploying Cisco Jabber for Windows............................................................................................ 2-3

Install and Configure Cisco Jabber for Windows ........................................................................ 2-35

Designing Cisco IM and Presence................................................................................................ 2-65

Integrating Cisco Unified CM and Cisco IM and Presence ......................................................... 2-97

Jabber for Everyone.................................................................................................................... 2-165

Cisco Unified IM and Presence Multi-Node deployments ........................................................ 2-179

Instant Messaging Compliance ,Logging and Chat Rooms........................................................2-197

Cisco Jabber For Mobile................................................................................................................ 3-1

Designing Cisco Jabber for Mobile Solution ................................................................................. 3-3

3 Designing and Implementing Cisco Jabber Table Of Contents

Introduction to Cisco Unified

5 Designing and Implementing Cisco Jabber Table Of Contents

Introduction to Cisco Unified

Mobile, dispersed workforces

The New Collaborative Workspace

Experience Cisco's Unified Communications capabilities that provide presence, instant

Unified Communications for Everyone

Social Media Meets Customer Care

100 million Apple iPhones sold to date

New Collaborative Workspace

Collaboration Architecture Differentiates Business Value

Transform business processes

The Cisco collaboration architecture offers you significant competitive

Collaboration is emerging as the next breakthrough source of effectiveness and

Collaboration Architecture Differentiates Business Value by aligning this

Transform business processes

Boost organizational efficiency

Accelerate your time to market

Provide an integrated user experience and extend the

Cisco Jabber for Everyone

Cisco Jabber for mobile devices

Cisco Jabber Video for TelePresence

Cisco Virtual Experience Clients

Cisco UC IntegrationTM for Microsoft Lync

Third-party XMPP clients.

Cisco Jabber for Everyone

Cisco Jabber for mobile devices

Cisco Jabber Video for TelePresence (Movi)

Cisco Virtual Experience Clients

Cisco UC IntegrationTM for Microsoft Lync

Third-party XMPP clients and applications

All-in-one UC Application Collaborate from Any Workspace

Presence & IM PC, Mac, tablet, smart phone

Voice, Video, voice messaging On-premises and Cloud

Desktop sharing, conferencing Integration with Microsoft Office

Best Experience Across PC, Tablet

Citrix XenDesktop 5.0 or 5.5

Standard based XMPP protocol

Chat history and logging

Encrypt instant messaging communications using up to 256-bit Advanced Encryption Standard

Industry standard based voice and video for greater

Initiate multiparty voice and web meetings.

Drop down list provide a list of hardware/software calling options.

WebEx Ad-hoc Desktop Share Video desktop Share (BFCP)

Extensible Tab /HTML Apps

Voice dialing Enterprise Telephony Features

Lower Mobility Costs