Client

CachePasswordMobile

Applies to Cisco Jabber for mobile clients.

Specifies whether the client stores the password in the cache or not.

  • true (default)—The password field is filled and Automatic sign-in is displayed. The client stores the user password in cache; therefore, the users can automatically sign in when the client starts.

  • false—After the client successfully registers to the Cisco Unified Communications Manager, the password field is empty and Automatic sign-in is not displayed. The client cannot store the user password in cache; therefore, the users must enter their password each time the client starts.


Note

The client displays Automatic sign-in on first sign-in, or if the user clears the application data.

Example: <CachePasswordMobile>true</CachePasswordMobile>

CacheSessionCookieInDevice

Applies to Cisco Jabber for iPhone and iPad

Specifies whether Cisco Jabber for iPhone and iPad should cache the cookies to the iOS keychain. The SSO cookies cached in the iOS keychain allows users to sign in to Cisco Jabber automatically if the app stops working in the background.

  • true (default)—The cookies are cached to the iOS keychain.

  • false—The cookies are not cached to the iOS keychain.

ChatAlert

Applies to Cisco Jabber for Windows

Specifies the default sound for chat alerts. Users can change this value in the Sounds and Alerts tab of the Options window.

Example: <ChatAlert>IMAlert_1</ChatAlert>

JawsSounds

Applies to Cisco Jabber for Windows

Determines whether the default Windows notification sound is played when a contact search returns a result.

  • true (default)—The default Windows notification sound is played when a contact search returns a result.

  • false—No notification sound is played when a contact search returns a result.

EnablePrt

Applies to Cisco Jabber for desktop clients.

Specifies if the Report a problem menu item is available in the Help menu in the client.

  • true (default)—The Report a problem menu item is available.

  • false—The Report a problem menu item is removed.

Example: <EnablePrt>True</EnablePrt>

If you disable this parameter, users can still manually use the Start Menu > Cisco Jabber directory, or the Program files directory and launch the Problem Report Tool manually.

If a user manually creates a PRT, and this parameter value is set to false, then the zip file created from the PRT has no content.

EnablePrtEncryption

Enables problem report encryption. For Cisco Jabber for desktop clients, configure this parameter with the PRTCertificateName parameter. For Cisco Jabber for mobile clients, configure this parameter with the PRTCertificateUrl parameter.

  • true—PRT files sent by Cisco Jabber clients are encrypted.

  • false (default)—PRT files sent by Cisco Jabber clients are not encrypted.

PRT encryption requires a public or private key pair to encrypt and decrypt the Cisco Jabber problem report. For more information, refer to the Decrypt the Problem Report section in the document Features and Options for Cisco Jabber.

Example:<EnablePrtEncryption>true</EnablePrtEncryption>

PRTCertificateUrl

Applies to Cisco Jabber for mobile clients.

Specifies the URL to the certificate with a public key in the trusted root certificate store. The client downloads the public key, and uses it to encrypt the Cisco Jabber problem report. If EnablePrtEncryption is true, and no certificate is downloaded, due to a wrong URL or a network problem, Cisco Jabber does not send a PRT.

Example:<PRTCertificateUrl>http://server_name/path/Certificate_Name</PRTCertificateUrl>

PrtCertificateName

Applies to Cisco Jabber for desktop clients.

Specifies the name of a certificate with a public key in the Enterprise Trust or Trusted Root Certificate Authorities certificate store. The certificate public key is used to encrypt Cisco Jabber Problem reports. You must configure this parameter with the EnablePrtEncryption parameter.

Example:<PrtCertificateName>Certificate_Name</PrtCertificateName>

EnableFecc

Applies to all Cisco Jabber clients.

Specifies whether the ability to control far-end cameras is enabled in the client.

  • true (default)—Far-end camera control is enabled. The Far-End Camera Control button is enabled on the call video window.

  • false—Far-end camera control is disabled. The Far-End Camera Control button is disabled on the call video window, even if the endpoint can control far-end camera.

Example: <EnableFecc>false</EnableFecc>

ContactCardonHover

Applies to Cisco Jabber for Windows.

Specifies whether contact cards are displayed when you hover over contact names in your Contacts list and in search result.

  • true (default)—The contact card is displayed if you hover over contacts in the hub window or in a search result. For Jabber for Windows the contact card is displayed when you press CTRL + I over a contacts' name.

  • false—The contact card is not displayed when you hover over names in the Contacts list or in a search result.

Example: <ContactCardonHover>false</ContactCardonHover>

HideCallControlStrip

Applies to Cisco Jabber for Windows.

Specifies whether the call control strip is displayed in the call window.

  • enable—Displays the call control strip during calls. On the top bar of the Cisco Jabber call window, users have a new option to see or hide the call control strip.

  • disable (default)—Hides the call control strip during calls. Users see a video-only window without the call control strip.

Example:

<HideCallControlStrip>enable</HideCallControlStrip>

PrtLogServerURL

Specifies the custom script for submitting problem reports. For more information, see Configure Problem Reporting section from the document Features and Options for Cisco Jabber.

Example:<PrtLogServerURL>http://server_name:port/path/prt_script.php</PrtLogServerURL>

UpdateURL

Applies to Cisco Jabber desktop clients.

Specifies the URL to the automatic updates XML definition file on your HTTP server. The client uses this URL to retrieve the update XML file. For more information, see Configure Automatic Updates section from the document Features and Options for Cisco Jabber.

Example: <UpdateURL>http://http_servername/UpdateURL_file</UpdateURL>

jabber-plugin-config

Applies to Cisco Jabber for desktop clients.

Contains plug-in definitions such as custom embedded tabs that display HTML content. For more information, see Custom Embedded Tab Definitions section from the document Features and Options for Cisco Jabber.

Example: 
<jabber-plugin-config>
<browser-plugin>
<page refresh="true" preload="true">
<tooltip>Cisco</tooltip>
<icon>http://www.cisco.com/web/fw/i/logo.gif</icon>
<url>www.cisco.com</url>
</page>
</browser-plugin>
</jabber-plugin-config>

Forgot_Password_URL

Applies to Cisco Jabber for Windows.

Specifies the URL of your web page for users to reset or retrieve forgotten passwords.

In hybrid cloud-based deployments, use the Cisco WebEx Administration Tool to direct users to the web page to reset or retrieve forgotten passwords.

Example:

<Forgot_Password_URL>http://http_servername/Forgot_Password_URL</Forgot_Password_URL>

Persistent_Chat_Enabled

Applies to Cisco Jabber for desktop clients.

Specifies whether the persistent chat feature is available in the client.

  • true—The persistent chat interface is shown in the client.

  • false (default)—The parameter is set to the default value if the setting is not present in the configuration file.

Example: <Persistent_Chat_Enabled>true</Persistent_Chat_Enabled>

ChatTelephonyEscalationLimit

Applies to Cisco Jabber for Windows.

Defines the maximum number of participants allowed when telephony escalations are enabled for group chats and persistent chat.

Default value is 25 participants. If you set it to zero participants, then the parameter is disabled. However, there is no maximum limit for the participants.

Example: <ChatTelephonyEscalationLimit>10</ChatTelephonyEscalationLimit>

PersistentChatTelephonyEnabled

Applies to Cisco Jabber for Windows.

Specifies if the Call button is available when users are in persistent chat conversations.

  • true (default)—Enables the Call button in persistent chat, which allows users to click on it to initiate a phone call.
  • false—The Call button won't be displayed in persistent chat, so users can't initiate a conference.

Example: <PersistentChatTelephonyEnabled>false</PersistentChatTelephonyEnabled>

pChatShare

Applies to Cisco Jabber for Windows.

Defines whether screen sharing capabilities are enabled in persistent chat rooms.

  • true (default)—Screen sharing capabilities are enabled for users in persistent chat rooms. Users see the Share screen option displayed.

  • false—Screen sharing capabilities are disabled for users in persistent chat rooms. Users do not see the Share screen option displayed.

Example: <pChatShare>false</pChatShare>

pChatMeeting

Applies to Cisco Jabber for Windows.

Defines whether the Meet Now option is enabled in persistent chat rooms.

  • true (default)—WebEx meeting capabilities are enabled for users in persistent chat rooms. Users see the Meet Now option displayed.

  • false—WebEx meeting capabilities are disabled for users in persistent chat rooms. Users do not see the Meet Now option displayed.

Example: <pChatMeeting>false</pChatMeeting>

MaxNumberOfBookmarks

Applies to Cisco Jabber for desktop clients.

Specifies the maximum number of bookmarks allowed in persistent chat rooms.

  • 30 (default)—sets a maximum of 30 bookmarks.

Example: <MaxNumberOfBookmarks>20</MaxNumberOfBookmarks>

Mention_P2Pchat

Applies to Cisco Jabber for Windows.

Specifies whether mentions are enabled in person to person chat.

  • true (default)—Enables mentions in person to person chat.

  • false—Disables mentions in person to person chat.

Example: <Mention_P2Pchat>false</Mention_P2Pchat>

Mention_GroupChat

Applies to Cisco Jabber for Windows.

Specifies whether mentions are enabled in group chat.

  • true (default)—Enables mentions in group chat.

  • false—Disables mentions in group chat.

Example: <Mention_GroupChat>false</Mention_GroupChat>

Mention_PersistentChat

Applies to Cisco Jabber for Windows.

Specifies whether mentions are enabled in persistent chat.

  • true (default)—Enables mentions in persistent chat.

  • false—Disables mentions in persistent chat.

Example: <Mention_PersistentChat>false</Mention_PersistentChat>

UseSystemLanguage

Applies to Cisco Jabber for Windows Release 11.1(1) onwards.

Specifies which language is used for the client. The language is determined using the following process:

  1. The system checks the bootstrap file. If the language is specified in the bootstrap file (using the LANGUAGE parameter), then the specified language is used.

  2. If the language is not specified in the bootstrap file, then the system checks the UseSystemLanguage parameter:

    • true—The language is set to the same value as the operating system.

    • false (default)—The client uses the regional language as specified by the user. The regional language is set at Control Panel > Clock, Language, and Region > Region and Language > Change the date, time, or number format > Formats tab > Format dropdown.

Example:<UseSystemLanguage>true</UseSystemLanguage>

If the language is not specified in the bootstrap file and the UseSystemLanguage parameter is not included in the jabber-config.xml file, then the regional language is used.


Note

When this parameter is specified in the jabber-config.xml file on a TFTP server, it becomes effective only after the client is restarted (File > Exit).

spell_check_enabled

Applies to Cisco Jabber for Windows.

Specifies whether spell check is enabled in the client. Spell check supports autocorrect, allows users to select the correct word from a list of suggestions, and add a word to the dictionary.

  • true—Spell check is enabled.

  • false (default)—Spell check is disabled.

Example:<spell_check_enabled>true</spell_check_enabled>

spell_check_language

Applies to Cisco Jabber for Windows.

Specifies the default spell check language used. The client uses the default spell check language set. You can define the default language dictionary that you want the client to use.

From the conversation windows, users can select different default languages for each user they chat with.

Example: <spell_check_language>1031</spell_check_language> defines German as the default spell check language.

Disable_IM_History

Applies to Cisco Jabber for Windows.

Specifies whether the client retains the chat history after participants close the chat window.

Note

This parameter is not available for IM-only deployments.

  • true—Client does not retain the chat history after participants close the chat window.

  • false (default)—Client retains the chat history:

    • After participants close the chat window.

    • Until the participants sign out.

Before you configure this parameter, ensure that the message archiving is disabled on the server.

Example: <Disable_IM_History>true</Disable_IM_History>

If the participants reopen the chat window, only the last 99 messages are displayed.

EnableAutosave

Applies to Cisco Jabber for Windows.

Prerequisites:

  • Users must have a Cisco Unified Communications Manager account.

Specifies whether users can save instant messages automatically each time they close a conversation. Enable the option in the client as follows:

  • Windows—File > Options > Chats > Autosave each chat when closing the conversation.

  • true—The check box is available.

  • false (default)—The check box is unavailable.

Example: <EnableAutosave>true</EnableAutosave>

AutosaveChatsLocation

Applies to Cisco Jabber for Windows.

Defines the path where instant messages and file transfers are automatically saved each time a user closes a conversation. Use the absolute path on the local file system. Chats are saved in a folder called MyJabberChats and files are saved in a folder called MyJabberFiles.

If the AllowUserSelectChatsFileDirectory parameter is set to false, then this parameter works with the MyJabberFilesLocation parameter as follows:

  • If both the AutosaveChatsLocation parameter and the MyJabberFilesLocation parameter have a value, then the MyJabberFilesLocation value takes priority.

  • If the MyJabberFilesLocation parameter does not have a value, then the AutosaveChatsLocation value determines the path to the MyJabberChats and MyJabberFiles folders.

  • If both the AutosaveChatsLocation parameter and the MyJabberFilesLocation parameter have no value, then all chats and files are saved to the default location (Documents folder).

Example: <AutosaveChatsLocation>Local_Path</AutosaveChatsLocation>

AllowUserSelectChatsFileDirectory

Applies to Cisco Jabber for Windows.

Determines whether users can change the directory for the MyJabberChats and MyJabberFiles folders.

  • true (default)—Users can change the directory of the MyJabberChats and MyJabberFiles folders using the Change Folder button on the Chats tab of the Options dialog.

  • false—Users are not allowed to change the directory for the MyJabberChats and MyJabberFiles folders. The Change Folder button is not visible on the Chats tab of the Options dialog. The directory for the MyJabberChats and MyJabberFiles folders is determined by the AutosaveChatsLocation parameter.

If this parameter is not set, then the behavior is as for true.

Example: <AllowUserSelectChatsFileDirectory>true</AllowUserSelectChatsFileDirectory>

MyJabberFilesLocation

Applies to Cisco Jabber for Windows.

Defines the path where instant messages and file transfers are automatically saved each time a user closes a conversation. Chats are saved in a folder called MyJabberChats and files are saved in a folder called MyJabberFiles.

The user sets this parameter in the Chats tab of the Options dialog. When the user clicks the Change Folder button, a browse dialog opens and the filepath to the chosen folder is written to the MyJabberFilesLocation parameter.

This parameter can be set only if the AllowUserSelectChatsFileDirectory parameter is set to false.

This parameter works with the AutosaveChatsLocation parameter as follows:

  • If both the AutosaveChatsLocation parameter and the MyJabberFilesLocation parameter have a value, then the MyJabberFilesLocation value takes priority.

  • If the MyJabberFilesLocation parameter does not have a value, then the AutosaveChatsLocation value determines the path to the MyJabberChats and MyJabberFiles folders.

  • If both the AutosaveChatsLocation parameter and the MyJabberFilesLocation parameter have no value, then all chats and files are saved to the default location (Documents folder).

RestoreChatOnLogin

Applies to Cisco Jabber for desktop clients.

Specifies if the Remember my open conversations check box on the General tab of the Options window is checked when users sign in for the first time.

  • true—The Remember my open conversations check box is checked when users sign in to Cisco Jabber for the first time. Each time users sign into the client, all the person-to-person conversations that were open when they signed out are restored.

  • false (default)—The Remember my open conversations check box is not checked when users sign in to Cisco Jabber for the first time.

Users can override the initial setting by checking or unchecking the Remember my open conversations check box at any time.


Note

If chat history is not enabled, then the restored chat windows are empty.

Example: <RestoreChatOnLogin>false</RestoreChatOnLogin>

J2JMaxBandwidthKbps

Applies to all Cisco Jabber clients in cloud deployments only.

Specifies the maximum bandwidth (in kilobits per second) to be used for Jabber to Jabber calls. The video quality (resolution) of the call is lowered so that it meets the bandwidth limit.

On startup, Cisco Jabber applies this setting from the jabber-config.xml file that is downloaded from Cisco WebEx Messenger.

  • Minimum value—128 kbps. Values lower than this are automatically increased to 128Kbps.

  • Maximum value—4000 kbps. This is the default value. Values higher than 4000 kbps are automatically decreased to 4000 kbps.

SystemIdleDuringCalls

Applies to Cisco Jabber for Windows.

Specifies if the screen saver or computer lock function activates during a Cisco Jabber call if the user is inactive, and if the function is enabled on your Windows computer.

This parameter does not control any behavior for incoming calls when the screen is already locked or the screen saver is already on.

  • true—Screen saver can activate during calls.

  • false (default)—Screen saver cannot activate during calls or when users receive a new incoming call alert. When the call ends, or the new incoming call alert is accepted or rejected, then the screen saver or screen lock is enabled again.

Example: <SystemIdleDuringCalls>true</SystemIdleDuringCalls>

ShowRecentsTab

Applies to Cisco Jabber for Windows.

Specifies if you want to show or hide users' call history in the Recents tab on the Cisco Jabber hub window.

  • true (default)—The Recents tab is displayed.

  • false—The Recents tab is not displayed.

Example: <ShowRecentsTab>false</ShowRecentsTab>

SwapDisplayNameOrder

Applies to all Cisco Jabber clients.

Specifies that for certain locales, when the displayname directory field is empty or not available, users' own display names and the display names of their contacts can be changed to Lastname, Firstname format.

  • true (default)—In the following locales: Chinese (Hong Kong), Chinese (People's Republic of China), Chinese (Taiwan), Japanese, Korean; the format for users' own display names and the display names of their contacts is in the Lastname, Firstname format.

  • false—Users' own display names and the display names of their contacts is in the Firstname, Lastname format.

Example: <SwapDisplayNameOrder>false</SwapDisplayNameOrder>

MakeUsernameReadOnly

Applies to Cisco Jabber for desktop clients.

Makes the Username field on the Sign In screen read-only after the user signs in successfully for the first time.

  • true—Username field on the Sign In screen becomes read-only after the user signs in successfully for the first time. To enable the Username field again, or to switch to a different user, users must reset Cisco Jabber from the File menu.

  • false (default)—Username field on the Sign In screen remains editable after the user signs in successfully for the first time.

Example: <MakeUsernameReadOnly>true</MakeUsernameReadOnly>

ForceLogoutTimerDesktop

Applies to Cisco Jabber desktop clients.

Specifies the number of minutes of inactivity before the user is automatically signed out of Cisco Jabber desktop clients. If the parameter is not set, then the client does not sign out automatically.

The value for minutes is from 1 to 480.

Example:

<ForceLogoutTimerDesktop>15</ForceLogoutTimerDesktop>

ForceLogoutTimerMobile

Applies to Cisco Jabber mobile clients.

Specifies the number of minutes of inactivity before the user is automatically signed out of Cisco Jabber mobile clients. If the parameter is not set the client does not sign out automatically.

The value for minutes is from 1 to 480.

Example: <ForceLogoutTimerMobile>15</ForceLogoutTimerMobile>