Jabber Deployment Revisited

Transcription

1

2 Jabber Deployment Revisited Part 1: Deployment and Provisioning Bryan Morris Technical Marketing Engineer Cisco Jabber Team

3 Cisco Spark How 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 cs.co/ciscolivebot#

4 PART TWO PART ONE Jabber Modes Enabling Users for Jabber Connecting Jabber to Services Jabber User Authentication Users & Contacts Installing Jabber Clients Jabber IM & Presence Voice/Video Calling Conferencing Options Desktop Share Application Integration Jabber Diagnostics 4

5 PART TWO PART ONE Jabber Modes Enabling Users for Jabber Connecting Jabber to Services Jabber User Authentication Users & Contacts Installing Jabber Clients IM & Presence Voice/Video Calling Conferencing Options Desktop Share Application Integration Jabber Diagnostics 5

6 This presentation assumes 1. Jabber On-Premise 2. Jabber Client UC Manager 11.5SU3a+

7 JABBER MODES EXPLAINED

8 Jabber Operating Modes Jabber provides multiple operating modes to meet different customer requirements. IM Only Mode Desk phone Control * * Extend & Connect Full UC Mode Mix different Cisco Jabber modes to create your end user experience Soft Phone Mode Soft Phone Mode (with Contact list) Soft Phone for * VDI mode * Not available on all platforms 8

9 Infrastructure Services for Jabber UC Manager Services Required User Management Required Config/Profile Management Call Control SIP CTI Control Contact resolution (UDS) 9

10 Infrastructure Services for Jabber UC Manager Services Required User Management Required Config/Profile Management Call Control SIP CTI Control Contact resolution (UDS) NEW in Jabber 12.0 IM & Presence Services Contact List Storage Presence Service Instant Messaging 10

11 Infrastructure Services for Jabber UC Manager Services Required User Management Required Config/Profile Management Call Control SIP CTI Control Contact resolution (UDS) IM & Presence Services Contact List Storage Presence Service Instant Messaging IM ONLY MODE 11

12 Infrastructure Services for Jabber UC Manager Services Required User Management Required Config/Profile Management Call Control SIP CTI Control Contact resolution (UDS) IM & Presence Services Contact List Storage Presence Service Instant Messaging SOFT PHONE Client ONLY 12

13 Infrastructure Services for Jabber UC Manager Services Required User Management Required Config/Profile Management Call Control SIP CTI Control Contact resolution (UDS) NEW in Jabber 12.0 IM & Presence Services Contact List Storage Presence Service Instant Messaging Enable/Display IM&Presence in Messaging/Presence Settings SOFT PHONE + Contact List 13

14 Infrastructure Services for Jabber UC Manager Services Required User Management Required Config/Profile Management Call Control SIP CTI Control Contact resolution (UDS) IM & Presence Services Contact List Storage Presence Service Instant Messaging FULL Unified Communications Mode 14

15 Infrastructure Services for Jabber UC Manager Services Required User Management Required Config/Profile Management Call Control SIP CTI Control Contact resolution (UDS) IM & Presence Services Jabber 12.0 more flexibility to use services Contact List Storage Presence Service Instant Messaging Other Services Visual Voic Conference Bridge Mobile & Remote Access WebEx/Spark Services Contact resolution (LDAP) 15

16 Building Clusters UC CLUSTER Single Node: 25,000 Users Single Cluster: Up to 6 Nodes per cluster deployed in pairs for HA 75,000 Users Single or Multi-domain configuration 16

17 Building Clusters Scale solution with more clusters UC CLUSTER UC CLUSTER Single or Multi-domain configuration Single or Multi-domain configuration 17

18 Building Clusters Voice/IM&P Clusters UDS Discovery Home Cluster VOICE/VIDEO CLUSTER UDS Discovery VOICE/VIDEO CLUSTER NEW in 12.0 (11.5SU4) 1 2 CENTRALISED IM&P CLUSTER (No Telephone Services) Single node for User management Note: No SIP publish trunk required for centralised IM&P Model (client based) 18

19 CREATING JABBER USERS

20 Base Config Jabber User Structure Example for Full UC deployment Modify to change operating mode Home Cluster End User Group Membership UC Manager End Users Address Scheme IM & Presence Service Mobile (BOT/TCT) UserID IM&P enabled DN/URI Associations to User DEFAULT Presence Domain (XMPP) Voice/Video Services SIP URI VisualVM Directory Conf (WebEx) CTI (DeskPh) *(IM&P profile not used) Jabber XML AND/OR Service Profile UC Manager UserID synced from LDAP (or locally created) Soft (CSF) Desk/CTI (SEP) Associated Devices CTI Group Membership DN/URI Associations to Device Directory Number 20

21 Creating Jabber Users User Creation using LDAP Sync/Feature Template SYNC Users via LDAP + Feature template Creates the User Sets Home cluster Assigns Service profile Enables for IM&P Assigns groups Creates DN Creates SIP URI Quick User/Phone Add Creates Device Associates to Line Associates to User Associates for presence 21

22 Creating a Service Profile on UC Manager Service profile is a collection of UC service definitions Create voic if using Cisco Unity Connection Mail store is not required as Jabber uses VMREST API Create on Unity Conference server Profile is using WebEx Meetings Set Directory Profile. Uncheck UDS if using LDAP Define profiles if not using auto-discovery Technically only required for Centralized IM&P deployments but good practice to set Only required if deploying desk phone control mode Alternatively <usecucmgroupforcti>true</usecucmgroupforcti> 22

23 Create User Profile on UC Manager Goto User Management>User Settings>User Profile Associate universal templates to User Profile 23

24 Create Universal Device & Line Templates on UC Manager Universal Device and Line Templates are associated to use via User Profile Go to User Management>User/Phone Add>

25 Create Universal Device & Line Templates on UC Manager Universal Device and Line Templates are associated to use via User Profile Go to User Management>User/Phone Add>

26 Create Feature Group Template on UC Manager Goto User Management>User/Phone Add>Feature Group Template Check Home Cluster Enabled IM as required Select service profile Select user profile Enabled CTI if using desk phone control mode 26

27 LDAP: UC Manager UserID This is the UserID we will use to login to Jabber In a single domain recommendation is samaccountname In a multi-domain forest recommendation is: userprincipalname 27

28 Communication Addresses XMPP (Jabber ID) Administrator can decide what schema to use for XMPP address format Option 1: (Default JID mode) JID is created based on UC manager ID + admin defined presence domain Option 2: (flexible JID mode) JID is created based on or MS SIP address Why choose this method: Default IM&P server configuration Presence ID = UC manager user ID Doesn t require addition directory config Why choose this method: UC Manager user ID <> ID Aligns and IM&P Address Supports Multi-domain configuration Note: requires contact source configuration in jabber-config.xml file 28

29 LDAP: Sync Define Sync settings Account Search base Attributes Remember: this is used for UDS contact source If using Flexible JID set Directory URI 29

30 Communication Addresses Flexible JID mode Flexible JID mode needs to be configured on presence server On presence server Go to: Presence>Settings>Advanced Configuration Change the IM Address Scheme to Directory URI NOTE: LDAP config in UC manager must also be mapped (we will see this later) 30

31 LDAP: Sync Group Settings Group settings allow us to apply the Feature Group template and define a mask to import directory numbers from AD/LDAP Feature Template 31

32 User Creation process Running Sync imports users SYNC Users via LDAP + Feature template Creates the User Sets Home cluster Assigns Service profile Enables for IM&P Assigns groups Creates DN Creates SIP URI Quick User/Phone Add Creates Device Associates to Line Associates to User Associates for presence 32

33 Add Device to LDAP Sync'd Used Go to User Management>User/Phone Add>Quick User/Phone Add 33

34 Add Device to LDAP Sync'd Used Go to User Management>User/Phone Add>Quick User/Phone Add 34

35 Add Device to LDAP Sync'd Used Go to User Management>User/Phone Add>Quick User/Phone Add 35

36 The End Result Device Created 36

37 The End Result Directory number associated to new device Directory URL populated User associated with Line for presence 37

38 Summary of User Creation 1: We took the User from the directory with directory number and URI 2: We sync'd the user including group membership and service profile : We enabled IM&P and other settings with a feature template 4: We auto created directory number with URI based on 5: We created device and associated line and user with quick phone add 38

39 HOW JABBER CONNECTS TO UC SERVICES

40 Understanding Jabber Configuration Store Jabber Clients maintain a local configuration store Store contains service profile, jabber-config and buddy list configuration data Store is AES-256-CBC with self-generated encryption keys Keys are stored in keychain, keystore, profile depending on platform FAST Login 1 to 5 minutes* On next login config & contacts restored from local storage for fast login experience * Config then refreshed for persistent connection every 7~9 hours 40

41 Jabber Day Zero Login and Regular Login Day 0 Login On Day 0 client retrieves config and contacts FAST Login Contact List and client config are encrypted and saved locally 1 to 5 minutes* On next login config & contacts restored from local storage for fast login experience * Config then refreshed for persistent connection every 7~9 hours 41

42 Day Zero Service Discovery Day 0 Login On Day 0 client retrieves config and contacts Jabber needs to find its services. On-Premise Deployment or Cloud Deployment? DAY 0 LOGIN Locate Home Cluster Jabber finds services using Service Discovery Seed = Service Domain example.com DNS & REST requested used to locate service UDS (REST) used to identify home cluster Configuration Store can then be populated 42

43 How to find the Service Domain DAY 0 LOGIN The service domain may be identified using the client. Ask the User Automatic (Client knew Service domain) Manual - AVOID!!! (Don t discover, I ll tell you) 43

44 Service Domain - Automatic Discovery Methods DAY 0 LOGIN If logged into windows domain then environment variables show UPN (override with UPN_DISCOVERY_ENABLED) EMM can push configuration for mobile clients (ios/android) msiexec /i CiscoJabberSetup.msi SERVICES_DOMAIN=example.com MSI install switches or package management (SCCM/GP) ciscojabber://provision?servicesdomain=example.com URL Provisioning 44

45 Cloud Discovery (WebEx Messenger) DAY 0 LOGIN Jabber will also check if the Jabber domain is enabled for WebEx Messenger Client sends REST request to Cisco WebEx service to check domain If response from cloud indicates the domain is enabled for WebEx Messenger then client will automatically switch to cloud mode. If your organisation is using on-premise mode please contact WebEx support to disable cloud. WebEx Messenger Jabber Client 45

46 On Premise Discovery Jabber will send a DNS request to try and locate a UC manager cluster to register to. Admin must create DNS SRV record(s) pointing a UC manager node in a cluster Discovery can also support multiple clusters with cluster discovery (discussed later) DNS Server DAY 0 LOGIN UC Manager Corporate Network DNS SRV Request for _cisco-uds._tcp.servicedomain.com Jabber Client 46

47 Service Discovery Cluster discovery DAY 0 LOGIN Once Jabber has a Cisco-UDS server address from DNS SRV it will connect to UDS server Firstly, it will check the version of UC Manager Secondly it will confirm if this is the home cluster for the jabber user If the user is provisioned on the cluster the server will respond with local server address Where is my home cluster 47

48 Service Discovery Cluster discovery Cluster 2 DAY 0 LOGIN In a multi-cluster if the user doesn t exist on the queried server a cluster discovery is performed to known clusters. The UDS server will query other clusters defined in cluster ILS configuration. (UDS REST is used) Users home cluster is defined in end user configuration Cluster 1 UDS Request UDS Request Cluster 3 48

49 Service Discovery Cluster discovery Cluster 2 DAY 0 LOGIN In a multi-cluster if the user doesn t exist on the queried server a cluster discovery is performed to known clusters. The UDS server will query other clusters defined in cluster ILS configuration. (UDS REST is used) Users home cluster is defined in end user configuration Cluster 1 Home Sweet Home!!! Cluster 3 49

50 Service Discovery Home Cluster Cluster 2 DAY 0 LOGIN Jabber will request a list of all UDS nodes in the cluster, randomize the list and connect to a UDS node in home cluster. Jabber will now proceed to download configuration info from UDS and TFTP services on UC Manager/IM&P <XML> User Profile Service Profile Jabber-config Device List Device Config Contact List Configuration downloaded to local config store 50

51 Jabber Diagnostics will show you all the UDS REST and TFTP requests the Jabber client made during service discovery

52 Day Zero Login is complete. FAST LOGIN Day 0 Login On first login client retrieves config and contacts FAST Login Config and contacts refreshed from server after login Contact List and client config are encrypted and saved locally 1 to 5 minutes* On next login config & contacts restored from local storage for fast login experience User can force early refresh using Refresh configuration if required * Config then refreshed every 7~9 hours 52

53 Edge Discovery Always performed FAST LOGIN Jabber also performs Edge discovery with a 2 nd SRV request DNS Server (external) Different Servers DNS Server (internal) UC Manager Am I inside the corporate network Internet Expressway Expressway Corporate Network DNS SRV Request for _collab-edge._tcp.servicedomain.com This DNS record ONLY exists on external DNS server DNS SRV Request for _cisco-uds._tcp.servicedomain.com Jabber Client 53

54 Secure Communication - Cert Requirements Jabber uses secure communications to connect to UC services CA signed Certificates must be in place Default self-signed certs will generate following error message 54

55 Certificate Signing Request Certificate management is performed in OS admin tomcat certificate is required for UC manager TFTP/UDS services cup-xmpp certificate is required for XMPP on IM&P If using multi-domain then all domains must be in SAN Jabber will check certificate revocation (both internally and externally) 55

56 Cisco Collaboration Cloud On-boarding Push Notifications If using Jabber ios clients you also need to connect your UC Manager cluster to the Cisco Collaboration Cloud. Alternative routes via Proxy or Expressway fos-a.wbx2.com push.webexconnect.com idbroker.webex.com Call/Chat event for Jabber User 443/TCP Cisco Cloud Apple Notification from /8 5223/TCP /8 443/TCP Jabber ios Corporate Firewall Apple icloud 56

57 Cisco Collaboration Cloud On-boarding Push Notifications Advanced Features> Cisco Cloud Onboarding New configuration screen in UC manager from 11.5SU3 Process creates machine account based on UC manager license. Customer doesn t require Spark org. Process can also install required Certificates for connection to cloud. 57

58 HOW JABBER AUTHORISATION WORKS

59 Service Authorisation and Authentication? Jabber must authenticate to services like UDS, XMPP, Unity and expressway Jabber will query UC manager to identify the authorisation method deployed. SSO Discovery: SSO Discovery will return on of 4 responses.. 42

60 SSO Discovery Responses If running UC Manager 9.x,10.x,11.0,(11.5,12.x optional) 1. Username/password no refresh token (UC or LDAP Authentication) 2. SAML-SSO no refresh token (IDP Authentication) If running UC Manager 12.0 (incl SU3+) 3. OAuth 2.0 with refresh token (UC or LDAP Authentication) 4. OAuth 2.0 with SAML-SSO and refresh token (IDP Authentication) When using remote access Expressway can be hardcoded to single authentication method or can query cluster on users behalf 43

61 How do you know your using OAuth? Once OAuth is enabled Jabber login screen will change. Login screen will not be presented as webpage from UC manager 61

62 How does OAuth 2.0 with refresh work.. LDAP User IDP User Jabber discovers New Authorisation flow is being used. Authorisation Service redirects client to authentication Service before authorisation can take place. CUCM User UC Manager Authentication Jabber 11.9 Client UC Manager Authorisation Authorised Users Only (Token required) UC Manager UDS Service IM&P Chat Service Unity Connection Voic 62

63 How does OAuth 2.0 with refresh work.. LDAP User IDP User Jabber will authenticate with Authentication service. Authentication method is dependant on UC Manager configuration CUCM User UC Manager Authentication Jabber 11.9 Client UC Manager Authorisation Authorised Users Only (Token required) UC Manager UDS Service IM&P Chat Service Unity Connection Voic 63

64 How does OAuth 2.0 with refresh work.. CUCM User LDAP User IDP User Authentication service refers Jabber back to Authorisation service Access and Refresh tokens issued Jabber 11.9 Client UC Manager Authorisation UC Manager UDS Service IM&P Chat Service Unity Connection Voic 64

65 How does OAuth 2.0 with refresh work.. CUCM User LDAP User IDP User Once issued Access token used for service access All CUCM services, IM&P services trust token Unity Connection can also trust CUCM token UC Manager Authentication Jabber 11.9 Client UC Manager Authorisation UC Manager UDS Service IM&P Chat Service Unity Connection Voic 65

66 How does OAuth 2.0 with refresh work.. CUCM User LDAP User Jabber 11.9 Client IDP User UC Manager Authentication 60 Mins No need To go back to Authentication UC Manager Authorisation Before access token life expires Jabber will use Refresh token to request new Access token from OAuth server. UC Manager UDS Service IM&P Chat Service Unity Connection Voic 66

67 How does OAuth 2.0 with refresh work.. LDAP User IDP User When Refresh token expires full authentication required again CUCM User UC Manager Authentication Jabber 11.9 Client 60 Days UC Manager Authorisation Authorised Users Only (Token required) UC Manager UDS Service IM&P Chat Service Unity Connection Voic 67

68 Jabber 11.9 OAuth User Experience On first login client requires full authentication If access or refresh token still valid token is used for authorisation 68

69 Turning on OAuth 2.0 with Refresh token OAuth with Refresh Tokens must be enabled on UC manager/im&p On Unity the admin must configure Authz server and then enable in enterprise parameters OAuth must also be enabled on expressway if using MRA. 69

70 UNDERSTANDING USERS & CONTACTS

71 Communication Addresses The user will have a UC manager userid cholland (typically AD userid) The user will have communication addresses XMPP Address Chat / Presence E.164 Address Voice/Video Calling SIP Address Voice/Video Calling Jabber internally operates on communication addresses NOTE: If deploying phone mode with contacts you still need to plan XMPP address as contact list is store on presence server 71

72 Jabber must be able to resolve Communication addresses!!! Jabber must has a contact resolution service (WebEx, LDAP, UDS) Contact service populates JIDs with Display Name (Eyeball friendly information) Communications Addresses (addresses to call) Photos / Avatar (enhances User experience) Other attributes (Job, Address etc.) 72

73 Contact Source Summary Network Contact Sources Platform Contact Sources WebEx LDAP UDS Outlook Notes Custom Device Cache (Local) Cache entry expires after 1 day + random delta Jabber will automatically connect to contacts sources Admin can configure sources Jabber maintains local cache Jabber manages duplicate contacts across multiple sources 73

74 On Premise Contact Sources UDS Mode SYNC UDS LDAP Proxy mode LDAP Mode LDAP LDAP LDAP Default Configuration Simple configuration UC manager based 80,000 contacts max No Search scope (apart from LDAP sync) On Premise + MRA No Address attributes Web server required for photo support Reduced MS office integration New in UC Manager 11.5 Uses UDS REST API Proxy to LDAP server No 80,000 limit On Premise + MRA support No Address attributes Web server required for photo support Global Search scopes Reduced MS office integration Direct LDAP v3 connection Most scalable LDAP/GC DNS SRV discovery Most customizable method (Attributes map/authentication) Not supported for MRA (auto fall back to UDS source) Richest Attribute set Full MS Office support Native photo support Per service profile scope 74

75 SYNC UDS Contact Source Local Database LDAP Enabled in Service profile User Management>User Setting>Service Profile Server is randomly selected node in cluster (Avoid using UdsServer setting in Jabber-config.xml as this can overload single UC Manager node) Limited Attribute mapping configured in System>LDAP>LDAP Directory 75

76 UDS Contact Source - LDAP Proxy Client is enabled using service profile as with regular UDS mode UDS Proxy is enabled in System>LDAP>LDAP Search LDAP 76

77 UDS Contact Source - LDAP Proxy Phone and Directory URI can be remapped LDAP LDAP hosts are defined as UC services (up to 3) 77

78 UDS Photo source UDS doesn t support photo objects Photos must be loaded from web server Photos can be JPG, PNG or BMP with a recommended size of 128x128 pixels Web Server (unauthenticated) Jabber will resize/crop photos to fit client interface Admin must add following lines to jabberconfig.xml for UDS photo operation <UdsPhotoUriWithToken> 78

79 LDAP Contact Source LDAP Jabber uses LDAP integration called Cisco Directory integration(cdi) Configuration is by Service Profile & Jabber-config.xml (if required) CDI supports server auto-discovery CDI support full directory attribute mapping CDI supports a number of authentication methods: SASL-KERBEROS, SASL-EXTERNAL, Basic BIND and anonymous Basic BIND supports admin or user defined credentials for access CDI provides optimizations for Active Directory (ANR and Server discovery) 79

80 Server Connection: Server Auto discovery For Zero Configuration Jabber will try to detect LDAP servers. Jabber will query DNS domain for LDAP server based on Windows Environment, Admin defined domain, service domain (LdapUserDomain parameter used by admin defined domain) Uses standard DNS SRV Records _gc._tcp.domain.com (1 st choice) _ldap._tcp.domain.com (2 nd choice) Automatic discovery using DNS SRV records Jabber will query directory type (AD/OpenLDAP) to set base attribute mapping Jabber will query defaultnamecontext to use if search base not defined by admin (Jabber 11.8(1)) Allows LDAP load distribution!!! 80

81 Server Connection: Administrator defined Server Admin can define LDAP server address in service profile or config file. NOTE: Do not define server to use auto discovery Service profile allows alignment to groups of users!!! Admin defined FQDN or IP Address in Service profile 81

82 Search: Where to Search? Jabber will try to read the RootDSE of the directory to automatically identify search base for Zero Configuration. Admin can also define search bases in service profile Service profile accepts up to 3 search bases cn=users1,dc=example,dc=com cn=users2,dc=example,dc=com cn=users3,dc=example,dc=com Jabber-config.xml file can accept 5 if required <SearchBase1> <SearchBase5> If using phone mode also add to jabber-config.xml <PresenceDomain> 82

83 LDAP CDI Authentication SASL: Simple Authentication and Security Layer GSSAPI : Generic Security Services Application Program Interface Kerberos GSSAPI (WIN/MAC) External (WIN/MAC) Admin Shared Credentials Jabber UserID (Not OAUTH) Jabber User Entered Anonymous BIND GSSAPI/SASL Methods SIMPLE BIND Methods Anon Method Order defined by <LdapSupportedMechanisms>GSSAPI EXTERNAL PLAIN</LdapSupportedMechanisms> GSSAPI/SASL methods are default for Windows and Mac and managed in jabber config.xml. SASL falls back to SIMPLE if no SASL method available SIMPLE BIND is managed using service profiles Anonymous BIND is managed using Jabber-config.xml 83

84 LDAP CDI Authentication GSSAPI GSSAPI allows Jabber to use Kerberos authentication (AD Directory) If a Kerberos key is available for LDAP server then Jabber will attempt to a SASL/Kerberos authentication to server Workstation must be logged into Active Directory Domain Note: SASL EXTERNAL is the alternative to GSSAPI typically used with physical card authentication GSSAPI/EXTERNAL config can be managed using jabber-config.xml <LdapSupportedMechanisms>GSSAPI EXTERNAL PLAIN</LdapSupportedMechanisms> admin can define which authentication methods to use. 84

85 LDAP CDI Authentication GSSAPI Admin Quick TIP The klist.exe command displays keys / tickets available Jabber can use Kerberos is ticket exists for LDAP server domain 85

86 LDAP CDI Authentication SIMPLE BIND Service Profile. Admin Shared Credentials Jabber UserID (Not OAUTH) Check Use Logged on User Credentials Admin Shared Credentials Enter on service profile NOT currently available in UC Manager 12 (workaround: set in jabber-config.xml) User enters LDAP credentials in client Leave all fields empty 86

87 LDAP CDI Authentication Anonymous BIND Anonymous BIND Not commonly used for security reasons GSSAPI/EXTERNAL config can be managed using jabber-config.xml <UseAnonymousBinding>TRUE</UseAnonymousBinding> 87

88 Server Optimization Tips LDAP Server Optimization Tips for LDAP service optimization 1) DO Use Global Catalog rather than Domain controller (3268 / 3269) 2) DO Index ALL Jabber key fields. i.e. telephone numbers 3) DO Distribute load across LDAP servers with DNS/SRV records 4) Do use service profiles to create group/location based server connections 88

89 LDAP Photo Objects Jabber CDI can retrieve photos directly from LDAP Server LDAP Server Photos can be JPG, PNG or BMP with a recommended size of 128x128 pixels Jabber will resize/crop photos to fit client interface 89

90 LDAP alternative photo source If you LDAP server doesn t hold photos they can be loaded from a web server Photos can be JPG, PNG or BMP with a recommended size of 128x128 pixels Web Server (unauthenticated) Jabber will resize/crop photos to fit client interface Admin must add following lines to jabberconfig.xml for UDS photo operation <PhotoUriSubstitutionEnabled>True</PhotoUriSubstitutionEnabled> <PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSubstitutionToken> <PhotoUriWithToken> 90

91 NOW WE INSTALL JABBER CLIENTS

92 Getting the Jabber Client Software Windows: Mac : Cisco Jabber for Windows Install Cisco Jabber for Windows Admin (COP files, custom MST, AD proxy address tool) Cisco Jabber JAWS Scripts DeskPhone Video Services Interface Cisco Jabber for Mac Installer Cisco Jabber for Mac App (manual) Mobile Apps only distributed on App Stores 92

93 Installing on Windows Jabber for Windows is installed from MSI Client MSI can be pushed using management app (GP/SCCP) MSI can be deployed with switches MSI can be modified with MST msiexec /i CiscoJabberSetup.msi parameter=value Useful Settings UPN_DISCOVERY_ENABLED= CLEAR=1 Settings to be aware of CLICK2X= SERVICES_DOMAIN= VOICE_SERVICE_DOMAIN= EXCLUDED_SERVICES= LANGUAGE= Settings to avoid! PRODUCT_MODE= CUP_ADDRESS= CCMCIP= TFTP= CTI= 93

94 Installing on Mobile devices (ios/android) App Store Jabber Mobile Apps are only published on App Stores NOT available on cisco.com Can be downloaded by end user Can be pushed onto device from public App store If Application is pushed onto device then a AppConfig compliant MDM can be used to push parameters to client. Airwatch Example 94

95 Keeping Jabber up to date Major Jabber release every 6 months approximately (MR every 8 Weeks) Jabber provides a built in feature for pushing updates Add an entry to jabber-config.xml pointing at a second XML file <UpdateUrl> Update file should contain following. For mac add a duplicate block with JabberMac Force update option 95

96 JABBER BASIC DEPLOYMENT COMPLETE

97 PART TWO PART ONE Jabber Modes Enabling Users for Jabber Connecting Jabber to Services Jabber User Authentication Users & Contacts Installing Jabber Clients IM & Presence Voice/Video Calling Conferencing Options Desktop Share Application Integration Jabber Diagnostics 97

98 Cisco Spark How 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 cs.co/ciscolivebot#

99 Please complete your Online Session Evaluations after each session Complete 4 Session Evaluations & the Overall Conference Evaluation (available from Thursday) to receive your Cisco Live T-shirt All surveys can be completed via the Cisco Live Mobile App or the Communication Stations Complete Your Online Session Evaluation Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at

100 Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Tech Circle Meet the Engineer 1:1 meetings Related sessions 100

101 Thank you

102