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 all Cisco Jabber clients.
Maximum value—4000 kbps. This is the default value. Values higher than 4000 kbps are automatically decreased to 4000 kbps.
Example: <EnableNGEPolicy>never</EnableNGEPolicy>
Applies to Cisco Jabber for desktop clients.
Always (default)—Logs are always written to disc at DEBUG level. No option appears in the client Help menu.
UserCanEnable—Allows users to decide whether logs are written to disc or not. Setting this value creates a Detailed Logging option in the Help menu of the client, where the user can enable or disable detailed logging. If enabled, DEBUG level logging is created, and if disabled, INFO level logging is created.
Never—Logs are never written to disc. INFO level logging is created. When a PRT is manually generated, in-memory logs are flushed to a temporary file that is deleted as soon as the PRT is generated.
Example: <LogWritingDesktop>UserCanEnable</LogWritingDesktop>
For INFO level logging, logs are kept in the in-memory buffer only, which is circular.
For DEBUG level logging, the in-memory buffer is flushed to disc when it is full. When resetting Jabber, all logs on disc are wiped.
Applies to Cisco Jabber for desktop clients.
If you configure the LogWritingDesktop parameter with the value UserCanEnable, then this parameter defines the number of hours that the desktop client writes logs to the disc. After the defined period expires, all logs are cleared from the disc.
If you do not specify a value for this parameter (default), then the client writes logs to the disc indefinitely, or until the user disables detailed logging.
Example: <DetailedLogDurationDesktop>10</DetailedLogDurationDesktop>
Applies to Cisco Jabber for mobile clients.
Always (default)—Logs are always written to disc at DEBUG level. No option appears in the client Help menu.
UserCanEnable—Allows users to decide whether logs are written to disc or not. Setting this value creates an Detailed Logging option in the Help menu of the client, where the user can enable or disable detailed logging. If enabled, DEBUG level logging is created, and if disabled, INFO level logging is created.
Never—Logs are never written to disc. INFO level logging is created. When a PRT is manually generated, in-memory logs are flushed to a temporary file that is deleted as soon as the PRT is generated.
Example: <LogWritingMobile>UserCanEnable</LogWritingMobile>
For INFO level logging, logs are kept in the in-memory buffer only, which is circular.
For DEBUG level logging, the in-memory buffer is flushed to disc when it is full. When resetting Jabber, all logs on disc are wiped.
Applies to Cisco Jabber for mobile clients.
If you configure the LogWritingMobile parameter with the value UserCanEnable, then this parameter defines the number of hours that the mobile client writes logs to the disc. After the defined period expires, all logs are cleared from the disc.
If you do not specify a value for this parameter (default), then the client writes logs to the disc indefinitely, or until the user disables detailed logging.
Example: <DetailedLogDurationMobile>10<DetailedLogDurationMobile>
Applies to Cisco Jabber for mobile clients.
Specifies whether the user can send or receive files on mobile.
true—Users cannot send or receive files on mobile.
false (default)—Users can send or receive files on mobile.
Example: <Disallow_File_Transfer_On_Mobile>true</Disallow_File_Transfer_On_Mobile>
Applies to all Cisco Jabber clients in cloud deployments.
Disables the multiple device messaging feature.
true—Disables the multiple device messaging feature.
false (default)—The multiple device messaging feature is enabled. Users can see all sent and received messages on all devices that they are signed into.
Note | Multiple device messaging does not support file transfer or screen captures. Files are available only on the active devices that sent or received the files. |
Example:
<Disable_MultiDevice_Message>true</Disable_MultiDevice_Message>
Enables or disables video capabilities during a Cisco Jabber video call.
true (default)—Users can make and receive video calls.
false—Users cannot make or receive video calls.
Example: <EnableVideo>false</EnableVideo>
Sets the phone type for users when the client starts for the first time. Users can change their phone type after starting the client for the first time. The client then saves the user preference, and uses it for the next time when the client starts.
deskphone—Use the desk phone device for calls.
softphone (default)—Use the software phone (CSF) device for calls.
Note | This parameter does not apply to Jabber deployed in a Virtual environment. |
Applies to Cisco Jabber for Windows.
Lets users add, edit, and delete remote destinations through the client interface. Use this parameter to change the default behavior when you provision Extend and Connect capabilities.
By default, if a user's device list contains only a CTI remote device, the client does not let that user add, edit, or delete remote destinations. This occurs to prevent users from modifying dedicated remote devices that you assign. However, if the user's device list contains a software device or a desk phone device, the client lets users add, edit, and delete remote destinations.
true—Users can add, edit, and delete remote destinations.
false (default)—Users cannot add, edit, and delete remote destinations.
Example: <UserDefinedRemoteDestinations>true</UserDefinedRemoteDestinations>
Applies to Cisco Jabber for Windows.
Allows you to determine whether users with multiple devices can edit or add remote destinations. For more information, see Configure Extend and Connect chapter from the document On-Premises Deployment for Cisco Jabber .
true (default)—Users with multiple devices can edit or add remote destinations.
false—Users with multiple devices cannot edit or add remote destinations.
Example: <RemoteDestinationEditingWithMultipleDevices>false</RemoteDestinationEditingWithMultipleDevices>
Applies to Cisco Jabber for Windows and Cisco Jabber for Android.
Specifies if users can search for and add local Microsoft Outlook or IBM Notes (release 11.1) contacts to their contact lists.
true (default)—Users can search for and add local contacts to their contact lists.
false—Users cannot search for or add local contacts to their contact lists.
Example: <EnableLocalAddressBookSearch>false</EnableLocalAddressBookSearch>
Applies to Cisco Jabber for Windows.
Lets users search for and add local IBM Notes contacts to their contact lists.
true—Users can search for and add local contacts from IBM Notes to their contact lists.
Note | The EnableLocalAddressBookSearch parameter must also be set to true. |
false (default)—Users cannot search for or add local contacts from IBM Notes to their contact lists.
Example: <EnableLotusNotesContactResolution>true</EnableLotusNotesContactResolution>
Applies to Cisco Jabber for Windows.
Example: <EnableAccessoriesManager>false</EnableAccessoriesManager>
Applies to Cisco Jabber for Windows.
Disables specific Accessories Manager plugins from third party vendors such as Jabra or Logitech. You should set the name of the plugin DLL file as the value. Use a comma to separate multiple values.
<BlockAccessoriesManagerPlugins> JabraJabberPlugin.dll,lucpcisco.dll </BlockAccessoriesManagerPlugins>
Applies to Cisco Jabber for Windows.
Example: <ForceFontSmoothing>false</ForceFontSmoothing>
Applies to all Cisco Jabber clients.
Example: <EnableBFCPVideoDesktopShare>false</EnableBFCPVideoDesktopShare>
Example: <EnableP2PDesktopShare>false</EnableP2PDesktopShare>
Example: <PreferP2PDesktopShare>true</PreferP2PDesktopShare>
Applies to Cisco Jabber for Windows
Enables Cisco Jabber clients to send information about all user actions to the Presence server for compliance or auditing purposes.
ScreenShareAuditMessagestrue—Cisco Jabber sends information to the Presence server about user actions during IM-only screen sharing.
false (default)—Cisco Jabber does not send any information to the Presence server about user actions during IM-only screen sharing.
Note | If you want to enable this feature, ensure that all Cisco Jabber clients are running at least release 11.0(1). If some clients are running older versions, the information that is collected during IM-only screen sharing is sent to the older Cisco Jabber clients as instant messages. |
Example: <ScreenShareAuditMessages>true</ScreenShareAuditMessages>
Example: <Meetings_Enabled>false</Meetings_Enabled>
Applies to all Cisco Jabber clients.
If your client is enabled for IM-only mode, then you must set this parameter to false. If you do not set this parameter in IM-only mode deployments, then users may see disabled telephony capabilities on their user interface.
Example: <Telephony_Enabled>false</Telephony_Enabled>
Example: <Voicemail_Enabled>false</Voicemail_Enabled>
Applies to Cisco Jabber for Windows.
Example: <EnableSaveChatToFile>false</EnableSaveChatToFile>
Applies to Cisco Jabber for Windows.
Example: <PrintIMEnabled>false</PrintIMEnabled>
Applies to Cisco Jabber for Windows.
Defines a catalog of security labels, such as SECRET and CONFIDENTIAL, that users must apply before they send an instant message. The label appears before each message that is sent. For example, SECRET: message text.
You can specify a maximum of 20 labels.
Cisco Jabber does not control message distribution based on these labels. Any such control requires the use of a third-party product, such as a Compliance server, which supports XEP-0258 label headers.
XEP-0258 is used to implement security labels. For more information, refer to XEP-0258: Security Labels in XMPP.
Example for jabber-config.xml for security labels:
<InstantMessageLabels> <item selector="Classified|SECRET"> <securitylabel xmlns='urn:xmpp: sec-label:0'> <displaymarking fgcolor='black' bgcolor='red'>SECRET </displaymarking> </securitylabel> </item> <item…> … </item> </InstantMessageLabels>
Applies to Cisco Jabber for desktop clients.
Example: <EnableSIPURIDialling>true</EnableSIPURIDialling>
Applies to all Cisco Jabber clients.
The mail attribute is used by default.
The value you specify must match the directory URI setting for users in Cisco Unified Communications Manager or the Cisco WebEx Administration Tool.
Example for EDI :<DirectoryURI>mail</DirectoryURI>
Example for BDI :<BDIDirectoryURI>mail</BDIDirectoryURI>
Applies to all Cisco Jabber clients.
Specifies a prefix to remove from the DirectoryUri or BDIDirectoryUri value.
For example, if your directory URI is sip:amckenzie@example.com, set DirectoryUriPrefix or BDIDirectoryUriPrefix to sip:.
Example for EDI :<DirectoryUriPrefix>sip:</DirectoryUriPrefix>
Example for BDI :<BDIDirectoryUriPrefix>sip:</BDIDirectoryUriPrefix>
Applies to Cisco Jabber for Windows.
Note | This parameter does not take effect when users connect to the corporate network through Expressway for Mobile and Remote Access. In this case, UDS provides contact resolution and the client cannot query the directory. |
Example: <ForceC2XDirectoryResolution>false</ForceC2XDirectoryResolution>
Applies to Cisco Jabber for Windows.
Example: <AlertOnAvailableEnabled>false</AlertOnAvailableEnabled>
Applies to all Cisco Jabber clients.
You can specify multiple, comma-separated values to exclude multiple services.
Example: <ServiceDiscoveryExcludedServices> WEBEX,CUCM </ServiceDiscoveryExcludedServices>
Specifies the Fully Qualified Domain Name that represents the DNS domain where the DNS SRV records for _collab-edge and _cisco-uds are configured.
The VoiceServicesDomain value will be voice.example.com.
Applies to Cisco Jabber for Mac.
If you configured this parameter for earlier versions of Cisco Jabber for Windows, it can still be used for this release. However, we recommend using the DeskPhoneModeWindowBehavior parameter instead.
Example: <CTIWindowBehaviour>Never</CTIWindowBehaviour>
Applies to Cisco Jabber for Windows.
Example: <DeskPhoneModeWindowBehavior>Never</DeskPhoneModeWindowBehavior>
Applies to Cisco Jabber for Windows.
Example: <SoftPhoneModeWindowBehavior>Never</SoftPhoneModeWindowBehavior>
Applies to Cisco Jabber for desktop clients.
Example: <EnableCallPickup>true</EnableCallPickup>
Applies to Cisco Jabber for desktop clients.
Example: <EnableGroupCallPickup>true</EnableGroupCallPickup>
Applies to Cisco Jabber for desktop clients.
Example: <EnableOtherGroupPickup>true</EnableOtherGroupPickup>
Applies to Cisco Jabber for desktop clients.
Example: <EnableHuntGroup>true</EnableHuntGroup>
Applies to Cisco Jabber for desktop clients.
Example: <PreventDeclineOnHuntCall>true</PreventDeclineOnHuntCall>
Applies to all Cisco Jabber clients.
Example: <TelemetryEnabled>false</TelemetryEnabled>
Applies to all the Cisco Jabber clients.
This identifier must be globally unique regardless of the method used to create the GUID.
Example: <TelemetryCustomerID>customerIdentifier</TelemetryCustomerID>
Applies to Cisco Jabber for mobile clients.
Example: <TelemetryEnabledOverCellularData>false</TelemetryEnabledOverCellularData>
Example: <EnableMediaStatistics>FALSE</EnableMediaStatistics>
Applies to Cisco Jabber for Windows.
true (default)—Dialog box is enabled, and users are asked to confirm that they want to place the call.
false—Dialog box is disabled, and the call is made without requesting confirmation first. This may cause accidental or unwanted calls.
Note | The CiscoTelProtocolPermissionEnabled parameter replaces the EnableTelProtocolPopupWindow parameter. Both parameters are supported in the client, however the dialog box is disabled if of the either parameter is set to false. |
Example: <CiscoTelProtocolPermissionEnabled>false</CiscoTelProtocolPermissionEnabled>
Applies to Cisco Jabber for Windows.
Example: <ClickToCallProtocolPermissionEnabled>false</ClickToCallProtocolPermissionEnabled>
Applies to Cisco Jabber for Windows.
Example: <ClickToCallWithEditProtocolPermissionEnabled>false</ClickToCallWithEditProtocolPermissionEnabled>
Applies to Cisco Jabber for mobile clients.
Specifies if a dialog box is shown asking users whether they want to return to another application when a call ends or to stay in Jabber.
Example: <CiscoTelProtocolCrossLaunchBackNotificationEnabled>false</CiscoTelProtocolCrossLaunchBackNotificationEnabled>
Applies to Cisco Jabber for mobile clients.
Users can specify parameters in a URL that are used to launch back to the original app. CrossLaunchBackSchema is a white list of allowed app schemas that can be cross launched back. You can specify additional parameters with each schema to allow cross launching the app with additional parameters. You can set specific parameters for the launched back schema. For example, for http, you can set the web site “www.cisco.com”. After specifying a schema and any additional parameters, use the semicolon to specify any additional schema you want to add.
Example: <CiscoTelProtocolCrossLaunchBackSchema>AppSchema1://parameter1; AppSchema2</CiscoTelProtocolCrossLaunchBackSchema>
Specifies whether users sign in by using single sign-on (SSO).
Example: <SSO_Enabled>FALSE</SSO_Enabled>
Applies to all the Cisco Jabber clients.
Example: <ServicesDomainSsoEmailPrompt>ON</ServicesDomainSsoEmailPrompt>
Example: <EnableForensicsContactData>false</EnableForensicsContactData>
Applies to Cisco Jabber for Windows.
This parameter is used with SharePortRangeSize to specify a port range to use when users share their screen from a chat window.
If you do not configure these parameters, then the client uses the default port range for IM screen share, 49152 to 65535. For more information on default port ranges, see the topic on Ports and Protocols in the Cisco Jabber Planning Guide.
The value you enter specifies the start of the port range. The minimum value is 1024. The value cannot exceed 65535 minus the SharePortRangeSize.
<Policies> <SharePortRangeStart>45130</SharePortRangeStart> <SharePortRangeSize>100</SharePortRangeSize> </Policies>This example gives the port range 45130 to 45230.
Applies to Cisco Jabber for Windows.
Specifies the size of the port range, when used with the SharePortRangeStart parameter. The minimum value is 40. The value when added to the SharePortRangeStart parameter cannot exceed 65535
For more information on port ranges, see the topic on Ports and Protocols in the Planning Guide for Cisco Jabber.
<Policies> <SharePortRangeStart>45130</SharePortRangeStart> <SharePortRangeSize>100</SharePortRangeSize> </Policies>
Applies to all Cisco Jabber clients.
Example: <EnableTelProtocol>false</EnableTelProtocol>
Applies to Cisco Jabber for Android, iPhone and iPad, and Windows.
Example: <EnableCiscoTelProtocol>false</EnableCiscoTelProtocol>
Applies to Cisco Jabber for Android, iPhone and iPad, and Windows.
Example: <EnableClickToCallProtocol>false</EnableClickToCallProtocol>
Applies to all Cisco Jabber clients.
Example: <EnableSIPProtocol>false</EnableSIPProtocol>
Applies to all Cisco Jabber clients.
Example: <EnableIMProtocol>false</EnableIMProtocol>
Applies to Cisco Jabber for Android, iPhone and iPad, and Windows.
Example: <EnableXMPPProtocol>false</EnableXMPPProtocol>
Applies to Cisco Jabber for Android, iPhone and iPad, and Windows.
Example: <EnableCiscoIMProtocol>false</EnableCiscoIMProtocol>
Applies to Cisco Jabber for Windows.
Example: <EnableCiscoTelConfProtocol>false</EnableCiscoTelConfProtocol>
Applies to Cisco Jabber for Windows.
Example: <EnableCiscoIMGroupProtocol>false</EnableCiscoIMGroupProtocol>
Applies to Cisco Jabber for Android, iPhone and iPad, and Mac.
Example: <EnableProvisionProtocol>false</EnableProvisionProtocol>
Applies to Cisco Jabber for mobile.
Example: <EnableShareProtocol>false</EnableShareProtocol>
Applies to Cisco Jabber for Android.
Specifies the number of times sharing files or messages can be initiated. For example, if theShareProtocolRateLimit is 3, and the ShareProtocolTimeLimit is 15 seconds, then a user can start files sharing or message sharing on Cisco Jabber three times every 15 seconds.
You can set the value between 1 to 100. The default value is 3.
Example: <ShareProtocolRateLimit>10</ShareProtocolRateLimit>
Applies to Cisco Jabber for Android.
Specifies the time within which sharing files or messages can be initiated. You can set the value between 1 to 300 seconds. The default value is 15 seconds.
Example: <ShareProtocolTimeLimit>10</ShareProtocolTimeLimit>
Applies to Cisco Jabber for mobile clients.
Example: <EnableCiscoChatProtocol>false</EnableCiscoChatProtocol>
Applies to Cisco Jabber for mobile clients.
Example: <EnableStatusProtocol>false</EnableStatusProtocol>
Applies to Cisco Jabber for mobile clients.
Example: <EnableProfileProtocol>false</EnableProfileProtocol>
Applies to Cisco Jabber for Mac.
Specifies if there is a limit on the number of times the telephony protocol handler is used in the client.
true (default)—Rate limiting is enabled for executing the telephony protocol handlers.
false—Rate limiting is disabled for executing the telephony protocol handlers.
Example: <EnableTelephonyProtocolRateLimit>false</EnableTelephonyProtocolRateLimit>
Applies to Cisco Jabber for Windows, Mac, and Android.
Specifies the number of times a call can be initiated from one of the telephony protocol handlers (tel: ciscotel, sip). For example, if the TelephonyProtocolRateLimit is 2, and the TelephonyProtocolTimeLimit is 10 seconds, then a user can start a call from one of the telephony protocol handlers two times every 10 seconds.
You can set the value between 1 to 100. The default value is 2.
Note | Only one protocol handler can be processed at one time. Any other protocol handler arriving when the user already has a call alert are either discarded or queued up. |
Example: <TelephonyProtocolRateLimit>10</TelephonyProtocolRateLimit>
Applies to Cisco Jabber for Windows, Mac, and Android.
Specifies the time within which a user can start a call from one of the telephony protocol handlers (sip, tel, ciscotel) before the TelephonyProtocolRateLimit is hit or reset. The default value for initiating a call from one of the telephony protocol handlers is 10 seconds for every two attempts. You can set the value between 1-300 seconds.
Example: <TelephonyProtocolTimeLimit>10</TelephonyProtocolTimeLimit>
Applies to Cisco Jabber for Android.
Specifies the number of times the URL provision protocol can be initiated.
For example, if the ProvisionProtocolRateLimit is 3 times, and the ProvisionProtocolTimeLimit is 15 seconds, then a user can launch Cisco Jabber with the URL provision three times every 15 seconds.
You can set the value between 1 to 100. The default value is 3.
Example: <ProvisionProtocolRateLimit>10</ProvisionProtocolRateLimit>
Applies to Cisco Jabber for Android.
Specifies the time within which the URL provision protocol can be initiated. You can set the value between 1 to 300 seconds. The default value is 15 seconds.
Example: <ProvisionProtocolTimeLimit>10</ProvisionProtocolTimeLimit>
Applies to Cisco Jabber for Android on Synergy devices.
Specifies the number of times that users can cross-launch after adding a contact with a URL to their contact lists. The Add Contact scheme can be used to add contacts into the contact list of a user with a URL (such as contact=username@cisco.com). For example, if the AddContactProtocolRateLimit is 3, and the AddContactProtocolTimeLimit is 15 seconds, then a user can cross-launch the Add Contact scheme on Cisco Jabber three times every 15 seconds.
You can set the value between 1 to 100. The default value is 3.
Example: <AddContactProtocolRateLimit>10</AddContactProtocolRateLimit>
Applies to Cisco Jabber for Android on Synergy devices.
Specifies the time within which users can cross-launch after adding a contact with a URL to their contact lists. You can set the value between 1 to 300 seconds. The default value is 15 seconds.
Examples: <AddContactProtocolTimeLimit>10</AddContactProtocolTimeLimit>
Applies to Cisco Jabber for Android on Synergy devices.
Specifies the number of times that the users can launch the Presence or Edit Presence screens from other applications. For example, if the PresenceProtocolRateLimit is three times, and the PresenceProtocolTimeLimit is 15 seconds, then a user can start the launch of Presence or Edit Presence screens from other applications three times every 15 seconds.
You can set the value between 1 to 100. The default value is 3.
Example: <PresenceProtocolRateLimit>10</PresenceProtocolRateLimit>
Applies to Cisco Jabber for Android on Synergy devices.
Specifies the time within which users can launch the Presence or Edit Presence screens from other applications. You can set the value between 1 to 300 seconds. The default value is 15 seconds.
Example: <PresenceProtocolTimeLimit>5</PresenceProtocolTimeLimit>
Applies to Cisco Jabber for Android on Synergy devices.
Specifies the number of times that users can launch the Profile screen of a contact from other applications. For example, if the ProfileProtocolRateLimit is three times, and the ProfileProtocolTimeLimit is 15 seconds, then a user can start the launch of the Profile screen of a contact from other applications three times every 15 seconds.
You can set the value between 1 to 100. The default value is 3.
Example: <ProfileProtocolRateLimit>10</ProfileProtocolRateLimit>
Applies to Cisco Jabber for Android on Synergy devices.
Specifies the time limit for users to launch the Profile screen of a contact from other applications. You can set the value between 1 to 300 seconds. The default value is 15 seconds.
Example: <ProfileProtocolTimeLimit>10</ProfileProtocolTimeLimit>
Specifies the fully qualified domain name (FQDN) of Cisco Unified Communications Manager service.
Defines the URL for the Self Care Portal when no default service profile is selected in Cisco Unified Communications Manager.
Example: <selfcareURL>http://server_name/selfcareURL</selfcareURL>