BRKUCC-2060 - Cisco Collaboration Enterprise Mobility Solutions (2013 London)

Session BRKUCC-2060
Cisco Collaboration Enterprise

Mobility Solutions
Matthew Jordy
Technical Marketing Engineer, Cisco
BRKUCC-2060
2013 Cisco and/or its affiliates. All rights reserved.
Cisco Public
BRKUCC-2060
Abstract
This session describes how Cisco's collaboration enterprise mobility solutions
provide fixed mobile convergence (FMC) and fixed mobile substitution (FMS)
features and functionality to enable mobile workers both inside and outside of the
enterprise. This session covers the following Cisco collaboration mobility solutions:
1. FMC with the Cisco Unified Communications Manager Cisco Unified Mobility feature set
2. FMS with Cisco mobile clients and solutions for smartphones and tablets including Cisco
Jabber
These solutions provide a comprehensive set of mobility features and functions for
enterprise mobile workers. Individually or in tandem these FMC and FMS solutions
not only provide enterprise connectivity and persistent reachability to mobile users
regardless of location, but they also provide productivity improvements both for the
mobile user as well as users inside the enterprise that the mobile user may
communicate with.
Further these solutions provide a good return on investment by allowing enterprises
to reduce the use of cellular minutes for business calls.
BRKUCC-2060
Cisco Public
Please consult the latest applicable product

documentation for specific feature,
software version, and hardware version
support requirements
BRKUCC-2060
Session Logistics
For
Your
Reference
= HOMEWORK
While the intermediate session will begin with a brief overview of these
solutions, to maximize the material learned, attendees should have some
familiarity with these enterprise Cisco mobility applications. Attendees should
also have a good understanding of IP telephony and familiarity with Cisco
Unified Communications Manager's features and functions.
Appendix slides (basic features and additional solution information).
Session time: 2 hours
Please ask questions as we go 3 types of questions:

Questions I'll answer
Questions I'll defer to later in the session
Questions I don't know the answer to, outside the scope of our session, or those that
consume too much time
Come see me after session to chat and/or leave your

name, email, and question(s) so I can get back to you.
BRKUCC-2060
Cisco Public
BRKUCC-2060
Complete the Online

Session Evaluation
BRKUCC-2060
Cisco Public
55
BRKUCC-2060
Agenda
Cisco Collaboration Mobility Solutions Overview

Fixed Mobile Convergence with Cisco Unified Mobility
Fixed Mobile Substitution with Cisco Mobile Client Solutions
Cisco Collaboration Mobility Solutions Summary
BRKUCC-2060
Cisco Public
Cisco Collaboration Mobility Solutions

Overview
DN: 51234
Campus/
Single Site
Cisco Unified Mobility

Hardware Moves
Extension Mobility
Fixed Mobile
Convergence
WLAN Roaming
Mobile Voice
Network
DN: 51234
Extension
Mobility
PSTN
WLAN
Roaming
IP/WAN
Bridging Enterprise
and Provider Mobility
Cisco Mobile Clients
Enterprise
Internet
Device Mobility
Mobile
Data
Fixed
Mobile
Network
Substitution
PSTN
Mobile Voice/
Data Network
WLAN
(802.11)
Remote
BRKUCC-2060
VPN IP Phone or Soft Client

w./ PC VPN
Cisco Virtual Office
Cisco Public

Fixed Mobile Convergence (FMC): Linking User's Enterprise and Mobile Lines
What is fixed mobile convergence?

PSTN
Mobile Voice
Network
(Carrier)
Mobile Line
Enterprise Line
Integrating or linking a user's enterprise line with their mobile line

BRKUCC-2060
Cisco Public

Fixed Mobile Substitution (FMS): Enabling User's Enterprise Line on Mobile Device
What is fixed mobile substitution?

Considerations:
Software/application
required on the mobile
device. What
device(s) do I need?
PSTN
Mobile Data
Network
(Carrier)
Mobile Voice
Network
(Carrier)
WLAN/Mobile Data?
Substitution: Do I
need an enterprise
device?
WLAN
(802.11)
Mobile Line
Enterprise Line
Moving or enabling the enterprise line on the user's mobile device

BRKUCC-2060
Cisco Public

Fixed Mobile Convergence
BRKUCC-2060
Cisco Public
10

Overview
PSTN
Gateway
WAN
Cisco
Unified Mobility
User
PSTN
Cisco Unified
Communications
Manager
Cisco
Unified Mobility
User
Cisco Unified Mobility provides

a mechanism for linking a
users enterprise desk phone
(or enterprise directory number)
to their mobile device(s).
BRKUCC-2060
Cisco Unified Mobility includes the following

benefits:
Single enterprise number for all calls whether handled by

enterprise desk phone or mobile phone
Enterprise dialing from mobile devices for toll reduction,

mobile phone number masking, access to non-DID enterprise
extensions.
Features delivered on any mobile phone regardless of mobile

platform or provider with no requirement for software or data
plan.
Cisco Public
11

Feature Overview
Feature
Enterprise
2-stage
dialing
Description
Mobile Connect (SNR)
Incoming calls to users enterprise number rings both desk

phone and configured Remote Destination(s)
Mobile Voice Access (MVA)
Provides the ability to make calls from mobile phone using

the enterprise IP telephony infrastructure
Enterprise Feature Access (EFA)
Provides identical functionality as Mobile Voice Access

without the IVR component
Desk Phone/Remote Destination

Pickup
Once incoming mobility call has been answered, call can

be moved between desk phone and Remote Destination(s)
Mid-Call Features
Provides the ability to invoke enterprise features Hold,

Resume, Transfer, Conference, Directed Call Park, and
Session Handoff from the Remote Destination/mobile
phone for active mobility calls
Single Enterprise Voicemail Box

(mobile voicemail avoidance)
Per Remote Destination timers ensure that when mobility

user is unavailable, unanswered incoming calls are
forwarded to enterprise voicemail box rather than mobile or
other voicemail box
Call Filtering
Per Remote Destination filtering allowing or blocking calls

based on caller ID access lists and/or time of day.
BRKUCC-2060
Cisco Public
Unified
Mobility
User
PSTN
Enterprise
Voicemail
2-Stage Dialing
Single Enterprise
Voicemail Box
Mobile
Connect/SNR
12
IP desk phone is not required. Remote

Destination Profile could instead share line
with Extension Mobility device profile or
simply a directory number on the system.

Configuration and Call Routing Concept
Remote Destination Profile
Unified Mobility User
IP Phone
Virtual Phone
Shared Line
Line Level Settings
DN: 408 555-1234
Partition
Calling Search Space
Remote Destination
Profile Level
Configuration
Device Level
Configuration
Call Routing and
Media Resource
Allocation for
Remote
Destinations
Device Pool
Rerouting CSS
User Hold Audio Source
Network Hold Audio Source
408 555-7890
Remote Destination #1
BRKUCC-2060
408 555-6789
XXX XXX-XXXX
Call Routing
and Media
Resource
Allocation for
IP Phones
Device Pool
Common Device Configuration
Media Resource Group List
Maximum of
10 per user
!
CAUTION
Alternate
Number
Remote Destination N
Cisco Public
13

Automatic Caller ID Matching
For all inbound calls to Cisco Unified CM the caller ID is automatically

compared against all configured remote destinations
Cisco Unified
CM Cluster
PSTN
Gateway
Inbound caller ID:

9195552345
MATCH
PSTN
Configured Remote
Destinations:
4085551234
4085555678
4085550987
.
.
.
9195552345
9195556789
9195558765
If a match is found, user is identified and call is anchored in the enterprise

Automatic caller ID matching also results in the replacement of the users
remote destination/mobile number with the users enterprise directory number
Matching requires explicit match remote destinations must be unique
BRKUCC-2060
Cisco Public
14

Enterprise Call Anchoring: Mobility Calls
All calls made or received on behalf of users Remote Destination are
automatically anchored through the enterprise gateway
1
Mid-Call
Features
Mobile Connect
Inbound Calls Answered
at Desk Phone or at
Remote Destination Phone
DTMF
PSTN
Gateway
In-Progress
Mobile Voice Access Call

Outbound Calls Generated
from
ACTIVE
Remote Destination Phone
PSTN
Enterprise Feature
Access
(Two-Stage Dialing)
Outbound Calls Generated
from Remote
Destination Phone
Inbound Calls from

Remote Destination
Incoming Calls from
Configured Remote
Destination Phones
BRKUCC-2060
Desk
Phone
Pickup
Cisco Unified
CM Cluster
Cisco Public
15

Mobile Voicemail Avoidance: Single Enterprise Voicemail Box
Unanswered calls to
user's enterprise
number should always
end up in the
enterprise voicemail
box
Mobile provider
voicemail
Cisco Unified
Communications
Manager
PSTN
STOP
Mobile Voice
Network
(Carrier)
Two ways to ensure

that mobile voicemail
is avoided:
PSTN
Gateway
1. Timer Control: Answer Too
Soon/Late timers (per Remote

Destination)
BRKUCC-2060
Mobile Device
Enterprise
voicemail
Cisco Unified
Mobility User
Cisco Public
Enterprise Line/Device
16

Mobile Voicemail Avoidance: Single Enterprise Voicemail Box (cont.)
1. On answer, prompt played to user requesting key
press.
Unanswered calls to
2. User presses key generating DTMF to Unified CM
user's enterprise
Mobile provider
and voice path is cut-through.
number should
always voicemail
3. If DTMF tone not received, Unified CM disconnects
end up in the outbound call leg and routes inbound call toPSTN
Mobile Voice
Network
box
(Carrier)
Cisco Unified
Communications
Manager
PSTN
Gateway
Enterprise
voicemail
Two ways to ensure

that mobile voicemail
is avoided:
1. Timer Control: Answer Too
Soon/Late timers (per Remote
Mobile Device
Destination)
Cisco Unified
Mobility User
2. User Control*: Prompted DTMF confirmation on answer

BRKUCC-2060
Requires Unified CM 9.0 or later
Cisco Public
17

Design Considerations
The following design-related information should be considered when deploying Cisco Unified
Mobility:
Capacity/Scalability
Maximum of 15,000 Remote Destinations per Unified CM cluster

Increased PSTN gateway utilization (most call flows typically involve multiple PSTN call legs)
High Availability
X X
Caller ID
Redundancy for Remote Destination/Remote Destination Profile via device pools/CM groups.
Cisco Unified Mobility features are all natively redundant within Unified CM
No Mobile Voice Access or Mobile Connect enable/disable without Publisher node
Gateway and PSTN access redundancy as usual
Caller ID
BRKUCC-2060
Inbound: Required for Enterprise Feature Access (2-stage dialing)

Outbound: Original caller ID for Mobile Connect calls may be restricted by provider. Use
Redirected Dialed Number Identification Service (RDNIS)/SIP Diversion Header if provider
supports
Cisco Public
18
18

Design Considerations (cont.)
The following design-related information should be considered when deploying Cisco Unified
Mobility (cont.):
PSTN resource utilization increases with Cisco Unified Mobility. To reduce PSTN
load, consider the following recommendations:
PSTN
BRKUCC-2060
Limit users to a single Remote Destination
Educate users to disable Mobile Connect when it's not going to be used
Utilize allow/block caller ID access lists and/or time of day filtering to limit calls forwarded to
PSTN
Cisco Public
19
19
Cisco Mobile Client Solutions

Fixed Mobile Substitution
BRKUCC-2060
Cisco Public
20

Agenda
Cisco Collaboration Mobility Solutions Overview

Fixed Mobile Convergence with Cisco Unified Mobility
Fixed Mobile Substitution with Cisco Mobile Client Solutions
Overview
Clients, Devices, and Configuration Overview
Cisco Unified Mobility Integration
Handoff
Dial via Office
Design and Deployment Considerations
Jabber IM and Other Mobile Clients
Bring Your Own Device (BYOD)
BlackBerry Mobile Voice System (MVS)
Cisco Collaboration Mobility Solutions Summary

BRKUCC-2060
Cisco Public
21

Overview
Collaboration Call Control
Cisco mobile clients enable

mobile users to:
Leverage the enterprise IP
telephony infrastructure for voice
and video services (VVoIP) via
WLAN or remote secure data
attachment
Leverage back-end
on-premises or
cloud-based
application servers
for additional collaboration
services messaging,
presence, directory lookups.
When enterprise
connectivity is not
available, devices with
cellular voice radios fall
back to the mobile
voice/PSTN
network
BRKUCC-2060
PSTN
Gateway
PSTN
Mobile Voice
Network
Cisco VCS
Cisco Unified CM
WLAN
(802.11)
SIP
Cisco Unity
Connection
hello
DMZ
Public/Private
WLAN
Data (802.11)
LDAP
Mobile
Network
(Data Channel)
XMPP, LDAP,
IMAP/VMREST
XMPP, LDAP,
IMAP/VMREST
Cisco IM
and Presence
On-Premises Enterprise and

Collaboration Applications
Internet
Cisco ASA
Cisco
Jabber
Video
Cisco
Voice (cellular)
WebEx
Data, signaling, and VVoIP

XMPP, SSL, HTTPS
2013 Cisco
and/or its affiliates.Applications
All rights reserved.
Cloud-based
Collaboration
Cisco Public
22

Feature Summary
Cisco mobile clients provide the following high-level features and functionality:
SIP client registration to Unified CM (or VCS in some cases) for voice/video services
Voice/video over Wi-Fi with 802.11 a/b/g/n connectivity or mobile data network
!
Connectivity over the Internet from public/private Wi-Fi hotspots or mobile data network may require remote secure
CAUTION
enterprise connectivity. Cisco cannot guarantee voice quality or troubleshoot connectivity issues when
devices are connected over the Internet
Dial via Office providing automated enterprise dialing for work calls using the mobile voice network for audio
and the IP network (802.11 or mobile data) for SIP signaling.*
Mobile access to enterprise calling features: abbreviated extension dialing, call hold/resume, call transfer,
conference calling, and call park
Manual handoff (WLAN to cellular): Ability to move out of the enterprise while on active call *
Access to enterprise directory for lookups via LDAP
XMPP-based enterprise IM/chat and presence/availability with Cisco Unified Presence (on-premises) or
Cisco WebEx Connect/Messenger (cloud-based).
Enterprise visual voicemail for visual navigation of the voicemail box

Mobile Connect (SNR) and mobile voicemail avoidance when integrated with Unified Mobility*
BRKUCC-2060
* Dual-mode devices only (cellular voice radio)
Cisco Public
23

Clients, Devices, and Configuration Overview
BRKUCC-2060
Cisco Public
24

Devices and Clients Overview
Cisco Jabber for iPhone and Android provides SIPbased voice capabilities Unified CM registration and voice over IP
(WLAN or mobile data) calling and automated enterprise dialing using the
mobile voice network with Dial via Office.
Cisco Jabber IM for Android, BlackBerry, and

iPhone provides XMPP-based IM and presence
capabilities Relies on either Cisco Unified Presence or cloudbased Cisco WebEx Messenger.
Cisco Jabber for iPad provides both SIP-based voice and

video capabilities (Unified CM or Cisco VCS registration) AND
XMPP-based IM/presence within a single device or client.
BRKUCC-2060
Cisco Public
25

Coming
Soon
Please refer to applicable product documentation on

Cisco.com for the latest feature, software, and
hardware version support requirements.
Devices and Clients: Cisco Jabber 9.1 for iPhone
Cisco Jabber for iPhone client registers as a SIP device with Cisco Unified CM
Device and Cisco Unified CM version support:
Client
Cisco Jabber for

iPhone
Device Support
iPhone 3GS, 4, 4S, and 5

iPod Touch (3rd and 4th
generation)
Minimum iOS
Version
iOS 6
Cisco Unified CM
Versions
7.1(5)
8.0(3)
8.5(1)
8.6(2)
8.6?/9.1?*
Cisco Unified CM
Express (CME) 8.6
and 8.8 are also
supported.
Beyond voice over WLAN/mobile data network functionality the Cisco Jabber for
iPhone client provides a number of additional features:
Dial via office enabling enterprise calling over the mobile voice network and PSTN
Enterprise directory access (requires Microsoft Active Directory or Open LDAP)
Enterprise visual voicemail (requires Cisco Unity Connection 7.x, 8.x, and 9.x)
Survivable Remote Site Telephony (SRST) failover support (requires SRST 8.6 or later)
User sign-in/out leveraging Unified CM Extension Mobility feature
* Required versions for DVO. Specific
supported versions to be determined.
BRKUCC-2060
Cisco Public
26
Please refer to applicable product documentation on

Cisco.com for the latest feature, software, and
Devices and Clients: Cisco Jabber 9.1 for Android
Cisco Jabber for Android client registers as a SIP device with Cisco Unified CM
Device and Cisco Unified CM version support:
Client
Cisco Jabber for

Android
Device Support **
Android OS Version
Samsung Galaxy Nexus

Samsung Galaxy S3
Android 4.1.1
Samsung Galaxy S2
Android 2.3.6
Cisco Unified
CM Versions
7.1(5)
8.0(3)
8.5(1)
8.6(2)
8.6?/9.1?*
Beyond voice over WLAN/mobile data network functionality the Cisco Jabber for
Android client provides a number of additional features:
Dial via office enabling enterprise calling over the mobile voice network and PSTN
Ring volume lockdown/control enabling administrative control of ring volume for noisy environments
Enterprise directory access (requires Microsoft Active Directory )
Enterprise visual voicemail (requires Cisco Unity Connection 7.x, 8.x, or 9.x)
* Required versions
** Although not officially supported, Cisco Jabber for Android runs on many Android OS 2.3, 4.0 and 4.1
devices with various limitations depending on the device.
BRKUCC-2060
Cisco Public
for DVO. Specific

supported versions
to be determined.
27
Please refer to applicable product documentation

on Cisco.com for the latest feature, software, and
Devices and Clients: Cisco Jabber 9.2 for iPad
Cisco Jabber for iPad mobile client registers as a SIP device with
Unified CM or TelePresence Video Communications Server (VCS)
Device support and call control versions:

Client
Cisco Jabber
for iPad
Device Support
iPad2, iPad (3rd and 4th

generations)
Minimum
iOS Version
iOS 6
Call Control Versions

for Voice and Video
Voice and video:

Unified CM 8.0(3), 8.5(1), 8.6(2), 9.0
TelePresence VCS 6.0 and later (also requires Cisco
TMS 13.1 or later)
Voice-only:
Unified CM 7.1(5), 8.0(3), 8.5(1), 8.6(2), 9.0
Provides voice and video over WLAN/mobile data network functionality

Video: Precision Video Engine - H.264 video (VGA) / Audio: G.711, G.722.1
Additional features include:
XMPP-based IM/Presence w./ Unified Presence on-premises or WebEx Messenger off-premises
Enterprise directory access (requires Microsoft Active Directory or OpenLDAP)
Enterprise visual voicemail (requires Cisco Unified CM and Cisco Unity Connection 8.5 and later)
BRKUCC-2060
Cisco Public
28

Cisco Unified CM: Cisco Jabber Device Configuration
Cisco Dual Mode for Android
Device configured with
device name that must be
all uppercase and start
with BOT.
For example: BOTJSMITH
(Must be all upper-case, no more than 15
characters total. Can include A-Z, 0-9, dot
(.), dash (-), or underscore (_)).
Cisco Dual Mode for iPhone

with TCT.
For example: TCTJSMITH
BRKUCC-2060
Cisco Public
29

Cisco Unified CM: Cisco Jabber Device Configuration (cont.)
Cisco Jabber for Tablet
with TAB.
For example: TABJSMITH
When registering to Cisco TelePresence VCS call control services, the Cisco
Jabber for iPad client device is configured and provisioned using the jabbertablet
provisioning template and Cisco TelePresence Management Suite (TMS).
BRKUCC-2060
Cisco Public
30

Cisco Unified CM: Cisco Jabber Device Configuration (cont.)
!
CAUTION
COP file required for all currently supported versions of

Unified CM:
Device COP file must be loaded on each node of the cluster.
Each node must be rebooted before adding or configuring a device.
COP file download:
http://www.cisco.com/cisco/software/release.html?mdfid=283812787&softwareid=284006014 (Android)
http://www.cisco.com/cisco/software/release.html?mdfid=284288351&softwareid=284006014 (iPad)
http://www.cisco.com/cisco/software/release.html?mdfid=283760466&softwareid=284006014 (iPhone)
Configuration of mobility client devices is same as with

regular IP phone (Device Pool, Calling Search Space, etc.).
Device specific configuration varies depending on client type.
BRKUCC-2060
Cisco Public
31

Cisco Jabber: Install and Configuration
Cisco Jabber client applications for iPhone and iPad must be

downloaded from the Apple App Store
(either directly via iPhone/iPad or using

iTunes on a PC and then synchronizing to USB attached iPhone/iPad)
Cisco Jabber client applications for Android must be downloaded from

the Google Play [formerly Android Market]
(either directly via Android device or

using a PC and then synchronizing to USB attached Android device)
After install and launch of Cisco Jabber application a set-up wizard

walks user through configuration/provisioning of various features.
BRKUCC-2060
Cisco Public
32

Cisco Jabber: User Configuration - Android
BRKUCC-2060
Cisco Public
33

Cisco Jabber: User Configuration - iPhone
BRKUCC-2060
Cisco Public
34

Cisco Jabber: User Configuration - iPad
Cisco Jabber for iPad is configured by

user selecting appropriate service (IM
and presence or video/voice services)
and then providing required server
hostname/IP, username, and password.
ucm-01.company.com
ucm-01.company.com
BRKUCC-2060
Cisco Public
35
NEW
Cisco Jabber for iPad 9.2: User Configuration Simplified
Simple Configuration - Simplified first-time sign-in experience.

User just enters their email address! Application discovers services,
connects, and prompts user for authentication as appropriate.
Requires DNS
SRV records in
the corporate
DNS server(s) to
direct the
application to
appropriate backend systems.
jsmith @ cisco.com
If no services are discovered, Cisco

Jabber for iPad reverts to wizard method
of configuration.
BRKUCC-2060
Cisco Public
36
NEW
Cisco Jabber for iPad 9.2: Simple Configuration Deployment Considerations

DNS SRV priority
Example DNS SRV records for various deployment types:
(1 ) and weight (2 )
st
Unified CM-only
_cisco-phone-tftp._tcp.example.com SRV 0
0 69 cucm.example.com
_cisco-phone-http._tcp.example.com SRV 0
0 80 cucm.example.com
nd
indication
DNS SRV port

number indication
_sip._tcp.internal.example.com SRV 0 0 5060 vcsc.example.com
VCS-only
_sip._tcp.external.example.com SRV 0 0 5060 vcse.example.com
IM/Presence-only
(OR IM/Presence +
Unified CM)
WebEx-only
(OR WebEx + Unified CM
or VCS)
_cuplogin._tcp.example.com SRV 0 0 8443 cup.example.com
_xmpp-client._tcp.example.com SRV 0 8443 loginp.webexconnect.com
IM/presence
DNS SRV
only
_xmpp-client._tcp.example.com SRV 0 5222 c2s.example.com.webexconnect.com
DNS SRV considerations:

If multiple servers are provided for a single service, then multiple DNS SRV records are required with appropriate
priority and weight to control client distribution.
Port numbers are not used by Cisco Jabber, but they should still be configured with default values.
When deploying IM/presence AND call control services, only IM/presence DNS SRV records are required.
BRKUCC-2060
Cisco Public
37
NEW
Cisco Jabber for iPad 9.2: Simple Configuration Deployment Considerations (cont.)
Distributed call processing deployments (multiple Unified CM clusters):
Centralized TFTP server required
Example DNS SRV record:
_cisco-phone-tftp._tcp.example.com 0 0 69 cftp.example.com
Note: HTTP DNS SRV record should not be configured
Device names must be unique across all clusters
BRKUCC-2060
Cisco Public
38

BRKUCC-2060
Cisco Public
39
Mobility Identity What's so special?
Dual-ring avoidance: Mobile

Connect engaged *ONLY* when
the mobile client device is not
registered to Unified CM (or when
DVO is enabled)
Configuration and Call Routing Concept

Cisco Dual Mode for iPhone/Android
Client Device Type
IP Phone
Enables dual-mode handoff and

Dial via Office
Shared Line
Line Level Settings
DN: 408 555-1234
Partition
Client Mobile Device

Level Configuration
Device Level
Configuration
Device Pool
Rerouting CSS
Call Routing and

Media Resource
Allocation for
Client-Based
Mobile Devices
No Remote Destination Profile
408 555-7890
Mobility Identity
BRKUCC-2060
408 555-6789
XXX XXX-XXXX
Call Routing
and Media
Resource
Allocation for
IP Phones
Device Pool
Common Device Configuration
Media Resource Group List
Maximum of 1 Mobility
Identity and 9 Remote
Destinations per user
Cisco Public
40
Cisco Mobility Client Solutions

Call 51234
Cisco Unified Mobility Integration: Dual-Ring Avoidance
Incoming calls are NOT

1st: VoIP
2nd: Mobile
Connect
routed to Mobility Identity

via Mobile Connect when
client device is
connected to the
enterprise and registered
to Cisco Unified CM
Incoming calls are routed
to Mobility Identity via
Mobile Connect when
client device is not
connected/registered to
enterprise (assuming Mobile
Connect is enabled and call
filtering/time of day routing permits)
BRKUCC-2060
Call 1 408 555-1234

Cisco Unified
Communications Manager
PSTN
Gateway
PSTN
WLAN
(802.11)
Mobile Voice
Network
(Carrier)
Cisco Unified
Mobility User
Enterprise Number
(408) 555-1234
Mobility Identity
(NO Enterprise
Attachment)
Same
Device
Mobile Client Voice Network

Connectivity Only
Enterprise Line
(Enterprise
Attachment)
Mobile Client Enterprise
Connectivity
NOTE: Incoming calls directly to the mobile phone number will ring the mobile voice/
cellular
interface even when the dual-mode phone
is associated to the enterprise WLAN. 41
Cisco Public

Cisco Unified Mobility: Mobility Identity
Mobility Identities have the
same configuration and
behavioral characteristics as
Remote Destinations
High availability and capacity

considerations are the same for
Mobility Identities.
Automatic Caller ID Matching and

Enterprise Call Anchoring (mid-call
features, desk phone pickup)
behave the same with Mobility
Identities
Maximum total of 15,000 Remote

Destinations AND Mobility
Identities
BRKUCC-2060
Cisco Public
42

Handoff
BRKUCC-2060
Cisco Public
43

Handoff Terminology: Hand-Out v. Hand-In
Moving calls from enterprise WLAN to cellular voice network and vice-versa
is generally referred to as Handoff
PSTN
Gateway
Hand-out: Moving calls from

enterprise WLAN to cellular
network
PSTN
Mobile
Voice
Network
AP
Enterprise WLAN
Cellular/Mobile Voice
PSTN
Gateway
Hand-in: Moving calls from

cellular network to enterprise
WLAN
PSTN
Mobile
Voice
Network
AP
Cellular/Mobile Voice
BRKUCC-2060
Cisco Public
Enterprise WLAN
44

Cisco Jabber: Handoff Considerations
Cisco Jabber for iPhone supports two hand-out methods:

1. Mobility Softkey method: Handoff indication signaled to Unified CM over WLAN.
System generates call TO mobile device's mobile voice number (Mobility Identity).
(Same operation as "Send Call to Mobile Phone"/Remote Destination pickup)
2. Handoff DN method: Handoff indication signaled to Unified CM over WLAN. Device

generates call FROM mobile voice number to Unified CM handoff number.
Method used depends on Transfer to Mobile Network setting on Cisco Dual-Mode for iPhone
device configuration page
Cisco Jabber for Android supports only the Mobility Softkey method (System
generates call TO mobile device's mobile voice network interface/Mobility Identity.)
Hand-in (cellular to WLAN) is not supported with Cisco Jabber

BRKUCC-2060
Cisco Public
45

Supported with Cisco Jabber
for iPhone and Android
Hand-Out: Mobility Softkey Method

Unified CM generates a call
to the mobility users
configured Mobility Identity
number via the enterprise
PSTN gateway
Cisco Unified
CM Cluster
PSTN
Gateway
PSTN
Mobile
5
Voice
Network
On answer, Unified CM
redirects original RTP
stream that was
traversing the WLAN to
the enterprise PSTN
gateway resulting in
enterprise call anchoring.
Initial voice
media path
Handoff
background call leg
Final voice
media path
BRKUCC-2060
AP
Mobile
Voice
4
User is now able to move
out of the enterprise and
away from enterprise
WLAN coverage.
WLAN
Same
Phone
An existing call between

the iPhone or Android
mobile client device on
the enterprise WLAN and
a phone on the PSTN.
User pushes Use Mobile
Network softkey from incall menu and mobile
client signals to Unified
CM its intention to handout.
Mobility Softkey: Handoff indication signaled to Unified CM over WLAN

which in turn generates call to mobile device's mobile voice network
interface (Mobility Identity). Once answered call media is redirected from
WLAN to enterprise PSTN gateway.
Cisco Public
46

Supported with Cisco Jabber
for iPhone only
Hand-Out: Handoff DN Method

Because Unified CM
relies on inbound
caller ID to identify
the call being handed
off, ensure native
iPhone caller ID is
iPhone mobile client

automatically makes call
via mobile voice network
interface to Handoff
Number configured within
Unified CM.
Unified CM verifies caller ID of

inbound call to handoff number to
ensure it matches configured
Mobility Identity. If so, Unified CM
redirects original media stream that
was traversing the WLAN to the
enterprise PSTN gateway and call is
anchored in the enterprise.
Initial voice
media path
Handoff
background call leg
Final voice
media path
BRKUCC-2060
Cisco Unified
CM Cluster
Handoff Number: 1234

Handoff Number DID: +1 408 555 1234
PSTN
Gateway
(Tap: Settings > Phone > Show

My Caller ID)
PSTN
Mobile
5
Voice
Network
AP
Mobile
Voice
User is now able to
move out of the
enterprise and away
from enterprise WLAN
coverage.
For
Your
Reference
4
WLAN
Same
Phone
An existing call between

the iPhone mobile client
device on the enterprise
WLAN and a phone on
the PSTN.
User pushes Use Mobile
Network softkey from incall menu and iPhone
mobile client indicates to
Unified CM its intention to
hand-out.
Handoff DN: Hand-off indication signaled to Unified CM over WLAN

which in turn generates call from mobile device's mobile voice network
interface to handoff number. Once answered call media is redirected
from WLAN to enterprise PSTN gateway.
Cisco Public
47

Dial via Office
BRKUCC-2060
Cisco Public
48

Dial via Office
The Dial via Office (DVO) feature enables Cisco mobile client devices to
automatically dial an outgoing call through the enterprise
All voice media traverses the mobile voice network and PSTN
Why enable and use Dial via Office?
All voice signaling (SIP) traverses the IP connection (802.11 WLAN or mobile data)
between the client and Unified CM.
IP path DOES NOT provide ample bandwidth/throughput to ensure good voice quality
DVO moves media to the mobile voice network/PSTN which ensures high quality voice
IP path DOES NOT provide reliable connection to prevent call disconnects

Audio is maintained even in cases of IP connection failure
Benefits:
BRKUCC-2060
Cost savings for international and possibly long distance calls

Mobile phone number masking: System sends users enterprise number as caller ID
Enterprise call anchoring (desk phone pickup, DTMF-based mid-call features)
Cisco Public
49

Dial via Office Architecture
All call signaling

traverses the 802.11
WLAN or mobile
data IP connection
between the client
and Unified CM.
Call Media
(Voice)
PSTN
Mobile Voice
Network
BRKUCC-2060
Cisco Unified CM
Enterprise
WLAN
All call media

traverses the mobile
voice network,
PSTN, and
enterprise gateway.
PSTN
Gateway
(802.11)
Call
Signaling
(SIP)
Cisco ASA
Public/Private
WLAN
(802.11)
Mobile Data
Network
(Data Channel)
Call signaling
Voice media
Internet
Cisco Public
50
After the user answers at the

mobile device, Unified CM
extends a call to the number
the user dialed. The user
begins to hear ring-back.
Dial via Office Reverse
Cisco Jabber 9.1

supports Dial via Office
Reverse (DVO-R)
DVO-R calls are set up
by the Unified CM
system calling the user's
mobile number
(configured as a Mobility
Identity)
Coming
Soon
+1 (408) 555-7890
Once the call is
answered at the
target number,
Unified CM anchors
the call in the
enterprise gateway
3
4
Mobile Voice
Network
PSTN
Gateway
PSTN
Unified CM extends a
call to the mobile
number (Mobility
Identity) of the Cisco
Jabber client device.
Cisco Unified CM
2
Call Media
(Voice)
Enterprise
1 WLAN
(802.11)
Cisco ASA
Public/Private
WLAN
Data (802.11)
Mobile
Network
User selects contact or dials

(Data Channel)
number +1 408 555 7890.
Cisco Jabber client signals to
Unified CM over the IP path
(WLAN or mobile data)
BRKUCC-2060
Internet
Cisco Public
Call signaling
Call Signaling
(SIP)
Voice media
51

Dial via Office Reverse Using Alternate Callback Number
Cisco Jabber 9.1

supports Dial via Office
Reverse (DVO-R)
DVO-R calls are set up
by the Unified CM
system calling the user's
mobile number
(configured as a Mobility
Identity)
DVO-R calls may also
be setup using a userspecified alternative
callback number
NOTE: DVO-R calls using
an alternate callback
number are not anchored
BRKUCC-2060
After the user answers at the

mobile device, Unified CM
extends a call to the number
the user dialed. The user
begins to hear ring-back.
Coming
Soon
+1 (408) 555-7890
Once the call is
answered at the
target number,
Unified CM anchors
the call in the
enterprise gateway
3
4
Mobile Voice
Network
PSTN
Gateway
PSTN
Unified CM extends a
call to the alternate
callback number
configured on the Cisco
Jabber client device.
Cisco Unified CM
2
Call Media
(Voice)
Enterprise
1 WLAN
(802.11)
Cisco ASA
Public/Private
WLAN
Data (802.11)
Mobile
Network
User selects contact or dials

(Data Channel)
number +1 408 555 7890.
Cisco Jabber client signals to
Unified CM over the IP path
(WLAN or mobile data)
Internet
Cisco Public
Call signaling
Call Signaling
(SIP)
Voice media
52
Coming
Soon

Enabling Dial via Office: Cisco Unified CM Device Configuration
iPhone
Android
When enabling Dial via Office, the

"Enable Cisco Unified Mobile Communicator"
box must be checked on the device
configuration
page.
BRKUCC-2060
2013 Cisco
and/or its affiliates. All rights reserved.
Cisco Public
53
Coming
Soon

Cisco Jabber for Android and iPhone: Dial via Office Client Calling Options
!
CAUTION
The Cisco Jabber DVO

client calling option not
only determines the
enterprise call origination
method, but also the
enterprise call termination
method.
Mobility Identity or
user specified
alternate callback
number
BRKUCC-2060
Cisco Public
54
Coming
Soon

Cisco Jabber for Android and iPhone: DVO Client Calling Options - Outbound
Cisco Jabber DVO Calling Options
Automatically Select
Cisco Jabber
Call Direction
Outbound
Inbound
Voice over IP
Voice over IP
Always Use DVO
Always Use Internet
Outbound
Inbound
Outbound
Inbound
Dial Via Office
Mobile Connect
Voice over IP
Voice over IP
Device
IP Connection
802.11 WLAN
(Corporate/
enterprise)
802.11 WLAN
(Non-corporate)
Mobile Data
No IP
BRKUCC-2060
Dial via Office
Mobile Connect
Outbound: Native Cellular

Inbound: Mobile Connect
Cisco Public
55
Coming
Soon

Cisco Jabber for Android and iPhone: DVO Client Calling Options - Inbound
Cisco Jabber DVO Calling Options
Cisco Jabber
Call Direction
Outbound
Inbound
Voice over IP
Voice over IP
Always Use DVO
Always Use Internet
Outbound
Inbound
Outbound
Inbound
Dial Via Office
Mobile Connect
Voice over IP
Voice over IP
Device
IP Connection
802.11 WLAN
(Corporate/
enterprise)
802.11 WLAN
(Non-corporate)
Mobile Data
No IP
Dial via Office
Mobile Connect
Outbound: Native Cellular

Inbound: Mobile Connect
NOTE: Dual-ring avoidance (VoIP, then Mobile Connect) does not apply when
DVO calling
is enabled as all inbound calls
areCisco
routed
MobileAllConnect
BRKUCC-2060
2013
and/orby
its affiliates.
rights reserved.
Cisco Public
56
Coming
Soon

Dial via Office Client Calling Options: Usage Models for End-Users
Which Cisco Jabber calling option? Depends on the end-user profile

Always Use DVO
Typical Profile: User is highly mobile, almost never has WLAN coverage
Mobile data does not provide acceptable voice quality and reliability
Always Use Internet

Typical Profile: User is mobile within the office (home or enterprise) but
enterprise calling not typically needed outside the enterprise.
Cost is an important consideration (e.g. employee-owned device/BYOD)
Automatically Select (default)

Typical Profile: User is mobile both within and outside the office.
Provides potential least cost routing by taking advantage of VoIP when
Wi-Fi is available and falls back to mobile voice and data network
(DVO/Mobile Connect) when Wi-Fi is not available
BRKUCC-2060
Cisco Public
57

On answer the
called party may end
up in the mobile
voicemail box of the
calling user leading
to poor experience
Dial via Office Reverse: Voicemail Avoidance
Voicemail
avoidance is
important for
optimum DVO-R
experience.
POOR
EXPERIENCE
Cisco Unified CM
PSTN
Mobile
voicemail
User Control
(DTMF-based)
method is
recommended with
Unified CM 9.0 and
later.
NOTE: DVO-R calls using

an alternate callback
number DO NOT engage
voicemail avoidance
PSTN
Gateway
Mobile Voice
Network
(Carrier)
WLAN
(802.11)
Mobile Data
Network
(Data Channel)
With User Control voicemail avoidance, if no DTMF digit

is received by Unified CM, call will be disconnected
BRKUCC-2060
Cisco Public
Call Signaling
Voice media
58

Dial via Office: Mobile Toll Bypass Optimization
The Mobile Toll Bypass Optimization* feature provides least cost routing
functionality to mobile client Dial via Office (DVO) operations
Two components of the feature:

1. Multiple Enterprise Feature Access Numbers
Configuration of multiple system DIDs for Enterprise Feature Access (DVO

and Unified Mobility 2-stage dialing access numbers)
Enables configuration of per geographic location local or toll-free number
2. Mobility Profile
Per user or per user group profile configuration containing: DVO direction
(F or R), DVO-F Service Access Number and Enterprise Feature Access
Number pair, DVO-R Caller ID.
Applied to user's Mobility Identity
BRKUCC-2060
Cisco Public
* Requires Unified CM 8.5 or later

59

Dial via Office: Mobile Toll Bypass Optimization (cont.)
Multiple Enterprise
Feature Access
Numbers
Association of
Mobility Profile to
Mobility Identity
SJ Users profile
Per User/
Group
Mobility
Profiles
RTP Users profile
BRKUCC-2060
Cisco Public
60
Cisco Jabber does not support

the Mobility Profile calling
option setting. DVO-R is the
only calling option available.

Dial via Office: Mobile Toll Bypass Optimization
Dial via Office operation is controlled by the Mobility Profile assigned to the
Mobility Identity
Once call received
Determines DVO
direction.
(DVO-F) or answered
(DVO-R) Unified CM
sets up call to
dialed/target number
DVO-F: Client
automatically dials
DID number
received from
Unified CM
5
Mobile
Voice
Network
3B
PSTN
6
Call anchored in
enterprise
gateway
4
DVO-R: Unified
CM sets up call to
Mobility Identity
with appropriate
caller ID
Client signals call setup

request to dialed/target
number over secure
mobile data connection.
Mobile
Data
Network
Cisco Unified
CM 8.6 (or later)
ASA
Internet
3A
DVO-F: Unified CM
sends appropriate
DVO-F DID
(EFA/SA number)
to client.
Unified CM checks
user's mobility profile to
determine DVO method,
DID number to send for
DVO-F or number to
use for caller ID for
DVO-R
Mobile Voice Connection
Mobile Data Connection
Call Signaling
DVO-F call leg setup
DVO-R call-back leg setup
Target call leg setup
BRKUCC-2060
Cisco Public
61
Coming
Soon

Dial via Office: Mobility Profile Configuration
Configuration of a
Mobility Profile is not
required.
When configured, the
Mobility Profile has
limited client impact
This setting has no impact as
DVO-R is the only DVO
method supported.
This is the only setting which

takes affect. When configured,
this determines the caller ID on the
callback call leg
BRKUCC-2060
Cisco Public
62
Coming
Soon

Dial via Office: Default Enterprise Feature Access Number
If no Mobility Profile has been

configured for a dual-mode
device
the default Enterprise Feature
Access Number configured on
the system will be used as caller
ID on the DVO callback call leg
Failure to configure a default

Enterprise Feature Access
Number will result in DVO-R
call failures
BRKUCC-2060
Cisco Public
63

Dial via Office v. Extend and Connect
Do not confuse Dial via Office with Extend
and Connect.
Both provide automated enterprise dialing
PSTN
Mobile Voice
Network
Cisco Unified CM
with SIP signaling over the IP network but

Dial via Office is a feature specific to Cisco Jabber
Enterprise
WLAN
(802.11)
for smartphones
Public/Private
WLAN
(802.11)
Triggered by dual-mode device (cellular voice radio)

Media always terminates on the mobile voice network*
Cellular interface receives (DVO-R) or originates
PSTN
Gateway
Mobile Data
Network
(Data Channel)
Cisco ASA
Internet
(DVO-F**) first call leg
Extend and Connect is a feature specific to Cisco

Jabber for desktops
Triggered by Jabber desktop client

Media may or may not terminate on the mobile voice
DVO call signaling

DVO voice media
Extend & Connect call signaling
Extend & Connect voice media
network (call flow dependent)
* Except in the case of DVO-R using
Active remote destination always receives first call leg

BRKUCC-2060
alternate callback number

Cisco Public
**
DVO-F is not currently supported
64

Design and Deployment Considerations
BRKUCC-2060
Cisco Public
65

Dial Plan: Outbound Call Routing Voice/Video over IP and Dial via Office
PSTN
Calls originated from Cisco

Jabber/Mobility Identity
(VoIP, VVoIP, DVO)
Cisco Unified CM mobile device types contains two CSS settings which
control call routing from a mobile client device perspective: Calls originated from associated
BRKUCC-2060
Cisco Public
Remote Destinations (enterprise 2stage dialing) are also routed in

this manner.
66

Dial Plan: Inbound Call Routing Mobile Connect and Dial via Office Reverse
PSTN
Calls routed to Cisco

Jabber/Mobility Identity
(Mobile Connect, DVO-R)
Cisco Unified CM mobile device types contains two CSS settings which
control call routing from a mobile client device perspective: Calls routed to associated Remote
Rerouting Calling Search
BRKUCC-2060
2013 Cisco and/orSpace
its affiliates. All rights reserved.
Destinations (Mobile Connect) are

also routed in this manner.
Cisco Public
67

Dial Plan: Dual-Mode Jabber for Android and iPhone
End-User dialing behavior Dialing on the mobile voice

network/PSTN is different than dialing within the enterprise
network.
1. User Effort: Users check client registration/service icon.
If client is registered, user dials using enterprise dial plan (abbreviated dialing, PSTN steering
digits, etc.)
If client is not registered, user dials using PSTN dialing method (+ and/or E.164)
Cisco Jabber
1000
NOTE: Cisco Jabber for Android and iPhone are able to leverage
application dial rules within Unified CM to improve user dialing
experience BUT this DOES NOT help with global deployments!
Recommended
2. Administrator Effort: Unified CM dial plan configured to

accommodate PSTN/mobile voice network dialing.
BRKUCC-2060
User always dials all calls using + and/or full E.164 number (manually or from contacts)
Unified CM dial plan routes to local extensions as appropriate and/or prefixes appropriate
PSTN steering digits.
Cisco Public
68

Design Considerations: Voice and Video over WLAN
Basic VoWLAN network design requirements:
Cell radius or power-level boundary of

approximately -67 dBm (or less) is recommended
in order to minimizes packet loss.
Same channel cell separation of 19 dBm is

recommended to minimize co-channel interference
Channel cell overlap (on non-adjacent channels)

should be minimum of 20% to ensure seamless
roaming between APs.
Bluetooth headsets are not recommended with

mobile client handsets due to potential
interference on the 2.4 GHz band. Consider
using 5 GHz band for wireless attachment.
BRKUCC-2060
For more information on VoWLAN Design,

see the Voice over Wireless LAN 4.1
Design Guide at:
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mo
bility/vowlan/41dg/vowlan41dg-book.html
Cisco Public
69

Design Considerations: Wireless Site Survey
A wireless site-survey should be conducted prior to deploying

voice over WLAN mobile clients:
Verify radio frequency (RF) design

Verify non-overlapping channel configurations
Ensure appropriate AP coverage including considerations for:
Machinery, elevators, stairwells, and wall densities

Areas between buildings
Cell coverage patterns and antenna direction and attenuation
Ensure required data and traffic rates are provided

Identify and mitigate the impact of potential interference sources
including microwaves, cordless phones, rogue APs, and Bluetooth
devices
BRKUCC-2060
Cisco Public
70

Design Considerations: Public and Private WLAN Hotspots
Enterprise-class WLAN connectivity is recommended to ensure

acceptable voice and video quality and reliability for WLAN calls.
WLAN is everywhere, butnot all WLANs are equal

Public and private WLAN hotspots (home, hotel, airport, coffee shop, etc.)
Calls are traversing the Internet!!
x
x
x
x
x
Not enterprise-class WLAN

Not optimized for voice and video including no end-to-end QoS
Best-effort traffic based on network capacity
Usually unmanaged
Poor throughput, jitter, delay, and packet-loss can occur before

traffic even leaves WLAN hotspot
Cisco cannot guarantee acceptable voice and video quality or troubleshoot
connectivity issues for calls
traversing public or private WLANs.
Cisco Public
BRKUCC-2060
71
RTP
QoS
H.264
Bulk Data
Design Considerations: Quality of Service (QoS)
SIP
Cisco Jabber for Android and iPhone mobile clients appropriately mark layer 3 QoS
for both call media and signaling:
Voice signaling (SIP) DSCP 24 / PHB CS3

Voice media (RTP) DSCP 46 / PHB EF
Cisco Jabber for iPad only marks call signaling at layer 3 - it does not mark voice and
video media Best effort (DSCP 00 / PHB BE) - Remarking based on ports/protocols required
Cisco Jabber clients do not mark layer 2 WLAN User Priority QoS marking
Wireless layer 2 UP marking is unreliable as 3rd party devices/firmware manufacturers do not

honor these markings
Consider use of SIP Media Snooping on the WLAN infrastructure to detect SIP call setup and
termination and to provide improved throughput including wireless call admission control
Ensure that layer 3 DSCP mapping (wireless to wired QoS) on the first hop switch port is
configured such that priority queuing is provided for voice and dedicated
bandwidth is provided for video and call signaling traffic on the wired network
BRKUCC-2060
Cisco Public
72

Design Considerations: Emergency Calling
Calls for emergency services should be routed via the mobile provider
network whenever possible.
Mobile provider networks typically provide more accurate location information

than enterprise or public WLAN networks.
Cisco mobile client solutions provide mechanism for escaping or forcing of
emergency calls directly over PSTN or mobile voice network.
Mobile Clients Device Configuration

Avoids enterprise call routing (VoIP and DVO)
Applies to Cisco Jabber for iPhone/Android
BRKUCC-2060
Cisco Public
73

Design Considerations: Capacity and High Availability
The following design-related information should be considered when deploying Cisco mobile
client solutions:
Capacity/Scalability
Maximum of 15,000 Remote Destinations/Mobility Identities per Unified CM cluster.
Maximum of 8 simultaneous VVoWLAN bidirectional streams per 802.11 g/n (2.4 GHz) with
Bluetooth disabled or 802.11 a/n (5 GHz) channel cell assuming a video resolution of
720p (high-definition) and a video bit rate of up to 1 Mbps.
Maximum of 40,000 registration/devices per Unified CM cluster.*
Maximum of 27 simultaneous VoWLAN calls per 802.11 a/g/n channel cell (with 24 Mbps
data rate and higher and no Bluetooth).
High Availability
X X
BRKUCC-2060
Redundancy for client device registration via device pools/CM groups (or DNS with VCS).
Gateway and PSTN access redundancy is as usual, however branches in SRST mode will
provide limited mobile client support:
Cisco Jabber for iPhone client supports SRST fallback
* With Unified CM
All other devices will fall-back to cellular/mobile voice network when client de-registers from Unified CM. 8.6 and later
Mobile client VoIP/VVoIP features and operations (VoIP, VVoIP, handoff, mid-call features,
and move to desk phone) all natively redundant.
Cisco Public
74
74

Cisco Jabber IM and Other Mobile Clients
BRKUCC-2060
Cisco Public
75

Cisco Jabber: XMPP-Based IM and Presence On-Premises v. Cloud-Based
Cisco Jabber IM for Android, BlackBerry, and iPhone smartphones as well as

Cisco Jabber for iPad enable XMPP-based IM and Presence services.
Cisco IM
and Presence
WLAN
(802.11)
Cisco Jabber is able to connect to

on-premises Cisco IM and
Presence server for IM and
presence services
Public/Private
WLAN
Data (802.11) XMPP
hello
DMZ
Mobile
Network
(Data Channel)
Alternatively Cisco Jabber is able

to connect to cloud-based Cisco
WebEx Messenger for IM and
presence services
BRKUCC-2060
XMPP
On-Premises
IM & Presence
Internet
Cisco ASA
Cloud-Based
IM & Presence
XMPP
XMPP
Cisco
WebEx
Messenger
Cisco Public
76

XMPP
Cisco Jabber IM: Device and Firmware Support
Cisco Jabber IM supports the following platforms and software versions:

Client
Device Support
Cisco Jabber IM
for Android
All phones and

tablets running the
support Android OS
Client
Android OS
Version
2.6
4.0
4.1
Device Support
Bold 9000, 9650, 9700, 9780, &

Cisco Jabber IM for
BlackBerry
BRKUCC-2060
9900
Curve 8330, 8520, 8530, & 8900
Torch 9800, 9810, 9850
Tour 9630
IM and Presence Service Versions
Cisco Unified Presence/Cisco IM &
Presence 8.0(2) and higher

Cisco WebEx Messenger 7.5 and higher
BlackBerry
OS Version
OS 4.6
OS 4.7
OS 5.0
OS 6.0
OS 7.0
Cisco Public
IM and Presence Service

Versions
Cisco Unified Presence/Cisco
IM and Presence 8.0 and 8.5

Cisco WebEx Messenger
6.5, 6.7, and 7.0
77

XMPP
Cisco Jabber IM: Device and Firmware Support (cont.)
Cisco Jabber/Jabber IM supports the following platforms and software

versions (cont.):
Client
Device Support
iPhone 3GS, 4, 4S, and 5

iPod touch 4th and 5th
Cisco Jabber IM
for iPhone
Device Support
Cisco Jabber for

iPad
iPad2, iPad (3rd and

4th generations)

iOS 6
generation
Client
BRKUCC-2060
Minimum iOS
Version
Presence 8.0 and higher

Cisco WebEx Messenger 7.5 and
higher
Minimum iOS
Version
iOS 6
Presence 8.0 and higher

Cisco WebEx Messenger 7.5 and
higher
Cisco Public
78

Cisco Jabber for Android and iPhone: Call and Chat Cross-Launching
Cisco Jabber clients also provides cross-launch capabilities for

voice and IM applications.
Cisco Jabber Contact List
Cisco Jabber IM Contact Profile
John Smith (jsmith - EN
User selects Use Cisco

Jabber or Jabber button
from Contact Profile to
cross-launch Cisco
Jabber (if installed).
+1 555 123 4567
User selects Chat button

from Contact List to crosslaunch Cisco Jabber IM
(if installed).
+1 555 098 7654
Use SMS/
provider
messaging
BRKUCC-2060
Cisco Public
Use native
device dialer
(mobile voice/
cellular calling)
79

Cisco WebEx Mobile
Cisco WebEx Meetings can be accessed using the Cisco WebEx Mobile clients
Cisco WebEx Mobile clients are available for Android, BlackBerry, and Apple iOS
devices (available at appropriate application store).
The Cisco WebEx Mobile client enables mobile device users to:
Schedule, host, and attend meetings
View shared content and meeting participant list
Pass the ball to someone who wishes to share content
Send and receive video*
Apple iOS
Android
BRKUCC-2060
Cisco Public
* Supported only with iOS mobile devices
80

Cisco Jabber: Cisco AnyConnect Secure Mobile and Remote Connectivity
While VPN connection from mobile device/client to enterprise via WLAN or
mobile data network is possible, voice and video quality and application
response time are dependent on connection quality and cannot be
guaranteed.
Cisco Jabber for Android, iPad and iPhone support device-level SSL-based
Cisco AnyConnect Secure Mobile client for on-demand secure access back
Cisco Jabber for Android and iPhone
to the enterprise network.
Cisco Jabber w./ Cisco AnyConnect
Secure Mobile
Mobile Voice
Network
clients must be explicitly enabled (via

client settings) for connectivity over
mobile data network in order to send
VoIP over the 3G/4G/mobile data
network.
PSTN
DMZ
Mobile Data
Network
SSL
WLAN
Internet
Cisco ASA
When DVO is enabled for the client

device connectivity over mobile data
network is automatically enabled and
this setting is hidden
Because voice/video quality over Internet connections including 3G/4G mobile data networks varies
depending on the quality of the network connection, Cisco does not provide support to troubleshoot
voice/video quality or connectivity
issues for remote client attachment.
Cisco Public
BRKUCC-2060
81

Bring Your Own Device
BRKUCC-2060
Cisco Public
82

Bring Your Own Device (BYOD)/Any Device Overview
Security and management are important aspects of mobile device deployment within
the enterprise. Network-based security and management services should be
implemented when deploying Cisco mobile client solutions.
This is critical for

mobile clients
running on both
corporate assets
and on employee or
guest-owned
devices.
Cisco Jabber and

collaboration
services may be
deployed on top of
the Cisco BYOD
infrastructure
BRKUCC-2060
Personal/
Employee-Owned
Mobile Device
Cisco Jabber
PSTN
Access
Gateway
Mobile Voice
Network
(Carrier)
Cisco AnyConnect
PSTN
Cisco Unified
Communications
Manager
Cisco Unified
802.11
WLAN
Cisco
WLAN
Controller
Mobile Data
Network
Internet
Channel)
Bring Your Own Device(Data
Benefits
Company
Cisco Adaptive
Cisco Identity
Cisco Prime
Leverage non-corporate resources for "free"
Security Appliance
Services
Network Control
Not just mobile devices, mobile voice and data
(ASA)
Engine (ISE)
System (NCS)
services
Employees/Guests
Cisco Bring Your Own Device (BYOD)
Convenience
Smart Solution Infrastructure
Satisfaction
Cisco Public
Certificate
Authority
(CA)
Mobile Device
Manager
(MDM)
LDAP
Directory
83

Bring Your Own Device (BYOD) Access Use Cases: Basic Access
The Cisco BYOD infrastructure provides a range of access use cases to address various
device ownership and access requirements.
The following three high-level access use case models should be considered:
Basic Access
Basic Internet-only
access for guest/
personal devices: -
PSTN
Gateway
Mobile Voice
Network
(Carrier)
Enable personal device network

connectivity without access to
corporate resources.
PSTN
Cisco Unified
Communications
Manager
Cisco Unified
802.11
WLAN
Personal/
Employee-Owned
Mobile Device
Mobile Data
Network
(Data Channel)
Cisco
WLAN
Controller
Internet
Mobile Device
Manager
(MDM)
Cisco Adaptive
Cisco Identity
Security Appliance
Services
(ASA)
Engine (ISE)
Cisco Prime
Network Control
System (NCS)

BRKUCC-2060
Certificate
Authority
(CA)
Cisco Public
LDAP
Directory
84

Bring Your Own Device (BYOD) Access Use Cases: Limited Access
Basic Access
Basic Internet-only
access for guest/
personal devices: Enable personal device network
PSTN
Gateway
Cisco Jabber
Mobile Voice
Network
(Carrier)
PSTN
Cisco Unified
Communications
Manager
Limited Access
Cisco Unified
802.11
WLAN
Full access for

corporate devices: -
Cisco
WLAN
Controller
Certificate
Authority
(CA)
Enable corporate device

network connectivity with full
access to corporate resources
Corporate
Mobile Device
Mobile Data
Network
(Data Channel)
Internet
Mobile Device
Manager
(MDM)
Cisco Adaptive
Cisco Identity
Security Appliance
Services
(ASA)
Engine (ISE)
Cisco Prime
Network Control
System (NCS)

BRKUCC-2060
Cisco Public
LDAP
Directory
85

Bring Your Own Device (BYOD) Access Use Cases: Enhanced Access
Basic Access
Basic Internet-only
access for guest/
PSTN
Gateway
Cisco Jabber
Mobile Voice
Network
(Carrier)
PSTN
Cisco Unified
Communications
Manager
Limited Access
Full access for
Cisco Unified
802.11
WLAN
Cisco AnyConnect
Cisco
WLAN
Controller
Certificate
Authority
(CA)

Enhanced Access
Granular access for
corporate and guest/
personal devices: Enable corporate and personal
device network connectivity with
granular access to corporate
resources based on policy
BRKUCC-2060
EmployeeOwned OR
Corporate
Mobile Device
Mobile Data
Network
(Data Channel)
Internet
Mobile Device
Manager
(MDM)
Cisco Adaptive
Cisco Identity
Security Appliance
Services
For more information on Cisco BYOD Smart Solution
Infrastructure
and
(ASA)
Engine (ISE)
Cisco Prime
Network Control
System (NCS)
BYOD access use cases refer to the Cisco Bring Your Own Device
Smart Solution Design Guide available at
http://www.cisco.com/go/byoddesign
Cisco Public
LDAP
Directory
86

Design Considerations: Bring Your Own Device (BYOD) 1 of 2
Enable Cisco Jabber users for BYOD WLAN network attachment that does not
require user intervention*
Fast authentication/re-keying maximizes utilization of the voice/video over IP enterprise

telephony infrastructure.
Recommend: Certificate-based authentication + enforced device pin-lock policy
Depending on endpoint device, initial network attachment enrollment & flow varies
If two-factor authentication is required by corporate security policy, then user intervention is

required in order for the device to attach to the network.
Apple iOS devices can be on-boarded automatically using self-provisioning

Android devices requires intermediary step during self-provisioning: Provisioning supplicant
application (Cisco Network Setup Assistant) must be downloaded from Google Play requiring
Internet access.
Personal/employee-owned devices
If enterprise security policy requires remote-wipe or factory reset or provisioned mobile devices,
device owners should be made aware of this
Loss of personal data is possible, device owner should backup regularly
BRKUCC-2060
Cisco Public
* After initial provisioning/enrollment
87

Design Considerations: Bring Your Own Device (BYOD) 2 of 2
In order for Jabber to properly operate, infrastructure firewall traversal must be

allowed for required client application traffic .
Separate BYOD and Collaboration provisioning
Failure to implement firewall traversal means Jabber cannot access on-premises call control,
messaging, presence and directory services.
Today collaboration client and back-end application provisioning requires a separate set of
operational flows from the BYOD network device enrollment.
BYOD infrastructure must be QoS enabled
BRKUCC-2060
Collaboration applications depend on end-to-end QoS to ensure high-quality voice and video
Priority queuing for voice media and dedicated video and signaling bandwidth
Cisco Public
88

BlackBerry MVS
BRKUCC-2060
Cisco Public
89

BlackBerry Mobile Voice System (MVS): Overview
BlackBerry Mobile Voice System (MVS) solution enables BlackBerry users to
securely leverage the enterprise telephony infrastructure.
The BlackBerry MVS solution relies on Unified CM to provide SIP device

registration as well as underlying call routing.
Mobile Voice Mobile Voice
Network
System (MVS)
Client
PSTN
This solution is similar to Cisco

mobility solutions for other
vendor handsets and provides
similar or equivalent functionality.
SNR
Cisco Unified CM
Voice over WLAN/

Mobile Data
PSTN
Gateway
WLAN
(802.11)
SIP
SNR
Voice
Data
VoWLAN
BRKUCC-2060
Mobile Data
Network
(Data Channel)
Internet
Mobile Voice
BlackBerry
System Server
Enterprise Server
(MVS)
2013 Cisco and/or its affiliates.
(BES)All rights reserved.
BlackBerry MVS may be

deployed in parallel with
Cisco mobility clients for
non-BlackBerry handsets as
well as with Cisco Jabber IM
for BlackBerry
Automated
Enterprise Dialing
Cisco Public
90

BlackBerry Mobile Voice System (MVS): Features and Functionality
Provide access to UC features directly from native integrated client on

BlackBerry
Single number reach

Automated enterprise dialing (device-initiated, PBX-initiated)
Voice over WLAN (with automatic handoff) or mobile data network
Enterprise MWI and single voicemail box for all enterprise calls (mobile voicemail avoidance)
Enterprise mid-call features: Transfer, hold, call waiting, conferencing
Mobile phone masking (outgoing enterprise caller ID)
Move active calls between BlackBerry mobile device and desk phone
Call filtering and call screening
Relies on Unified CM for device registration and call routing via SIP integration
(SIP line and trunk)
SNR and automated enterprise dialing are delivered natively rather than via Cisco
Unified Mobility and Cisco Jabber (no Remote Destination Profile or Remote Destination/Mobility Identity)
BRKUCC-2060
Cisco Public
91

Summary
BRKUCC-2060
Cisco Public
92

Review and Wrap-Up
Cisco
Mobile Clients
DN: 51234
Campus/
Single Site

Hardware Moves
Extension
Mobility
PSTN
Fixed Mobile
Convergence
WLAN Roaming
WLAN
(802.11)
Mobile Voice/Extension
Data Network
Mobility
Mobile Voice
Network
DN: 51234
PSTN
Fixed Mobile Convergence w./

IP/WAN
Feature summary (Mobile
Internet
Connect, 2-stage dialing,
etc.)
WLAN
Roaming
and Provider
Mobility
Unified Mobility Integration
Enterprise
Configuration and
Design
Considerations
Cisco
Mobile
Clients
Mobile Data
Network
Dial via Office
Device Mobility
Automatic Caller ID Matching and

Call Anchoring
PSTN
Other mobile clients: Cisco AnyConnect

Secure Mobile, Cisco WebEx
Mobile
WLAN
Fixed Mobile
Mobile Voicemail Avoidance
Mobile Voice/
Data Network
(802.11)
Bring Your Own Device (BYOD)

Substitution
Design Considerations Remote

BRKUCC-2060
Fixed Mobile Substitution w./ Cisco

Mobile Client Solutions
Cisco Jabber /Jabber IM for Android,
iPhone, and iPad
Bridging Enterprise
BlackBerry MVS
VPN IP Phone or Soft Client
w./ PC VPN
Cisco Virtual Office
Cisco Public
93
For
Your
Reference
Application Feature Matrix (1 of 2)
Feature
Android
iOS
BlackBerry
Cisco Jabber
for Android
Cisco Jabber
IM
Cisco Jabber
for iPhone
Cisco Jabber
IM
Cisco Jabber for iPad
Cisco Jabber
IM
BlackBerry MVS
5.1
Single Number Reach,

Single Voicemail box
(via Unified Mobility)
Via MVS
Voice over WLAN/Mobile

Data
Video over WLAN/Mobile

Data
Hand-out (WLAN to
Cellular)
Manual
Manual
Automatic
Hand-in (Cellular to
WLAN)
Automatic
Device or PBXinitiated
Dial via Office
BRKUCC-2060
Supported
Not Supported
Support not applicable

Cisco Public
* DVO-R only and Requires

Cisco Jabber 9.1
94
For
Your
Reference
Application Feature Matrix (2 of 2)
Feature
Android
iOS
BlackBerry
Cisco Jabber
for Android
Cisco Jabber
IM
Cisco Jabber
for iPhone
Cisco Jabber
IM
Cisco Jabber for iPad
Cisco Jabber
IM
BlackBerry MVS
5.1
Visual Voicemail
MWI only
IM and Presence
Corporate Directory
Search
Via BES
Secure Remote
Enterprise Attachment
Cisco
AnyConnect
VPN
Cisco
AnyConnect
VPN
Cisco
AnyConnect
VPN
Cisco
AnyConnect
VPN
Cisco AnyConnect VPN
Via BES
Via BES and/or

native IPSec VPN
WebEx Meetings
Cisco WebEx
Mobile
Cisco WebEx
Mobile
Cisco WebEx
Mobile
Cisco WebEx
Mobile
Cisco WebEx Mobile
Cisco WebEx
Mobile
Cisco WebEx
Mobile
BRKUCC-2060
Supported
Not Supported
Support not applicable

Cisco Public
95
For
Your
Reference
Additional Resources 1 of 2
For additional information about Cisco mobile collaboration solutions:

Check out the latest Unified Communications SRND at:
http://www.cisco.com/go/ucsrnd (and specifically the Mobile Unified Communications / Mobile Collaboration
chapter)
Consult product documentation and collateral:
Cisco Unified Mobility:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/9_1_1/ccmfeat/CUCM_BK_C3E0EFA0_00_cucm-features-services-guide-91.html
Cisco Jabber and Jabber IM:

http://www.cisco.com/en/US/products/ps11678/tsd_products_support_series_home.html (Cisco Jabber for Android)
http://www.cisco.com/en/US/products/ps12746/tsd_products_support_series_home.html (Cisco Jabber IM for
Android)
http://www.cisco.com/en/US/products/ps11763/tsd_products_support_series_home.html (Cisco Jabber IM for
BlackBerry)
http://www.cisco.com/en/US/products/ps12430/tsd_products_support_series_home.html (Cisco Jabber for iPad)

http://www.cisco.com/en/US/products/ps11596/tsd_products_support_series_home.html (Cisco Jabber for iPhone)
BRKUCC-2060
Cisco Public
96
For
Your
Reference
Additional Resources 2 of 2
For additional information about Cisco mobile collaboration solutions:

Consult product documentation and collateral (cont.):
Cisco AnyConnect and WebEx Mobile:

http://www.cisco.com/web/products/voice/docs/c07_717020_00_jabber_guide.pdf (Cisco AnyConnect Deployment Guide for
Cisco Jabber)
http://www.cisco.com/en/US/products/ps10884/tsd_products_support_series_home.html (Cisco AnyConnect Secure Mobility
Client)
http://www.webex.com/products/web-conferencing/mobile.html (Cisco WebEx Meetings/Mobile)
Cisco Bring Your Own Device (BYOD):

http://www.cisco.com/go/byoddesign (Cisco BYOD Smart Solution Design Guide)
http://www.cisco.com/en/US/products/ps11640/tsd_products_support_series_home.html (Cisco Identity Services Engine)
http://www.cisco.com/en/US/netsol/ns1051/index.html (Cisco TrustSec Security Solutions)
BlackBerry Mobile Voice System (MVS) solution:

http://www.blackberry.com/mvs
http://www.blackberry.com/mvs5demo
BRKUCC-2060
Cisco Public
97
Recommended Reading for BRKUCC-2060
BRKUCC-2060
Cisco Public
98
Call to Action
Visit the Cisco Campus at the World of Solutions
to experience the following demos/solutions in action:
A. The New Collaborative Workspace for the Post PC Era (Cisco
TelePresence and Jabber, WebEx meeting and social with mobile devices,
customer collaboration with Finesse and Social Miner, Virtualization Experience
Client 6215)
F. Collaboration: Empower, Engage, Innovate (Cisco TelePresence,

mobile devices with Cisco Jabber and WebEx (social) applications)
Get hands-on experience with the following Walk-in Lab

LABUCC-2009 Webex Administration Interface
Meet the Engineer

Book face-to-face meeting or got to MTE village for ad-hoc meeting.
Jordy will be available after this session until MTE village closes
Discuss your projects challenges at

the Technical Solutions Clinics
BRKUCC-2060
Cisco Public
99
Feedback BRKUCC-2060
BRKUCC-2060
Cisco Public
100
100
Appendix
BRKUCC-2060
Cisco Public
102
Administrative and/or
user configurable:
Destination number(s)
and enable/disable.
Single Number Reach (SNR): Mobile Connect
Calls to user's
enterprise number
are extended to
user's enterprise
device and mobile
device. Answer at
either device.
!
CAUTION
Reach Me
Anywhere
PSTN
Mobile Voice
Network
(Carrier)
PSTN
Gateway
Cisco Unified
Communications
Manager
Simultaneous ring
not sequential.
Not just a mobile device: Can
be any off-system destination
home, travel location, etc..
Mobile Device
Cisco Unified
Mobility User
Up to ten destination numbers/devices.

BRKUCC-2060
Cisco Public
103

Desk Phone and Mobile Phone Pickup
Active call can be

moved between
mobile device and
enterprise device
Desk phone pickup:
Hang up at mobile,
resume at desk
phone.
Mobile device pickup:
Mobility softkey at
desk phone ('Send
call to mobile'),
answer at mobile.
BRKUCC-2060
PSTN
PSTN
Gateway
Mobile Voice
Network
(Carrier)
Cisco Unified
Communications
Manager
ACTIVE
Mobile Device
ACTIVE
Cisco Unified
Mobility User
Cisco Public
104

Call Filtering: Caller ID and Time of Day
Calls to user's
enterprise number can
be filtered to prevent or
allow extension of call
to user's mobile device:
1. Allowed/blocked
Administrative and/or
user configurable:
Access lists and ring
schedule.
PSTN
Mobile Voice
Network
(Carrier)
access lists for

filtering based on
incoming caller ID
(specific or range,
unknown or private)
2. Time of day filtering based on
Caller ID filtering e.g.:

408 555 1234
408 555 XXXX
408!
Not Available
Private
Time of day filtering e.g.:

Ring
mobile any
Cisco
Unified
time.
Communications
Ring mobile M-F
Manager
8:30 AM 5:30 PM
PSTN
Gateway
STOP
Mobile Device
Cisco Unified
Mobility User
configured ring schedule

BRKUCC-2060
Cisco Public
105

2-Stage Enterprise Dialing: Mobile Voice Access and Enterprise Feature Access
User can make calls

from mobile device
using the enterprise line
and IP telephony
network
Why? Cost savings,

mobile number masking,
and access to internalonly extensions
PSTN
Mobile Voice
Network
(Carrier)
PSTN
Gateway
Cisco Unified
Identification
and
Communications
Authentication:
Manager
Identification via
caller ID or user
input (Mobile Voice
Access only)
Method 1: Mobile Voice

Access IVR-based
Cisco Unified
Mobility User
feature
Mobile Device
Method 2: Enterprise Feature Access DTMFbased feature
BRKUCC-2060
Cisco Public
Authentication via
user PIN
106

Call Flow: Mobile Connect
3
Call placed to configured

Remote Destination
Dial:
919 555 1234
Matthew Jordy
Cisco Systems, Inc.
7100-9 Kit Creek Road
RTP, NC 27709
Email: mjordy@cisco.com
Call to Remote Destination

routed via enterprise
gateway to PSTN
(919) 444-6789
1
PSTN
Phone: (919) 555-1234
Mobility-enabled user
reachable via a single
number (enterprise)
Caller dials user's
enterprise number
and call received by
system
BRKUCC-2060
Cisco Unified
Mobile Device
Mobile Voice
Network
(Carrier)
PSTN
Gateway
Remote
Destination:
(919) 444-6789
Both devices ring. User

answers at either device.
Enterprise Number
Call extended to
enterprise device
Call extended to
Remote Destination
Profile via shared line
Remote
(919) 555-1234 Destination
Profile
SHARED LINE
Cisco Public
107

Call Flow: Enterprise 2-Stage Dialing Mobile Voice Access
Enterprise 2-stage
dialing user-system
interaction:
On answer at target, media

hairpinned in enterprise
PSTN gateway
User identified by
inbound caller ID user
prompted to enter
mobile number if caller
ID not received (MVA
only).
Caller ID at target is user's

enterprise number
User selects '1' to make

call and enters target
number.
Alternatively enters '2'
to enable or '3' to
disable Mobile Connect.
Enterprise Feature
Access operates the
same way, but no IVR
prompts and user can
only be identified by
inbound caller ID
BRKUCC-2060
(408) 777-6543
Dial:
919 222 3456
1
Mobile Device
dials system Mobile
Voice Access number
Call routed to
enterprise PSTN
gateway
Call placed to user entered

target number
Call routed via enterprise
gateway
toUnified
PSTN
Cisco
User prompted for PIN

number to authenticate
Inbound caller
ID: 919 555-1234
PSTN
Mobile Voice
Network
(Carrier)
3
PSTN
Gateway
Mobile Voice Access

number: 919 222 3456
Communication
between PSTN
gateway and Unified
CM
Exchange of voice
prompts and user key
presses
Remote
Destination:
(919) 444-6789
Enterprise Number
Remote
(919) 555-1234 Destination
Profile
SHARED LINE
Cisco Public
108
Keep in mind impact of settings/timers:

Per user: No Answer Ring Duration (line-level)
Global: Forward No Answer Timer (service parameter)

Remote Destination Timers
There are 3 timers which impact the behavior of Unified Mobility:

1. Delay Before Ringing Timer (Default 4000 milliseconds (4 seconds))
2. Answer Too Soon Timer (Default: 1500 milliseconds (1.5 seconds))
Mobile
voicemail
avoidance
Determines answer interval in which Unified CM will disconnect call leg to remote destination if
answer indication is received.
Increase or decrease based on how quickly mobile provider sends calls to mobile voicemail when
out-of-range or powered off
3. Answer Too Late Timer (Default: 19000 milliseconds (19 seconds))
Inbound call to
enterprise
number extended
to users
enterprise device
/number
Determines interval/threshold at which Unified CM will disconnect call leg to remote destination
Increase or decrease based on how long it takes mobile provider to send unanswered calls to
Call forwards to
mobile voicemail
If mobile VM answers within
this range, call leg cleared.
Other devices continue to ring.
Delay Before Ringing

Timer
Answer Too
SoonTimer
0s
BRKUCC-2060
5.5 s
4 sCisco and/or its affiliates. All rights reserved.

2013
If mobile VM answers within

this range, message will end
up in mobile VM box
Answer Too
LateTimer
Cisco Public
enterprise
voicemail
Mobile VM
Answers
18.5 s
23 s
109

Mobile Voice Access v. Enterprise Feature Access 2-Stage Dialing Comparison
Mobile Voice Access
Enterprise Feature Access
Configuration
requirements
H.323 or SIP VXML gateway + Mobile Voice

Access DID
Enterprise Feature Access DID
IVR
Yes
No
Authentication
End-user PIN #
End-user PIN #
Identification
Based on caller ID or user entry
Based on caller ID only
Calling phone
Call can be made from any PSTN phone
Call must be made from remote

destination phone
Mobile Connect
enable/disable
2 to enable, 3 to disable, any remote

destination
2 to enable, 3 to disable, only for calling

remote destination
Redundancy
None
Fully redundant
(Publisher required)
Both Mobile Voice Access and Enterprise Feature Access can be enabled
and in use simultaneously
BRKUCC-2060
Cisco Public
110

Mid-Call Feature Key Sequences
Default Enterprise Feature
Access Codes
Manual Key sequence
Hold
*81
*81
Exclusive Hold
*82
*82
Resume
*83
*83
Function
Transfer
Conference
Session Handoff
BRKUCC-2060
*84
1. Enter: *82 (Exclusive Hold)

2. New call to "Enterprise Feature Access" DID
3. On connect enter: <PIN_number> # *84 # <Transfer_Target/DN> #
4. Upon answer by transfer target (for consultive transfer) or upon ring
back (for early attended transfer) enter: *84
*85
1.
2.
3.
#
4.
*74
Enter: *82 (Exclusive Hold)

New call to "Enterprise Feature Access" DID
On connect enter: <PIN_number> # *85 # <Conference_Target/DN>
Upon answer by conference target enter: *85
1. Enter: *74
2. Answer at the desk phone upon ring and/or flash.
Cisco Public
111

Design Considerations: Scalability
Cisco Unified Mobility supports the following capacities:

Server Type*
Mobility-Enabled
Users per Cluster
Mobility-Enabled
Users per Node
MCS-7845
15,000
3,750
MCS-7835
10,000
2,500
MCS-7825
4,000
1,000
* Or virtualized equivalent
What is a mobility-enabled user? A user that has a Remote Destination Profile

and at least one Remote Destination configured
Capacity numbers are based on a single Remote Destination per user

As number of Remote Destinations per user increases, the number of mobilityenabled users decreases
BRKUCC-2060
Cisco Public
112

Design Considerations: PSTN
PSTN Connectivity
DTMF Relay: DTMF must be relayed out-of-bound (OOB) from PSTN
PSTN
to Unified CM for mid-call features, Enterprise Feature Access 2-stage

dialing, and user control DTMF-based* mobile voicemail avoidance.
TDM Connectivity: PRI required (no T1/E1-CAS, FXO, FXS, or BRI) for
timely connect/disconnect indication to Unified CM.
VoIP Connectivity: Service provider SIP trunk with Cisco Unified

Border Element demarc and no DTMF mid-call features (DTMF
interop)
Requires Unified CM 6.1(2) and later or 7.1(2) and beyond.

If provider uses codec other than G.711 ulaw, then transcoders are required for
Mobile Voice Access.
* Coming soon with Unified CM 9.0

BRKUCC-2060
Cisco Public
113

Enterprise Voice over IP Calling
Cisco mobile clients

register to Unified CM via
SIP:
Mobile device behaves just
like an enterprise phone
Voice over WLAN and voice over

mobile data calling available with Cisco
Jabber for Android, iPad, and iPhone.
Mobile Voice
Network
(Carrier)
IP voice path via WLAN

(802.11 a/b/g/n) or mobile
data network
Voice quality over mobile data
networks or non-enterprise
WLANs cannot be guaranteed.
Enterprise calling features

abbreviated extension dialing,
call hold/resume, call transfer,
conference calling, and call park
BRKUCC-2060
PSTN
PSTN
Gateway
Cisco Unified
Communications
Manager
VoIP
WLAN
(802.11)
Mobile Client
Device
SIP
Mobile Data
Network
(Data Channel)
WLAN
Hotspot
(802.11)
SIP signaling
Internet
VoIP
Media path
(VoIP)
Cisco ASA
Cisco Public
114

Enterprise voicemail integration is an
optional feature and available with
Cisco Jabber for Android, iPad, and
iPhone. Requires Cisco Unity
Connection.
Enterprise Voicemail Integration
Cisco mobile clients provide

access to enterprise
voicemail services:
Enterprise message waiting
indication (MWI) and visual
voicemail enabling visual
navigation of the enterprise
voicemail box via
IMAP/VMREST
Messages downloaded on
demand and played via phone
no need to navigate TUI
User may also click-to-call

enterprise voicemail system
BRKUCC-2060
Mobile Voice
Network
(Carrier)
Cisco Unified
Communications
Manager
PSTN
PSTN
Gateway
Cisco Unity
Connection
WLAN
(802.11)
Mobile Client
Device
IMAP/VMREST
Mobile Data
Network
(Data Channel)
U
IMAP/Visual
voicemail access
Internet
Cisco ASA
Cisco Public
Voice/TUI
voicemail access
115

Enterprise Directory Integration

provide access to
enterprise LDAP-compliant
directory services:
Enterprise directory access is an optional

feature available with Cisco Jabber for
Android, iPad, and iPhone. Requires specific
LDAP compliant directory.
Mobile Voice
Network
(Carrier)
PSTN
Search corporate directory

Add corporate directory
contacts to contact
lists/phonebooks and
buddy lists
PSTN
Gateway
Cisco Unified
Communications
Manager
WLAN
(802.11)
Mobile Client
Device
LDAP
LDAP
Directory
Mobile Data
Network
(Data Channel)
Internet
Cisco ASA
BRKUCC-2060
Cisco Public
116

Enterprise IM & Presence: Cisco Unified Presence and Cisco WebEx Connect

provide access to XMPPbased instant messaging
and presence services:
Enterprise IM and presence available with Cisco

Jabber IM for Android, BlackBerry, iPad, and
iPhone. Requires enterprise hardware/software
Cisco Unified
and license or WebEx
enablement/licensing.
Communications
Mobile Voice
Network
(Carrier)
PSTN
Cisco Unified
Presence may be
leveraged for onpremise integration
Cisco WebEx Connect
may be leveraged for
cloud-based
integration
PSTN
Gateway
Cisco Unified
Presence
(ONPREMISE)
WLAN
(802.11)
Mobile Client
Device
Cisco ASA
Mobile Data
Network
(Data Channel)
XMPP
On-premise
XMPP
Internet
XMPP
BRKUCC-2060
Manager
Cloud-based
XMPP
Cisco WebEx
(CLOUDBASED)
Cisco Public
117

Call Flow: Mobile Client and Mobile Connect
When mobile client device is NOT

attached to the enterprise network
call extended to Mobility
Identity/mobile client device on
mobile voice network/PSTN via
enterprise gateway.
reachable via a single
number (enterprise)
Caller dials user's
enterprise number
and call received by
system
Dial:
919 555 1234
(919) 444-6789
1
PSTN
Mobile Client
Device
(Mobility Identity)
Inbound call leg
Outbound call leg
(device inside/
attached to enterprise)
Outbound call leg

(device outside/NOT
attached to enterprise)
BRKUCC-2060
Cisco Unified
PSTN
Gateway
Mobile Voice
Network
(Carrier)
Same
Device
3
2
WLAN
(802.11)
Enterprise Number
(919) 555-1234
Call extended to enterprise device(s)

When mobile client device is attached
to the enterprise network device
receives call via VoIP. Call NOT
extended to Mobility Identity.
Enterprise Line
Cisco Public
Cisco Unified
Mobility User
118

Mobile client on mobile

device registers to
Cisco Unified CM as
users enterprise IP
phone.
Mobile number is
configured as a Mobility
Identity for Cisco
Unified Mobility.
Mobile Voice
Network
(Carrier)
ENTERPRISE
PHONE
PSTN
PSTN
Gateway
VoIP and DVO calling, visual

voicemail, directory
integration, etc.
Single
Device
Mobile Connect (SNR),

WLAN
(802.11)
voicemail avoidance,
Mobile Client
Device
Mobile Data
Network
MOBILITY
IDENTITY
Mobile Device
mobile
enterprise 2-stage dialing
(Data Channel)
BRKUCC-2060
Cisco Unified
Communications
Manager
Cisco Unified
Mobility User
Cisco Public
119

Cisco Unified Mobility Integration: Dual-Ring Avoidance
Incoming calls are NOT

1st: VoIP
2nd: Mobile
Connect
Call 51234
Call 1 408 555-1234
Cisco Unified
routed to Mobility Identity
PSTN
via Mobile Connect when
Gateway
client device
SIPisDual Mode Alert Timer service parameter:
PSTN CM checks for
connectedDetermines
to the
how long Unified
enterpriseCisco
and registered
WLAN
mobile SIP client
connectivity before
Mobile Voice
(802.11)
Network
to Cisco Unified
CM
extending call to Mobility
Identity (via Mobile
Cisco Unified
(Carrier)
Mobility User
Connect).
Incoming calls
are routed
to Mobility Identity via
Enterprise Number
Default is 1500 milliseconds
(408) 555-1234
Mobile Connect when
client device
is not
Recommend
minimum of 4500
milliseconds
Mobility Identity
Enterprise Line
Same
(NO
Enterprise
connected/registered to
(Enterprise
Attachment)
Device
Attachment)
enterprise (assuming Mobile
Connect is enabled and call

filtering/time of day routing permits)
BRKUCC-2060
Mobile Client Voice Network

Connectivity Only
Mobile Client Enterprise

Connectivity
NOTE: Incoming calls directly to the mobile phone number will ring the mobile voice/
cellular
interface even when the dual-mode phone
is associated to the enterprise WLAN.120
Cisco Public

Design Considerations: SIP Profile
To ensure that Cisco Jabber client maintains registration and connectivity to

Unified CM even when running in the background, a SIP profile should be
associated to the mobile client device.
Required Cisco Jabber SIP Profile Parameters

Default values
Android
iPad
iPhone
Timer Register Delta
120
60
60
Timer Register Expires
720
660
660
Timer Keep Alive Expires
720
660
660
Timer Subscribe Expires
720
660
660
Timer Subscribe Delta
15
15
Note: Values in red are non-default and must be configured on respective profile
BRKUCC-2060
Cisco Public
121

Cisco Unified CM: Associated Mobile Identity - Device Configuration
Mobility Identity associated to
the Cisco Dual Mode client
device is used for:
Mobile Connect
Dial via Office
BRKUCC-2060
Cisco Public
122

Cisco Unified CM: Mobile Identity Configuration
Mobility Identity: Corresponds to user's

mobile carrier phone
number
Voicemail Avoidance: User Control (DTMF-based) method
selected. Answer Too Soon Timer does not
take affect unless Time Control selected
Mobility Profile: Assigned to this dual-mode device
Dual Mode Phone: The device the
mobility identity is associated with
Mobile Connect: On/Off
BRKUCC-2060
Cisco Public
123
Coming
Soon

Dial via Office Calling Options: Call Flow Summary (1 of 2)
Always Use Internet
Always Use DVO

Cellular/PSTN:
Inbound AND
outbound calling
via PSTN/mobile
voice network
PSTN
PSTN
Gateway
PSTN
PSTN
Gateway
Mobile Voice
Network
Mobile Voice
Network
Cisco Unified CM
Cisco Unified CM
Enterprise
WLAN
(802.11)
Enterprise
WLAN
(802.11)
Cisco ASA
Cisco ASA
Public/Private
WLAN
(802.11)
Public/Private
WLAN
(802.11)
Mobile Data
Network
(Data Channel)
Mobile Data
Network
(Data Channel)
VoIP
Internet
Internet
DVO and Mobile Connect
Call signaling
Voice media
BRKUCC-2060
VoIP:
Inbound AND
outbound calling
via IP network
(signaling and
media)
No PSTN/cellular network traversal except

when client is not registered (dual-ring
avoidance) or when called or calling
number is PSTN-based.
Cisco Public
124
Coming
Soon

Dial via Office Calling Options: Call Flow Summary (2 of 2)
Mobile Data Connection
802.11 Connection
Cellular/PSTN:
Inbound AND
outbound calling
via PSTN/mobile
voice network
PSTN
PSTN
Gateway
PSTN
Mobile Voice
Network
Mobile Voice
Network
Cisco Unified CM
Cisco Unified CM
Enterprise
WLAN
(802.11)
Public/Private
WLAN
(802.11)
Mobile Data
Network
(Data Channel)
Enterprise
WLAN
(802.11)
Public/Private
WLAN
(802.11)
Cisco ASA
Mobile Data
Network
(Data Channel)
Internet
DVO and Mobile Connect
Call signaling
Voice media
BRKUCC-2060
PSTN
Gateway
Cisco ASA
VoIP:
Inbound AND
outbound calling
via IP network
(signaling and
media)
VoIP
Internet
No PSTN/cellular network traversal except

when client is not registered (dual-ring
avoidance) or when called or calling
number is PSTN-based.
Cisco Public
125

Cisco Unified Mobility Integration: Multiple Mobile Client Devices
When deploying multiple Cisco mobile clients for a single user:

Always configure/associate the Mobility Identity on the smartphone client device
Always configure/associate the Remote Destinations on the same client device
as the Mobility Identity. Cisco Dual Mode for iPhone/
Android
408 555-7890
Mobility Identity
IP Phone
408 555-6789
XXX XXX-XXXX
No Remote Destination Profile
Shared Line
Maximum of 1 Mobility
Identity and 9 Remote
Destinations per user
BRKUCC-2060
Cisco Public
126
Cisco Mobile Clients

Cisco Jabber for iPad: IM and Presence Deployment Models
Jabber for iPad may be deployed with a variety of call control and IM/presence
combinations:
IM/presence-only deployments: On-premises (Cisco IM & Presence) OR
cloud-based (Cisco WebEx Messenger)
Voice/video-only deployments: Cisco Unified CM OR Cisco TelePresence VCS
Voice/video and IM/presence deployments: When deploying Cisco VCS call control,
IM/presence services must be cloud-based (Cisco WebEx Messenger)
IM and Presence-Only
Deployments
hello
Voice/Video and IM/Presence

Deployments
Voice-Only & Voice/Video-Only

Deployments
OR
Cisco
OR
WebEx
Messenger
OR
hello
Cisco
Cisco IM & Presence

(on-premises)
Cisco WebEx
(cloud-based)
WebEx
Messenger
Cisco Unified CM
OR
Cisco
WebEx
Messenger
Cisco VCS
Cisco WebEx
(cloud-based)
BRKUCC-2060
Cisco VCS
Cisco Unified CM
Cisco Public
Cisco IM & Presence

(on-premises)
Cisco WebEx
(cloud-based)
127
Caller ID

Design Considerations: Caller ID
The following design-related information should be considered when deploying Cisco mobile
client solutions:
Inbound Caller ID to Enterprise Service provider must send appropriate inbound caller ID to
enterprise if any of the following are required:
Hand-out (WLAN to cellular) for Cisco Jabber for iPhone (Handoff DN method only).
Any Unified Mobility features that rely on inbound caller ID (DTMF-based mid-call features, automatic
inbound call anchoring, Enterprise Feature Access 2-stage dialing).
Outbound Caller ID from Enterprise
All VoIP and Dial via Office calls will send users enterprise number rather than the users mobile
number.
Caller ID Handling at the Mobile Client Device
Inbound calling number presentation for calls delivered via the IP network is dependent exclusively
on Unified CM configuration (transformation, phone number masks, etc.)
Most smartphone devices translate calling number presentation to calling name by leveraging
local native phone book/contact list (e.g. iOS, Android, BlackBerry).
Translation to calling name will be dependent on number format received and stored number phone book/contact list
format.
If mobile device does not have native phone book, then number will be presented as received from
the IP or mobile provider network
BRKUCC-2060
Cisco Public
128
128
For more information on Cisco BYOD Smart Solution Infrastructure

refer to the Cisco Bring Your Own Device Smart Solution Design
Guide available at http://www.cisco.com/go/byoddesign
Bring Your Own Device (BYOD) Access Use Cases

Basic Access
Basic Internet-only
access for guest/
PSTN
Gateway
Cisco Jabber
Mobile Voice
Network
(Carrier)
PSTN
Cisco Unified
Communications
Manager
Limited Access
Full access for
Cisco Unified
802.11
WLAN
Cisco AnyConnect
Cisco
WLAN
Controller
Certificate
Authority
(CA)

Enhanced Access
Granular access for
corporate and guest/
personal devices: Enable corporate and personal
device network connectivity with
granular access to corporate
resources based on policy
BRKUCC-2060
Employee-Owned
and/or CorporateOwned
Mobile Device
Mobile Data
Network
(Data Channel)
Internet
Mobile Device
Manager
(MDM)
Cisco Adaptive
Cisco Identity
Security Appliance
Services
(ASA)
Engine (ISE)
Cisco Prime
Network Control
System (NCS)

Cisco Public
LDAP
Directory
129

BRKUCC-2060 - Cisco Collaboration Enterprise Mobility Solutions (2013 London)

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BRKUCC-2060 - Cisco Collaboration Enterprise Mobility Solutions (2013 London)

Hochgeladen von

Copyright:

Verfügbare Formate

Session BRKUCC-2060

Cisco Collaboration Enterprise

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

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

Please consult the latest applicable product

Please ask questions as we go 3 types of questions:

Come see me after session to chat and/or leave your

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

Complete the Online

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

Cisco Collaboration Mobility Solutions Overview

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

Cisco Collaboration Mobility Solutions

Cisco Unified Mobility

Cisco Mobile Clients

VPN IP Phone or Soft Client

Cisco Collaboration Mobility Solutions

What is fixed mobile convergence?

Integrating or linking a user's enterprise line with their mobile line

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

Cisco Collaboration Mobility Solutions

What is fixed mobile substitution?

Moving or enabling the enterprise line on the user's mobile device

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

Cisco Unified Mobility

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

Cisco Unified Mobility

Cisco Unified Mobility

Cisco Unified Mobility provides

Cisco Unified Mobility includes the following

Single enterprise number for all calls whether handled by

Enterprise dialing from mobile devices for toll reduction,

Features delivered on any mobile phone regardless of mobile

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

Cisco Unified Mobility

Mobile Connect (SNR)

Incoming calls to users enterprise number rings both desk

Mobile Voice Access (MVA)

Provides the ability to make calls from mobile phone using

Enterprise Feature Access (EFA)

Provides identical functionality as Mobile Voice Access

Desk Phone/Remote Destination

Once incoming mobility call has been answered, call can

Provides the ability to invoke enterprise features Hold,

Single Enterprise Voicemail Box

Per Remote Destination timers ensure that when mobility

Per Remote Destination filtering allowing or blocking calls

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

IP desk phone is not required. Remote

Cisco Unified Mobility

Unified Mobility User

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

Cisco Unified Mobility

For all inbound calls to Cisco Unified CM the caller ID is automatically

Inbound caller ID:

If a match is found, user is identified and call is anchored in the enterprise

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

Cisco Unified Mobility

Mobile Voice Access Call

Inbound Calls from

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

Cisco Unified Mobility

Two ways to ensure

1. Timer Control: Answer Too