The client retrieves configuration settings from XML files that reside on your TFTP server. Understand when you should create a custom configuration and learn about the different types of configuration files you can create.
In most environments, Cisco Jabber for Windows does not require any configuration to connect to the contact source or other services. You should create a configuration file for Cisco Jabber for Windows only if the default configuration does not suit your environment or you require custom configuration.
You should configure Cisco Jabber for Windows if:
The client workstation is not on the Windows domain.
You connect to one of the following as the contact source:
Global configuration files apply to all Cisco Jabber for Windows users. Cisco Jabber for Windows downloads the global configuration file from your TFTP server during the login sequence.
The default name for the global configuration file is jabber-config.xml.
Group configuration files apply to subsets of Cisco Jabber for Windows users. Group configuration files take priority over global configuration files.
Cisco Jabber for Windows retrieves group configuration files after users sign in to their phone account in the client for the first time. Cisco Jabber for Windows then prompts the users to sign out. During the second login sequence, Cisco Jabber for Windows downloads the group configuration file from your TFTP server.
Cisco Jabber for Windows loads group configuration files as follows:
Users are not signed in
Users sign in and then Cisco Jabber for Windows notifies the users about the change to their configuration settings.
Users sign out.
Users sign in and then Cisco Jabber for Windows loads the group configuration settings.
Users are signed in and use software phones for calls
Cisco Jabber for Windows notifies the users about the change to their configuration settings.
Users sign out.
Users sign in and then Cisco Jabber for Windows loads the group configuration settings.
Users are signed in and use desk phones for calls
Users sign out.
Users sign in and then Cisco Jabber for Windows notifies the users about the change to their configuration settings.
Users sign out.
Users sign in and then Cisco Jabber for Windows loads the group configuration settings.
If users select the option to use software phones for calls before they sign out, Cisco Jabber for Windows notifies the users to sign out and then sign in again to load the group configuration settings.
Group Configuration File Names
You specify the name of the group configuration files in the Cisco Support Field on the CSF device configuration in Cisco Unified Communications Manager.
If you remove the name of the group configuration file in the CSF device configuration on Cisco Unified Communications Manager, Cisco Jabber for Windows detects the change, prompts the users to sign out, and loads the global configuration file. You can remove the name of the group configuration file in the CSF device configuration by deleting the entire configurationFile=group_configuration_file_name.xml string or by deleting the group configuration filename from the string.
If users have desk phone devices only, use the following command line argument to specify unique names configuration files for different groups:
TFTP_FILE_NAME
See the Install Cisco Jabber for Windows chapter for more information about the command line arguments.
Configuration filenames are case sensitive. Use lowercase letters in the filename to prevent errors and to ensure Cisco Jabber for Windows can retrieve the file from the TFTP server.
You must use utf-8 encoding for the configuration files.
The client cannot read configuration files that do not have a valid XML structure. Ensure you check the structure of your configuration file for closing elements and that elements are nested correctly.
Your XML can contain only valid XML character entity references. For example, use & instead of &. If your XML contains invalid characters, the client cannot parse the configuration file.
Tip
Open your configuration file in Microsoft Internet Explorer to see if any characters or entities are not valid.
If Internet Explorer displays the entire XML structure, your configuration file does not contain invalid characters or entities.
If Internet Explorer displays only part of the XML structure, your configuration file most likely contains invalid characters or entities.
You can create custom configuration files in on-premises and hybrid cloud-based deployments. In cloud-based deployments, you configure Cisco Jabber for Windows through the Cisco WebEx Administration Tool.
Specify Your TFTP Server Address
The client gets configuration files from the TFTP server. For this reason, you must specify your TFTP server address when you create configuration files.
Specify Your TFTP Server on Cisco Unified Presence
Complete the steps to specify the address of your TFTP server on Cisco Unified Presence.
Step 1
Open the Cisco Unified Presence Administration interface.
Step 2
Select Application > Cisco Jabber > Settings.
Note
In some versions of Cisco Unified Presence, this path is as follows: Application > Cisco Unified Personal Communicator > Settings.
The Cisco Jabber Settings window opens.
Step 3
Locate the fields to specify TFTP servers in one of the following sections, depending on your version of Cisco Unified Presence:
Cisco Jabber Security Settings
CUPC Global Settings
Step 4
Specify the IP address of your primary and backup TFTP servers in the following fields:
Primary TFTP Server
Backup TFTP Server
Backup TFTP Server
Step 5
Select Save.
Specify Your TFTP Server on Cisco Unified Communications IM and Presence
Complete the steps to specify the address of your TFTP server on Cisco Unified Communications IM and Presence.
Step 1
Open the Cisco Unified CM IM and Presence Administration interface.
Step 2
Select Application > Legacy Clients > Settings.
The Legacy Client Settings window opens.
Step 3
Locate the Legacy Client Security Settings section.
Step 4
Specify the IP address of your primary and backup TFTP servers in the following fields:
Primary TFTP Server
Backup TFTP Server
Backup TFTP Server
Step 5
Select Save.
Specify TFTP Servers in Hybrid Cloud-Based Deployments
In hybrid cloud-based deployments, you can specify your TFTP server address with the Cisco WebEx Administration Tool.
Step 1
Open the Cisco WebEx Administration Tool.
Step 2
Select the Configuration tab.
Step 3
Select Unified Communications in the Additional Services section. The Unified Communications window opens.
Step 4
Select the Clusters tab.
Step 5
Select the appropriate cluster from the list. The Edit Cluster window opens.
Step 6
Select Advanced Server Settings in the Cisco Unified Communications Manager Server Settings section.
Step 7
Specify the IP address of your primary TFTP server in the TFTP Server field.
Step 8
Specify the IP address of your backup TFTP servers in the Backup Server #1 and Backup Server #2 fields.
Step 9
Select Save. The Edit Cluster window closes.
Step 10
Select Save in the Unified Communications window.
Create Global Configurations
Configure the client for all users in your deployment.
Remember:
If your environment has multiple TFTP servers, you must ensure that the configuration file is the same on all TFTP servers.
Step 1
Create a file named jabber-config.xml with any text editor.
Use lowercase letters in the filename.
Use utf-8 encoding.
Step 2
Define the required configuration parameters in jabber-config.xml.
If the structure of your configuration file is not valid, Cisco Jabber for Windows cannot read the values you set. Review the XML samples in this chapter for more information.
Step 3
Host the group configuration file on your TFTP server.
See the Host Configuration Files topic for instructions.
Apply different client configurations to different sets of users.
If you provision users with CSF devices, you specify the group configuration file names in the Cisco Support Field field on the device configuration.
If users do not have CSF devices, set a unique configuration file name for each group during installation with the TFTP_FILE_NAME argument.
Before You Begin
The Cisco Support Field field does not exist on Cisco Unified Communications Manager version 8.6.x or lower. You must apply a COP file as follows:
Download the Cisco Jabber for Windows administration package from Cisco.com.
Copy ciscocm.addcsfsupportfield.cop from the Cisco Jabber for Windows administration package to your file system.
Deploy ciscocm.addcsfsupportfield.cop on Cisco Unified Communications Manager.
See the Cisco Unified Communications Manager documentation for instructions on deploying COP files.
The COP file adds the Cisco Support Field field to CSF devices in the Desktop Client Settings section on the Phone Configuration window.
Step 1
Create an XML group configuration file with any text editor.
The group configuration file can have any appropriate name; for example, jabber-groupa-config.xml.
Use lowercase letters in the filename.
Use utf-8 encoding.
Step 2
Define the required configuration parameters in the group configuration file.
If the structure of your configuration file is not valid, Cisco Jabber for Windows cannot read the values you set. Review the XML samples in this chapter for more information.
Step 3
Specify the name of the group configuration file.
Open the Cisco Unified CM Administration interface.
Select Device > Phone.
Find and select the appropriate CSF device to which the group configuration applies.
The Phone Configuration window opens.
Navigate to Product Specific Configuration Layout > Desktop Client Settings.
Enter configurationfile=group_configuration_file_name.xml in the Cisco Support Field field.
For example, enter the following: configurationfile=groupa-config.xml
Use a semicolon to delimit multiple entries. Do not add more than one group configuration file. The client uses only the first group configuration in the Cisco Support Field field.
If you host the group configuration file on your TFTP server in a location other than the default directory, you must specify the path and the filename; for example, configurationfile=/customFolder/groupa-config.xml.
Select Save.
Step 4
Host the group configuration file on your TFTP server.
See the Host Configuration Files topic for instructions.
You can host configuration files on any TFTP server. However, Cisco recommends hosting configuration files on the Cisco Unified Communications Manager TFTP server, which is the same as that where the device configuration file resides.
Step 1
Open the Cisco Unified OS Administration interface on Cisco Unified Communications Manager.
Step 2
Select Software Upgrades > TFTP File Management.
Step 3
Select Upload File.
Step 4
Select Browse in the Upload File section.
Step 5
Select jabber-config.xml on the file system.
Step 6
Do not specify a value in the Directory text box in the Upload File section.
You should leave an empty value in the Directory text box so that the configuration file resides in the default directory of the TFTP server.
You must restart your TFTP server before Cisco Jabber for Windows can access the configuration files.
Step 1
Open the Cisco Unified Serviceability interface on Cisco Unified Communications Manager.
Step 2
Select Tools > Control Center - Feature Services.
Step 3
Select Cisco Tftp from the CM Services section.
Step 4
Select Restart.
A window displays to prompt you to confirm the restart.
Step 5
Select OK.
The Cisco Tftp Service Restart Operation was Successful status displays.
Step 6
Select Refresh to ensure the Cisco Tftp service starts successfully.
What to Do Next
To verify that the configuration file is available on your TFTP server, open the configuration file in any browser. Typically, you can access the global configuration file at the following URL: http://tftp_server_address:6970/jabber-config.xml
Configuration File Structure
You create Cisco Jabber for Windows configuration files in XML format. The XML configuration files contain the following elements:
XML Declaration
Your configuration file must conform to XML format standards. The first element in your configuration file must be a declaration as in the following example:
<?xml version="1.0" encoding="utf-8"?>
Root Element
The root element contains all group elements. The root element must also contain a version attribute as in the following example:
The following table describes the parameters you can specify within the Client element:
Parameter
Value
Description
PrtLogServerUrl
URL
Specifies the custom script for submitting problem reports.
For more information about problem reports, see Configure Problem Reporting.
UpdateUrl
URL
Specifies the URL to the automatic updates XML definition file on your HTTP server. Cisco Jabber for Windows uses this URL to retrieve the update XML file from your HTTP server.
For more information about automatic updates, see Configure Automatic Updates.
In hybrid cloud-based deployments, you should use the Cisco WebEx Administration Tool to configure automatic updates.
jabber-plugin-config
Plug-in definition
Contains plug-in configuration elements.
You can define custom embedded tabs to display HTML content in Cisco Jabber for Windows. For more information, see Custom Embedded Tabs.
Forgot_Password_URL
URL
Specifies the URL of your web page for users to reset or retrieve forgotten passwords.
In hybrid cloud-based deployments, you should use the Cisco WebEx Administration Tool to direct users to the web page to reset or retrieve forgotten passwords.
Directory Parameters
This section describes the parameters you can specify within the Directory element.
The client maps attributes in the directory to fields in user profiles. For example, by default, the BusinessPhone parameter maps to the telephoneNumber attribute.
As a result, the client retrieves the value of the telephoneNumber attribute from your directory for each user. That value then displays as the work phone number in the user profile. If your organization uses an attribute other than telephoneNumber for business phone numbers, you should change the mapping in the configuration file.
The following table describes the parameters for mapping directory attributes:
Parameter
Default Value
CommonName
cn
DisplayName
displayName
Firstname
givenName
Lastname
sn
EmailAddress
mail
SipUri
msRTCSIP-PrimaryUserAddress
PhotoSource
thumbnailPhoto
BusinessPhone
telephoneNumber
MobilePhone
mobile
HomePhone
homePhone
OtherPhone
otherTelephone
Title
title
CompanyName
company
UserAccountName
sAMAccountName
DomainName
userPrincipalName
Location
co
Nickname
displayName
PostalCode
postalCode
State
st
StreetAddress
streetAddress
Important:
The client uses the sAMAccountName attribute to resolve contacts in your directory by default.
When you synchronize users from your directory to Cisco Unified Communications Manager, you can specify the attribute for the user ID. If that attribute is not sAMAccountName, you must specify it in your configuration file as follows:
<UserAccountName>attribute-name</UserAccountName>
See the Specify an LDAP Attribute for the User ID topic for more information.
The following table describes parameters for configuring your directory connection:
Parameter
Value
Description
ConnectionType
0
1
Specifies if the client connects to a Global Catalog or a Domain Controller.
0
Connect to a Global Catalog. This is the default value.
1
Connect to a Domain Controller.
PrimaryServerName
IP address
FQDN
Specifies the address of the primary directory server.
This parameter is required for manual connections where the client cannot automatically discover the directory server.
SecondaryServerName
IP address
FQDN
Specifies the address of the backup directory server.
This parameter is required for manual connections where the client cannot automatically discover the directory server.
ServerPort1
Port number
Specifies the port for the primary directory server.
ServerPort2
Port number
Specifies the port for the backup directory server.
UseWindowsCredentials
0
1
Specifies if the client uses Microsoft Windows usernames and passwords.
0
Do not use Microsoft Windows credentials.
Specify credentials with the ConnectionUsername and ConnectionPassword parameters.
1
Use Microsoft Windows credentials. This is the default value.
ConnectionUsername
Username
Specifies a username to connect to the directory server.
Important: The client writes the username to a log file as plain text.
If you specify credentials in the configuration, you should use a shared, read-only directory account for all users.
ConnectionPassword
Password
Specifies a password to connect to the directory server.
Important: The client writes the password to a log file as plain text.
If you specify credentials in the configuration, you should use a shared, read-only directory account for all users.
UseSSL
0
1
Use SSL for secure connections to the directory.
0
Do not use SSL. This is the default value.
1
Use SSL.
UseSecureConnection
0
1
Encrypt all data over the network, including authentication and query data.
0
Enable data encryption. This is the default value.
1
Disable data encryption.
Directory Query Parameters
The following table describes parameters for configuring how Cisco Jabber for Windows queries your directory:
Parameter
Value
Description
BaseFilter
Base filter
Specifies a base filter for Active Directory queries.
Specify a directory subkey name only to retrieve objects other than user objects when you query Active Directory.
The default value is (&(objectCategory=person).
Configuration files can contain only valid XML character entity references. Use & instead of & if you specify a custom base filter.
PredictiveSearchFilter
Search filter
Defines a filter to apply to predictive search queries.
The default value is anr=
See the Predictive Search topic for more information.
DisableSecondaryNumberLookups
0
1
Specifies whether users can search for alternative contact numbers if the work number is not available, such as the mobile, home, or other number.
0
Users can search for alternative contact numbers. This is the default value.
1
Users cannot search for alternative contact numbers.
PhoneNumberMasks
Mask string
Specifies masks to use when users search for phone numbers.
For example, a user receives a call from +14085550100. In the directory, this number is +(1) 408 555 0100.
The following mask resolves the number: +14081+(#) ### ### ####
The length of mask strings cannot exceed the size restriction for registry subkey names.
See the Phone Masks topic for more information.
SearchTimeout
Number of seconds
Specifies the timeout period for queries in seconds.
The default value is 5.
UseWildcards
0
1
Enables wildcard searches.
0
Do not use wildcards. This is the default value.
1
Use wildcards.
If you use wildcards, it might take longer to search the directory.
SearchBase1
SearchBase2
SearchBase3
SearchBase4
SearchBase5
Searchable organizational unit (OU) in the directory tree
Specifies a location in the directory server from which searches begin. In other words, a search base is the root from which the client executes a search.
By default, the client searches from the root of the directory tree. You can specify the value of up to five search bases in your OU to override the default behavior.
Active Directory does not typically require a search base. You should specify search bases for Active Directory only for specific performance requirements.
You must specify a search base for directory servers other than Active Directory to create bindings to specific locations in the directory.
Tip
Specify an OU to restrict searches to certain user groups.
For example, a subset of your users have instant messaging capabilities only. Include those users in an OU and then specify that as a search base.
You can set masks to use when Cisco Jabber for Windows searches your directory for a phone number with the PhoneNumberMasks parameter.
Phone masks apply to phone numbers before Cisco Jabber for Windows searches your directory. If you configure phone masks correctly, directory searches succeed as exact query matches and prevent any impact to performance of your directory server.
The following table describes the elements you can include in a phone mask:
Element
Description
Phone number pattern
Provides a number pattern to retrieve phone numbers from your directory.
To add a phone mask, you specify a number pattern that applies to the mask.
For example, to specify a mask for searches that begin with +1408, you can use the following mask: +1408|+(#) ### ### ####
To enable a mask to process phone numbers that have the same number of digits, but different patterns, use multiple masks with the same number of digits.
For example, your company has site A and site B. Each site maintains a separate directory in which the phone numbers have different formats, such as the following:
+(1) 408 555 0100
+1-510-5550101
The following mask ensures you can use both numbers correctly: +1408|+(#) ### ### ####|+1510|+#-###-#######.
Pipe symbol (|)
Separates number patterns and masks.
For example, +1408|+(#) ### ### ####|+34|+(##) ### ####.
Wildcard character
Substitutes one or more characters for a subset of possible matching characters.
Any wildcard character can exist in a phone mask.
For example, an asterisk (*) represents one or more characters and can apply to a mask as follows: +3498|+##*##*###*####. Using this mask with the wildcard, a phone number search can match any of the following formats:
+34(98)555 0199
+34 98 555-0199
+34-(98)-555.0199
Reverse mask
Applies a number pattern from right to left.
For example, a mask of +3498|R+34 (98) 559 #### applied to +34985590199 results in +34 (98) 559 0199.
You can use both forward and reverse masks.
Contact Photo Parameters
The following table describes parameters for configuring how Cisco Jabber for Windows retrieves contact photos:
Parameter
Value
Description
PhotoUriSubstitutionEnabled
true
false
Specifies if photo URI substitution is enabled.
true
Photo URI substitution is enabled.
false
Specifies if photo URI substitution is disabled. This is the default value.
Photo URI substitution is supported only if you use EDI for directory integration.
PhotoUriSubstitutionToken
Directory attribute
Specifies a directory attribute to insert in the photo URI; for example, sAMAccountName.
PhotoUriWithToken
URI
Specifies a photo URI with a directory attribute as a variable value; for example, http://staffphoto.example.com/sAMAccountName.jpg.
To configure photo URI substitution, you set the directory attribute as the value of PhotoUriSubstitutionToken.
Remember: To resolve contact photos with UDS, you must specify the format of the contact photo URL as the value of the PhotoUriWithToken parameter.
Photo Formats and Dimensions
Cisco Jabber for Windows can display photos in most common file formats, including JPG, PNG, BMP, and GIF.
Important:
Contact photos in GIF format might render incorrectly or with less than optimal quality. To obtain the best quality, you should use PNG format for your contact photos.
The best dimensions for contact photos in Cisco Jabber for Windows are 128 by 128 pixels. Cisco Jabber for Windows automatically resizes images larger than 128 by 128 pixels.
To configure integration with OpenLDAP using anonymous binds, you must set the following parameters:
Parameter
Value
Description
DirectoryServerType
EDI
Connects to an LDAP directory service.
ConnectionType
1
Connects to a Domain Controller.
PrimaryServerName
IP address
Hostname
Specifies the primary server.
UseWindowsCredentials
0
Do not use Microsoft Windows credentials.
UseSecureConnection
1
Do not encrypt authentication and query data.
SearchBase1
Root of the directory service or the organizational unit (OU)
Specifies a location in the directory service from which searches begin.
UserAccountName
Unique identifier such as uid or cn
Specifies the directory attribute that holds the user account ID.
BaseFilter
Object class that your directory service uses; for example, inetOrgPerson.
Specifies which objects are returned when browsing for the search base.
PredictiveSearchFilter
uid or other search filter
Disambiguates the search string and returns results that match the attributes that are set for Ambiguous Name Resolution (ANR) on your directory service.
The following table describes the parameters you can specify within the Policies element in both on-premises deployments and hybrid cloud-based deployments:
Parameter
Value
Description
Video_Disabled
true
false
Enables or disables video capabilities.
true
Users cannot make or receive video calls.
false
Users can make and receive video calls. This is the default value.
In hybrid cloud-based deployments, you can set policies for the client through the Cisco WebEx Administration Tool. See Using policy actions available in Cisco WebEx for a list of available policies and descriptions.
You can specify service credentials parameters in your configuration so that users do not need to authenticate with certain services.
Voicemail Service Credentials
You can specify the following parameter to configure voicemail service credentials within the Voicemail element:
Parameter
Value
Description
VoiceMailService_UseCredentialsFrom
phone
Specifies that the client uses the phone service credentials to access voicemail services.
Ensure the user's phone service credentials match their voicemail service credentials. If you set this configuration, users cannot specify voicemail service credentials in the client interface.
This parameter is not set by default.
Important:
You can set this parameter in hybrid cloud-based deployments only.
In on-premises deployments, set a credentials source for voicemail services on the presence server. See the Set Up Voicemail section in the Cisco Jabber for Windows Server Setup Guide for more information.
The following is an example of the voicemail service credentials parameter:
You can specify the following parameter to configure phone service credentials within the CUCM element:
Parameter
Value
Description
PhoneService_UseCredentialsFrom
presence
Specifies that the client uses the presence service credentials to access phone services.
Ensure the user's presence service credentials match their phone service credentials. If you set this parameter, users cannot specify phone service credentials in the client interface.
Important:
You can set this parameter in on-premises deployments only.
The following is an example of the phone service credentials parameter:
To enable automatic updates, you create an XML file that contains the information for the most recent version, including the URL of the installation package on the HTTP server. The client retrieves the XML file when users sign in, resume their computer from sleep mode, or perform a manual update request from the Help menu.
Note
In hybrid cloud-based deployments, you should use the Cisco WebEx Administration Tool to configure automatic updates.
Before You Begin
Install and configure an HTTP server to host the XML file and installation package.
Ensure users have permission to install software updates on their workstations.
In some cases, Microsoft Windows stops update installations if users do not have administrative rights on their workstations.
Step 1
Host the update installation program on your HTTP server.
Step 2
Create an update XML file with any text editor.
XML files for automatic updates have the following structure:
URL of the installation package on your HTTP server.
Example:
The following is example XML for automatic updates:
<JabberUpdate>
<LatestBuildNum>12345</LatestBuildNum>
<LatestVersion>9.x</LatestVersion>
<Message><![CDATA[<b>This new version of Cisco Jabber lets you do the following:</b><ul><li>Feature 1</li><li>Feature 2</li></ul>For
more information click <a target="_blank" href="http://cisco.com/go/jabber">here</a>.]]></Message>
<DownloadURL>http://http_server_name/CiscoJabberSetup.msi</DownloadURL>
</JabberUpdate>
Step 4
Save and close your update XML file.
Step 5
Host your update XML file on your HTTP server.
Step 6
Specify the URL of your update XML file as the value of the UpdateUrl parameter in your configuration file.
Configure Problem Reporting
Setting up problem reporting enables users to send a summary of issues that they encounter with the client. There are two methods for submitting problem reports as follows:
Users submit the problem report directly through the client interface.
Users save the problem report locally and then upload it at a later time.
The client uses an HTTP POST method to submit problem reports. Create a custom script to accept the POST request and specify the URL of the script on your HTTP server as a configuration parameter. Because users can save problem reports locally, you should also create an HTML page with a form to enable users to upload problem reports.
Before You Begin
Complete the following steps to prepare your environment:
Install and configure an HTTP server.
Create a custom script to accept the HTTP POST request.
Create an HTML page to host on the HTTP server to enable users to upload problem reports that are saved locally. Your HTML page should contain a form that accepts the problem report saved as a .ZIP archive and contains an action to post the problem report using your custom script.
The following is an example form that accepts problem reports:
The following table describes the elements and attributes for defining custom embedded tabs:
Parameter
Value
Description
browser-plugin
All custom tab definitions
Contains all definitions of custom embedded tabs.
page
One custom tab definition
Contains the definition of a custom embedded tab.
refresh
true
false
Controls when the content of the embedded tab refreshes. Specify one of the following values:
true
The content refreshes each time the user selects the embedded tab.
false
The content refreshes only if users restart the client or sign out and sign in again. This is the default value.
This parameter is optional.
refresh is an attribute of the page element.
preload
true
false
Controls when the content of the embedded tab loads. Specify one of the following values:
true
The content loads when the client starts.
false
The content loads when users select the embedded tab. This is the default value.
This parameter is optional.
preload is an attribute of the page element.
tooltip
String of unicode characters
Defines the text that displays when users hover their cursors over the embedded tab.
This parameter is optional.
icon
URL
Specifies the location of the icon for the embedded tab. You can specify a local icon or a hosted icon.
Local Icon
Specify the URL of local icons as follows: file://path/icon_name.
For example, <icon>file://c:/icons/icon.png</icon>.
Hosted Icon
Specify the URL of hosted icons as follows: http://full_path/icon_name.
For example, <icon>http://domain/icons/icon.png</icon>
You can use any icon that Microsoft Internet Explorer can render, including .JPG, .PNG, and .GIF.
See the Custom Icons topic for information about dimensions and formats for custom icons.
This parameter is optional. If you do not specify an icon, or if the icon you specify does not load successfully, the client loads a default icon.
url
URL
Specifies the URL of the HTML page, or other content, that displays in the embedded tab.
The client uses the Internet Explorer rendering engine to display the content of the embedded tab. For this reason, you can specify the URL of any content that Internet Explorer supports.
Note
Cisco Jabber for Windows supports Internet Explorer version 9 or earlier. If a later version of Internet Explorer is installed on a workstation, the client uses Internet Explorer in version 9 mode.
This parameter is required.
Custom Icons
Icons for custom embedded tabs contain ten frames for each state within a single image file.
Note
To achieve optimal results, your custom icons should conform to the following guidelines:
Dimensions: 20 x 20 pixels
1 pixel of padding between each frame. 1 pixel of padding results in a working icon space of 19 by 19 pixels.
Transparent background
PNG file format
Each frame of an icon represents the following states:
Normal
Pressed
Hover
Disabled
Focused
Selected and normal
Selected and pressed
Selected and hover
Selected and disabled
Selected and focused
The following is an example icon:
The following are the hexadecimal color codes for each frame of the preceding icon. Use these color codes for a consistent appearance with your custom icons.
#4f6b7c
#2aa6c7
#99b5c7
#FFFFFF
#19bae3
#19bae3
#2aa6c7
#99b5c7
#FFFFFF
#19bae3
Chats and Calls from Custom Tabs
You can use protocol handlers to start chats and calls from custom embedded tabs.
Use the XMPP: or IM: protocol handler to start chats.
Use the TEL: protocol handler to start audio and video calls.
For more information, see the Protocol Handlers topic.
Feedback
