Cisco Jabber: Deploying Cisco Jabber on Premise

Transcription

1

2 Cisco Jabber: Deploying Cisco Jabber on Premise Bryan Morris Technical Marketing Manager

3 Session Description Cisco Jabber clients provides the ability to communicate using instant messaging, voice, video and desktop collaboration. Jabber is built on open standards for interoperability and integrates with commonly used desktop business applications. Jabber allows an organisation to choose either cloud or on premise deployment to align with business requirements. This session is one of two related session. When booking this session please make sure you select the session which aligns to your deployment model. In this session we will explore the deployment process for ON-PREMISE deployment. Subjects covered in this session include On Premise solution components, directory requirements, IM & Presence, UC manager integration, voice, video, desktop sharing and collaboration, Microsoft Office integration and client extensibility 3

4 Deploying Cisco Jabber Desktop Clients Session Agenda Cisco Jabber Product Set Jabber IM & Presence Architecture Creating Users On Premise Contact Sources Unified Communications WebEx Meetings Integration with Microsoft Office Extending Cisco Jabber Summary Cisco Jabber with Cisco IM and Presence 4

5 Deploying Cisco Jabber Desktop Clients Cisco Jabber Product Portfolio All-in-one UC Application Presence & IM Voice, Video, voice messaging Desktop sharing, conferencing Collaborate from Any Workspace PC, Mac, tablet, smart phone On-premises and Cloud Integration with Microsoft Office 5

6 Cisco Jabber Workflows available in Cisco Jabber Instant Messaging Rich / Group Chat Presence Contact User Management Search & Authentication App Integration (MS Office) Enterprise Call Control Business Video Cisco Jabber & Client Services Framework MediaNet Visual Voic Conferencing Web/Desktop Collaboration

7 A Brief tour of Jabber Jabber for Windows Cisco Jabber provides you a hub view. The hub view displays contacts with presence and provides search capabilities Standards based Voice and high definition video calling Chat, Group Chat, Federated Chat, Chat history, File Transfer, Screen Capture and Emoticons Collaboration using Desktop sharing and Web Conferencing 7

8 Planning your Jabber Deployment Chat/IM & Presence Planned deployments are successful deployments!

9 Cisco Jabber Deployment Planing Your Deployment Decide on a Jabber deployment model. Check current software versions deployed (if applicable) Check current/required Licensing in place. Plan your baseline deployment? (Scaling, Servers) Review the release notes for software version you re going to deploy! Confirm where/how users will be created? Confirm how users are going to be authentication? Decide which contact lookup sources you re going to use? Plan which additional feature you re going to deploy? Network bandwidth and policy requirements Configure internal firewalls based on traffic types. 9

10 Jabber On Premise Solution Architecture Baseline Architecture Feature Configuration Unified Communications Voice Messaging WebEx Meetings Application Integration Baseline Configuration (IM Only deployment) IM & Presence Service User Authentication and Policy Contact Information User Creation Baseline Architecture Cloud / SAAS Deployment On Premise Deployment 10

11 Jabber On Premise Solution Architecture On Premise Architecture Presence and IM services deployed used either on premise or cloud model Federated Organisation Active Directory (Options) UC Manager Call Control UC Manager IM & Presence Unity Connection (optional) WebEx Meetings Server (optional) Internet Home Office Federated Organisation Sync & authentication Jabber Desktop (Desk Phone mode) Jabber Desktop (Soft Phone Mode) Jabber Desktop (Soft Phone Mode) Jabber Mobile & Tablet Telepresence Endpoint Telepresence Room

12 Jabber On Premise Solution Architecture Baseline Architecture Feature Configuration Unified Communications Voice Messaging WebEx Meetings Application Integration Baseline Configuration (IM Only deployment) IM & Presence Service User Authentication and Policy Contact Information User Creation Jabber for Everyone Baseline Architecture Cloud / SAAS Deployment On Premise Deployment 12

13 Jabber On Premise Solution Architecture Solution Components 9.0 Unified Communications Manager Cluster Contact Source Call Control Server UC Manager 7.1(3) 9.x IM & Presence Server Presence 8.6 or 9.x Directory UC Manager UDS Active Directory 2003 Active Directory 2008 Microsoft ADAM Microsoft AD LDS OpenLDAP User/Device Administation Device Discovery TFTP/HTTP Config Service Client Service Configuration SIP Call Control CTI Device Control Voice/Video Routing Media Resource Control Contact Search (Optional) Database XMPP/SIP Instant Messaging XMPP/SIP Presence Service XMPP/SIP Routing XMPP/SIP Federation Contact List Storage Configuration Gateway* Database Sync (from CUCM) IM Logging routing *Unified presence 8.x provided Client profiles pre 9.x Contact Search Contact Resolution Telephone Resolution Authentication (Optional) Contact Photo* * Contact Photos may be provided by Contact source or HTTP service.

14 Jabber On Premise Solution Architecture Scaling Solution to Customer Requirements JABBER Domain Example.com UC Manager Cluster UC Manager IM&P Server Sub-Custer Enterprise License Manager Sub Cluster Host Cluster (User Management) High Availability 25,000 IM users 15,000 UC users High Availability =50,000 IM users =30,000 UC users High Availability =75,000 IM users =45,000 UC users

15 Jabber On Premise Solution Architecture Instant Message Policy IM Policy can be managed by the admin IM Policy can be set to disable IM or features Users enabled for IM will be able to: Start Point to Point IM Start group chat session Use Rich Text IM Screen Capture (Windows only) File Transfer (Jabber Clients only) IM logging can be configured on Cisco presence server Server logging Actiance application 15

16 Jabber On Premise Solution Architecture IM Federation Industry standard based federation for presence and IM services Multi-protocol federation XMPP SIP/SIMPLE Inter-domain federation Inter-organisation Intra-domain federation (Microsoft OCS / LYNC) Public Service Federation Google / AOL 16

17 Creating Jabber Users TASK LIST (on premise / pre 9) Create/Sync Users in CUCM Enable Users for Presence/Client Access Configure Contact Source Access Configure LDAP/EDI access - or - Configure UDS Contact Service Deploy Client Installer 17

18 Creating Jabber Users What s your JID? (Jabber ID) Cluster UserID Jabber Domain AADAMS@EXAMPLE.COM Jabber ID or JID Consider your Jabber domain carefully, you ll live with it for a while! Multi-modal communications address ( , IM, Voice, Video & Federation) User created on UC Manager (can be synced from LDAP, AD Server) User is authenticated (can be authenticated from LDAP/AD or *SSO) (H1 CY13) Presence domain is configured on Presence server

19 Creating Jabber Users Adding Users as UC Manager Users Option 1 (recommended) Unified Communication Manager Active Directory (or supported directory) User Data User Data Recommended Configuration is to synchronise Corporate directory with UC Manager. Key samaccountname, mail, employeeid, Telephone, UserPrinciplename Option 2 UC manager User Administration Users created via Web admin or via Bulk Administration Tool (BAT) Call Control Server Jabber Client Jabber User [User@XMPP Domain] IM & Presence Server Jabber will authenticate to services on UC manager and Presence server Services can authenticate user locally or back to directory service Jabber on premise deployment will introduce single sign on (SSO) in H1 CY13

20 Creating Jabber Users Enabling Users for IM & Presence Users are enabled for IM and Presence in UC manager 9.0 Enabling the User for IM&P will enable them and allocate them to a node in the IM&P nodes If using 7.x or 8.x UC manager then users are enabled on 8.X presence server.

21 Creating Jabber Users IM and Presence Architecture Unified Communication Manager Active Directory (or supported directory) Contact Sources User Data User Data or Call Control Server Additional configuration may be downloaded from UC Manager. [Jabber-config.xml] IM & Presence Server Jabber will download configuration information from the presence server Jabber will download saved contact list from presence server Contact search and resolution Instant messaging and presence is routed via UC manager IM & Presence server Contact cache also maintained locally Jabber Client Jabber User Domain] Done

22 Jabber Contact Sources Information/Access to Directory Service Clients search the directory to add contacts, resolve contacts and phone numbers. What directory does the organisation use?, Do they use more than one Which Jabber Contact Source are we going to deploy You need to understand the directory infrastructure Directory Architecture (AD?, Domain?, Forest) Attribute Usage / Mapping (custom attributes) Connection Parameters (LDAP / LDAPS, DC / GC,Ports) Data completeness / Data quality (Phone Formats?) Phone numbers should not include space, dash or bracket etc. 22

23 Jabber Contact Sources Selecting a Contact Source LDAP based contact Source (On Prem Default) Active Directory by default but can be customized for other directory environments HTTP/REST based contact Source (On Prem) Built into UC Manager 8.6(2)+ and provides and alternative to LDAP integration WebEx Contact Source (cloud) Default for cloud based deployments MS Outlook Contacts Search local contacts from Jabber (requires Windows 9.1) 23

24 Jabber Contact Sources EDI : Enhanced Directory Integration (LDAP) On Premise Jabber for Windows by default uses autodiscovery for LDAP directory access (EDI Mode) Workstation MUST be a member of a domain for auto discovery to work Clients connect to a Global Catalog server in the current domain (windows selects exact GC, so distributes load) Client uses encrypted authentication to directory based on current logged on user (workstation) Ambiguous name resolution (ANR) is used for search, ANR is more efficient and uses less server resources than other search methods.

25 Jabber Contact Sources EDI : Enhanced Directory Integration (LDAP) Consider the following multi-site active directory environment. 4. Large domains with multiple GCs will distribute clients 2. Client uses EDI to connect to directory 1. Workstation discovered DC/GC using DNS SRV 3. Client authenticated using existing domain authentication 25

26 Jabber Contact Sources EDI : Customization - One Model doesn t fit all. Administrator can customize many elements of EDI operation for different deployment environments. The Administrator creates a custom XML configuration file for directory access. TFTP or HTTP is used to download file Filename: Jabber-config.xml Only define non default items. XML CNF Admin created custom XML file Custom Config <?xml version="1.0" encoding="utf-8"?> <config version="1.0"> <Directory> <DirectoryServerType>EDI</DirectoryServerType> <PrimaryServerName>D1.test.lab</PrimaryServerName> <ServerPort1>1234</ServerPort1> </Directory> </config> (example only) 1) Client checks UC Manger TFTP for custom config 2) Client connects to LDAP server NOTE: AD Contact source does not use CUP LDAP profile 26

27 Jabber Contact Sources EDI : Alternative Directory Access EDI can connect to a single AD forest. If you need to connect to multiple forests you can use Microsoft AD Application mode / lightweight directory services. ADAM/LDS is commonly used to build to an aggregated directory from multiple AD forests EDI also supports ADAM/LDS using proxy authentication. Connection to other LDAP application servers (i.e. non Microsoft) Cisco Clients US-ORG EU-ORG AP-ORG Sync & Auth Sync & Auth LDAP Server 27

28 Jabber Contact Sources EDI : Custom Directory Access Parameters Connection Settings Connection Type UseSecureConnection UseSSL PrimayServerName Port1 SecondaryServerName Port2 Search SearchBase1 SearchBase2 SearchBase3 BaseFilter Attribute Map CommonName Nickname FirstName PostalCode LastName State Address StreetAddress SipUri PhotoURI BusinessPhone CompanyName HomePhone UserAccount OtherPhone Domain PreferredNumber Location Title Authentication UseWindowsCredentials ConnectionUsername ConnectionPassword 28

29 Jabber Contact Sources EDI: Example Configurations Connect to DC not GC <?xml version="1.0" encoding="utf-8"?> <config version="1.0 > <Directory> <DirectoryServerType>EDI</DirectoryServerType> <ConnectionType>1</ConnectionType> </Directory> </config> Manual Server selection <?xml version="1.0" encoding="utf-8"?> <config version="1.0 > <Directory> <DirectoryServerType>EDI</DirectoryServerType> <PrimaryServerName>primary_server_name.domain.com</PrimaryServerName> <ServerPort1>1234</ServerPort1> <SecondaryServerName>secondary_server_name.domain.com</SecondaryServerName> <ServerPort2>5678</ServerPort2> </Directory> </config> 29

30 Jabber Contact Sources EDI : Example Configurations Common access account <UseWindowsCredentials>0</UseWindowsCredentials> <ConnectionUsername>ldap_user</ConnectionUsername> <ConnectionPassword>ldap_password</ConnectionPassword> Search specified OU <SearchBase1>ou=employee,dc=example,dc=com</SearchBase1> Exclude defined entry based on attribute <BaseFilter>(&(objectCategory=person)(UserAccountControl: :=2)</BaseFilter> Use alternative attribute for phone <BusinessPhone>aNonDefaultTelephoneNumberAttribute</BusinessPhone> <MobilePhone>aNonDefaultMobileAttribute</MobilePhone> <HomePhone>aNonDefaultHomePhoneAttribute</HomePhone> <OtherPhone>aNonDefaultOtherTelephoneAttribute</OtherPhone> Note: Jabber-config.xml file also holds a number of other configuration parameters, alternative files can also be defined by administrator. 30

31 Jabber Contact Sources Retrieving Photos for Contacts Jabber provides a number of methods to retrieve contact photos to support many different customer environments Option 1: Cloud Default (no config) WebEx Contact Photos Photo can be JPG,PNG or BMP Recommended size 128x128 but jabber can resize Directory Active Dir Web Server Note: Option 2 & 3 phase object to detect binary object or URL Web Server Option 2: On Prem Default (no config) Active Directory Binary Objects Retrieve binary photo from thumbnailphoto attribute load with Powershell Option 3: On Prem PhotoURL Attribute/ Retrieve URL Option 4: On Prem (XML config) URL Substitution/Macro style Jabber will also retrieve thumbnail photos from MS Outlook for personal contacts if photo available

32 Jabber Contact Sources Retrieving Photos for Contacts EDI Photo Service Configuration XML file settings Number / Name resolution should be configured/operational Use custom configuration settings to configure photos Directory method Photo Parameters Example Value PhotoSource Client will parse attribute to binary object or URI Substitution method Photo Parameters PhotoUriSubstitutionEnabled PhotoUriWithToken PhotoUriSubstitutionToken Example Value True samaccountname Define in XML Config File 32

33 Jabber Contact Sources UDS User Data Services (Contact Service) Sync Directory Source CUCM Clusters When using the UDS Contact Record Source the client performs contact resolution against communication manager. Resolve Client resolves contact lookups against UDS Steve Smith (1) The communications manager Universal Data Service provides an optimized contact lookup service from CUCM 8.6(2) UDS provides a cross cluster contact service supporting up to 160,000 contacts. UDS support being added to all Jabber clients. 33

34 Jabber Contact Sources UDS Configuration UDS Record source is configured in UC manager 8.x via jabber-config.xml file <?xml version="1.0" encoding="utf-8"?> <config version="1.0"> <Directory> <DirectoryServerType>UDS</DirectoryServerType> <PhotoURISubstitutionEnabled>True</PhotoURISubstitutionEnabled> <PhotoURISubstitutionToken>uid</PhotoURISubstitutionToken> <PhotoURIWithToken> </Directory> </config> 34

35 Software Deployment Client Deployment Jabber for Windows is shipped as an MSI Installer Windows XP 32bit, Vista 32/64 bit, Windows 7 32/64 bit and Apple OS X Jabber doesn t need to prompt users for server addresses. Package the client for your organisation Use SRV service discovery Use Installer command line options Use Installer properties file Client can check for updates on start-up 35

36 Software Deployment Manual Service Configuration Server and server type can also be manually configured in Jabber client. Settings can also be configured during installer Admin can specify installer parameters to select presence server 36

37 Software Deployment Windows Client Install/Packaging MSI Installer Command line switches Default configuration Cloud mode Install with switches Msiexec.exe /i CiscoJabberSetup.msi TYPE=CUP/Webex ADDRESS=x.x.x.x DOMAIN=example.com LANGUAGE=xxxx TFTP_FILE_NAME=myfile.xml FORGOT_PASSWORD_URL= SSO_ORG_DOMAIN= Repacking with Microsoft ORCA 37

38 Software Deployment DNS SRV Service Discovery Jabber windows can use DNS SRV records for IM & P service discovery Cluster A Admin defines SRV record in DNS server Cluster B Optional Redirection CUP Servers DNS Server SRV lookup for CUP_LOGIN IM&P cluster can perform client redirection in multi cluster deployment 3 Client 38

39 Software Deployment Creating DNS SRV Record SRV record is created in DNS server In DNS Manager create SRV record with: Server:_cuplogin Protocol:_tcp 39

40 Planning your Jabber Deployment Unified Communications and more Planned deployments are successful deployments!

41 Jabber On Premise Solution Architecture Unified Communications Feature Configuration Jabber UC Unified Communications Voice Messaging WebEx Meetings Application Integration Baseline Configuration (IM Only deployment) IM & Presence Service User Authentication and Policy Contact Information User Creation Baseline Architecture Cloud / SAAS Deployment On Premise Deployment 41

42 Unified Communications Modes of Operation Desk Phone Mode Jabber client controls Cisco Phone to make and receive calls. Includes Video for Cisco Voice handsets Soft Phone Mode Audio uses sound devices on workstation. Video is displayed on workstation, audio is via headset (recommended) or PC Speakers. Extend & Connect Mode Control PBX/PSTN Phone from Jabber (Requires UC Manger 9.1 which must be connected to PBX via SIP/Telco trunk) Clients can be configured for all modes of operation Voice/Video only mode currently being worked on for release H1 CY12 42

43 Unified Communications Voice and Video Unified Communication Manager Call Control Server User Data User Data IM & Presence Server Jabber Client Jabber User Domain] Jabber connect to UC Manager using CCMCIP(UDS) to Populate device list If connecting in Soft phone mode Jabber connects as a SIP / CSF endpoint If connecting in Desk phone mode Jabber connects to UC manager with CTI

44 Unified Communications Client Configuration Jabber / UC Manager User Service Profile Devices User Rights Profile for UC Services Device Types eg CSF, TAB, BOT, TCT User Roles, Rights and Associations Configure Profiles Add Devices Assign Rights

45 Unified Communications Planning for Desk Phone Control Configuration Client must be configured with CCMCIP, TFTP and CTI Server name/addresses Client will use CCMCIP Service to discover device information (Authenticated) User must have Standard End user right to connect to CCMCIP Server) Client will connect to CTI server to control device (CTI authenticated) Device must have CTI control enabled User must be associated to device User must have CTI group/role membership Voice Video* On Premise phone presence requires user to be associated to line Publish trunk must be configured between CUCM and CUP Devices must be enabled for video operation. 45

46 Unified Communications Planning for Soft Phone Configuration Voice Video Desktop Share Client must be configured with CCMCIP, TFTP Server name/addresses Client will use CCMCIP Service to discover device information (Authenticated) User must have Standard End user right to connect to CCMCIP Server) Client will download CSF device config from TFTP server Client will register using SIP to UC manager call control agent On Premise phone presence requires user to be associated to line Publish trunk must be configured between CUCM and CUP 46

47 Unified Communications CCMCIP Service - [ Configured on Presence Server] (Desk phone and Soft phone modes) CCMCIP service is used to learn about the devices associated to the logged in user. The CCMCIP provides an HTTPS based service for user/device association information. A profile is required to define where the CCMCIP services are located. To login to CCMCIP user must be a member of standard CCM User group Users must be associated to profile (unless default) 47

48 Unified Communications Configuring TFTP Server [ Configured on Presence Server ] (Desk phone and Soft phone modes) Configured on CUP server in CUPC Settings TFTP Server is used to download: CNF configuration file when using soft phone mode Custom Configuration file for Enhanced Directory integration Application Dial rules (if configured) Directory Lookup rules (if configured) 48

49 Unified Communications Creating CTI Profiles [ Configured on UC Manger ] Desk phone mode requires a CTI configuration Additional profiles can be created to distribute CTI Load Users must have CTI group membership (Standard CTI) Users must be associated to profile (unless default) Service Profile UC Services IM & Presence Profile Directory Profile* CTI Profile Voic Profile Conferencing Profile Presence Server 8.x CTI Profile created on CUP Presence Server 9.x CTI Profile created as part of UC Service profile on UC manager 49

50 Unified Communications CSF Device (Soft Phone Only) Jabber Device Types CSF TCT TAB CSF BOT CTIRD Device Naming Convention Free form, no correlation to username required Any character [A-Z,0-9] up to 15 characters Required Device Parameters Parameters without default values (must be explicitly set) Device Name Device Pool, Phone Buttons Template, Device Security Profile, SIP Profile 50

51 Unified Communications Device / Line Association (Soft & Deskphone Modes) Device must be associated to user Standard CCM User required for CCMCIP access Line needs to be associated to user Line Presence (this is configured on device) 51

52 Unified Communications Group/Role Membership (Soft & Deskphone Mode) User be given required permissions on UC Manager Soft Phone required permissions Standard CCM End Users Allows access to CCMCIP Service Desk Phone Control required permissions Standard CCM End Users Allows access to CCMCIP Service Standard CTI Enabled Standard CTI allow control of Phones supporting connected xfer/conf Standard CTI Allow control of phones supporting Rollover mode 52

53 Unified Communications Configuring Publish Trunk SIP Trunk User Off Hook User On Hook On Premise deployments use Network based presence updates for call state Create SIP Trunk to CUP server host/address Update Service Parameter Service Parameter Cisco Call Manager CUP PUBLISH Trunk (set to Trunk Name) CUP Tasks Create Presence Gateway Type: CUCM Gateway: CUCM Host/address 53

54 Unified Communications Cisco Jabber Video Engine Cisco Jabber Video Engine is a H.264 AVC standard based media engine using in Cisco Jabber clients. The Engine provides full HD interoperability between Jabber desktop clients and telepresence solutions. Provides standard based audio (G.711a/u, G.722.1, G.729a) Provides Video rate adaption and support for Cisco ClearPath Media Resilience Mechanisms. (Rate adaption required RTCP) Supports frame sizes from QCIF to 720p HD at up to 30 frames per second.

55 Unified Communications Cisco Jabber Video Engine Supported Encoding for transmit QCIF (176 x CIF (352 x w288p(512 x q720p (640 x VGA (640 x w448p(768 x w576p(1024 x w720p (1280 x Client will decode any resolution within negotiated H.264 level Factors which influence video frame rates Camera / Light Conditions - Rate encoded by sender Network conditions - UC Manager configuration CPU and load on receiver - Rate Adaption (RTCP) 55

56 Unified Communications Video Rate Adaption - Enabling RTCP on UC Manager Device>Device Settings>Common Phone Profile The Product specific configuration layout on certain devices allows this to be overridden. Example 9971 has a device level RTCP option. 56

57 Unified Communications Desk Phone Video Jabber uses CDP protocol to discover tethered Cisco Phone. CAST protocol is used to negotiate video sessions based on call setup (lip sync) Jabber controls the phone using CTI protocol in desk phone mode CDP/CAST support is provided by Cisco Medianet MSI installer. (must be present)

58 Unified Communications Multi-Party Voice & Video Calling Jabber clients support multi-party conferences Ad-hoc conference uses Media groups in UC Manager Conference capability will depend on DSP architecture available in media resource group Audio only Audio and video DSP provided by Software bridge only Router DSP Farm Multi-point conference unit Scheduled video conferences call also supported Video Multipoint Conferencing Units Cisco TelePresence MCU 4500 Series Cisco TelePresence Server 7010 Cisco TelePresence Server 8000 Cisco Integrated Services Router (with PVDM3) 58

59 Unified Communications Dial Plan Considerations Directory Number Destination Number If UC Manager dial plan does not match the LDAP dial plan you may need to use rules or translation patterns. When initiating calls we need convert E.164 numbers to the UC manager dial plan When receiving calls we need to extend internal numbers to E.164 Application Dial Rules Translation Patterns Directory Lookup Rules PhoneLookupMasks Rules are created on CUCM and downloaded using TFTP A COP file must be applied to update dial rules 59

60 Unified Communications Dial Plan Mapping 60

61 Unified Communications Using Phone Masks for Formatted Strings A phone mask can be used if your directory has formatted number strings in phone attributes A phone mask can be used to add brackets, spaces, dashes and other character to a number string before a search +(1) A phone mask is a client configuration parameter and is part of the EDI custom directory configuration Phone mask PhoneNumberMasks (#) ### ### #### #-###-####### Single parameters supports multiple masks, format is area code (pipe) mask. Use pipe for additional masks. 61

62 Unified Communications Configuring Video Desktop Share Jabber for Windows supports Binary Floor Control Protocol (BFCP) for desktop sharing (RFC 4582). BFCP will encode a video stream of the senders desktop, this can be in addition to a camera video stream. Video desktop sharing can be between Jabber client and Cisco Video endpoints Requires UC Manager 8.6 and based on version may require COP file Camera Video Stream Jabber Client Device Configuration or SIP profile Jabber Client Desktop Video Stream EX Series 62

63 Unified Communications Voic Access/Visual Voic Jabber can visually display voice messages from Cisco Unity Connection. A voic Service profile defines Unity Connection a mail store information. UC Services Cisco Unity Connection Messaging Service Profile IM & Presence Profile Directory Profile* CTI Profile Voic Profile Conferencing Profile 63

64 Unified Communications Service Account Policies Jabber for Windows 9.1 will automatically link Presence and Phone services account. Administrator can link Unity and Presence account together. Passwords must be synchronised UC Manager 9.0/IM&P 9.0 Service Profile UC Manager 7/8+CU CUP Application Profile 64

65 Cisco WebEx Meetings Escalate to a Web Conference Cisco Webex provides a web based conferencing service Service Profile Administrator can create profiles for Cloud and On Premise WebEx services Jabber can support integration to WebEx SSO enabled sites Jabber can support 3 rd Party TSP services with Webex Meetings UC Services IM & Presence Profile Directory Profile* CTI Profile Voic Profile Conferencing Profile Cisco WebEx Meetings is a could based conferencing solution Cisco WebEx Meetings Server is an on premise, highly secure, fully virtualized, conferencing solution 65

66 Cisco WebEx Meetings Calendar Integration Wednesday, September 19 Jabber will show a schedule of WebEx meetings and other appointments in a Jabber Tab. Meetings information is retrieved from WebEx Meetings services as well as a choice between Microsoft Outlook, Lotus Notes or Google calendar.

67 Microsoft Office Integration Microsoft Office 2007 Integration Office 2007 integration allows conversations to be initiated directly inside Office and SharePoint applications Microsoft SharePoint 2007 Cisco Presence Light-Ups Word Microsoft Outlook 2007 Cisco Click to IM/Call 67

68 Microsoft Office Integration Microsoft Office 2010 Integration Office 2010 integration allows conversations to be initiated directly inside Office and SharePoint applications Cisco Click to IM/Call Cisco Presence Light-up 68

69 Microsoft Office Integration Active Directory requirements (Outlook Contact View) Cisco AD Wizard is a bulk update tool for settings proxyaddress (download from CUPC admin pack on cisco.com) Office 2010 requires the AD proxyaddress attribute to be populated with SIP URI for presence to be associated This can be set by administrator in Active Directory Users and Computers Exchange Management Console ADSI Edit 69

70 Microsoft Office Integration Understanding ProxyAddress Update process Exchange AD ProxyAddresses Populate SIP:[Jabber ID] Sync to Exchange Global Address List Offline Address List Generate Offline Address Book This process can take 24 hours to sync without Admin intervention Download Address Book Presence Light-up Offline Address List Outlook 70

71 Extending Cisco Jabber Extensible Tab / HTML Apps Jabber uses the Segoe UI font which can be applied using CSS for common UE styling HTML window instance running in client Up to 4 user defined tabs can be created If no Icon is created default globe icon is displayed HTML apps can leverage IM and Call URI for click to X Jabber SDK could be used to provide further functions. 71

72 Extending Cisco Jabber Creating dynamic tabs with URI s Administrators can include URL s in the HTML to provide click to X functions: This include XMPP: Start an IM conversation with a contact TEL: Make a call to a number (with confirmation, RFC based) Clicktocall: make a call to a number without confirmation TEL: URI 72

73 Extending Cisco Jabber Custom Tab Configuration File All tabs are held in the custom configuration file <?xml version="1.0" encoding="utf-8"?> <config version="1.0"> <Client> <jabber-plugin-config> <browser-plugin> <page refresh="false" preload="true"> <tooltip>sample App</tooltip> <icon> <url> </page> <page refresh="true" preload="true"> <tooltip>cisco</tooltip> <icon> <url> </page> </browser-plugin> </jabber-plugin-config> </Client> </config> Registry Settings are no longer used for Tab configuration 73

74 Cisco Jabber Considerations for Deploying MAC Client Directories Jabber for Mac doesn t auto-detect active directory configuration, LDAP profile is created on CUP Server Mac doesn t support binary object lookup for photos Photo URI configured on CUP Server Video Jabber for Mac support to be released shortly Desktop Share BFCP desktop sharing roadmap item, Webex desktop share supported Custom Tabs Custom Tabs not currently supported on Mac client 74

75 Summary First thought to take away In this session we have focused on Jabber deployments on premise Jabber can be deployed both in a Cloud and On-Premise model to fit your organisation Cloud based Deployment On Premise Deployment 75

76 Summary Second thought to take away In this session we have focused on the Jabber for Windows client Jabber can be deployed on the devices your organisation uses and on the devices your staff want to use. Windows Apple OSX Apple IOS (iphone/ipad) Android Web SDK 76

77 Summary Cisco Jabber is a flexible architecture which provides a cross platform, intuitive user experience with rich productive multi-modal communications Thank you for your attention 77

78 Call to Action Visit the Cisco Campus at the World of Solutions to experience Cisco innovations in action Get hands-on experience attending one of the Walk-in Labs Schedule face to face meeting with one of Cisco s engineers at the Meet the Engineer center Discuss your project s challenges at the Technical Solutions Clinics 78

79 79

80