Configuring Localization Support

Table Of Contents

Configuring Localization Support

Contents

Information About Localization

System-Defined Locales

User-Defined Locales

Localization Support for Phone Displays

Multiple Locales

How to Configure Localization Support

Installing System-Defined Locales for Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971

Installing User-Defined Locales

Verifying User-Defined Locales

Configuring Multiple Locales

Verifying Multiple Locales

Configuration Examples for Localization

Multiple User and Network Locales: Example

User-Defined Locales: Example

Where to Go Next

Additional References

Related Documents

Technical Assistance

Feature Information for Localization Support

Configuring Localization Support

Last Updated: September 13, 2007

This chapter describes the localization support in Cisco Unified Communications Manager Express (Cisco Unified CME) for languages other than English and network tones and cadences not specific to the United States.

Finding Feature Information in This Module

Your Cisco Unified CME version may not support all of the features documented in this module. For a list of the versions in which each feature is supported, see the "Feature Information for Localization Support" section.

Contents

• Information About Localization

• How to Configure Localization Support

• Configuration Examples for Localization

• Where to Go Next

• Additional References

• Feature Information for Localization Support

Information About Localization

To configure localization support, you should understand the following concepts:

• System-Defined Locales

• User-Defined Locales

• Localization Support for Phone Displays

• Multiple Locales

System-Defined Locales

Cisco Unified CME provides built-in localization support for 12 languages including English and 16 countries including the United States. Network locales specify country-specific tones and cadences; user locales specify the language to use for text displays.

Configuring system-defined locales depends on the type of IP phone:

•Cisco Unified IP Phone 7905, 7912, 7940, and 7960—System-defined network locales and user locales are preloaded into Cisco IOS software. No external files are required. Use the network-locale and user-locale commands to set the locales for these phones.

•Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971—You must download locale files to support the system-defined locales and store the files in flash memory, slot 0, or on an external TFTP server. See the "Installing System-Defined Locales for Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971" section.

User-Defined Locales

The user-defined locale feature allows you to support network and user locales other than the system-defined locales that are predefined in Cisco IOS software. For example, if your site has phones that must use the language and tones for Traditional Chinese, which is not one of the system-defined choices, you must install the locale files for Traditional Chinese.

In Cisco Unified CME 4.0 and later, you can download files to support a particular user and network locale and store the files in flash memory, slot 0, or an external TFTP server. These files cannot be stored in the system location. User-defined locales can be assigned to all phones or to individual phones.

User-defined language codes for user locales are based on ISO 639 codes, which are available at the Library of Congress website: http://www.loc.gov/standards/iso639-2/. User-defined country codes for network locales are based on ISO 3166 codes.

For configuration information, see the "Installing User-Defined Locales" section.

Localization Support for Phone Displays

On the Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971, menus and prompts that are managed by the locale file for the IP phone type (.jar) or the Cisco Unified CME dictionary file are localized. Display options configured through Cisco IOS commands are not localized.

The following display items are localized by the IP phone (.jar file):

•System menus accessed with feature buttons (for example, messages, directories, services, settings, and information).

•Call processing messages

•Soft keys (for example, Redial and CFwdALL).

The following display items are localized by the dictionary file for Cisco Unified CME:

•Directory Service (Local Directory, Local Speed Dial, and Personal Speed Dial)

•Status Line

Display options configured through Cisco IOS commands are not localized and can only be displayed in English. For example, this includes features such as:

•Caller ID

•Header Bar

•Phone Labels

•System Message

Multiple Locales

In Cisco Unified CME 4.0 and later, you can specify up to five user and network locales and apply different locales to individual ephones or groups of ephones using ephone templates. For example, you can specify French for phones A, B, and C; German for phones D, E, and F; and English for phones G, H, and I. Only one user and network locale can be applied to each phone.

Each of the five user and network locales that you can define in a multilocale system is identified by a locale tag. The locale identified by tag 0 is always the default locale, although you can define this default to be any supported locale. For example, if you define user locale 0 to be JP (Japanese), the default user locale for all phones is JP. If you do not specify a locale for tag 0, the default is US (United States).

To apply alternative locales to different phones, you must use per-phone configuration files to build individual configuration files for each phone. The configuration files automatically use the default user-locale 0 and network-locale 0. You can override these defaults for individual phones by configuring alternative locale codes and then creating ephone-templates to assign the locales to individual ephones.

For configuration information, see the "Configuring Multiple Locales" section.

How to Configure Localization Support

This section contains the following tasks:

• Installing System-Defined Locales for Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971 (required)

• Installing User-Defined Locales (optional)

• Verifying User-Defined Locales (optional)

• Configuring Multiple Locales (optional)

• Verifying Multiple Locales (optional)

Installing System-Defined Locales for Cisco Unified IP Phone 7906, 7911, 7941, 7961, 7970, and 7971

Network locale files allow an IP phone to play the proper network tone for the specified country. You must download and install a tone file for the country you want to support.

User locale files allow an IP phone to display the menus and prompts in the specified language. You must download and install JAR files and dictionary files for each language you want to support.

To download and install locale files for system-defined locales, perform the following steps.

Prerequisites

•Cisco Unified CME 4.0(2) or a later version.

•You must create per-phone configuration files as described in the "SCCP: Defining Per-Phone Configuration Files and Alternate Location" section on page 147.

Restrictions

•Localization is not supported for SIP phones.

•Cisco Unified IP Phone 7931G supports United States English only.

•Phone firmware, configuration files, and locale files must be in the same directory, except the directory file for Japanese and Russian which must be in flash memory.

DETAILED STEPS

Step 1 Go to http://www.cisco.com/cgi-bin/tablebuild.pl/CME-Locale

You must have an account on Cisco.com to access the Software Download Center. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Step 2 Select your version of Cisco Unified CME.

Step 3 Select the TAR file for the locale you want to install. Each TAR file contains locale files for a specific language and country and uses the following naming convention:

CME-locale-language_country-CMEversion

For example, CME-locale-de_DE-4.0.2-2.0 is German for Germany for Cisco Unified CME 4.0(2).

Step 4 Download the TAR file to a TFTP server that is accessible to the Cisco Unified CME router. Each file contains all the firmware required for all phone types supported by that version of Cisco Unified CME.

Step 5 Use the archive tar command to extract the files to flash, slot 0, or an external TFTP server.

Router# archive tar /xtract source-url flash:/file-url

For example, to extract the contents of CME-locale-de_DE-4.0.2-2.0.tar from TFTP server 192.168.1.1 to router flash memory, use this command:

Router# archive tar /xtract tftp://192.168.1.1/cme-locale-de_DE-4.0.2-2.0.tar flash:

Step 6 See Table 15 and Table 16 for a description of the codes used in the filenames and the list of supported directory names.

Each phone type has a JAR file that uses the following naming convention:

language-phone-sccp.jar

For example, de-td-sccp.jar is for German on the Cisco Unified IP Phone 7970.

Each TAR file also includes the file g3-tones.xml for country-specific network tones and cadences.

Table 15 Phone-Type Codes for Locale JAR Files

Phone Type

Phone Code

7906/7911

tc

7941/7961

mk

7970/7971

td

Table 16 System-Defined User and Network Locales

Language

Language Code

User-Locale
Directory Name

Country Code

Network-Locale
Directory Name

English

en

English_United_States¹

US

United_States

English_United_Kingdom

UK

United_Kingdom

CA

Canada

Danish

dk

Danish_Denmark

DK

Denmark

Dutch

nl

Dutch_Netherlands

NL

Netherlands

French

fr

French_France

FR

France

CA

Canada

German

de

German_Germany

DE

Germany

AT

Austria

CH

Switzerland

Italian

it

Italian_Italy

IT

Italy

Japanese²

jp

Japanese_Japan

JP

Japan

Norwegian

no

Norwegian_Norway

NO

Norway

Portuguese

pt

Portuguese_Portugal

PT

Portugal

Russian

ru

Russian_Russia

RU

Russian_Federation

Spanish

es

Spanish_Spain

ES

Spain

Swedish

se

Swedish_Sweden

SE

Sweden

¹English for the United States is the default language. You do not need to install the JAR file for U.S. English unless you assign a different language to a phone and then want to reassign English.

²Katakana is supported by Cisco Unified IP Phone 7905, 7912, 7940, and 7960. Kanji is supported by Cisco Unified IP Phone 7911, 7941, 7961, 7970, and 7971.

Step 7 If you store the locale files in flash or slot 0: on the Cisco Unified CME router, create a TFTP alias for the user locale (text displays) and network locale (tones) using this format:

Router(config)# tftp-server flash:/jar_file alias directory_name/td-sccp.jar
Router(config)# tftp-server flash:/g3-tones.xml alias directory_name/g3-tones.xml

Use the appropriate directory name shown in Table 16 and remove the two-letter language code from the JAR file name.

For example, the TFTP aliases for German and Germany for the Cisco Unified IP Phone 7970 are:

Router(config)# tftp-server flash:/de-td-sccp.jar alias German_Germany/td-sccp.jar
Router(config)# tftp-server flash:/g3-tones.xml alias Germany/g3-tones.xml

Note On Cisco 3800 series routers, you must include /its in the directory name (flash:/its or slot0:/its). For example, the TFTP alias for German for the Cisco Unified IP Phone 7970 is:
Router# tftp-server flash:/its/de-td-sccp.jar alias German_Germany/td-sccp.jar

Step 8 If you store the locale files on an external TFTP server, create a directory under the TFTP root directory for each user and network locale.

Use the appropriate directory name shown in Table 16 and remove the two-letter language code from the JAR file name.

For example, the user-locale directory for German and the network-locale directory for Germany for the Cisco Unified IP Phone 7970 are:

TFTP-Root/German_Germany/td-sccp.jar
TFTP-Root/Germany/g3-tones.xml

Step 9 For Russian and Japanese, you must copy the UTF8 dictionary file into flash to use special phrases.

•Only flash can be used for these locales. Copy russian_tags_utf8_phrases for Russian; Japanese_tags_utf8_phrases for Japanese.

•Use the user-locale jp and user-locale ru command to load the UTF8 phrases into Cisco Unified CME.

Step 10 Assign the locales to phones. To set a default locale for all phones, use the user-locale and network-locale commands in telephony-service configuration mode.

Step 11 To support more than one user or network locale, see the "Configuring Multiple Locales" section.

Step 12 Use the create cnf-files command to rebuild the configuration files.

Step 13 Use the reset command to reset the phones and see the localized displays.

Installing User-Defined Locales

You must download XML files for locales that are not predefined in the system. To install up to five user-defined locale files to use with phones, perform the following steps.

Prerequisites

•Cisco Unified CME 4.0(3) or a later version.

•You must create per-phone configuration files as described in the "SCCP: Defining Per-Phone Configuration Files and Alternate Location" section on page 147.

Restrictions

•Localization is not supported for SIP phones.

•User-defined locales are not supported on the Cisco Unified IP Phone 7920 or 7936.

•User-defined locales are not supported if the configuration file location is system.

•When you use the setup tool from the telephony-service setup command to provision phones, you can only choose a default user locale and network locale, and you are limited to selecting a locale code that is supported in the system. You cannot use multiple locales or user-defined locales with the setup tool.

•When using a user-defined locale, the phone normally displays text using the user-defined fonts, except for any strings that are interpreted by Cisco Unified CME, such as "Cisco/Personal Directory," "Speed Dial/Fast Dial," and so forth.

Step 1 Go to http://www.cisco.com/cgi-bin/tablebuild.pl/CME-Locale

Step 2 Select your version of Cisco Unified CME.

Step 3 Select the TAR file for the locale that you want to install. Each TAR file contains locale files for a specific language and country and uses the following naming convention:

CME-locale-language_country-CMEversion-fileversion

For example, CME-locale-zh_CN-4.0.3-2.0 is Traditional Chinese for China for Cisco Unified CME 4.0(3).

Step 4 Download the TAR file to a TFTP server that is accessible to the Cisco Unified CME router. Each file contains all the firmware required for all phone types supported by that version of Cisco Unified CME.

Step 5 Use the archive tar command to extract the files to slot 0, flash, or an external TFTP server.

Router# archive tar /xtract source-url flash:/file-url

For example, to extract the contents of CME-locale-zh_CN-4.0.3-2.0.tar from TFTP server 192.168.1.1 to router flash memory, use this command:

Router# archive tar /xtract tftp://192.168.1.1/cme-locale-zh_CN-4.0.3-2.0.tar flash:

Step 6 For Cisco Unified IP Phones 7905, 7912, 7940, or 7960, go to Step 11.
For Cisco Unified IP Phones 7911, 7941, 7961, 7970, or 7971, go to Step 7.

Step 7 Each phone type has a JAR file that uses the following naming convention:

language-type-sccp.jar

For example, zh-td-sccp.jar is Traditional Chinese for the Cisco Unified IP Phone 7970.

See Table 17 and Table 18 for a description of the codes used in the filenames.

Table 17 Phone-Type Codes for Locale Files

Phone Type

Code

7906/7911

tc

7941/7961

mk

7970/7971

td

Table 18 Language Codes for User-Defined Locales

Language

Language Code

Bulgarian

bg

Chinese

zh

Finnish

fi

Hungarian

hu

Korean

ko

Polish

pl

Step 8 If you store the locale files in flash or slot 0: on the Cisco Unified CME router, create a TFTP alias using this format:

Router(config)# tftp-server flash:/jar_file alias directory_name/td-sccp.jar

Remove the two-letter language code from the JAR filename and use one of five supported directory names with the following convention:

user_define_number, where number is 1 to 5

For example, the alias for Chinese on the Cisco Unified IP Phone 7970 is:

Router(config)# tftp-server flash:/zh-td-sccp.jar alias user_define_1/td-sccp.jar

Note On Cisco 3800 series routers, you must include /its in the directory name (flash:/its or slot0:/its). For example, the TFTP alias for Chinese for the Cisco Unified IP Phone 7970 is:
Router(config)# tftp-server flash:/its/zh-td-sccp.jar alias user_define_1/td-sccp.jar

Step 9 If you store the locale files on an external TFTP server, create a directory under the TFTP root directory for each locale.

Remove the two-letter language code from the JAR filename and use one of five supported directory names with the following convention:

user_define_number, where number is 1 to 5

For example, for Chinese on the Cisco Unified IP Phone 7970, remove "zh" from the JAR filename and create the "user_define_1" directory under TFTP-Root on the TFTP server:

TFTP-Root/user_define_1/td-sccp.jar

Step 10 Go to Step 13.

Step 11 Download one or more of the following XML files depending on your selected locale and phone type. All required files are included in the JAR file.

7905-dictionary.xml
7905-font.xml
7905-kate.xml
7920-dictionary.xml
7960-dictionary.xml
7960-font.xml
7960-kate.xml
7960-tones.xml
SCCP-dictionary.utf-8.xml
SCCP-dictionary.xml

Step 12 Rename these files and copy them to flash, slot 0, or an external TFTP server. Rename the files using the format user_define_number_filename where number is 1 to 5. For example, use the following names if you are setting up the first user-locale:

user_define_1_7905-dictionary.xml
user_define_1_7905-font.xml
user_define_1_7905-kate.xml
user_define_1_7920-dictionary.xml
user_define_1_7960-dictionary.xml
user_define_1_7960-font.xml
user_define_1_7960-kate.xml
user_define_1_7960-tones.xml
user_define_1_SCCP-dictionary.utf-8.xml
user_define_1_SCCP-dictionary.xml

Step 13 Copy the language_tags_file and language_utf8_tags_file to the location of the other locale files (flash, slot 0, or TFTP server). Rename the files to user_define_number_tags_file and user_define_number_utf8_tags_file respectively, where number is 1 to 5 and matches the user-defined directory.

Step 14 Assign the locales to phones. See the "Configuring Multiple Locales" section.

Step 15 Use the create cnf-files command to rebuild the configuration files.

Step 16 Use the reset command to reset the phones and see the localized displays.

Verifying User-Defined Locales

See the "Verifying Multiple Locales" section.

Configuring Multiple Locales

To define one or more alternatives to the default user and network locales, and apply them to individual phones, perform the following steps.

Prerequisites

•Cisco Unified CME 4.0 or a later version.

•To specify alternative user and network locales for individual phones in a Cisco Unified CME system, you must use per-phone configuration files. For more information, see the "SCCP: Defining Per-Phone Configuration Files and Alternate Location" section on page 147.

•You can also use user-defined locale codes as alternative locales after you download the appropriate XML files. See the "Installing User-Defined Locales" section.

Restrictions

•Multiple user and network locales are not supported on the Cisco Unified IP Phone 7902G, 7910, 7910G, or 7920, or the Cisco Unified IP Conference Station 7935 and 7936.

•When you use the setup tool from the telephony-service setup command to provision phones, you can only choose a default user locale and network locale, and you must select a locale code that is predefined in the system. You cannot use multiple or user-defined locales with the setup tool.

SUMMARY STEPS

1. enable

2. configure terminal

3. telephony-service

4. user-locale user-locale-tag [user-defined-code] language-code

5. network-locale network-locale-tag [user-defined-code] country-code

6. create cnf-files

7. exit

8. ephone-template template-tag

9. user-locale user-locale-tag

10. network-locale network-locale-tag

11. exit

12. ephone phone-tag

13. ephone-template template-tag

14. exit

15. telephony service

16. reset {all [time-interval] | cancel | mac-address mac-address | sequence-all}

17. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

telephony-service
Example:

Router(config)# telephony-service

Enters telephony-service configuration mode.

Step 4

user-locale user-locale-tag [user-defined-code] language-code
Example:

Router(config-telephony)# user-locale 1 U1 ZH

Specifies a language for phone displays.

•user-locale-tag—Assigns a locale identifier to the language code. Range is 0 to 4. This argument is required when using multiple locales; otherwise the specified language is the default applied to all phones.

•user-defined-code—(Optional) Assigns one of the user-defined codes to the specified language code. Valid codes are U1, U2, U3, U4, and U5.

•language-code—Type ? to display a list of system-defined codes. United States (US) is the default. You can assign any valid ISO 639 code to a user-defined code (U1 to U5).

Step 5

network-locale network-locale-tag [user-defined-code] country-code
Example:

Router(config-telephony)# network-locale 1 FR

Specifies a country for tones and cadences.

•network-locale-tag—Assigns a locale identifier to the country code. Range is 0 to 4. This argument is required when using multiple locales; otherwise the specified country is the default applied to all phones.

•user-defined-code—(Optional) Assigns one of the user-defined codes to the specified country code. Valid codes are U1, U2, U3, U4, and U5.

•country-code—Type ? to display a list of system-defined codes. United States (US) is the default. You can assign any valid ISO 3166 code to a user-defined code (U1 to U5).

Step 6

create cnf-files
Example:

Router(config-telephony)# create cnf-files

Builds the required XML configuration files for IP phones. Use this command after you update configuration file parameters such as the user locale or network locale.

Step 7

exit
Example:

Router(config-telephony)# exit

Exits telephony-service configuration mode.

Step 8

ephone-template template-tag
Example:

Router(config)# ephone template 1

Enters ephone-template configuration mode.

•template-tag—Unique sequence number that identifies this template during configuration tasks.

Step 9

user-locale user-locale-tag
Example:

Router(config-ephone-template)# user-locale 2

Assigns a user locale to this ephone template.

•user-locale-tag—A locale tag that was created in Step 4. Range is 0 to 4.

Step 10

network-locale network-locale-tag
Example:

Router(config-ephone-template)# network-locale 2

Assigns a network locale to this ephone template.

•network-locale-tag—A locale tag that was created in Step 5. Range is 0 to 4.

Step 11

exit
Example:

Router(config-ephone-template)# exit

Exits ephone-template configuration mode.

Step 12

ephone phone-tag
Example:

Router(config)# ephone 36

Enters ephone configuration mode.

•phone-tag—Unique sequence number that identifies this ephone during configuration tasks.

Step 13

ephone-template template-tag
Example:

Router(config-ephone)# ephone-template 1

Applies an ephone template to an ephone.

•template-tag—Number of the template to apply to this ephone.

Step 14

exit
Example:

Router(config-ephone)# exit

Exits ephone configuration mode.

Step 15

telephony-service
Example:

Router(config)# telephony-service

Enters telephony-service configuration mode.

Step 16

reset {all [time-interval] | cancel | mac-address mac-address | sequence-all}
Example:

Router(config-telephony)# reset all

Performs a complete reboot of all phones or the specified phone, including contacting the DHCP and TFTP servers for the latest configuration information.

•all—All phones in the Cisco Unified CME system.

•time-interval—(Optional) Time interval, in seconds, between each phone reset. Range is 0 to 60. Default is 15.

•cancel—Interrupts a sequential reset cycle that was started with a reset sequence-all command.

•mac-address mac-address—A specific phone.

•sequence-all—Resets all phones in strict one-at-a-time order by waiting for one phone to reregister before starting the reset for the next phone.

Step 17

end
Example:

Router(config-telephony)# end

Returns to privileged EXEC mode.

Verifying Multiple Locales

Step 1 Use the show telephony-service tftp-bindings command to display a list of configuration files that are accessible to IP phones using TFTP, including the dictionary, language, and tone configuration files.

Router(config)# show telephony-service tftp-bindings

tftp-server system:/its/SEPDEFAULT.cnf
tftp-server system:/its/SEPDEFAULT.cnf alias SEPDefault.cnf
tftp-server system:/its/XMLDefault.cnf.xml alias XMLDefault.cnf.xml
tftp-server system:/its/ATADefault.cnf.xml
tftp-server system:/its/XMLDefault7960.cnf.xml alias SEP00036B54BB15.cnf.xml
tftp-server system:/its/germany/7960-font.xml alias German_Germany/7960-font.xml
tftp-server system:/its/germany/7960-dictionary.xml alias German_Germany/7960-dictionary.xml
tftp-server system:/its/germany/7960-kate.xml alias German_Germany/7960-kate.xml
tftp-server system:/its/germany/SCCP-dictionary.xml alias German_Germany/SCCP-dictionary.xml
tftp-server system:/its/germany/7960-tones.xml alias Germany/7960-tones.xml

Step 2 Ensure that per-phone configuration files are defined with the cnf-file perphone command.

Step 3 Use the show telephony-service ephone-template command to check the user locale and network locale settings in each ephone template.

Step 4 Use the show telephony-service ephone command to check that the correct templates are applied to phones.

Step 5 If the configuration file location is not TFTP, use the debug tftp events command to see which files Cisco Unified CME is looking for and whether the files are found and opened correctly. There are usually three states ("looking for x file" "opened x file" and "finished x file"). The file is found when all three states are displayed. For an external TFTP server you can use the logs from the TFTP server.

Configuration Examples for Localization

This section contains the following examples:

• Multiple User and Network Locales: Example

• User-Defined Locales: Example

Multiple User and Network Locales: Example

The following example sets the default locale of 0 to Germany, which defines Germany as the default user and network locale. Germany is used for all phones unless you apply a different locale to individual phones using ephone templates.

telephony service
cnf-file location flash:
cnf-file perphone
user-locale 0 DE
network-locale 0 DE

After using the previous commands to define Germany as the default user and network locale, use the following commands to return the default value of 0 to US:

telephony service
no user-locale 0 DE
no network-locale 0 DE

Another way to define Germany as the default user and network locale is to use the following commands:

telephony service
cnf-file location flash:
cnf-file perphone
user-locale DE
network-locale DE

After using the previous commands, use the following commands to return the default to US:

telephony service
no user-locale DE
no network-locale DE

The following example defines three alternative locales: JP (Japan), FR (France), and ES (Spain). The default is US for all phones that do not have an alternative applied using ephone templates. In this example, ephone 11 uses JP for its locales, ephone 12 uses FR, ephone 13 uses ES, and ephone 14 uses the default, US.

telephony-service
cnf-file location flash:
cnf-file perphone
create cnf-files
user-locale 1 JP
user-locale 2 FR
user-locale 3 ES
network-locale 1 JP
network-locale 2 FR
network-locale 3 ES
create cnf-files

ephone-template 1
user-locale 1
network-locale 1

ephone-template 2
user-locale 2
network-locale 2

ephone-template 3
user-locale 3
network-locale 3

ephone 11
button 1:25
ephone-template 1

ephone 12
button 1:26
ephone-template 2

ephone 13
button 1:27
ephone-template 3

ephone 14
button 1:28
User-Defined Locales: Example

The following example shows user-locale tag 1 assigned to code U1, which is defined as ZH for Traditional Chinese. Traditional Chinese is not predefined in the system so you must download the appropriate XML files to support this language.

In this example, ephone 11 uses Traditional Chinese (ZH) and ephone 12 uses the default, US English. The default is US English for all phones that do not have an alternative applied using ephone templates.

telephony-service
cnf-file location flash:
cnf-file perphone
user-locale 1 U1 ZH
network-locale 1 U1 CN

ephone-template 2
user-locale 1
network-locale 1

ephone 11
button 1:25
ephone-template 2

ephone 12
button 1:26

Where to Go Next

Ephone Templates

For more information about ephone templates, see "Creating Templates" on page 927.

Additional References

The following sections provide references related to Cisco Unified CME features.

Related Documents

Related Topic

Document Title

Cisco Unified CME configuration

• Cisco Unified CME Command Reference

• Cisco Unified CME Documentation Roadmap

Cisco IOS commands

• Cisco IOS Voice Command Reference

• Cisco IOS Software Releases 12.4T Command References

Cisco IOS configuration

• Cisco IOS Voice Configuration Library

• Cisco IOS Software Releases 12.4T Configuration Guides

Phone documentation for Cisco Unified CME

• Quick Reference Cards

• User Guides

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register on Cisco.com.

http://www.cisco.com/techsupport

Feature Information for Localization Support

Table 19 lists the features in this module and enhancements to the features by version.

To determine the correct Cisco IOS release to support a specific Cisco Unified CME version, see the Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_documentation_roadmap09186a0080189132.html.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 19 lists the Cisco Unified CME version that introduced support for a given feature. Unless noted otherwise, subsequent versions of Cisco Unified CME software also support that feature.

Table 19 Feature Information for Localization Support

Feature Name

Cisco Unified CME Version

Feature Information

Multiple Locales

4.0

Support for multiple user and network locales was introduced.

User-Defined Locales

4.0

User-defined locales were introduced.

Language	Language Code	User-Locale Directory Name	Country Code	Network-Locale Directory Name
English	en	English_United_States¹	US	United_States
		English_United_Kingdom	UK	United_Kingdom
			CA	Canada
Danish	dk	Danish_Denmark	DK	Denmark
Dutch	nl	Dutch_Netherlands	NL	Netherlands
French	fr	French_France	FR	France
French	fr	French_France	CA	Canada
German	de	German_Germany	DE	Germany
			AT	Austria
			CH	Switzerland
Italian	it	Italian_Italy	IT	Italy
Japanese²	jp	Japanese_Japan	JP	Japan
Norwegian	no	Norwegian_Norway	NO	Norway
Portuguese	pt	Portuguese_Portugal	PT	Portugal
Russian	ru	Russian_Russia	RU	Russian_Federation
Spanish	es	Spanish_Spain	ES	Spain
Swedish	se	Swedish_Sweden	SE	Sweden

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	telephony-service Example: Router(config)# telephony-service	Enters telephony-service configuration mode.
Step 4	user-locale user-locale-tag [user-defined-code] language-code Example: Router(config-telephony)# user-locale 1 U1 ZH	Specifies a language for phone displays. •user-locale-tag—Assigns a locale identifier to the language code. Range is 0 to 4. This argument is required when using multiple locales; otherwise the specified language is the default applied to all phones. •user-defined-code—(Optional) Assigns one of the user-defined codes to the specified language code. Valid codes are U1, U2, U3, U4, and U5. •language-code—Type ? to display a list of system-defined codes. United States (US) is the default. You can assign any valid ISO 639 code to a user-defined code (U1 to U5).
Step 5	network-locale network-locale-tag [user-defined-code] country-code Example: Router(config-telephony)# network-locale 1 FR	Specifies a country for tones and cadences. •network-locale-tag—Assigns a locale identifier to the country code. Range is 0 to 4. This argument is required when using multiple locales; otherwise the specified country is the default applied to all phones. •user-defined-code—(Optional) Assigns one of the user-defined codes to the specified country code. Valid codes are U1, U2, U3, U4, and U5. •country-code—Type ? to display a list of system-defined codes. United States (US) is the default. You can assign any valid ISO 3166 code to a user-defined code (U1 to U5).
Step 6	create cnf-files Example: Router(config-telephony)# create cnf-files	Builds the required XML configuration files for IP phones. Use this command after you update configuration file parameters such as the user locale or network locale.
Step 7	exit Example: Router(config-telephony)# exit	Exits telephony-service configuration mode.
Step 8	ephone-template template-tag Example: Router(config)# ephone template 1	Enters ephone-template configuration mode. •template-tag—Unique sequence number that identifies this template during configuration tasks.
Step 9	user-locale user-locale-tag Example: Router(config-ephone-template)# user-locale 2	Assigns a user locale to this ephone template. •user-locale-tag—A locale tag that was created in Step 4. Range is 0 to 4.
Step 10	network-locale network-locale-tag Example: Router(config-ephone-template)# network-locale 2	Assigns a network locale to this ephone template. •network-locale-tag—A locale tag that was created in Step 5. Range is 0 to 4.
Step 11	exit Example: Router(config-ephone-template)# exit	Exits ephone-template configuration mode.
Step 12	ephone phone-tag Example: Router(config)# ephone 36	Enters ephone configuration mode. •phone-tag—Unique sequence number that identifies this ephone during configuration tasks.
Step 13	ephone-template template-tag Example: Router(config-ephone)# ephone-template 1	Applies an ephone template to an ephone. •template-tag—Number of the template to apply to this ephone.
Step 14	exit Example: Router(config-ephone)# exit	Exits ephone configuration mode.
Step 15	telephony-service Example: Router(config)# telephony-service	Enters telephony-service configuration mode.
Step 16	reset {all [time-interval] \| cancel \| mac-address mac-address \| sequence-all} Example: Router(config-telephony)# reset all	Performs a complete reboot of all phones or the specified phone, including contacting the DHCP and TFTP servers for the latest configuration information. •all—All phones in the Cisco Unified CME system. •time-interval—(Optional) Time interval, in seconds, between each phone reset. Range is 0 to 60. Default is 15. •cancel—Interrupts a sequential reset cycle that was started with a reset sequence-all command. •mac-address mac-address—A specific phone. •sequence-all—Resets all phones in strict one-at-a-time order by waiting for one phone to reregister before starting the reset for the next phone.
Step 17	end Example: Router(config-telephony)# end	Returns to privileged EXEC mode.

Related Topic	Document Title
Cisco Unified CME configuration	• Cisco Unified CME Command Reference • Cisco Unified CME Documentation Roadmap
Cisco IOS commands	• Cisco IOS Voice Command Reference • Cisco IOS Software Releases 12.4T Command References
Cisco IOS configuration	• Cisco IOS Voice Configuration Library • Cisco IOS Software Releases 12.4T Configuration Guides
Phone documentation for Cisco Unified CME	• Quick Reference Cards • User Guides

Feature Name	Cisco Unified CME Version	Feature Information
Multiple Locales	4.0	Support for multiple user and network locales was introduced.
User-Defined Locales	4.0	User-defined locales were introduced.