Cisco Jabber configuration

2. Understanding
Cisco Jabber
Service Discovery &
Client Configuration
Seongho Hong, Technical Marketing Engineer
BRKCOL-2344

3. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
How
cs.co/clus17/#BRKCOL-2344Cisco Spark spaces will be
available until July 3, 2017.

4. • What is Service Discovery
• Tuning Service Discovery
• Service Discovery Scenarios
• Finding Home Cluster
• Configuration Considerations
• Configuring for Mobile
• Closing Thoughts
Agenda

5. What is Service Discovery

6. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Service Discovery is for Cisco Jabber to…
Subscribe to…
UC Services
Discover…
UC Services
Determine…
Deployment Type
Cloud or On-Premises
Detect…
Edge Location
Inside or Outside
BRKCOL-2344 6

7. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Why Service Discovery?
Cisco Jabber’s cross-platform initiative
Minimizes the chance for misconfiguration
Reduces help desk support calls
Enhances the first time user experience
BRKCOL-2344 7

8. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 8BRKCOL-2344
First Time Jabber Experience… Good or Bad?
OR
Service
Discovery

9. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 9BRKCOL-2344
Three Key Components in Service Discovery
Send HTTP
Request &
DNS
Queries
Connect to
Primary
Authenticator
Download
Configs
Full Service Discovery

10. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 10BRKCOL-2344
Sending HTTP Request and DNS Queries
Messenger
http://loginp.webexconnect.com/cas/
FederatedSSO?org=[domain_name]
DNS
Queries
Internal or
externalHTTP
Request to
CAS*
* CAS: Connect Authentication Service
DNS
SRV Records:
_cisco-uds._tcp.<domain_name>
_cuplogin._tcp.<domain_name>
_collab-edge._tls.<domain_name>

11. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 11BRKCOL-2344
Determining Deployment Type (HTTP Request)
Messenger
OR• Jabber is deployed in either cloud or
hybrid model
• Primary Authenticator = WebEx
Messenger
• Returns from DNS queries will used only
for edge detection
• Jabber is deployed in on-premises
model
• Primary Authenticator = Unified CM
• Returns from DNS queries will be
used to find Unified CM and for edge
detection
Messenger
Am I your
organization?
Yes
Am I your
organization?
NO

12. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 12BRKCOL-2344
Detecting the Edge (DNS Queries)
OR
• Jabber is inside the corporate network
• Traffic is directed to Unified CM
• Jabber is outside the corporate network
• Traffics is transformed using base64 and
directed via Expressway
_cisco-uds
Unified
CM
DNS
_collab-edge
Expressway-E
DNS
Caution:
• _cisco-uds should never be
deployed in the external DNS.
• If both return, _collab-edge will
be ignored.
Expressway-C

13. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
When any of the configuration re-fetch timers expires n/a Yes
When the manual Refresh Configuration is initiated by the user n/a Yes
11.9 or later
with Fast Login
Enabled
Yes
No
Yes
Yes
13BRKCOL-2344
What Triggers Full Service Discovery?
Triggering Event 11.8 or earlier
First time user login (after new installation with no locally cached
config info) Yes
Subsequent user login (with locally cached config info) Yes
Network change events (e.g. the user moves into the corporate
network or VPN gets turned on) Yes
Transport errors (SIP, XMPP & HTTP) (e.g. the user moves out
from the corporate network) Yes
New in
11.9

14. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 14BRKCOL-2344
Required Information for Service Discovery
• Send HTTP Request
• Send DNS Queries
• Connect to Unified CM or
WebEx Messenger*
• Download Configurations
* WebEx Messenger requires
user_name@domain_name
Domain
(Name)
User
Name

15. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Setting Service Discovery Domain at First Login
• Manual entry by end user
• username@<domain_name>
• May or may not be user’s email address
• Automatic discovery using UPN
• Jabber for Windows only
• Pre-set by administrator
• MSI Transformation (Windows only)
• Configuration URL (Mac, iOS & Android)
• EMM* (iOS, Android)
• jabber-config.xml
BRKCOL-2344 15
* EMM: Enterprise Mobility Management
smckenna@
example.com
Service
Discovery
Tuning

16. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Subsequent Login Process
• In 11.8 or earlier:
• Run the full service discovery
• Use cached information for user name and
service discovery domain  no need to be
provided
• In 11.9 or later with fast login enabled:
• Will not run the full service discovery
• Use cached information to attempt to connect
to UC services  no need to be provided
• Send DNS queries in the background to
determine if the edge connection is required
BRKCOL-2344 16
New in
11.9

17. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Service Discovery Using Microsoft Windows UPN
• Jabber for Windows will not prompt user to enter
login credentials until the user’s Windows
machine is connected to a network
• Once a network connection becomes available,
Jabber will initiate service discovery
• Jabber will use domain UPN (User Principal
Name) for service discovery
UPN=username@<user_dns_domain>
e.g. UPN=smiller@example.com
example.com is used as service discovery domain
smiller is used for home cluster discovery
• Can be disabled (enabled by default) during
installation using MSI file ( fall back to manual)
UPN_DISCOVERY_ENABLED=false
17BRKCOL-2344
Type “set” at the prompt to display information above.
Network becomes
available
No first
login
screen!

18. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 18BRKCOL-2344
Different Ways to Set Service Discovery Domain
Jabber
Platform
UPN Manual MSI
Transformation
Configuration
URL
EMM jabber-
config.xml
Android ✔ ✔ ✔ ✔
iOS ✔ ✔ ✔ ✔
Mac ✔ ✔ ✔
Windows ✔ ✔ ✔ ✔
The domain Jabber uses to send HTTP request to WebEx Messenger and DNS queries to DNS server
✔: Default No additional
work from admin
Additional work from
admin is required

19. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 19BRKCOL-2344
Services Domain vs. Voice Services Domain
Services Domain
• Domain used to send HTTP request
to WebEx Messenger
• Set automatically equal to Service
Discovery Domain (from end user
or UPN on Windows) unless explicitly
preset by system admin
• Can be preset via MSI, URL, or EMM
Voice Services Domain
• Domain used to send DNS queries to
DNS server
• Set automatically equal to Services
Domain unless explicitly preset by
system admin
• Can be preset via MSI, URL, EMM,
or jabber-config.xml
• Recommended only for hybrid
deployments

20. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 20BRKCOL-2344
Services Domain vs. Voice Services Domain (Cont.)
DNS
DNS queries using
VoiceServicesDomain
Messenger
HTTP CAS request
using ServicesDomain
ServicesDomain
VoiceServicesDomain
Service Discovery
Domain from User or
Windows UPN
AND/OR
Admin presets:
ServicesDomain
VoiceServicesDomain

21. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 21BRKCOL-2344
Setting Domains for Service Discovery – Example 1
ServicesDomain
= example.com
Messenger
http://loginp.webexconnect.com/cas
/FederatedSSO?org=example.com
DNS
_cisco-uds._tpc.example.com
_cuplogin._tcp.example.com
_collab-edge._tls.example.com
End User Input or
Windows UPN
example.com
VoiceServices
Domain =
example.com

22. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 22BRKCOL-2344
Setting Domains for Service Discovery – Example 2
ServicesDomain
= example.com
Messenger
http://loginp.webexconnect.com/cas
/FederatedSSO?org=example.com
DNS
_cisco-uds._tpc.example.com
_cuplogin._tcp.example.com
_collab-edge._tls.example.com
Admin presets:
ServicesDomain
=example.com
VoiceServices
Domain =
example.com

23. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 23BRKCOL-2344
Setting Domains for Service Discovery – Example 3
ServicesDomain
= example.com
VoiceServices
Domain =
uc.example.com
Messenger
http://loginp.webexconnect.com/cas
/FederatedSSO?org=example.com
DNS
_cisco-uds._tpc.uc.example.com
_cuplogin._tcp.uc.example.com
_collab-edge._tls.uc.example.com
Recommended only for hybrid deployments
where WebEx Messenger domain is not same
as on-premises UC domain!
OR
Admin presets:
ServicesDomain
=example.com
VoiceServicesDomain
=uc.example.com
End User Input or
Windows UPN
example.com
Admin presets:
VoiceServicesDomain
=uc.example.com

24. Tuning Service Discovery

25. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Fine-Tuning for Best User Experience
• Administrative ability to provide/preset information at the beginning of the
service discovery process
• No need to manually enter username@domain_name on first login
• Highly recommended especially when:
• Using not-well-known domains
• UC services domain ≠ WebEx domain (in hybrid deployments)
• Service(s) needs to be excluded
Service
Discovery
Configuration URL
MSI Transformation
EMM App Config
Best End User
Experience
BRKCOL-2344 25

26. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 26BRKCOL-2344
Configuration Keys for Service Discovery Tuning
Key for Services
Domain
Key for Voice Services
Domain
Key for Service Exclusion
MSI
Transformation
SERVICES_DOMAIN VOICE_SERVICES_DOMAIN EXCLUDED_SERVICES
Configuration
URL
ServicesDomain VoiceServicesDomain ServiceDiscoveryExcludedServices
EMM App
Config
ServicesDomain VoiceServicesDomain ServiceDiscoveryExcludedServices
jabber-
config.xml
Not Available VoiceServicesDomain ServiceDiscoveryExcludedServices

27. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
MSI Transformation for Jabber for Windows
MS Orca tool for transforming .msi file
Use CiscoJabberProperties.mst file to
transform CiscoJabberSetup.msi
msiexec /i CiscoJabberSetup.msi SERVICES_DOMAIN=example.com
VOICE_SERVICES_DOMAIN=uc.example.com
BRKCOL-2344 27
Or, use the command installer switches:

28. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Configuration URL for Non-Windows Platforms
• Works on Mac, Android & iPhone/iPad
• Download/install Jabber prior to executing configuration URL
• During installation, Jabber registers ciscojabber protocol handler
• URL can be sent to users via email or on a web page
ciscojabber://provision?ServicesDomain=example.com&VoiceServicesDomain=example.corp
• As user clicks the URL, Jabber will be cross-launched and the information in the
URL will be used for service discovery
28BRKCOL-2344

29. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Messenger
29BRKCOL-2344
Service Discovery Tuning using jabber-config.xml
• Jabber downloads from Unified CM
(uploaded by admin)
• Must login inside the corporate network
at least once (even for the hybrid model)
• Jabber downloads from WebEx Messenger
Org Admin (uploaded by admin)
• Requires Jabber 11.5 or higher
• The first time login doesn’t have to be inside
the corporate network
Unified
CM
jabber-config.xml
jabber-
config.xml
Caution: When jabber-config.xml exists in both Unified CM and WebEx Messenger,
the configurations from WebEx Messenger take higher priority.
OR

30. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Excluding UC Service(s) during Service Discovery
• Use configuration parameters to exclude
certain UC service(s) during the service
discovery process
• ServiceDiscoveryExcludedServices in
configuration URL or EMM App Config
• EXCLUDED_SERVICES in MSI transformation
• Possible values: CUCM, CUP, WEBEX
• Common use cases
• WebEx Messenger had been trialed (it’s no
longer used but the domain is still registered)
• A subset of people need to Jabber in the phone
only mode
30BRKCOL-2344
Messenger
smckenna
@
example.com
Internal
DNS
DNS SRV
lookup
_cisco-uds
Unified CM
address
HTTP
Request to
CAS URL for
example.com
Exclude
WebEx
service

31. Service Discovery Scenarios

32. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Example Corporation
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM & IM/P
example.com
example.corp
ucm.example.corp
imp.example.corp
expwy-c.example.comexpwy-e.example.com
• On premises UC services only
• Internally use example.corp which is not resolvable from outside
• Externally use example.com which is publicly resolvable
• User’s email is username@example.com
• example.com not in WebEx
BRKCOL-2344 32

33. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Example Corporation – Service Discovery Option 1
• Create internal record for example.com
(the external domain is resolvable
inside)
• Users just enter their email address at
the first screen
• The admin may preset Services
Domain to example.com (user input is
not needed)
33BRKCOL-2344
Internal
DNS example.com
cpaige@example.com ServicesDomain=
example.com
OR

34. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 34BRKCOL-2344
Example Corporation – Service Discovery Option 1
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM & IM/P
example.com
example.corp
ucm.example.corp
imp.example.corp
expwy-c.example.comexpwy-e.example.com
cpaige@example.com
_collab-edge._tls.
example.com 
expwy-e.example.com
_cisco-uds._tcp.
example.com 
ucm.example.corp
cpaige@example.com
SRV Record
SRV Record
OR
ServicesDomain=
example.com
OR
ServicesDomain=
example.com
example.com

35. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Example Corporation – Service Discovery Option 2
• Create external DNS record for
example.corp (the internal domain is
resolvable outside)
• Users may enter their email address at
the first screen when the admin presets
Voice Services Domain to
example.corp
• The admin can preset Services Domain
to example.corp (user input is not
needed)
35BRKCOL-2344
External
DNS example.corp
ServicesDomain=
example.corp
VoiceServicesDomain=
example.corp
cpaige@example.com
OR

36. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 36BRKCOL-2344
Example Corporation – Service Discovery Option 2
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM & IM/P
example.com
example.corp
ucm.example.corp
imp.example.corp
expwy-c.example.comexpwy-e.example.com
cpaige@example.com
VoiceServicesDomain=
example.corp
_collab-edge._tls.
example.corp 
expwy-e.example.com
_cisco-uds._tcp.
example.corp 
ucm.example.corp
cpaige@example.com
VoiceServicesDomain=
example.corp
SRV Record
SRV Record
OR
ServicesDomain=
example.corp
OR
ServicesDomain=
example.corp
example.corp

37. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Example Corporation – Service Discovery Option 3
• Create a subdomain, uc.example.com,
in both internal and external DNS
• Users may get instructed to enter
uc.example.com at the first screen
• The admin can preset Services Domain
to uc.example.com to improve user
experience (user input is not needed)
• Highly recommended
37BRKCOL-2344
cpaige@uc.example.com ServicesDomain=
uc.example.com
OR
uc.example.com
Internal
DNS
External
DNS
uc.example.com

38. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 38BRKCOL-2344
Example Corporation – Service Discovery Option 3
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM & IM/P
example.com
example.corp
ucm.example.corp
imp.example.corp
expwy-c.example.comexpwy-e.example.com
cpaige@uc.example.com
OR
ServicesDomain=
uc.example.com
cpaige@uc.example.com
OR
ServicesDomain=
uc.example.com
_collab-edge._tls.
uc.example.com 
expwy-e.example.com
_cisco-uds._tcp.
uc.example.com 
ucm.example.corp
SRV Record
SRV Record
uc.example.com
uc.example.com

39. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 39BRKCOL-2344
Service Discovery in Hybrid Deployment
• Returned results from DNS queries
will not be used to find Unified CM
(still crucial for edge detection when
from outside)
• Users inside the corporate network
will have no problem connecting to
on-premises services
• UC Cluster(s) must be configured in
WebEx Messenger Org Admin
(otherwise, Jabber will not attempt to
connect to any on-premises
infrastructure)
• UC Cluster(s) in WebEx Messenger Org
Admin will take higher priority than
Unified CM Service Profile
• UC Cluster(s) in WebEx Messenger Org
Admin must specify the correct Home
Cluster information for each user (Home
cluster discovery will not be performed)
• Admin must preset Jabber so that it can
perform service discovery on two
domains to find WebEx Messenger
service and to discover DNS SRV
records

40. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 40BRKCOL-2344
Hymple Corporation – Hybrid Deployment
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM
hymple.com
uc.hymple.com
ucm.hymple.corp
expwy-c.hymple.comexpwy-e.hymple.com
Messenger
hymple.com
• IM and Presence from WebEx Messenger; on-premises voice/video services
• Internally use hymple.corp; externally use hymple.com
• Already deployed subdomain, uc.hymple.com, internally and externally
_collab-edge._tls.
uc.hymple.com 
expwy-e.hymple.com
SRV Record
hymple.corp
uc.hymple.com
_cisco-uds._tcp.
uc.hymple.com 
ucm.hymple.corp
SRV Record

41. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 41BRKCOL-2344
Hymple Corporation – User Option 1
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM
hymple.com
ucm.hymple.corp
expwy-c.hymple.comexpwy-e.hymple.com
cpaige@uc.hymple.com
cpaige@uc.hymple.com
_collab-edge._tls.
uc.hymple.com 
expwy-e.hymple.com
Messenger
hymple.com
Cannot
connect to
WebEx
Messenger SRV Record
Users cannot connect to WebEx Messenger service!
Cannot
connect to
WebEx
Messenger
uc.hymple.com
_cisco-uds._tcp.
uc.hymple.com 
ucm.hymple.corp
SRV Recordhymple.corp
uc.hymple.com

42. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 42BRKCOL-2344
Hymple Corporation – User Option 2
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM
hymple.com
uc.hymple.com
hymple.corp
uc.hymple.com
ucm.hymple.corp
expwy-c.hymple.comexpwy-e.hymple.com
cpaige@hymple.com
cpaige@hymple.com
_collab-edge._tls.
uc.hymple.com 
expwy-e.hymple.com
Messenger
hymple.com
Cannot find
uc.hymple.com 
Cannot connect to
Unified CM SRV Record
External users cannot connect to on-premises UC services!
No problem
connecting to
Unified CM
_cisco-uds._tcp.
uc.hymple.com 
ucm.hymple.corp
SRV Record

43. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 43BRKCOL-2344
Hymple Corporation – User Option 3
External
DNS
Internal
DNS
Expressway-E Expressway-C
Unified CM
hymple.com
uc.hymple.com
ucm.hymple.corp
expwy-c.hymple.comexpwy-e.hymple.com
_collab-edge._tls.
uc.hymple.com 
expwy-e.hymple.com
Messenger
hymple.com
cpaige@hymple.com
VoiceServicesDomain=
uc.hymple.com
cpaige@hymple.com
VoiceServicesDomain=
uc.hymple.com
SRV Record
Both internal and external users can connect to all services!
VoiceServices
Domain not
used!
_cisco-uds._tcp.
uc.hymple.com 
ucm.hymple.corp
SRV Recordhymple.corp
uc.hymple.com

44. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 44BRKCOL-2344
Service Discovery Tuning for Hybrid Deployment
Option 1: MSI/URL/EMM
• ServicesDomain = example.com & VoiceServicesDomain = uc.example.com
• WebEx Messenger HTTP request against example.com
• DNS queries for uc.example.com
• Still requires UC Cluster(s) settings in WebEx Messenger Org Admin
Option 2: jabber-config.xml
• Upload jabber-config.xml in WebEx Messenger Org Admin
• <VoiceServicesDomain>uc.example.com</VoiceServicesDomain>
• DNS queries for uc.example.com as user next time signs in
• Still requires UC Cluster(s) settings in WebEx Messenger Org Admin

45. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
No Split Brain DNS?
• Some organizations rely on public DNS for all records
• No internal DNS / no split brain DNS
• Common in universities and education environments
• All traffic to be routed through MRA
• Do NOT deploy _cisco-uds
• Deploy _collab-edge on public DNS
• Expressway-C will route Jabber to a random associated
Unified CM cluster to perform home cluster query
• Jabber will find and be directed to the home cluster using
Unified CM’s ILS (Intercluster Lookup Service)
• Consider impacts of routing all Jabber traffic through
Expressway (scalability and feature availability)
45
SRV Record
_collab-edge
Public
DNS
Expressway
Internet
UC Services
BRKCOL-2344

46. Finding Home Cluster

47. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Home Cluster Discovery
1. DNS SRV returns a node in Cluster_1
2. Jabber connects to the node in Cluster_1 and asks for home cluster of cholland
3. Cluster_1 queries other clusters for cholland via ILS and returns Cluster_2 to Jabber
4. Jabber connects to Cluster_2 for service
47BRKCOL-2344
ILS
Cluster_1
Cluster_2
Cluster_3
cholland’s
home cluster
DNS
Charles
Holland
(cholland)
4
2
1
Jabber does not
use home cluster
discovery when it’s
deployed with
WebEx Messenger.
3
3

48. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Assigning Users to Their Home Cluster
• Each user must belong to a cluster (only to
one cluster)  home cluster
• ILS (Intercluster Lookup Service) is used to
locate the home cluster
• Home cluster can be assigned manually,
using LDAP sync agreement or using BAT
• Do not make more than one cluster as
home cluster for a user
48BRKCOL-2344

49. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 49BRKCOL-2344
Jabber Home Cluster Request
The request can be sent to any
Unified CM node in any cluster as
long as the ILS is configured and
running for all clusters.
The Publisher
address of
the user’s
home cluster
The username from
user_name@<domain_name>
that the user entered
From the DNS SRV
lookup query
request
response
via UDS
REST API

50. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Jabber Servers Request
50BRKCOL-2344
Jabber will select one of these hosts at random and
use that node for device discovery and UDS directory
integration (if enabled)
The Publisher
address of the
user’s home cluster
request
response
via UDS
REST API

51. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Jabber User Request
51BRKCOL-2344
User information request
requires user authentication.
A randomly chosen node
within the user’s home
cluster.
request
response
via UDS
REST API

52. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Jabber Start-Up URLs & Search Queries
• UDS Version: https://CUCM_ADDRESS:8443/cucm-uds/version
• Cluster User (Home Cluster): https://CUCM_ADDRESS:8443/cucm-uds/clusterUser?username=USERID
• UDS Servers: https://CUCM_ADDRESS:8443/cucm-uds/servers
• UDS User Profile: https://CUCM_ADDRESS:8443/cucm-uds/user/USERID
• TFTP Service Profile: http://CUCM_ADDRESS:6970/SPDefault.cnf.xml
• TFTP jabber-config.xml: http://CUCM_ADDRESS:6970/jabber-config.xml
• UDS User Devices: https://CUCM_ADDRESS:8443/cucm-uds/user/USERID/devices
• TFTP Device Profile: http://CUCM_ADDRESS:6970/CSF_USERID.cnf.xml
• UDS Search User: https://CUCM_ADDRESS:8443/cucm-uds/users?name=pa
• UDS Number User: https://CUCM_ADDRESS:8443/cucm-uds/users?numberlast=7803
• UDS userID User: https://CUCM_ADDRESS:8443/cucm-uds/users?username=seongho
• UDS Email User: https://CUCM_ADDRESS:8443/cucm-uds/users?email=seongho@tme-example.com
52BRKCOL-2344

53. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 53BRKCOL-2344
Cisco UDS API Reference in DevNet
https://developer.cisco.
com/site/user-data-
services/

54. Configuration
Considerations

55. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Hybrid
Deployment
UC Cluster Settings &
jabber-config.xml in
Org Admin
Device
Configurationjabber-
config.xml
Messenger
On-Premises
Deployment
UC Service
Profile
jabber-
config.xml
IM &
Presence
Device
Configuration
Where Does Cisco Jabber Get Configuration?
55
End
User
Input
BRKCOL-2344
Local
Cache
MSI, URL
or EMM

56. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 56
Priority of Configuration Source
• Jabber takes configurations from
multiple sources
• Configuration sources have different
priorities
• Jabber builds a local operating
configuration which is made up from all
the sources
• Configuration is created at parameter
level, e.g.,
LDAP Host from jabber-config.xml
LDAP User ID from Service Profile
LDAP Password from Service Profile
BRKCOL-2344
Local/Bootstrap
Service Profile
IM and Presence
jabber-config.xml
Jabber’s
Operating
Configuration
Highest
Priority

57. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Configuration Best Practice for Service Profile
• Make most use of Service Profile to configure Jabber
• jabber-config.xml can be used inclusive for settings that
are not exposed in Service Profile
• Remember that Service Profile has the highest
priority after local/bootstrap configurations
• Check all the default settings in your Service Profile
to ensure they provide the configurations you want
• Define default template before you create users
• Host Name/IP Address in UC Service should match
with CN (Common Name) in the certificate
57BRKCOL-2344
CN =
cuc.example.corp

58. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Configuration Best Practice for jabber-config.xml
• Keep jabber-config.xml as simple and minimal as possible
• Include only the settings you need
• Do not specify the default values
• Remember that configurations in Service Profile take
higher priority (one setting from only one source)
• Double check the content of the current jabber-config.xml
using a browser
http://<your_tftp_server_address>:6970/jabber-config.xml
58BRKCOL-2344
OVER
configurations
 Higher
chance for
errors!

59. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Local Cache and Configuration File Encryption
• Starting 11.9, Jabber will encrypt most cache and
configuration files before it stores them on the
user’s device*
• AES-256-CBC with self-generated encryption keys
• Supported on Android, iOS, Mac, Windows
• The encryption keys are stored only locally on the
user’s device in:
• Keychain in iOS/Mac
• KeyStore on Android
• User profile directory in Windows
59BRKCOL-2344
New in
11.9
* The earlier versions of Jabber can encrypt a subset
of cache and configuration files using AES-128.

60. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Cisco Jabber for Mobile in App Sandbox
Cisco Jabber App
User Data
Contacts List Avatar Files Favorites
Certificates
Log Files
User Settings
App Sandbox
Server ConfigsUser Credentials
Voicemail
Chat History Recents
Application X
App Sandbox
Application Y
App Sandbox
Application Z
App Sandbox
60
Encrypted using
AES-256-CBC
Mobile Device
New in
11.9
BRKCOL-2344

61. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Cisco Jabber for Mobile in App Sandbox (Cont.)
• Everything in the app sandbox will be removed when Jabber gets uninstalled
• On Android, user credentials are encrypted using AES-256-CBC* before they
get stored in the sandbox
• On iOS, user credentials are stored only in the iOS Keychain (encrypted
container), not in the sandbox
• Accepted self-signed server certificates are stored encrypted on iOS; stored
unencrypted on Android
• Chat history gets stored only when enabled by the system admin
61BRKCOL-2344
* AES-256-CBC is new in 11.9. AES-128-CBC is supported in 11.8.

62. Configuring Cisco
Jabber for Mobile

63. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Where to Find the Latest Jabber Mobile Clients
• Cisco Jabber is a public app with free
download
• Best practice is for end users to
download/upgrade directly from App
Store or Google Play
• 3rd party EMM* solution can be used to
configure/distribute Jabber within an
organization
* EMM (Enterprise Mobility Management)
63BRKCOL-2344

64. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 64
Common Questions from Jabber Customers
Does Jabber
support MDM?
If so which
MDM vendor?
Can I manage
Jabber using
the MDM I have
deployed?
Can I distribute
Jabber using
my MDM
console?
Does/will Jabber
work with the MDM
my company has?
BRKCOL-2344

65. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 65
What is MDM, MAM, or EMM?
Mobile Device
Management (MDM)
BYOD or corp devices
Mobile Application
Management (MAM)
Public or internal apps
Mobile Content
Management (MCM)
Files or webpages
Single Sign-On
Security Policies
Enterprise Mobility
Management (EMM)
BRKCOL-2344

66. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 66
What is MDM, MAM, or EMM?
Mobile Device
Management (MDM)
BYOD or corp devices
Mobile Content
Management (MCM)
Files or webpages
Single Sign-On
Security Policies
Enterprise Mobility
Management (EMM)
Mobile Application
Management (MAM)
Public or internal apps
BRKCOL-2344

67. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
• Wrapping tool provided
by each MAM vendor
• No code change on app
(as long as compatible)
• Internal distribution only
(not on public app store)
• Compatibility or update
issues
App Wrapping
• SDK provided by each
MAM vendor
• SDK must be imported
into app (per vendor)
• Multiple versions of app
on public app store
• Potential feature gaps
with public apps
SDK
• Standard APIs available
for mobile native OS
• Small code change on
app
• Only single version of
app on public app store
API
Different Ways to Manage Apps via MAM
67BRKCOL-2344
Most
economical &
scalable
approach

68. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
The AppConfig Community
• Standard way for enterprise mobile apps to interpret
configurations & policies from EMM
• App configuration
• Enterprise connectivity
• SSO & access control
• Security policies
68
http://www.appconfig.org
BRKCOL-2344
Cisco was one of
the initial founding
members.

69. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 69BRKCOL-2344
Jabber on Mobile and App Configuration via EMM
“Managed App Configuration” NSUserDefaults API
“App Restrictions” get/setRestrictions API
EMM Platform
Deploying
Jabber with
configuration
EMM Managed Jabber
Configuration Key Definition** Captured from
AirWatch Console
Managed
Device

70. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 70BRKCOL-2344
AppConfig Configuration Keys Supported by Jabber
InvalidCertificateBehavior
ServicesDomain
VoiceServicesDomain
ForceLaunchBrowser
ServicesDomainSsoEmailPrompt
Telephony_Enabled
ServiceDiscoveryExcludedServices
TelemetryEnabled
Meetings_Enabled
Telephony_P2P_Enabled
EnableTelProtocol
EnableCiscoTelProtocol
EnableClickToCallProtocol
EnableSIPProtocol
EnableIMProtocol
EnableXMPPProtocol
EnableCiscoIMProtocol
EnableProvisionProtocol
EnableShareProtocol
EnableCiscoChatProtocol
EnableStatusProtocol
EnableProfileProtocolThe above keys can be also
specified using Configuration URL.
The above keys can be also
specified in jabber-config.xml.

71. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
• Latest version
• Managed app only*
Jabber for Mobile
• iOS 8.0 or higher
• Android 5.0 or
higher
Device OS
• Solution which
supports standard
APIs defined in
AppConfig**
EMM
Requirements for Jabber AppConfig
* Jabber installed directly from App Store or Google Play will not support app configuration via EMM.
** Jabber has been tested with AirWatch for app configuration. Visit The AppConfig community to find the
list of vendors who support AppConfig.
71BRKCOL-2344

72. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 72
Two Options to Pre-Configure Jabber for Mobile
Jabber
downloaded from
App Store
Managed Jabber
pushed from EMM
App ConfigurationConfiguration URL
BRKCOL-2344

73. How to
Configure/Deploy
Cisco Jabber using
AirWatch Console

74. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 74BRKCOL-2344
AirWatch Console: Search Jabber in App Store

75. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 75BRKCOL-2344
AirWatch Console: Add and Configure Jabber

76. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 76BRKCOL-2344
AirWatch Console: App Configuration for Jabber

77. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 77BRKCOL-2344
AirWatch Console: Jabber is Activated

78. Closing Thoughts

79. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Key Takeaways
• Let Service Discovery configure Cisco Jabber for
you and your end users
• Use Service Profile as much as possible to keep
jabber-config.xml as simple as possible
• In 11.9, Cisco Jabber will be much quicker to sign
in and much more efficient to update configurations
• In 11.9, Cisco Jabber will be much more secure to
encrypt most local data on the device
79BRKCOL-2344

80. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
• Give us your feedback to be
entered into a Daily Survey
Drawing. A daily winner will
receive a $750 gift card.
• Complete your session surveys
through the Cisco Live mobile
app or on www.CiscoLive.com/us.
Complete Your Online
Session Evaluation
Don’t forget: Cisco Live sessions will be
available for viewing on demand after the
event at www.CiscoLive.com/Online.

81. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public
Continue Your Education
• Demos in the Cisco campus
• Lunch & Learn
• TTGEN-1003 on Wednesday
• Meet the Engineer 1:1 meetings
• Walk-ins are welcome!
• Related sessions
• BRKCOL-2013 – Understanding How to Make the Most of Your Jabber Deployment
• BRKUCC-3347 – Troubleshooting Jabber Like a TAC engineer
• BRKCOL-2170 – Deploying Cisco Jabber in a Virtual Environment
81BRKCOL-2344

82. Thank you

84. © 2017 Cisco and/or its affiliates. All rights reserved. Cisco Public 84
Collaboration Cisco Education Offerings
Course Description Cisco Certification
CCIE Collaboration Advanced Workshop (CIEC) Gain expert-level skills to integrate, configure, and troubleshoot complex
collaboration networks
CCIE® Collaboration
Implementing Cisco Collaboration Applications
(CAPPS)
Understand how to implement the full suite of Cisco collaboration
applications including Jabber, Cisco Unified IM and Presence, and Cisco
Unity Connection.
CCNP® Collaboration
Implementing Cisco IP Telephony and Video
Part 1 (CIPTV1)
Implementing Cisco IP Telephony and Video
Part 2 (CIPTV2)
Troubleshooting Cisco IP Telephony and Video
(CTCOLLAB)
Learn how to implement Cisco Unified Communications Manager, CUBE,
and audio and videoconferences in a single-site voice and video network.
Obtain the skills to implement Cisco Unified Communications Manager in a
modern, multisite collaboration environment.
Troubleshoot complex integrated voice and video infrastructures
CCNP® Collaboration
Implementing Cisco Collaboration Devices
(CICD)
Implementing Cisco Video Network Devices
(CIVND)
Acquire a basic understanding of collaboration technologies like Cisco Call
Manager and Cisco Unified Communications Manager.
Learn how to evaluate requirements for video deployments, and implement
Cisco Collaboration endpoints in converged Cisco infrastructures.
CCNA® Collaboration
For more details, please visit: http://learningnetwork.cisco.com
Questions? Visit the Learning@Cisco Booth
BRKCOL-2344