Third Party Integrations

Integration with Microsoft Products

Applies to: Cisco Jabber for Desktop Clients

Cisco Jabber for Windows supports a range of Microsoft products that integrate with the application. This section describes the support and integrations for these products.

Internet Explorer

Microsoft Internet Explorer 8 or later is required. Cisco Jabber for Windows uses the Internet Explorer rendering engine to display HTML content.

Cisco Jabber for Windows requires Internet Explorer active scripting to render IMs. See https:/​/​windows.microsoft.com/​en-US/​windows/​help/​genuine/​ie-active-script for instructions on enabling active scripting.


Note

Internet Explorer 9 users in Cloud-based deployments that use Single Sign On (SSO) get security alerts when they sign in to Cisco Jabber for Windows. Add webexconnect.com to the list of websites in the Compatibility View Settings window of Internet Explorer 9 to stop these alerts.

Office

Integration with the following versions of Office is supported:

  • Microsoft Office 2016, 32 and 64 bit

  • Microsoft Office 2013, 32 and 64 bit

  • Microsoft Office 2010, 32 and 64 bit

Office 365

Microsoft Office 365 supports different configuration types based on the plan or subscription type. Cisco Jabber for Windows has been tested with small business plan P1 of Microsoft Office 365. This plan requires an on-premises Active Directory server.

Client-side integration with Microsoft Office 365 is supported with the following applications:

  • Microsoft Office 2016, 32 bit and 64 bit

  • Microsoft Office 2013, 32 bit and 64 bit

  • Microsoft Office 2010, 32 bit and 64 bit

  • Microsoft SharePoint 2010

SharePoint

Integration with the following versions of SharePoint is supported:

  • Microsoft SharePoint 2013

  • Microsoft SharePoint 2010

Availability status in Microsoft SharePoint sites is supported only if users access those sites with Microsoft Internet Explorer. You should add the Microsoft SharePoint site to the list of trusted sites in Microsoft Internet Explorer.

Calendar Integration and Contact Resolution

Applies to: Cisco Jabber for Windows

You can use the following client applications for calendar integration and contact resolution:

  • Microsoft Outlook 2016, 32 bit and 64 bit

  • Microsoft Outlook 2013, 32 bit and 64 bit

  • Microsoft Outlook 2010, 32 bit and 64 bit

  • IBM Lotus Notes 9, 32 bit

  • IBM Lotus Notes 8.5.3, 32 bit

  • IBM Lotus Notes 8.5.2, 32 bit

  • IBM Lotus Notes 8.5.1, 32 bit

  • Google Calendar (calendar integration only)

Calendar integration and contact resolution are achieved with one or more of the following parameters:

  • CalendarIntegrationType—Determines which calendar is integrated with the Meetings tab on the client. Users can overwrite this value with the Calendar integration type field on the Calendar tab of the Options window.

  • EnableLocalAddressBookSearch—Specifies if users can search for and add local Microsoft Outlook or IBM Notes contacts to their contact lists.

  • EnableLotusNotesContactResolution—Lets users search for and add local IBM Notes contacts to their contact lists.

The following table shows how these parameters interact to achieve calendar integration and contact resolution with third party products.

Table 1 Options for Calendar Integration and Contact Resolution

Parameter Values

Contact Resolution

Calendar Integration

EnableLocalAddress BookSearch

EnableLotusNotes ContactResolution

CalendarIntegration Type

false

false

0 - none

None

None

true

false

0 - none

Microsoft Outlook

None

false

true

0 - none

None

None

true

true

0 - none

Microsoft Outlook

None

false

false

1 - Microsoft Outlook

None

Microsoft Outlook

true

false

1 - Microsoft Outlook

Microsoft Outlook

Microsoft Outlook

false

true

1 - Microsoft Outlook

None

Microsoft Outlook

true

true

1 - Microsoft Outlook

Microsoft Outlook

Microsoft Outlook

false

false

2 - IBM Notes

None

IBM Notes

true

false

2 - IBM Notes

None

IBM Notes

false

true

2 - IBM Notes

None

IBM Notes

true

true

2 - IBM Notes

IBM Notes

IBM Notes

false

false

3 - Google

None

Google

true

false

3 - Google

None

Google

false

true

3 - Google

None

Google

true

true

3 - Google

None

Google

Chat History in Microsoft Outlook

Applies to: Cisco Jabber for Windows

This feature is available in the following versions of the client:

Version of Cisco Jabber for Windows

Supported Servers

10.6

Microsoft Exchange 2013

Microsoft Exchange 2010

11.0

Microsoft Office 365

Microsoft Exchange 2013

Microsoft Exchange 2010

You can enable the client to automatically save chat histories to a Cisco Jabber Chats folder in the user's Microsoft Outlook application. When a user closes a chat window, the client saves the IM conversation to the Exchange server.

To enable the feature, you must:

  1. Set the EnableSaveChatHistoryToExchange parameter to true in the jabber-config.xml file.

  2. (optional) Set up a method to authenticate users to the Exchange server. If you don't specify an authentication method, then users can authenticate directly from the Outlook tab in the Options menu of their clients.

  3. Specify the method for determining which server to use.

For more information about all of the parameters that are needed to enable this feature, see the Parameters Reference Guide.

Limitations for Saving Chat History to an Outlook Folder

This feature can only be enabled if users have a Cisco Unified Communications Manager account.

Limitations with Authentication Methods over Cisco Expressway for Mobile and Remote Access

If you are enabling this feature for users connecting via the Expressway for Mobile and Remote Access, the following limitations apply:

  • If the client detects that the user is connecting via the Expressway, then the client uses the External Server option for the Exchange connection. If the external server is not set, then it uses the internal server.

  • If the client detects that the user is not connecting via the Expressway, then the client uses the Internal Server option for the Exchange connection. If the internal server is not set, the client uses the external server.

  • However, if either the internal or external server is set, but for some reason Cisco Jabber can't connect to it, the client doesn't revert to using the other server.

Authentication Modes

You must set up a method of authentication for the client to authenticate with the Exchange server. When authentication is complete, the client has access to the Exchange server which allows saving chat histories to a folder in Outlook.

If you do not specify an authentication method, then users must manually input their Exchange credentials in the Outlook tab in the client.

Authenticate Using Single Sign On for the Operating System

Applies to Cisco Jabber for Windows only.

The client uses the account details of the logged in user to authenticate with the Exchange server. This authentication method uses the Windows NT Lan Manager (NTLM) security protocol.

Note

Do not use this authentication method if some users share the same Windows account. The client authenticates with the account on the Operating System, and not with the user who is logged in to Cisco Jabber. For example, User A logs onto a Windows machine and then logs into Cisco Jabber for a morning shift. When the shift is done, Jabber is reset and User B logs into the client for the afternoon shift. Because User A is logged into the Windows account, then the chat messages from User B are saved in the Outlook account for User A.

Before You Begin

Users and their computers must use domains. Authentication using single sign on does not work if users are local Windows users.

Procedure
In the jabber-config.xml file, set the ExchangeAuthenticateWithSystemAccount parameter to true.

Authenticate by Synching Credentials

You can sync the Exchange credentials with another set of credentials for users, such as the Cisco Unified Communications Manager IM and Presence credentials. Using this method, the client uses the credentials to authenticate to the Exchange server.

Procedure
    Step 1   In the jabber-config.xml file, configure the Exchange_UseCredentialsFrom parameter.
    Step 2   Define the value of the parameter as the service that you want used to sync credentials. For example, <Exchange_UseCredentialsFrom>CUCM</Exchange_UseCredentialsFrom>. In this example, Cisco Unified Communications Manager is defined as the service which provides the Exchange server with credentials for authentication.

    Specify Server Addresses

    After you enable an authentication method for the client to access the Exchange server, you must enable a method for the client to specify the Exchange server address.

    If you do not specify server addresses, then users must manually enter the internal and external Exchange servers in the client, in the Outlook > Advanced tab of the Options menu.

    Detect Server Addresses Automatically

    Applies to Cisco Jabber for Windows only.

    You can configure the client to automatically discover the Exchange servers based on users' domain. This domain is defined when you set up the authentication method by using the domain that was specified for the user's credentials.

    Procedure
      Step 1   In the jabber-config.xml file, configure the ExchangeAutodiscoverDomain parameter.
      Step 2   Define the value of the parameter as the domain to discover the Exchange server. The client uses the domain to search for the Exchange server at one of the following Web addresses:

      https://<domain>/autodiscover/autodiscover.svc

      https://autodiscover.<domain>/autodiscover/autodiscover.svc

      Define Server Addresses

      You can define the internal and external Exchange server addresses in the configuration file.

      Procedure
        Step 1   In the jabber-config.xml file, configure the InternalExchangeServer and ExternalExchangeServer parameters.
        Step 2   Define the value of the parameters using the Exchange server addresses.

        Microsoft Outlook Calendar Events

        Applies to: Cisco Jabber for Windows

        You must apply a setting in Microsoft Outlook so that calendar events display in Cisco Jabber for Windows.

        Procedure
          Step 1   Open the email account settings in Microsoft Outlook, as in the following example:
          1. Select File > Account Settings.
          2. Select the Email tab on the Account Settings window.
          Step 2   Double-click the server name.

          In most cases, the server name is Microsoft Exchange.

          Step 3   Select the Use Cached Exchange Mode checkbox.
          Step 4   Apply the setting and then restart Microsoft Outlook.

          When users create calendar events in Microsoft Outlook, those events display in the Meetings tab.

          Microsoft Outlook Presence Integration

          Applies to: Cisco Jabber for Desktop Clients

          To enable integration with Microsoft Outlook, you must specify SIP:user@cupdomain as the value of the proxyAddresses attribute in Microsoft Active Directory. Users can then share availability in Microsoft Outlook.

          Use one of the following methods to modify the proxyAddresses attribute:

          • An Active Directory administrative tool such as Active Directory User and Computers

            The Active Directory User and Computers administrative tool allows you to edit attributes on Microsoft Windows Server 2008 or later.

          • ADSchemaWizard.exe utility

            The ADSchemaWizard.exe utility is available in the Cisco Jabber administration package. This utility generates an LDIF file that modifies your directory to add the proxyAddresses attribute to each user with the following value: SIP:user@cupdomain.

            You should use the ADSchemaWizard.exe utility on servers that do not support the edit attribute feature in the Active Directory User and Computers administrative tool. You can use a tool such as ADSI Edit to verify the changes that you apply with the ADSchemaWizard.exe utility.

            The ADSchemaWizard.exe utility requires Microsoft .NET Framework version 3.5 or later.

          • Create a script with Microsoft Windows PowerShell

            Refer to the appropriate Microsoft documentation for creating a script to enable presence in Microsoft Outlook.

          Enable Presence with the Active Directory User and Computers Tool

          Complete the following steps to enable presence in Microsoft Outlook for individual users with the Active Directory User and Computers administrative tool:

          Procedure
            Step 1   Start the Active Directory User and Computers administrative tool. You must have administrator permissions to run the Active Directory User and Computers administrative tool.
            Step 2   Select View in the menu bar and then select the Advanced Features option from the drop-down list.
            Step 3   Navigate to the appropriate user in the Active Directory User and Computers administrative tool.
            Step 4   Double click the user to open the Properties dialog box.
            Step 5   Select the Attribute Editor tab.
            Step 6   Locate and select the proxyAddresses attribute in the Attributes list box.
            Step 7   Select Edit to open the Multi-valued String Editor dialog box.
            Step 8   In the Value to add text box, specify the following value: SIP:user@cupdomain.

            For example, SIP:msmith@cisco.com.

            Where the user@cupdomain value is the user's instant messaging address. cupdomain corresponds to the domain for Cisco Unified Presence or Cisco Unified Communications Manager IM and Presence Service.

            Add Local Contacts from Microsoft Outlook

            Cisco Jabber for Windows lets users search for and add local contacts in Microsoft Outlook.

            All local contacts in Microsoft Outlook must have instant message addresses and phone numbers. These details allow client users to do the following:

            • add local Microsoft Outlook contact to their contact lists

            • see contact photos from the client

            • send instant messages to local contacts

            • call local contacts from the client

            Administrator Tasks

            To enable this integration with Microsoft Outlook, you must enable Cached Exchange Mode on the Microsoft Exchange server.

            To allow users to search for local contacts in Microsoft Outlook from the client, users must have profiles set in Microsoft Outlook.

            User Tasks

            Users must set the correct calendar preference on the client.

            1. Select File > Options.

            2. Select the Calendar tab.

            3. Select Microsoft Outlook.

            4. Restart Cisco Jabber to apply the change.

            IBM Notes Contact Search and Calendar Integration

            Applies to: Cisco Jabber for Windows

            Cisco Jabber for Windows supports IBM Notes calendar integration in the Meetings tab of the client. Cisco Jabber also lets users search for and add local contacts from IBM Notes. To enable this integration with IBM Notes, you must set the following parameters:

            • EnableLocalAddressBookSearch=true

            • EnableLotusNotesContactResolution=true

            • CalendarIntegrationType=2

            The CalendarIntegrationType parameter can be overridden by users. To enable calendar integration and contact resolution with IBM Notes, users must ensure that the Calendar integration type on the Calendar tab of the Options window is set to IBM Notes.


            Note

            In order for users to be able to successfully add IBM Notes contacts to their contact lists, the Messaging ID field in IBM Notes must contain a valid value.

            Contact Resolution for Incoming Calls

            For incoming calls, Cisco Jabber for Windows does not search the address book in IBM Notes, therefore only the phone number for an IBM Notes contact shows in the call history. If Cisco Jabber users subsequently search for the contact associated with the phone number, the call history changes to show the contact's name instead of the phone number.