CME Localization Support

Localization is used to define phone parameters on country bases. Those parameters can be language to use for text displays (user-local) or country-specific tones and cadences (network-local).  CME has built-in system-locals for 16 countries and 12 languages.

For SCCP phones:

• For 7905, 7912, 7940, and 7960 phones, system-locals files are preloaded in IOS. Only remaining is to apply the desired localization.
• For 6921, 6945, 7906, 7911, 7921, 7931, 7941, 7961, 7970, 7971, 8941, 8945, and Cisco IP Communicator phones, system-locals files should be uploaded to IOS (obtained from cisco.com site). The next step will be applying the desired local.

For SIP phones localization has been introduced in CME 8.6. But you need to upload the local files for system-built locals (this is applicable for all SIP Phones types).

CME has an option to create user-defined locals. Those will allow to create custom parameters (user/network locals) and upload their own files.

Important Note about User Localization

Phone displays (menus and prompts) are managed by CME Dictionary & IP Phone Local File. Those displays can be localized by User-Local. Other types of displays which are configured by IOS can't be localized (English display only).

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

Configuration

1. Download the tar file which contain all localization files.

2. Extract the file in routers flash (archive tar /xtract source-url flash:/file-url)

3. Create TFTP alias for localization files (for phones that require manual upload of the files). Two files should be assigned to TFTP server which are user-local and network-local:
   tftp-server flash:/jar_file alias directory_name/jar_file 
   tftp-server flash:/g3-tones.xml alias directory_name/g3-tones.xml
   
   TIP: You may initiate a "debug tftp packets" to see the exact file name which phones are requesting after changing the local. Then you configure the correct alias.

4. Apply the required local globally to SCCP/SIP CME. This will be applied to all phones.  telephony-service
    user-locale DK
    network-locale DK
   !
   voice register global
    user-locale DK
    network-locale DK
   
   Note: In case the files are missing from the TFTP server default local will be used which is English US.

Additionally, each CME can provide support up to 5 simultaneous locals. To achieve this, you need to assign 5 tags to 5 locals (languages and tones), then recall those tags in ephone-templates/voice-register-templates. Finally those templates should be assigned to endpoints. Those will override the global local applied in CME.

Example,

telephony-service

 user-locale 1 DE

!

ephone-template  1

 user-locale 1

!

ephone  1

 ephone-template 1

Alternatively, new feature is introduced in CME which is local installer (SCCP in version 7.0.1 and SIP in version 9.0). In this feature you need to define the local language/country to be used as well as the localization tar file. CME will automatically, extract the tar file and create TFTP alias for the required files. 

telephony-service

 user-locale [user-locale-tag] country-code load TAR-filename

!

voice register global

 network-locale [user-locale-tag] country-code load TAR-filename

Note: In case this feature is used, TAR file should be located in the same path for phone configuration file.