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>

Applies to Cisco Jabber desktop clients.

Specifies whether files are automatically accepted by users during file transfer. This parameter doesn't apply to images, which you can configure using the AutoAcceptImages parameter.

• true—Files are automatically accepted to be downloaded when sent in an IM.

• false (default)—Files are not automatically accepted and the recipient must manually agree to receive the file.

Example: <AutoAcceptFileTransfer>true</AutoAcceptFileTransfer>

Applies to Cisco Jabber for desktop clients.

Set up .jpg, .jpeg, .gif, and .png images to be automatically accepted by users. The AutoAcceptFileTransfer parameter (which is off by default) does not affect this parameter as it does not apply to image files.

true (default)—Images are automatically accepted in the client.

false—Images are not automatically accepted and standard file transfer is used.

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>

Applies to Cisco Jabber for mobile clients.

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

• true (default)— The client stores the user password in cache; therefore, the users can automatically sign in when the client starts.

• false— The client cannot store the user password in cache; therefore, the users must enter their password each time the client starts.

Applies to Cisco Jabber for iPhone and iPad

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>

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>

Applies to Cisco Jabber for desktop clients.

Example: <ContactCardonHover>false</ContactCardonHover>

Applies to Cisco Jabber for mobile clients.

Specifies what happens when a Jabber user taps a contact from the contacts list or from the contact search result.

• Chat (default)—The client starts a chat session with the contact.

• Call—The client starts a VoIP call with the contact.

Note	These values are case-sensitive.

The setting specified for DefaultActionOfContactList parameter is not applicable for users with a Phone Only or IM Only account. If the Call option is configured for users who have full service deployed, then the client starts a mobile call when phone service is not available.

Example: <DefaultActionOfContactList>Call</DefaultActionOfContactList>

Applies to all Cisco Jabber clients from 11.8 version onwards.

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

Note	This parameter is not available for IM-only deployments.

Prerequisite: Before you configure this parameter, you must uncheck the UI setting Allow clients to log instant message history option in the IM and Presence Server.

• 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.

Example: <Disable_IM_History>true</Disable_IM_History>

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

Applies to Cisco Jabber for Windows

Example: <DisableAudioDucking>true</DisableAudioDucking>

Applies to Cisco Jabber for Windows and Cisco Jabber for Mac.

Specifies whether users receive reminders for Webex Meetings that are in their Jabber Meetings tab.

• true—Reminders are disabled.

• false (default)—Reminders are enabled.

Applies to Cisco Jabber for Windows

< DisableRemoteDesktopControl >true</ DisableRemoteDesktopControl >

Applies to Cisco Jabber for Windows .

Determines whether the Cisco Jabber popup meeting reminder is displayed for non-accepted Webex Meetings.

• true—The Jabber popup meeting reminder isn't displayed for Webex Meetings that have not been accepted.

• false (default)—The Jabber popup meeting reminder is displayed for non-accepted Webex Meetings.

Example:<DisableNonAcceptMeetingReminder>false</DisableNonAcceptMeetingReminder>

Applies to Cisco Jabber for Windows

Determines whether the Start online button is displayed in the Meetings tab for non-Webex Meetings. This parameter has no effect on Webex Meetings.

• true (default)—The Start online button does not display in the Meetings tab for non-Webex Meetings.

• false —The Start online button displays in the Meetings tab for non-Webex Meetings.

Example:<DisableStartOnlineForOfflineMeeting>false</DisableStartOnlineForOfflineMeeting>

Applies to Cisco Jabber for desktop clients.

Example: <EnableAutosave>true</EnableAutosave>

Applies to Cisco Jabber for desktop clients.

Set up inline images so that they are allowed or prevented from being displayed in the client without being downloaded first.

• true (default)—The image is displayed in Jabber automatically.

• false—File transfer is used where users must accept an image to see it.

Example: <EnableInlineImages>false</EnableInlineImages>

Applies to all Cisco Jabber clients.

Example: <EnableFecc>false</EnableFecc>

Applies to Cisco Jabber for desktop clients.

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.

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>

Applies to Cisco Jabber for Windows .

Specifies whether users receive reminders for Microsoft Outlook, Google Calendar, , IBM Notes and other non-Webex Meetings that are in their Jabber Meetings tab.

• true—Reminders are enabled.

• false (default)—Reminders are disabled.

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>

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>

Applies to Cisco Jabber for Desktop clients.

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>

Applies to Cisco Jabber for Windows.

Example:

<HideCallControlStrip>enable</HideCallControlStrip>

Applies to all clients.

Specifies the network IP protocol for the Cisco Jabber client.

• IPV4_Only—Jabber will only attempt to make IPv4 connections.

• IPV6_Only—Jabber will only attempt to make IPv6 connections.

• Dual_Stack (Default)—Jabber can connect with either IPv4 or IPv6.

Example:<IP_Mode>IPV4_Only</IP_Mode>

Applies to Cisco Jabber for all 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.

<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>

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.

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.

Applies to all Cisco Jabber clients for on-premises deployments.

Note	Do not use the LdapAnonymousBinding parameter with any of the following parameters because they can cause conflicting configuration: LDAP_UseCredentialsFrom ConnectionUsername and ConnectionPassword

Example: <LdapAnonymousBinding>true</LdapAnonymousBinding>

Applies to Cisco Jabber for desktop .

Example: <MaxNumberOfBookmarks>30</MaxNumberOfBookmarks>

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>

Applies to Cisco Jabber for Windows.

Example: <Mention_GroupChat>false</Mention_GroupChat>

Applies to Cisco Jabber for Windows.

Example: <Mention_P2Pchat>false</Mention_P2Pchat>

Applies to Cisco Jabber for Windows.

Example: <Mention_PersistentChat>false</Mention_PersistentChat>

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).

Applies to Cisco Jabber for Windows.

Example: <pChatMeeting>false</pChatMeeting>

Applies to Cisco Jabber for Windows.

Example: <pChatShare>false</pChatShare>

Applies to Cisco Jabber for desktop clients.

Example: <Persistent_Chat_Enabled>true</Persistent_Chat_Enabled>

Applies to Cisco Jabber for Windows.

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

Example: <PersistentChatTelephonyEnabled>false</PersistentChatTelephonyEnabled>

Applies to Cisco Jabber for Windows.

Keeps IM notifications of new messages on the screen until you dismiss them so they do not fade away. Newer notifications are stacked above older ones.

• true - Messages can stay on the screen until users dismiss them. Users have the option to turn persistent display off in their Options menu under Notifications.

• false (default) - Messages do not remain on the screen until dismissed. Messages are displayed and begin to fade away until there is no notification and only a flashing Jabber icon on the taskbar.

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>

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>

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>

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>

Applies to Cisco Jabber for Windows.

If a screen reader is running, displays informational messages in Jabber as pop-out windows.

• true (default) - If a screen reader is running, messages that are otherwise displayed in the client are instead displayed as pop-out windows for screen readers to capture them. If a screen reader is not running, informational messages are displayed as normal.

• false - If a screen reader is running, messages are not displayed in a pop-out window.

Applies to Cisco Jabber for mobile clients.

Specifies if the mobile icon is displayed when a user signs in to Jabber using mobile device. The mobile icon is available next to the user's availability status.

• On—The mobile icon is displayed. Also, the Show icon when on mobile option is not available in the client.

• Off—The mobile icon is not displayed. Also, the Show icon when on mobile option is not available in the client.

• Default_on (default)—The mobile icon is displayed only if the user enables Show icon when on mobile option in the client. When the user launches the client, by default the Show icon when on mobile option is enabled.

• Default_off—The mobile icon is displayed only if the user enables Show icon when on mobile option in the client. When the user launches the client, by default the Show icon when on mobile option is disabled.

• Empty or no value—The mobile icon is displayed.

<ShowIconWhenMobile>Default_on</ShowIconWhenMobile>

Applies to Cisco Jabber for Windows.

Example: <ShowRecentsTab>false</ShowRecentsTab>

Applies to Cisco Jabber for Windows.

Example:<spell_check_enabled>true</spell_check_enabled>

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.

Applies to all the Cisco Jabber clients.

Example:

<STARTUP_AUTHENTICATION_REQUIRED>false</STARTUP_AUTHENTICATION_REQUIRED>

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.

Example: <SwapDisplayNameOrder>false</SwapDisplayNameOrder>

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.

Example: <SystemIdleDuringCalls>true</SystemIdleDuringCalls>

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>

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).