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.
Example: <Set_Status_Away_On_Inactive>false</Set_Status_Away_On_Inactive>
Sets the amount of time, in minutes, before the availability status changes to Away if users are inactive.
The default value is 15.
Example: <Set_Status_Inactive_Timeout>10</Set_Status_Inactive_Timeout>
Applies to Cisco Jabber for Windows.
Example: <Set_Status_Away_On_Lock_OS>false</Set_Status_Away_On_Lock_OS>
Example: <StartCallWithVideo>false</StartCallWithVideo>
Server settings take priority over this parameter in the client configuration file. However, if users change the default option in the client user interface, that setting takes priority over both the server and client configurations.
Open the Cisco Unified CM Administration interface.
Select
.Set a value for the Never Start Call with Video parameter and then select Save.
Applies to Cisco Jabber for Windows .
Example: <Start_Client_On_Start_OS>true</Start_Client_On_Start_OS>
Applies to Cisco Jabber for desktop clients.
Applies to Cisco Jabber for Windows.
Specifies if users can create custom embedded tabs in the client.
true (default)—Menu option to create custom tabs is shown in the client.
false— Menu option to create custom tabs is not shown in the client.
Example: <AllowUserCustomTabs>false</AllowUserCustomTabs>
Example: <ShowContactPictures>false</ShowContactPictures>
Applies to Cisco Jabber for Windows and mobile clients only.
Example: <ShowOfflineContacts>false</ShowOfflineContacts>
Applies to Cisco Jabber for desktop clients.
Specifies whether the Location tab is available in the client.
true (default)—The Location tab is shown in the client.
false—The Location tab is not shown in the client.
Example: <Location_Enabled>false</Location_Enabled>
Applies to Cisco Jabber for desktop clients.
Example: <LOCATION_MATCHING_MODE>MacAddressWithSubnet</LOCATION_MATCHING_MODE>
Applies to Cisco Jabber for desktop clients.
Specifies whether the Location feature is enabled and whether users are notified when new locations are detected.
ENABLED (default)—Location feature is turned on. Users are notified when new locations are detected.
DISABLED—Location feature is turned off. Users are not notified when new locations are detected.
ENABLEDNOPROMPT—Location feature is turned on. Users are not notified when new locations are detected.
Example: <Location_Mode>DISABLED</Location_Mode>
Applies to Cisco Jabber for Windows.
Example: <DockedWindowVisible>false</DockedWindowVisible>
Applies to Cisco Jabber for Windows.
Example: <DockedWindowPosition>TopLeft</DockedWindowPosition>
Applies to Cisco Jabber for Windows.
Specifies the number of days before the call history is deleted.
If the value is zero or if it is not specified, then the call history is not deleted until the count exceeds the maximum number of stored calls.
Example: <Callhistory_Expire_Days>2</Callhistory_Expire_Days>
Applies to Cisco Jabber for Windows for on-premises and Office 365 deployments.
Enables the client to automatically save chat histories to a Cisco Jabber Chats folder in users' Microsoft Outlook application.
Example: <EnableSaveChatHistoryToExchange>true</EnableSaveChatHistoryToExchange>
Applies to Cisco Jabber for Windows for on-premises and Office 365 deployments.
Replaces the EnableSaveChatHistoryToExchange parameter.
Specifies if users can save chat history to a Cisco Jabber Chats folder in users' Microsoft Outlook application.
DisabledByPolicy (default)—Users cannot save chat history to Microsoft Outlook. The option Save chat sessions to "Cisco Jabber Chats" Folder in Microsoft Outlook is not visible in the client.
EnabledByPolicy—Chats are saved to Microsoft Outlook. The option Save chat sessions to "Cisco Jabber Chats" Folder in Microsoft Outlook is visible in the client, but users cannot access it.
Note | With this option, you must set up a method of authentication for the client to authenticate with the Exchange server. You can choose to authenticate using single sign-on, or by Synching credentials. For more information, see the On-Premises Deployment for Cisco Jabber. |
DisabledByDefault—Users can save chats to Microsoft Outlook. The option Save chat sessions to "Cisco Jabber Chats" Folder in Microsoft Outlook is unchecked in the client, but users can change it.
EnabledByDefault—Users can save chats to Microsoft Outlook. The option Save chat sessions to "Cisco Jabber Chats" Folder in Microsoft Outlook is checked in the client, but users can change it.
Example: <SaveChatHistoryToExchangeOperationMode>EnabledByDefault</SaveChatHistoryToExchangeOperationMode>
Applies to Cisco Jabber for Windows.
An authentication method to the Microsoft Exchange server. To save chat history to a Microsoft Outlook folder, the parameter enables the client to use the operating system account details of the signed in user to authenticate with the Exchange server. This authentication method uses the Windows NT LAN Manager (NTLM) security protocol.
true (default)—The client uses the operating system account details of the user to authenticate to the Exchange server.
false—The client does not use the user's operating system account details to authenticate to the Exchange server. Instead, users must enter their credentials in the Outlook tab of the Options dialog.
If you are using an Office 365 deployment, keep the value as false.
Example: <ExchangeAuthenticateWithSystemAccount>false</ExchangeAuthenticateWithSystemAccount>
Applies to Cisco Jabber for Windows for on-premises and Office 365 deployments.
An authentication method to the Microsoft Exchange server. To save chat history to a Microsoft Outlook folder, it synchronizes the Exchange credentials using one of the following Authenticator argument credentials for users:
CUP—Use IM and Presence Service credentials for Exchange
CUCM—Use Cisco Unified Communications Manager credentials for Exchange
WEBEX—Use Cisco WebEx credentials for Exchange
Define the value of the parameter as the authenticator for the service that you want used to sync credentials.
Example: <Exchange_UseCredentialsFrom>CUCM</Exchange_UseCredentialsFrom>.
Applies to Cisco Jabber for Windows for on-premises and Office 365 deployments.
If you have different domains for the Exchange Server and Cisco Unified Communications Manager.
If your Cisco Unified Communications Manager is pre 10.5 Release and you want to authenticate with Office 365. In pre 10.5 Cisco Unified Communications Manager, credentials do not contain a domain, however authentication with Office 365 does require a domain. Use this parameter to set a domain for the Exchange server.
Note | For Cisco Jabber for Windows, this parameter does not have any effect if the ExchangeAuthenticateWithSystemAccount parameter is set to true. |
Applies to Cisco Jabber for Windows for on-premises and Office 365 deployments.
Specifies the domain that the client uses to search for the Exchange server. This is used when the domain of the exchange server is different to the domain of the users credentials.
Define the value of the parameter as the domain to discover the Exchange server. The client uses the domain to search for the Exchange server at one of the following web addresses:
https://<domain>/autodiscover/autodiscover.svc
https://autodiscover.<domain>/ autodiscover/autodiscover.svc
Example: <ExchangeAutodiscoverDomain>domain</ExchangeAutodiscoverDomain>
Applies to Cisco Jabber for Windows for on-premises and Office 365 deployments.
Method of specifying server address. To save chat history to an Outlook folder, manually defines the internal Exchange server.
Example: <InternalExchangeServer>Internal_exchange_server</InternalExchangeServer>
Applies to Cisco Jabber for Windows for on-premises and Office 365 deployments.
Specifies the Exchange server address, the client uses this server when saving chat history to an Outlook folder.
Example: <ExternalExchangeServer>external_exchange_server</ExternalExchangeServer>
Applies to all Cisco Jabber clients.
Example: <EnableBridgeConferencing>true</EnableBridgeConferencing>
Applies to Cisco Jabber for mobile clients.
Specifies if the native contacts in the phone are loaded on Cisco Jabber contact list or not.
true—Native contacts are loaded on the Cisco Jabber contact list.
false(default)—Native contacts are not loaded the Cisco Jabber contact list.
Example: <EnableLoadAddressBook>true</EnableLoadAddressBook>
Applies to all clients.
Example: <UseBridgeForConferenceCalls>false</UseBridgeForConferenceCalls>
Applies to all clients.
Specifies the pattern for conference service in the client. For example, if the pattern is set as %%uid%%@example.com, and the user Adam McKenzie's user id is amckenzie, then the conference service is automatically set as amckenzie@example.com. This parameter is used with the EnableBridgeConferencing.
Example:<UserBridgeUriAdmin>%%uid%%@example.com</UserBridgeUriAdmin>
Applies to all clients.
Specifies how the client connects to meetings in Cisco Collaboration Meeting Rooms. For example, if you set the parameter to WebExOnly, and when users select Join in the Meetings Tab or on the Meeting invitation, they are connected to the conference using Cisco WebEx.Example: <ConfMediaType>WebExOnly</ConfMediaType>
Applies to Cisco Jabber for Windows.
0—Disables calendar integration in the Meetings tab of the client user interface. If you disable this parameter, the Meetings tab in the client is empty, but the Meetings tab remains on the hub window.
1—Enables Microsoft Outlook calendar integration in the Meetings tab of the client user interface.
2—Enables IBM Lotus Notes calendar integration in the Meetings tab of the client user interface.
3—Enables Google Calendar integration in the Meetings tab of the client user interface.
Restart Cisco Jabber to apply the changes.
Example: <CalendarIntegrationType>1</CalendarIntegrationType>
Note | Client users can override this setting on the Calendar tab of the Options dialog. |
Applies to Cisco Jabber for Windows.
Defines the number of minutes after which IBM Lotus Notes or Google calendars refresh. The default value is zero, meaning that the calendars do not automatically refresh.
Note | A high frequency refresh may affect performance of the IBM Lotus Notes server. |
Example: <CalendarAutoRefreshTime>5</CalendarAutoRefreshTime>
Applies to Cisco Jabber for Android and iPhone and iPad only.
The conference call service is enabled or disabled based on these conditions:
Conference Service is ON (default)—If UserBridgeUriAdmin is set to not null and bridgeConferencingEnabledByUser is set to true.
Conference Service is OFF— If UserBridgeUriAdmin is set to null and bridgeConferencingEnabledByUser is set to true.