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
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
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: All clients
Users can add groups to their contact lists in Cisco Jabber. The groups are created in the enterprise's Microsoft Active Directory and then are imported into Cisco Unified Communications Manager IM and Presence Service. When enterprise groups are set up and enabled on Cisco Unified Communications Manager IM and Presence Service, Cisco Jabber users can add enterprise groups to their contact list from the client.
Using enterprise groups is supported when on the Expressway for Mobile and Remote Access.
Before you can set up enabling adding enterprise groups to contact lists for your users, you must configure the feature on the server, see Enable Enterprise Groups section. For more information about enterprise groups, see the Feature Configuration Guide for Cisco Unified Communications Manager, Release 11.0(1) .
Enterprise Groups for Cisco Unified Communications Manager IM and Presence Service is available to on-premises deployments only. Enterprise Groups are already supported on cloud deployments.
Security Group is supported from Cisco Unified Communications Manager IM and Presence Service 11.5 or later.
Presence is unsupported for contacts in enterprise groups of over 100 people who are IM-enabled, unless the user has other presence subscriptions for a contact. For example, if users have someone added to their personal contact list who is also listed in an enterprise group of over 100 people, then presence is still displayed for that person. Users who are not IM-enabled do not affect the 100 person presence limit.
Nested groups cannot be imported as part of an enterprise group. For example, in an AD group, only group members are imported, not any embedded groups within it.
If your users and AD Group are in different organizational units (OUs), then before you add the contacts to the AD Group, you must sync both OUs with Cisco Unified Communications Manager, and not just the OU that the AD Group is in.
If you have the minimum character query set to the default value of 3 characters, then user searches for enterprise groups will exclude any two letter group names (for example: HR). To change the minimum character query for EDI, BDI, or UDS connections, change the value of the MinimumCharacterQuery parameter.
Enterprise groups with special characters cannot be located during searches if the special characters are among the first 3 characters (or whatever value you have defined as the minimum character query) of the name.
We recommend that you only change the distinguished name of enterprise groups outside of core business hours, as it would cause unreliable behavior from the Cisco Jabber client for users.
If you make changes to enterprise groups, you must synch the Active Directory with Cisco Unified Communications Manager afterwards in order for the changes to be applied.
When a directory group is added to Cisco Jabber, the profile photos are not displayed immediately because of the sudden load that the contact resolution places on the directory server. However, if you right-click on each group member to view their profile, the contact resolution is resolved and the photo is downloaded.
Intercluster peering with a 10.x cluster: If the synced group includes group members from a 10.x intercluster peer, users on the higher cluster cannot view the presence of synced members from the 10.x cluster. This is due to database updates that were introduced in Cisco Unified Communications Manager Release 11.0(1) for the Enterprise Groups sync. These updates are not a part of the Cisco Unified Communications Manager Releases 10.x. To guarantee that users homed on higher cluster can view the presence of group members homed on the 10.x cluster, users on the higher cluster should manually add the 10.x users to their contact lists. There are no presence issues for manually added user.
There is no search capability for enterprise groups when connecting using UDS, so users must know the exact enterprise group name that they want to add to their contact lists. There is a search capability for enterprise groups when connecting using EDI or BDI.
Enterprise group names are case-sensitive.
If two enterprise groups within an AD Forest have the same name, then users get an error when trying to add the group. This issue does not apply to clients using EDI or BDI.
The enterprise parameter Directory Group Operations on Cisco IM and Presence in the Enterprise Parameter Configuration window allows you to enable or disable the Enterprise Groups feature. Follow these steps to enable the Enterprise Groups feature.
The Cisco DirSync feature service must be running.
Applies to: All clients
File transfers and screen captures are enabled in Cisco Unified Communications Manager IM and Presence Service. There are additional parameters that are specified in the Cisco Jabber client configuration file. For more information on these parameters, see the Policies parameters.
To configure file transfers and screen captures in Cisco Unified Communications Manager IM and Presence Service 9.x or later, see Enable File Transfers and Screen Captures.
For peer to peer chats, see Enable File Transfer and Screen Captures for Peer to Peer Chats only.
For group chats and chat rooms, see Enable File Transfer and Screen Captures for Group Chat Rooms.
To configure maximum file transfer size, see Configuring Maximum File Transfer Size.
This applies to Cisco Unified Communication Manager IM and Presence Service 9.x, 10.0.x, and 10.5.1. You can enable or disable file transfers and screen captures using the Cisco XCP Router service on Cisco Unified Communications Manager IM and Presence Service. File transfers and screen captures parameter is enabled by default.
File transfers and screen captures are supported for both desktop and mobile clients.
Step 1 | Open the Cisco Unified CM IM and Presence Administration interface. |
Step 2 | Select . |
Step 3 | Select the appropriate server from the Server drop-down list. |
Step 4 | Select
Cisco
XCP Router from the
Service drop-down list.
The Service Parameter Configuration window opens. |
Step 5 | Locate the Enable file transfer parameter. |
Step 6 | Select the
appropriate value from the
Parameter Value drop-down list.
If you disable the setting on Cisco Unified Communications Manager IM and Presence Service, you must also disable file transfers and screen captures in the client configuration. |
Step 7 | Select Save. |
Files and screen captures transferred are stored on a file server and the metadata is logged to a database server. For Cisco Jabber clients that do not support chat rooms, this option enables file transfer in group chats.
When you enable this option, file transfers and screen captures are also available in peer to peer chats and the files and screen captures transferred are stored on a file server and the metadata is logged to a database server.
File transfer and screen captures for group chats and chat rooms is only available on Cisco Unified Communications Manager IM and Presence Service, release 10.5(2) or later.
Configure an external database to log metadata associated with the file transfer, see Database Setup for IM and Presence Service on Cisco Unified Communications Manager, Release 10.5(2) for further information.
Configure a network file server to save the file being transferred, see Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager, Release 10.5(2) for further information.
Step 1 | Open the Cisco Unified CM IM and Presence Administration interface. |
Step 2 | Select . |
Step 3 | In the File Transfer Configuration section select Managed File Transfer. |
Step 4 | In the Managed File Transfer Assignment section, assign the external database and the external file server for each node in the cluster. |
Step 5 | Select Save. |
Enable file transfer for peer to peer chats on Cisco Unified Communications Manager IM and Presence Service, release 10.5(2) or later. Files and screen captures are only transferred in a peer to peer chat. The file or screen capture information is not logged or archived.
Restart the Cisco XCP Router service.
The maximum file size is only available on Cisco Unified Communications Manager IM and Presence Service, release 10.5(2) or later.
The file transfer type selected is Managed File Transfer.
Restart the Cisco XCP Router service.
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: All clients, for cloud deployments.
Users who are signed into multiple devices can see all sent and received IMs on each device regardless of which device is active. Notifications are synchronized; if an IM is read on one device, it shows as read on other signed-in devices. This feature is enabled by default, but can be disabled with the Disable_MultiDevice_Message parameter. The following limitations apply:
Clients must be signed-in—Signed-out clients do not display sent or received IMs or notifications.
File transfer is not supported—Files are available only on the active devices that sent or received the file.
Group chat is not supported.
Multiple device messaging cannot be enabled if AES encryption is required.
Feature Functionality |
Description |
---|---|
Active Jabber clients enabled for Multiple Device Messaging |
Sent and received messages are displayed for the entire conversation. |
Inactive Jabber clients enabled for Multiple Device Messaging but signed in |
Sent and received messages are displayed for the entire conversation. |
Non-Multiple Device Messaging enabled Jabber clients and AES Encryption enabled Jabber clients |
Sent messages are only seen on sending device. Received messages are displayed on active devices only. |
For more information on parameters, see the latest Parameters Reference Guide for Cisco Jabber.
Applies to: Cisco Jabber for Windows, Cisco Jabber for Mac
Persistent chat must be enabled and configured on Cisco Unified Communications Manager IM and Presence Service before it can be used by the client.
Persistent chat is only available on Cisco Unified Communications Manager IM and Presence Service 10.0 and later.
Refer to Database Setup for IM and Presence Service on Cisco Unified Communications Manager for your release for information on the database configuration necessary to support the persistent chat feature. Database configuration must be performed before continuing with this task.
Local chat message archiving must be enabled for persistent chat. Local chat message archiving is enabled on Cisco Unified Communications Manager IM and Presence Service using the Allow clients to log instant message history setting, for more information, see the Enable Message Settings topic.
Step 1 | Open the Cisco Unified CM IM and Presence Administration interface. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 | Select . | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 | Select Enable Persistent Chat. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 | Ensure the settings How many users can be in a room at one time and How many hidden users can be in a room at one time under the Occupancy Settings section contain the same, non-zero value. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 5 | Configure the remaining settings as appropriate for your persistent chat deployment. We recommend the persistent chat settings in the following table.
|
Ensure you configure any client-specific parameters for persistent chat. For more information, see the Client parameters section of the latest Parameters Reference Guide for Cisco Jabber.
Enable file transfer in chat rooms. For more information, see Enable File Transfer and Screen Captures for Group Chats and Chat Rooms.
Note |
|
You administer persistent chat rooms from the Jabber client by creating rooms, delegating their moderators, and specifying members. The node on which the room is created is created automatically, although you can override it and specify a specific node. Administrators and moderators are privileged users in Persistent Chat rooms. You can administer Persistent Chat rooms on any service node that you are an administrator for on Cisco Unified Communications Manager IM and Presence servers.
Create rooms. When you create a room, you automatically become the room administrator.
Define and change up to 30 moderators for a chat room (who become room owners).
Specify and change the room name.
Define the maximum number of participants in a room. This number cannot be less than the number of participants already in a room.
Add and remove room members.
Block, remove, and revoke participants.
Destroy rooms (which removes it from the server, but the history is not deleted).
Room name (required, maximum 200 characters)
Description
Room type (public or restricted)
After the room type has been defined, it cannot be changed by anyone.
Specify whether to add the room to your My Rooms tab (off by default)
Add up to 30 moderators (who must have a valid Jabber ID to moderate a room).
Room password
After you create the room, you have the option to add members to the room immediately or at a later time. Refresh the All Rooms list in order to see your new room in the list of available rooms.
Persistent chat rooms that are password protected means that when users enter a room within a Jabber session, they must enter the password. Password protected rooms comply with the XEP-0045 specification from the XMPP Standards Foundation.
Applies to: All clients
You can enable or disable prompts for presence subscription requests from contacts within your organization. The client always prompts users for presence subscription requests from contacts outside your organization.
Users can choose to allow or block contacts from inside your organization.
you select Allow users to view the availability of other users without being prompted for approval, the client automatically accepts all presence subscription requests without prompting users.
you do not select Allow users to view the availability of other users without being prompted for approval, the client prompts users for all presence subscription requests.
If users choose to block contacts, only their existing contacts can see their availability status. In other words, only those contacts who have already subscribed to the user's presence can see their availability status.
Note | When searching for contacts in your organization, users can see the temporary availability status of all users in the organization. However, if User A blocks User B, User B cannot see the temporary availability status of User A in the search list. |
Users can choose the following options for contacts from outside your organization:
This feature is supported for on-premises deployments and is only available on Cisco Unified Communications Manager, release 8.x or later.
Step 1 | Open the Cisco Unified CM IM and Presence Administration interface. |
Step 2 | Select . The Presence Settings window opens. |
Step 3 | Select Allow users to view the availability of other users without being prompted for approval to disable prompts and automatically accept all presence subscription requests within your organization.
|
Step 4 | Select Save. |
Applies to:Cisco Jabber for Windows, Cisco Jabber for Mac.
This feature allows users to specify if open chat sessions are restored on next sign in. This only applies to 1:1 chats.
For desktop clients, this feature is configured using the RestoreChatOnLogin parameter. When the parameter is true the Remember my open conversations check box is selected on the General tab of the clients. The check box is not checked by default when users sign into Cisco Jabber for the first time.
For more information on parameters, see the Parameter Reference Guide for your release.
Applies to: All clients
Disable temporary presence to increase privacy control. When you configure this parameter, Cisco Jabber displays availability status only to contacts in a user's contact list.
This feature is supported for on-premises deployment and requires Cisco Unified Communications Manager, release 9.x or later.