The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Applies to: Cisco Jabber for Windows
You can add custom emoticons to Cisco Jabber for Windows by creating emoticon definitions in an XML file and saving it to the file system.
Note |
Cisco Jabber for Windows loads the custom emoticon definitions in emoticonDefs.xml.
Cisco Jabber for Windows loads emoticon definitions from emoticonDefs.xml.
<emoticons> <emoticon defaultKey="" image="" text="" order="" hidden=""> <alt></alt> </emoticon> </emoticons>
<emoticons> <emoticon defaultKey=":)" image="Emoticons_Smiling.png" text="Smile" order="1"> <alt>:-)</alt> <alt>^_^</alt> </emoticon> <emoticon defaultKey=":(" image="Emoticons_Frowning.png" text="Frown" order="2"> <alt>:-(</alt> </emoticon> </emoticons>
Applies to: Cisco Jabber for Windows
With Browser Click to Call, users can start a call from any of the following browsers:
Internet Explorer, from version 9
Mozilla Firefox, from version 38.0a1
Google Chrome, from version 45
Browser Click to Call is enabled with the CLICK2X installation parameter. If this parameter is set to ENABLED (default value), the feature is enabled. To disable this feature, you must set the CLICK2X installation parameter to DISABLE. For more information about the CLICK2X parameter, see the Deployment Guide for your release.
Click to Call from the Google Chrome browser requires user input before it can be enabled. After users install and sign into Cisco Jabber, they must restart the Google Chrome browser. When the browser opens, a popup displays requesting users to allow installation of the "Jabber Call" extension. Users must allow the installation by clicking Enable Extension. The extension is installed and users can now make calls by highlighting and right-clicking on any phone number that is displayed in the browser.
If users do not have administrator privleges for their machine, they do not receive the popup requesting them to allow installation of the "Jabber Call" extension. In this case, users must contact their system administrator to install the extension.
Click to Call from the Mozilla Firefox browser requires user input before it can be enabled. After users install Cisco Jabber, they must restart the Firefox browser. When the browser opens, a popup displays requesting users to allow installation of the "JabberCallAddOn" add-on. Users must allow the installation by clicking Allow this installation and Continue. The add-on is installed and users can now make calls by highlighting and right-clicking on any phone number that is displayed in the browser.
Click to Call from the Internet Explorer browser does not require any user permissions or installations.
Applies to: Cisco Jabber for Windows
The client uses an HTTP POST method to submit problem reports. Create a custom script to accept the POST request and specify the URL of the script on your HTTP server as a configuration parameter. Because users can save problem reports locally, you should also create an HTML page with a form to enable users to upload problem reports.
The following is an example form that accepts problem reports:
<form name="uploadPrt" action="http://server_name.com/scripts/UploadPrt.php" method="post" enctype="multipart/form-data"> <input type="file" name="zipFileName" id="zipFileName" /><br /> <input type="submit" name="submitBtn" id="submitBtn" value="Upload File" /> </form>
Applies to: Cisco Jabber for Windows
If instant messages and file transfers are automatically saved each time a user closes a conversation (with the EnableAutosave parameter), the default location for these files is the Documents folder. Chats are saved in a folder called MyJabberChats and files are saved in a folder called MyJabberFiles.
However, you can specify a different location with the AutosaveChatsLocation parameter or let users choose their own location with the AllowUserSelectChatsFileDirectory parameter. If users are allowed to set their own directory location, then the user setting takes priority over the system-defined setting. For more information about these parameters, see the Parameters Reference Guide for your release.
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:
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. |
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.
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.
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. |
Integration with the following versions of Office is supported:
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:
Integration with the following versions of SharePoint is supported:
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.
Applies to: Cisco Jabber for Windows
You must apply a setting in Microsoft Outlook so that calendar events display in Cisco Jabber for Windows.
When users create calendar events in Microsoft Outlook, those events display in the Meetings tab.
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.
Complete the following steps to enable presence in Microsoft Outlook for individual users with the Active Directory User and Computers administrative tool:
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:
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.
Users must set the correct calendar preference on the client.
Applies to: Cisco Jabber for Windows
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.
Set the EnableSaveChatHistoryToExchange parameter to true in the jabber-config.xml file.
(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.
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.
This feature can only be enabled if users have a Cisco Unified Communications Manager account.
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.
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.
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. |
Users and their computers must use domains. Authentication using single sign on does not work if users are local Windows users.
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.
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 Options menu.
tab of theApplies 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.
You can define the internal and external Exchange server addresses in the configuration file.