Cisco Jabber Have You Heard About the Latest Functionality?

Home , Virtual channel

#CLUS Cisco Jabber Have you heard about the latest functionality?

Shane Long Technical Marketing Engineer BRKCOL-2221

#CLUS Agenda

• Recent Highlights

• Configuration

• Security

• Media Enhancements

• Meeting Experience

• Jabber in VDI

• Jabber team messaging mode

• Looking ahead

• Summary

Questions? Use Cisco Webex Teams to chat with the speaker after the session How 1 Find this session in the Cisco Live Mobile App 2 Click “Join the Discussion” 3 Install Webex Teams or go directly to the team space 4 Enter messages/questions in the team space

Webex Teams will be moderated cs.co/ciscolivebot#BRKCOL-2221 by the speaker until June 16, 2019.

` IM&P Active Control Team Persistent Chat Multiline (CMS) messaging for Mobile mode Coming Soon `

SIP OAuth Jabber Jabber Meeting Phone Mode Chromebook config tool with Contacts VDI Update Controls support (Webex)

Jabber 12.0 Jabber 12.1 Jabber 12.5 Jabber 12.6 Jabber 12.7 2018 2019 MARCH and much more… AUGUST

IP Communicator Unified Personal Communicator Jabber 9.x-12.1 Jabber + UC Manager12.5 • Manual • Registry Keys • DNS SRV • DNS SRV • Virtual MAC Address • Unified Presence Server • jabber-config.xml (manual XML) • Service Profiles (including jabber • Service Profiles configuration) New!

Service Profile IM&P UC Service assigned CTI UC Service Mobile Device Voicemail User UC Service “Mobile config” Conference XML File User UC Service association to devices Directory Default UC Service jabber-config.xml Home IM&P File CSF Device Cluster enabled “Desktop config” XML File

Desk Phone membership of group End User Devices Group

membership of group CTI • Can be complex to manage Group • User needs a device to have a Group Membership non default configuration

Service Profile IM&P UC Service assigned CTI UC Service Mobile Device Voicemail User UC Service Conference User UC Service association to devices Directory UC Service

Home IM&P CSF Device Cluster enabled Jabber Client Configuration New in UCM 12.5 Desk Phone membership of group End User Devices Group

membership of group CTI Group Group Membership

• UC Manager based Jabber configuration tool • No more error prone XML file editing  • Specify key and value

• User/Group based configuration using service profile • Desktop and mobile specific configurations • Cluster wide

Common Settings Jabber desktop (CSF) will apply and specific configurations

Jabber mobile (TAB, TCT, BOT) will apply and specific configurations

1. UC Service for Common Desktop Specific Settings and optionally for Desktop and Mobile

2. Apply each UC Service type to specific section in Jabber Client Mobile Specific Settings Configuration profile

3. Apply Configuration to the Service Profile Service Profile User

• Jabber config Jabber will download NEW Jabber download Configuration Profile if available begin • If Jabber Configuration is NOT Generated by username, such as available, Jabber will download :6972/amckenzie.cnf.xml Jabber Client a) Device specific config (Cisco Configuration yes Support Field) Profile configured??? https://{cucm}:6972/JABXXX.cnf.xml b) Default jabber-config.xml

• Jabber 12.5+ is backward compatible no with default jabber-config.xml.

• UC Manager upgrade will not break Jabber device yes specific config existing config!

configured??? https://{cucm}:6972/userDefind.xml

Use default Build Config URL jabber-config.xml Download config https://{cucm}:6972/jabber-config.xml

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 12 Fast Login • After initial login, Jabber will read local config cache and login to services in parallel Config Refresh • Allows for faster login • Allows for login even if some critical services are offline (offline login)

• Background config refresh • ~0-5 mins of Jabber launch • ~7-9 hours of active Jabber session

connect

read • All Jabber cache is encrypted! (config, chat/call history, tokens etc)

Cached Settings • For testing/debugging purposes use on device “Refresh configuration”

Q) What data does Jabber store on a device?

A) Jabber configuration, call/chat history, contact lists, cached user credentials/OAuth token

All files are ENCRYPTED before being written to disk (AES-256-CBC)

Windows: Domain Login/Windows API Mac/iOS: KeyChain Android: Keystore

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 15 OAuth Refresh Tokens OAuth Refresh Tokens can be deployed independently of SSO • UC Manager 11.5SU3+ provides support for (SSO is recommended!) XCP OAuth Refresh tokens

• Once authenticated, Jabber is issued with

• Access Token UC Manager OAuth Service

• Refresh Token

• The Access Token has a short lifetime (60 mins). The Access token is used to gain access to a service. e.g. Cisco UDS.

• The Refresh Token has a long life (60 days default). The Refresh Token is used to retrieve a UDS new Access Token either before the current Access Token expires or at Jabber start up. The Refresh Token is stored on disk (encrypted) and is available across sessions (including non persistent VDI desktops)

SSO/IDP 1. On a first time login, Jabber connects to UC Manager authorization service and is redirected to LDAP Auth the configured authentication service (Jabber does

CUCM not have an access token yet) Auth

Authentication UC Manager Authorisation IM&P Chat Service Unity Connection Voicemail Authorised Users Only UC Manager (Token required) UDS Service

SSO/IDP 2. Jabber connects to authentication service. Authentication is performed – e.g. LDAP Auth username/password, SSO auth etc. Jabber receives

CUCM authentication assertion Auth

Authentication UC Manager authentication Authorisation IM&P Chat Service Unity Connection Voicemail Authorised Users Only UC Manager (Token required) UDS Service

SSO/IDP 3. Jabber uses assertion to request Access token and Refresh token from UC Manager authorisation LDAP Auth service Refresh token CUCM Auth Access token Authentication UC Manager Authorisation IM&P Chat Service Unity Connection Voicemail Authorised Users Only UC Manager (Token required) UDS Service

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 19 OAuth Flow (On Prem) 4. Jabber uses the Access token to gain access to SSO/IDP configured services. Jabber can now use these

LDAP services e.g. UDS, IM&P, voicemail Auth Refresh token CUCM Auth Access token Authentication UC Manager Authorisation IM&P Chat Service Unity Connection Voicemail Authorised Users Only UC Manager (Token required) UDS Service

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 20 OAuth Flow (On Prem) 5. The access token has a lifetime of 60 minutes. SSO/IDP Jabber will use the Refresh token to request a new

LDAP Access token at 0.75 times the Access token life (45 Auth minutes) Refresh token CUCM Auth Access token Authentication UC Manager Authorisation IM&P Chat Service Unity Connection Voicemail Authorised Users Only UC Manager (Token required) UDS Service

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 21 OAuth Flow (On Prem) 6. Jabber uses the renewed Access token to maintain SSO/IDP access to configured services. The new Access

LDAP tokens timer starts again (60 mins) Auth Refresh token CUCM Auth Access token Authentication UC Manager Authorisation IM&P Chat Service Unity Connection Voicemail Authorised Users Only UC Manager (Token required) UDS Service

SSO/IDP 7. The Refresh token expires after 60 days. The user will need to re authenticate once the Refresh token LDAP Auth expires. One authentication has taken place, a new

CUCM Refresh token and Access token will be granted Auth

Authentication UC Manager authentication Authorisation IM&P Chat Service Unity Connection Voicemail Authorised Users Only UC Manager (Token required) UDS Service

• As the Refresh token is about to expire, the user will be prompted to refresh their session (Jabber will use its active Refresh token to retrieve a new Refresh token)

• The user is prompted once per day from 3 days out of expiry (for 60 day lifetime)

• If the Refresh token expires, the user will be prompted to renew their session. This will require a re- authentication

• Observe the default timers!!

• For MRA, OAuth Refresh tokens can be enabled on Expressway

• OAuth tokens can be revoked (per user) from UC Manager

• OAuth will GREATLY ENHANCE the APNS experience

• OAuth Access tokens define a scope of capabilities

• Ability to configure Users MRA capabilities using OAuth scope.

• Configurable on a per user basis • MRA enablement • Desktop MRA enablement • Mobile MRA enablement • IM&P, voice and video enablement

• UC Manager 12.5 and Expressway X8.10 required

Q) Does Jabber support Multi Factor Authentication (MFA)?

A) Jabber can be deployed with MFA by enabling SSO and configuring the Identity Provider (IDP) to require 2 or more types of authentication. e.g. certificate and pincode.

Jabber offloads SSO authentication to the local OS (e.g. IE on Windows, Safari on Mac/iOS, OpenSSL on Android)

Q) Can Jabber be locked down to corporate managed devices?

A) A device needs something unique to identify securely itself to a system. E.g. MAC address, certificate etc. SSO can be deployed with certificate based authentication. Certificates can be deployed to corporate devices only.

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 28 Jabber On Premise Interfaces – pre UCM 12.5 IM&P – message, presence, contacts UC Manager - UDS Unity Cxn – visual voicemail

Oauth Access token

CTL file (certificate)

Expressway - MRA UC Manager – Softphone (Secure SIP)

• UC Manager SIP interface is not secure by default (out of the box) • When Jabber registers in softphone mode, SIP is sent over a TCP session (TCP 5060) • Jabber will send voice, video and video desktop share over an unencrypted UDP stream

• In UC Manager pre 12.5, UC Manager would be need to be deployed in “Mixed Mode” to enable SIP and media over TLS (secure SIP and media) • This is a cumbersome process for Jabber as the device needs to be CAPF enrolled by the user. • May require an authentication string on first time login • CAPF enrolment over MRA is not supported

• UC Manager 12.5 adds support for OAuth Access token based auth on the SIP interface • This allows Jabber to send/receive SIP and media over TLS without CAPF enrolment

• OAuth Refresh Tokens must be enabled!

• From the UC Manager CLI run the following command utils sipOAuth-mode enable

• System > Security > Phone Security Profile

• Set the Device Security Profile on each device (CSF, TAB, TCT, BOT)

• Jabber will default to connecting to UC Manager (SIP interface) on TCP 5090/5091 when SIP OAuth is enabled (System>Cisco Unified CM) • No more SIP in plaintext!

TCP(cucm.domain.com:5090)

• Ensure TCP 5090/5091 is open on UC Manager show open ports regexp 5090

• Jabber clients that establish a secure SIP session with UC Manager are capable of secure voice, video and video desktop share (sRTP) • CAPF enrolled • SIP OAuth

• Both endpoints in the call need to be sRTP enabled

• Look out for the lock icon!

• Media port range is still defined in the SIP Profile

Q) What is the a security best practice for Jabber deployment while maintaining a great user experience

A) Enable SSO. Enable OAuth refresh tokens. Enable SIP Oauth.

Remote User Corporate Network

DMZ

UC Internet Manager

Exp-C Exp-E

• Jabber MRA user calls a • Media will be routed via Jabber user on corporate Expressway pair network

Media Path

Remote User • Both Jabber clients are Corporate Network now registered via MRA

DMZ • Media will be hairpinned via the Expressway-C Internet UC Remote User Manager • Added latency

• Bandwidth Exp-C Exp-E consumption at Edge

Media Path

Remote User • UC Manager 12.5 offers Corporate Network support for ICE media

DMZ • Both Jabber clients are registered via MRA

Internet UC Remote User Manager • By enabling ICE Support Exp-C Exp-E Media will be sent point to point – media does not traverse Expressway

• Typically less latency • Reduced bandwidth requirements at the edge

Media Path

• Both endpoints need to be running in secure SIP/RTP mode CAPF enrolled device OR SIP OAuth device profile

• Server Requirements • UC Manager 12.5+ • Expressway X8.12+ • Jabber 12.6+

• Jabber 12.6 now supports up to 1080p video!

• Improved Desktop Sharing Experience • Single window mode • Video Desktop Share Quality – Jabber now has frame rate adaption for desktop share

• Wireless Sharing (Proximity) • Wireless screen share to premise registered endpoints • Cisco MX, SX, DX and IX Series, and Room Series devices supported

Jabber has added rich meeting controls for softphone • Active Control for CMS • Meeting Controls for Webex

 Layout Controls

Meeting Roster

Participant controls

Recording controls

• Users can choose their meeting experience with multiple layout options • Automatic • Equal • Prominent Equal Prominent • Single • Overlay

Single Overlay

• Joined participants and invited participants shown

• Participant Controls • Mute • Lock • Drop

Jabber Jabber Function Desktop Mobile Show participant List Yes Yes Change the Layout Yes Yes Show the active Speakers Yes Yes Show presenter Yes Yes Add a participant Yes Yes Mute/Unmute a participant Yes Yes Drop a participant Yes Yes Lock/Unlock conference Yes Yes Start/Stop recording Yes Yes Mobile Remote Access Yes Yes

CMS

Ensure iX is enabled on the SIP Profile of device and SIP Trunk to CMS

• Administrator can pre-configure users CMS space SIP URI/DN in Jabber (so they can escalate to it) • So your users do not have to do it!

• Example, create your CMS spaces with the [email protected] schema of uid@domain • Alice Holland (aholland) has a personal CMS space ([email protected]) Alice Hollands • Add the following jabber config Space

true %%uid%%@cms.example.com

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 47 Webex Meeting Controls Jabber Jabber Function Desktop Mobile Show participant List Yes Yes Change the Layout Yes Yes Show the active Speakers Yes Yes Mute/Unmute a participant Yes Yes Drop a participant Yes Yes Lock/Unlock conference Yes Yes Start/Stop recording Yes Yes PIN meeting Yes Yes Lobby Admit Yes No Assign Host Yes No Leave and assign host Yes No

SIP

Media

HTTPS (Meeting Controls)

Firewall Requirements (all outward)

*.wbx2.com TCP 443

*.webex.com TCP 443

*.ciscospark.com TCP 443

*.clouddrive.com TCP 443

1. Service Profile details Jabber Conference Service (Webex site)

2. Jabber retrieves calendar from Outlook (Google calendar and Lotus Notes also supported) 1 3 3. Jabber adds Webex dial into details from Webex 4 schedule Service Profile 4. User can join meeting 2 using Jabber (voice/video or cross launch of Webex Meetings app)

• Did you know Jabber has One Button to Push (OBTP) capabilities?

• User presented with Meeting reminder 5 minutes before scheduled meeting Q) Does 2 meeting join options confuse your endusers?

Add one to your jabber-config

BridgeOnly WebExOnly Join via SIP

Cross launch Webex

Data Center Virtual Desktop • Media Hairpinning Display Protocol • Decoded media Media Flow Thin embedded inside Client display protocol Signalling • Bandwidth Explosion Cisco • Latency Unified CM • Jitter • Bad UX Signalling • QoS is impossible Display Protocol

Media Flow Thin Virtual Desktop Client

Data Center Virtual Desktop • Media offloaded to the Display Protocol endpoint/thinclient JVDI Thin • Point to point media Client • No processing cost to Signalling VDI architecture Media Cisco Flow • No bandwidth Unified CM explosion • No media Signalling processing on VDI Display Protocol

JVDI Thin Virtual Desktop Client

Virtual 2. Virtual Desktops – VDI Agent, Jabber for Desktops Windows, JVDI Agent

Users

Endpoints 3. Endpoints - VDI Client, JVDI Client

• VXME is now call JVDI

• JVDI 12.6 has undergone a re-architecture • Faster to market with features Jabber • User experience alignment VDI • Current available features include Update • Mobile Remote Access • Video Desktop Share (BFCP) • Active Control/Webex Meeting Controls Supported with • 64 bit Windows support Citrix and VMware • SIP OAuth • N-2 upgrade path

• More features coming soon!

Data Centre Endpoint (Thin Client or PC) VDI VDI Virtual Channel Broker VDI Agent Client

Cisco Jabber Jabber VDI Client

SIP CTI Manager Line CTI Signalling SIP Signaling RTP Media (Voice, Video) Display Protocol API / Virtual Channel

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 57 Jabber VDI – Making a Call Data Centre Endpoint (Thin Client or PC) VDI VDI Virtual Channel Broker VDI Agent Client

Cisco Jabber Jabber VDI Client

SIP CTI Manager Line CTI Signalling SIP Signaling RTP Media (Voice, Video) Display Protocol API / Virtual Channel

Virtual Channel Broker VDI VDI Agent Access Cisco Jabber VDI Client

Jabber VDI SIP CTI Manager Client Line CTI Signalling SIP Signaling RTP Media (Voice, Video) Display Protocol API / Virtual Channel

Firmware Update via UC Manager & Jabber 520 Series 530 Series 560 Series Standard 560 Series Multibase Base Models in Series 521/522 531/532 561/562 561/562

Planned GA Now Shipping! Now Shipping! Now Shipping! Now Shipping!

Type Wired Wired with Quick Disconnect Wireless (DECT 6.0) Wireless (DECT 6.0)

Designed for Office Contact Center Office / Contact Center Office / Contact Center

Simultaneous connections 1 1 1 3

Connectors (included) 3.5mm and USB Adapter QD to RJ9 (for phones) USB-A and RJ9/RJ11 2 USB-A and RJ9/RJ11 or QD to USB Adapter (Y cable) (Y cable)

• Cisco Jabber is a flexible communications client • Flexible operating modes means an organisation can configure the Multiple Communication functions Jabber experience they need… • Phone only mode • IM only mode • Full UC mode • Jabber provides a new operating mode optimized for “team messaging”…… Multiple Device Platforms • Desktop and Mobile coming in Jabber 12.6

• Jabber uses Webex Teams platform for messaging (1:1 and spaces)

• Jabber uses on prem/hosted services for calling, voicemail, directory

• This is NOT the same as Jabber to Teams Interop (Hybrid Messaging)

Messaging Service UC Manager/HCS

Presence Service Unity Connection

Contacts Service Corporate Directory

Cisco Jabber Mobile Remote Access

Webex Messaging

Webex Meetings

UC Manager UC Manager

Webex messaging Webex Messaging

Webex Meetings Webex Meetings

UC Manager UC Manager

IM&P Messaging IM&P Messaging

Webex Meetings Webex Meetings Today

Premise UC Manager Unity Cxn LDAP/UDS

Jabber

Contacts Messaging Meetings Calling Voicemail Directory

• Recognizable Jabber conversation window experience • Persistent 1:1 conversations • Persistent Space conversations • List of members can be toggled on/off

• New search capabilities • Search for contacts • Search for messages • Search for files

• Personal Contact List • Search Corporate, Outlook contacts • Add/Delete contacts • Contact card • Migration of contacts from IM&P/Messenger to Jabber team messaging mode • Contacts must be Webex Teams Users – exist in CI database

• Webex Teams platform provides the Jabber client with presence Active

• Supports both Active x minutes ago • Time based presence On a call • Active based presence UC Manager based (Phone presence is reported by Jabber Client) In a meeting Including Webex meeting UC Manager based Do not disturb

Out of Office

• Persistent file sharing

• Post/download files

• Inline file preview

• New files tab

• List / Preview views

• Control Hub Policy

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 71 Features – Calling • Jabber will still use UC Manager/HCS for calling capabilities • The calling feature set is not impacted by moving messaging to team messaging

• Mode: Softphone, Deskphone, Extend & Connect • Platforms: Desktop, Mobile, VDI • Features: Multiline, Hunt Groups, Pickup, Far End Camera Control, Built in Bridge, Active Control etc

• Leverage Jabber’s rich telephone features

Answer Hold Decline Mute Call Forward Call Transfer Conference

Far End Call Pickup VDI Hunt Group Screen Share Camera Headset Voicemail

Many more feature provided CTI Controllable Call Call Mobile Remote by UC Manager Soft Phone Monitor Record Access Multi-Line History

2. Wizard to configure UC Manager integration opens. Is your Webex Teams domain the same as your UC Manager domain? (voice service domain) If Yes: Check the box. You are done! DNS If No: _cisco-uds._tcp.example.com Do not check the box. _collab-edge._tls.example.com The wizard will continue Voice Services Domain=example.com

• If your Voice Services Domain is NOT the same as the Webex Teams domain • Create a profile and specify the Voice Services Domain

• Jabber will perform SRV queries for UDS and COLLAB- EDGE using this domain

[email protected]

DNS _cisco-uds._tcp.barcelona.example.com _collab-edge._tls.barcelona.example.com Voice Services Domain=barcelona.example.com

• Team messaging mode enabled at a user level

• Users>Services>Messaging

Contact Migration Required • Only enable if users XMPP contacts need to be migrated to team messaging mode (discussed later in this presentation) Enable Jabber calling • Required to enable calling in Jabber when in team messaging mode

• Bulk user provision for Jabber team messaging mode can be done via CSV file

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 76 Architecture - Service Discovery 1. Jabber queries Webex Teams Service for domain tmedemo.com and user jvalluri 2. Webex Teams service Webex Webex Teams Teams redirects Jabber to IDP 3. User authenticates and 1 receives IDP cookie. 4. IDP cookie sent to Webex 4 Teams service. Jabber logs 2 IDP into team messaging mode

IDP 3

TMEdemo.com Webex Teams org is SSO enabled (recommended)

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 77 Architecture - Service Discovery 5. Jabber performs DNS SRV queries based on Voice Services Domain and discovers cisco-uds 6. Jabber connects to UC Manager and uses IDP cookie to gain Webex access (and retrieve OAuth 5 DNS Meetings tokens). 7. Jabber downloads Service _cisco-uds._tcp.tmedemo.com LDAP _collab-edge._tls.tmedemo.com Profile from UC Manager. Jabber performs a SIP 8 registration/CTI connection with 6 8 UC Manager – telephony will become available at this stage. (Telephony requires “Enable 8 Jabber calling” setting in Control Hub) 8. Jabber then connects to configured services e.g. Directory, Voicemail, Meetings, CTI Server. (Recommended to 7 SSO enable Voicemail and HIGHLY RECOMMENDED Meetings for the best SSO enable Webex Teams experience). and UCM – with the same IDP!

• If SSO is not enabled on Webex Teams and UC Manager • Your enduser will need to perform a manual sign in to UC Manager to enable phone services. • OAuth tokens will not be available in this mode • No Refresh Token login flow • No SIP OAuth capabilities

• Enable SSO on all platforms for the best experience

• Jabber will connect to Webex Teams contact source LDAP

AND Webex on-premise contact source Teams • Comprehensive detail in the contact card LDAP or UDS • Webex Teams service provides 1 Display Name 2 Email Avatar

• Jabber will then perform additional query against on prem contact source (LDAP or UDS) • On Prem directory service will provide Jabber Phone Numbers Job Title Company Name

1. Search for contact against Webex Teams contact service Webex Teams 2. Contact Service returns Email, Display Name and “chuck robb…” Avatar 1 2 3. Jabber queries premise LDAP or contact source via email 3 UDS address.

4 4. Premise contact service returns Job Title, Phone Numbers etc. 5 5. Jabber combines the information to provide inside the contact card +12345678

• By default Jabber will perform directory Example: queries against Webex Teams and then on

premise CI CI-UDS-LDAP

CI-UDS-LDAP Jabber will only search for contacts in CI. Jabber CI-UDS-LDAP will only find contacts that are synced to Webex Teams platform. Jabber will resolve the contact list using CI and UDS/LDAP. This will provide the most • ContactSearchSource comprehensive contact card Specifies which service Jabber will perform predictive search on

• ContactProfileSource Specifies the service Jabber will resolve contacts against

To do Status

Teams org and UC Manager enabled for SSO 

User account created in Control Hub and UC  Manager Jabber toggles enabled in Control Hub 

SRV Records deployed for UC Manager and MRA 

UC Manager Service Profiles created for Meetings,  CTI, Voicemail and Directory

WE CANNOT DO A FLASH CUT. WHAT ABOUT INTEROP?

Expressway

Webex Teams UC Manager • Hybrid Messaging Service is deployed Message as a connector on Expressway C AXL • AXL used to access User DB on IM&P Calendar XMPP • XMPP used for IM&P Messaging IM&Presence • HTTPS/TLS used for Teams

1:1 Messaging between Jabber and Webex Teams

Presence Mapping: Teams Presence will be mapped into Jabber presence

Notifications: Message, Message Read, “is Typing”, Missed Messages (in Teams), Message deleted

File transfer: Not supported. (Teams user can post file, Jabber will receive notification to get file in teams web client)

To use Messenger-Teams Interop…

1. Must be Webex Messenger Org*

Webex Teams 2. Webex Messenger Org must be enabled for Common Identity (CI)

3. All users must be enabled for Webex Teams & Jabber (free or licensed)

4. Machine account must be provisioned for Jabber access to Webex Teams Spaces (contact your Cisco Team)

To do Status

Teams org and UC Manager enabled for SSO 

User account created in Control Hub and UC  Manager Jabber toggles enabled in Control Hub 

SRV Records deployed for UC Manager and MRA 

UC Manager Service Profiles created for Meetings,  CTI, Voicemail and Directory Interop is turned on 

WHAT ABOUT CONTACT LISTS?

Webex Teams

0-5 mins after Jabber start up Contacts Friday 7-9 hours if Jabber is active Migrated Monday to Teams

• You can trial Jabber team messaging mode without enabling the toggle in Control Hub • If you do not have access to Control Hub • Webex Messenger is used in production

1. Reset Jabber

2. Select Advanced settings. (On Windows, you will need to reinstall Jabber and disable UPN Discovery to see Advanced settings)

msiexec /i CiscoJabberSetup.msi UPN_DISCOVERY_ENABLED=false CLEAR=1 /quiet

3. Select Team Messaging and Save. Sign in. NOTE: Calling will not be available in this mode

• Control Hub provides Jabber upgrade management

• Mobile clients still manged from App Stores

Consideration Notes Management Control Hub & UC Manager Authentication SSO Enablement recommended Directory Integration Teams and Prem Directory Presence Activity Based Desktop Share Video Desktop Share Compliance Enterprise Compliance Federation Federation with Teams Orgs. Analytics Rich Analytics in Control Hub Platform APIs Modern REST API service Software Upgrades Cloud Infrastructure Security Teams End to End security

https://www.cisco.com/c/en/us/products/collateral/collaboration- endpoints/ip-communicator/eol-notice-c51-740383.html

• Application Share • Send Voicemail • Team Messaging Mode Enhancements • Multiline for JVDI • CTI Monitoring on Mobile • UX Alignment • And much more…

Dark Mode, Classic View

Dark Mode, Modern View

Default Mode, Modern View

• Jabber 12.5 has delivered many on premise feature enhancements • SIP OAuth provides the best security/user experience • Jabber is the default CMS application now. Active Controls enhance the meeting experience. • Jabber config tool makes the administrators life easier!

• Jabber will continue to deliver features for on premise deployments

• 12.6 will see a large investment in Jabber VDI • Alignment to JCF architecture

• Jabber team messaging mode provides a mechanism for Jabber customers to migrate their messaging workload to the Webex Teams platform. Endusers will maintain the consistent Jabber user experience and UC Manager telephony set.

#CLUS BRKCOL-2221 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 98 Complete your online session • Please complete your session survey after each session. Your feedback evaluation is very important.

• Complete a minimum of 4 session surveys and the Overall Conference survey (starting on Thursday) to receive your Cisco Live water bottle.

• All surveys can be taken in the Cisco Live Mobile App or by logging in to the Session Catalog on ciscolive.cisco.com/us.

Cisco Live sessions will be available for viewing on demand after the event at ciscolive.cisco.com.

Demos in the Walk-in labs Cisco campus

Meet the engineer Related sessions 1:1 meetings

#CLUS #CLUS