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.
Specifies the address of the primary CCMCIP server.
Only if the address of your CCMCIP server is not the same as the TFTP server address.
If the address of the CCMCIP server is the same as the TFTP server address, the client can use the TFTP server address to connect to the CCMCIP server.
In deployments with Cisco Unified Communications Manager Release 8.
In deployments with Cisco Unified Communications Manager release 9 and later, the client can discover the CCMCIP server if you provision the _cisco-uds SRV record.
Cisco Unified Communications Manager release 9.x and earlier—If you enable Cisco Extension Mobility, the Cisco Extension Mobility service must be activated on the Cisco Unified Communications Manager nodes that are used for CCMCIP. For information about Cisco Extension Mobility, see the Feature and Services guide for your Cisco Unified Communications Manager release.
Example: <CcmcipServer1>server_address</CcmcipServer1>
Specifies the address of the secondary CCMCIP server.
Example: <CcmcipServer2>server_address</CcmcipServer2>
Specifies the address of the primary CTI server.
You should specify a CTI server address in the client configuration if users have desk phone devices.
Example: <CtiServer1>server_address</CtiServer1>
Specifies the address of the secondary CTI server.
Example: <CtiServer2>server_address</CtiServer2>
Example: <EnableCallPark>false</EnableCallPark>
Applies to Cisco Jabber for Mac and Cisco Jabber for mobile clients.
If EnableDSCPPacketMarking is configured with any of these values, then the user will not see Enable Differentiated Service for Calls option in the Cisco Jabber client.
Example: <EnableDSCPPacketMarking>false<EnableDSCPPacketMarking>
Applies to Cisco Jabber desktop clients.
Specifies the primary Cisco WebEx meeting site URL for users.
Cisco Jabber for Windows client populates the meeting site in the user's host account on the Options window. Cisco Jabber for Mac client populates the meeting site in the user's host account on the window. Users can enter their credentials to set up the host account and access their Cisco WebEx meetings, if the meeting site requires credentials.
If you specify an invalid meeting site, users cannot add, or edit, any meetings sites in the client user interface.
Example: <Meeting_Server_Address>Meeting_Site</Meeting_Server_Address>
Specifies the secondary Cisco WebEx meeting site URL for users.
Example: <Meeting_Server_Address_Backup>meeting_site</Meeting_Server_Address_Backup>
Specifies the tertiary Cisco WebEx meeting site URL for users.
Example: <Meeting_Server_Address2>meeting_site</Meeting_Server_Address2>
You deploy the client in phone mode.
The TFTP server address for the device configuration is different to the TFTP server address for the client configuration.
During installation, you should set the address of the TFTP server where the client configuration file resides with the following argument: TFTP.
Example: <TftpServer1>hostname</TftpServer1>
Specifies the address of the secondary Cisco Unified Communications Manager TFTP service.
Example: <TftpServer2>hostname</TftpServer2>
true—The Cisco Unified Communications Manager Group handles CTI load balancing. You should set this value in phone mode deployments only. In full UC mode, the presence server automatically handles CTI load balancing.
false (default)—The Cisco Unified Communications Manager Group does not handle CTI load balancing.
Example: <useCUCMGroupForCti>true</useCUCMGroupForCti>
Applies to Cisco Jabber for Windows.
true (default)—CTRL+SHIFT+J is enabled as the keyboard shortcut to make click-to-call.
false—The keyboard shortcut is disabled.
specify your own keyboard shortcut—Specify another keyboard shortcut as the value for this parameter, for example MakeCallHotKey=CTRL+SHIFT+R. Your own defined keyboard shortcut can use the following keys: CTRL and [SHIFT or ALT (but not both)], + a character, or CTRL + a character.
Example: <MakeCallHotKey>false</MakeCallHotKey>