You can modify configuration files and add customized files to the TFTP directory. You can modify files or add customized files to the TFTP directory in Cisco Unified Communications Operating System Administration, from the TFTP Server File Upload window. For information about how to upload files to the TFTP folder on a Cisco Unified Communications Manager server, see the Cisco Unified Communications Manager System Guide.
You can obtain a copy of the Ringlist.xml or Ringlist-wb.xml files and the List.xml file from the system using the following admin command-line interface (CLI) "file" commands:
For more information, see the Cisco Intercompany Media Engine Command Line Interface Reference Guide.
Custom Phone Ring Creation
The Cisco Unified IP Phone ships with two default ring types that are implemented in hardware: Chirp1 and Chirp2. Cisco Unified Communications Manager also provides a default set of additional phone ring sounds that are implemented in software as pulse code modulation (PCM) files. The PCM files, along with an XML file (named Ringlist.xml) that describes the ring list options that are available at your site, exist in the TFTP server on each Cisco Unified Communications Manager server.
For more information, see the "Custom Phone Rings" chapter in the Cisco Unified Communications Manager Features and Services Guide and the "Software Upgrades" chapter in the Cisco Unified Communications Operating System Administration Guide.
The following sections describe how you can customize the phone rings that are available at your site by creating PCM files and editing the Ringlist.xml file:
The Ringlist.xml file defines an XML object that contains a list of phone ring types. This file includes up to 50 ring types. Each ring type contains a pointer to the PCM file that is used for that ring type and the text that appears on the Ring Type menu on a Cisco Unified IP Phone for that ring. The Cisco TFTP server for each Cisco Unified Communications Manager contains this file.
The CiscoIPPhoneRinglist XML object uses the following simple tag set to describe the information:
Upload the new PCM files that you created to the Cisco TFTP server for each Cisco Unified Communications Manager in your cluster. For more information, see the "Software Upgrades" chapter in Cisco Unified Communications Operating System Administration Guide.
Save your modifications and close the Ringlist.xml file.
To cache the new Ringlist.xml file, stop and start the TFTP service by using Cisco Unified Serviceability or disable and reenable the "Enable Caching of Constant and Bin Files at Startup" TFTP service parameter (that is found in the Advanced Service Parameters area.)
Custom Background Images
You can provide users with a choice of background images for the LCD screen on their phones. Users can select a background image by pressing the Applications Menu button and choosing Settings > User Preferences > Background Images on the phone.
The image choices that users see come from PNG images and an XML file (called List.xml) that are stored on the TFTP server used by the phone. By storing your own PNG files and editing the XML file on the TFTP server, you can designate the background images from which users can choose. In this way, you can provide custom images, such as your company logo.
The following sections describe how you can customize the background images that are available at your site by creating your own PNG files and editing the List.xml file:
The List.xml file defines an XML object that contains a list of background images. The List.xml file is stored in the following subdirectory on the TFTP server:
For more information, see the "Software Upgrades" chapter in the Cisco Unified Operating System Administration Guide.
The List.xml file can include up to 50 background images. The images are in the order that they appear in the Background Images menu on the phone. For each image, the List.xml file contains one element type, called ImageItem. The ImageItem element includes these two attributes:
Image: Uniform resource identifier (URI) that specifies where the phone obtains the thumbnail image that will appear on the Background Images menu on a Phone.
URI: URI that specifies where the phone obtains the full size image.
The following example shows a List.xml file that defines two images. The required Image and URL attributes must be included for each image. The TFTP URI that is shown in the example is the only supported method for linking to full size and thumbnail images. HTTP URL support is not provided.
<CiscoIPPhoneImageList> - <!--
Please Add Images to the end of the list
<ImageItem Image="TFTP:Desktops/95x34x1/TN-Mountain.png" URL="TFTP:Desktops/95x34x1/Mountain.png" /> <ImageItem Image="TFTP:Desktops/95x34x1/TN-Ocean.png" URL="TFTP:Desktops/95x34x1/Ocean.png" /> </CiscoIPPhoneImageList>
The Cisco Unified IP Phone firmware includes a default background image. This image is not defined in the List.xml file. The default image is always the first image that appears in the Background Images menu on the phone.
PNG File Requirements for Custom Background Images
Each background image requires two PNG files:
Full size image: Version that appears on the on the phone.
Thumbnail image: Version that appears on the Background Images screen from which users can select an image. The thumbnail image must be 25% of the size of the full size image.
Many graphics programs provide a feature that will resize a graphic. An easy way to create a thumbnail image is to first create and save the full size image, then use the sizing feature in the graphics program to create a version of that image that is 25% of the original size. Save the thumbnail version with a different name than the full size image.
The PNG files for background images must meet the following requirements for proper display on the Cisco Unified IP Phone:
Full size image: 95 pixels (width) X 34 pixels (height)
Thumbnail image: 23 pixels (width) X 8 pixels (height)
Color palette: For best results, set to monochrome (1-bit) when you create a PNG file.
Set Up Custom Background Image
To configure custom background images for the Cisco Unified IP Phone, follow these steps:
Upload the new PNG files that you created to the following subdirectory in the TFTP server for the Cisco Unified Communications Manager:
The file name and subdirectory parameters are case sensitive. Be sure to use the forward slash "/" when you specify the subdirectory path.
To upload the files, choose Software Upgrades > Upload TFTP Server File in Cisco IPT Platform Administration. For more information, see the "Software Upgrades" chapter in Cisco Unified Communications Operating System Administration Guide. If the folder does not exist, the folder gets created and the files get uploaded to the folder.
You must also copy the customized images and files to the other TFTP servers that the phone may contact to obtain these files.
Cisco recommends that you also store backup copies of custom image files in another location. You can use these backup copies if the customized files are overwritten when you upgrade Cisco Unified Communications Manager.
Save your modifications and close the List.xml file.
When you upgrade Cisco Unified Communications Manager, a default List.xml file will replace your customized List.xml file. After you customize the List.xml file, make a copy of the file and store it in another location. After upgrading Cisco Unified Communications Manager, replace the default List.xml file with your stored copy.
To cache the new List.xml file, stop and start the TFTP service by using Cisco Unified Serviceability or disable and re-enable the Enable Caching of Constant and Bin Files at Startup TFTP service parameter (located in the Advanced Service Parameters).
Custom Background Images for Large Font Locales
Phone background images may not display properly when large font locales such as Chinese, Japanese, and Korean are used. To modify a background image for proper display, follow these guidelines:
Use the following file sizes when creating PNG files for the Japanese locale:
95x28 (full size image)
23x8 (thumbnail image)
Upload the image files to %TFTPPATH%/Desktops/95x28x1.
Modify or create the List.xml file in the %TFTPPATH%/Desktops/95x28x1 folder to include the following lines, where image.png is the name of your image file:
If Cisco Unified Communications Manager has been configured to use G.722 and if the far endpoint supports G.722, the call can connect using the G.722 codec in place of G.711. The user may notice greater audio sensitivity during the call. Greater sensitivity means improved audio clarity but also means that more background noise can be heard by the far endpoint—noise such as rustling papers or nearby conversations. Even without a wideband handset, some users may prefer the additional sensitivity of G.722. Other users may be distracted by the additional sensitivity of G.722.
Two parameters in Cisco Unified Communications Manager affect whether wideband is supported for this Cisco Unified Communications Manager server or a specific phone:
Advertise G.722 Codec: From Cisco Unified Communications Manager, choose System > Enterprise Parameters. The default value of this enterprise parameter is True, which means that all Cisco Unified IP Phone Models 7906G and 7911G that are registered to this Cisco Unified Communications Manager will advertise G.722 to Cisco Unified Communications Manager. For more information, see Cisco Unified Communications Manager System Guide, "Cisco Unified IP Phones" chapter.
Advertise G.722 Codec: From Cisco Unified Communications Manager, choose Device > Phone. The default value of this product-specific parameter is to use the value specified in the enterprise parameter. If you want to override this on a per-phone basis, choose Enabled or Disabled in the Advertise G.722 Codec parameter on the Product Specific Configuration area of the Phone Configuration window.