Cisco Unity System Administration Guide (With Microsoft Exchange), Release 4.0(3)
Languages

Table Of Contents

Languages

Overview: Languages

Setting Up Languages

Specifying Text to Speech Languages

Specifying Phone Languages

Specifying GUI Languages

TTY Overview

Setting Up Cisco Unity to Use the TTY Prompt Set

Disabling Cisco Unity Comfort Noise

Using the TTY Angel

Using NTS for Advanced TTY Features


Languages


Overview: Languages

The Cisco Unity Administrator provides settings for phone languages, Text to Speech (TTS), and GUI languages. Phone languages are the languages in which Cisco Unity can play system prompts to subscribers and callers; TTS languages are the languages in which Cisco Unity can play e-mail messages over the phone, and GUI languages are the languages in which the Cisco Unity Administrator is displayed.

The number of language licenses available determines how many phone, TTS, and GUI languages Cisco Unity can load and use at a time. For example, if your organization has two phone language licenses, but has four languages installed, Cisco Unity will allow you to load and use only two at any one time. You can, however, select which two are used, and you can change this selection at any time. This flexibility allows you to better manage the language needs of your users.

For the complete list of supported languages for Cisco Unity, refer to the "Cisco Unity Languages" section in Cisco Unity 4.0 System Requirements, and Supported Hardware and Software, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/40_sysrq.htm.


Caution Customizing system prompts is not supported for any of the Cisco Unity phone languages. All system prompts are automatically deleted and replaced whenever you upgrade Cisco Unity, including the installation of maintenance releases.

See the following sections:

Setting Up Languages

Specifying Text to Speech Languages

Specifying Phone Languages

Specifying GUI Languages

TTY Overview

Setting Up Languages

The phone, TTS, and GUI languages are chosen and installed during the initial Cisco Unity setup, and the applicable files are copied to the Cisco Unity server for each selected language.

One of the languages installed on the Cisco Unity server must match the Windows operating system locale selected during Windows installation. Additional languages may be installed as needed.

If during initial setup you did not install the language(s) you need, refer to the "Adding Languages" section in the "Modifying the Cisco Unity 4.0 System" chapter of the Cisco Unity Installation Guide for details on how to add or replace languages. If you are adding TTS, refer to the "Adding Text to Speech" section. (The Cisco Unity Installation Guide is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/unity40/inst/inst403/ex/index.htm.)


Caution Before removing a Cisco Unity language, confirm that it is not the language that matches the Windows locale, that it is not listed in the Loaded table on the System > Configuration > Phone Languages and/or GUI Languages pages, that it is not listed as the default Phone, TTS, or GUI language, and that it is not in use by any subscriber, routing rule, call handler, interview handler, or directory handler. Do not change the Windows locale language without updating all of the locations where the corresponding Cisco Unity languages (both old and new) are specified.

In the following circumstances, if the language specified is not listed in the Loaded table on the System > Configuration > Phone Languages and/or GUI Languages pages, Cisco Unity will use the default phone, TUI, or GUI language:

When a language is specified in a Cisco Unity component

When a language is specified as the Windows locale

When a language is passed to Cisco Unity by the Property Management System (for Hospitality integrations)


Caution If you have a Cisco Unity failover system, languages settings are not replicated between the primary and secondary servers. You must change values manually on both servers.

Specifying Text to Speech Languages

The Text to Speech language engine translates e-mail text into audio, enabling subscribers to listen to e-mail by using the phone. TTS is available only with Unified Messaging.

The default TTS language is specified during installation, and can be viewed and changed on the System > Configuration > Phone Languages page.

The Cisco Unity server can support the use of multiple additional TTS language engines, as needed. All supported TTS language engines are automatically installed with the Cisco Unity software. For a complete list of supported TTS language engines, refer to the "Cisco Unity Languages" section in Cisco Unity 4.0 System Requirements, and Supported Hardware and Software, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/sysreq/40_sysrq.htm.

Use of TTS is controlled by the number of Text to Speech session licenses, and by subscriber class of service. The number of simultaneous TTS sessions on a Cisco Unity server cannot exceed the maximum number of sessions supported for the applicable platform overlay, as specified in the Cisco Unity Supported Platforms List. Depending on the needs of your site, you can grant TTS use to all subscriber classes of service, or limit it to specific classes of service. For more information, see the "Class of Service Features Settings" section on page 14-11. (The Cisco Unity Supported Platforms List is available at http://www.cisco.com/warp/public/cc/pd/unco/un/prodlit/ucutp_st.htm.)

Typically, the phone language(s) that you install and choose for use by subscribers will also be used as their TTS language(s), with the following exceptions:

If you installed Australian English or New Zealand English as your phone language during setup, you also need to install either UK English or United States English language to serve as your default TTS language.

There is no applicable TTS language available for Brazilian Portuguese, Czech, or Korean.

Mainland Mandarin and Japanese TTS require specific language settings on the Cisco Unity server. If you are using either of these two languages, complete the following procedures, as applicable.

To Use Mainland Mandarin Text to Speech


Step 1 On the Windows Start menu, click Settings > Control Panel > Regional Options.

Step 2 On the General tab, in the Your Locale (Location) list, click Chinese (PRC).

Step 3 In the Language Settings for the System box, click Simplified Chinese.

If you have a multi-lingual system, choose additional languages as applicable.

Step 4 Click Set Default. The Set System Locale dialog box opens.

Step 5 In the Select Appropriate Locale list, click Chinese (PRC).

Step 6 Restart the Cisco Unity server for the changes to take effect.


To Use Japanese Text to Speech


Step 1 On the Windows Start menu, click Settings > Control Panel > Regional Options.

Step 2 On the General tab, in the Your Locale (Location) list, click Japanese.

Step 3 In the Language Settings for the System box, click Japanese.

If you have a multi-lingual system, choose additional languages as applicable.

Step 4 Click Set Default. The Set System Locale dialog box opens.

Step 5 In the Select Appropriate Locale list, click Japanese.

Step 6 Restart the Cisco Unity server for the changes to take effect.


Specifying Phone Languages

You specify a default phone language and other system-wide phone language settings on the System > Configuration > Phone Languages page.

If desired, you can customize the language setting for individual Cisco Unity components without changing the default language settings for the rest of the system. The phone language setting is available for the following Cisco Unity components: subscriber accounts, routing rules, call handlers, interview handlers, and directory handlers. For each of these entities, you can use the pages in the Cisco Unity Administrator to specify a phone language, or you can specify that the phone language be "Inherited."

With the Inherited setting, Cisco Unity determines the phone language to use for callers on a per-call basis, depending on how the call is processed. For example, you can set up a call handler with the Inherited language setting, and also set it up to receive calls from two different routing rules, each with a different language setting. (For example, one routing rule could be set up with a French language setting, while the second routing rule could be set to German.) In this situation, the language in which Cisco Unity plays the call handler system prompts will depend on which rule routed the call. However, note that if every component in your system that processes a call has been set with Inherited as the language setting, Cisco Unity will play the system prompts in the default phone language, because in effect none of the components will have been set to a specific language.

Recorded greetings are always played in the language in use when the greeting was recorded. For example, changing the language setting for the Opening Greeting call handler from U.S. English to French will not automatically convert the greeting that was originally recorded in English to one that is played back in French. The Opening Greeting must be re-recorded in French. This is also true for subscriber greetings and for other handlers.

For more information about the settings on the Phone Languages page, see the "Phone Languages Settings" section on page 29-6.

Do the procedure "To Change Phone Language Settings for Cisco Unity Components" to change the phone language settings for routing rules, call handlers, interview handlers, and directory handlers.

To specify phone language settings for individual subscribers, do the procedure "To Change Phone Language Settings for Subscriber Accounts." To modify language settings for multiple subscriber accounts, you can use the Cisco Unity Bulk Import wizard or the Bulk Edit utility (see the "Subscriber Settings" chapter for details). Note that subscribers can use the Cisco Unity Assistant to select the language that they hear when they log on to Cisco Unity by phone.

To Change Phone Language Settings for Cisco Unity Components


Step 1 In the Cisco Unity Administrator, go to the applicable Call Routing, Call Handler, Interview Handler, or Directory Handler page.

Step 2 Go to following page(s), as applicable:

For routing rules, go to the Direct Calls page or Forwarded Calls page.

For call handlers, go to the Profile page.

For interview handlers, go to the Profile page.

For directory handlers, go to the Profile page.

Step 3 In the Language field, select one of the languages listed, or select Inherited.

Step 4 Re-record applicable greetings in the new language.


To Change Phone Language Settings for Subscriber Accounts

For each subscriber account, you can specify the language in which system prompts are played to callers (this affects prompts such as "Record your message at the tone"), and you can change the language that subscribers hear when listening to the subscriber conversation.

Note that if the class of service to which a subscriber belongs has TTS, the language you select in the Subscriber's Language field also controls the language that the TTS e-mail reader uses. Before changing the phone and TTS language for a subscriber, verify that you have the applicable languages installed. See the "Setting Up Languages" section for more information.


Step 1 In the Cisco Unity Administrator, go to any Subscriber page.

Step 2 Do the following actions, as applicable:

To change the phone language for callers, go to the Messages page. In the Language That Callers Hear field, select a specific language, or select Inherited.

To change the phone language for subscribers, go to the Conversation page. In the Subscriber's Language field, select one of the languages listed.

Ask the subscriber to re-record their greeting(s) in the new language.


Specifying GUI Languages

You specify a default GUI language and other system-wide GUI language settings on the System > Configuration > GUI Languages Page. To change the GUI language used in the Cisco Unity Administrator and the Cisco Personal Communications Assistant (PCA), select a language in the browser. (Subscribers use the Cisco PCA to access the Cisco Unity Assistant and the Cisco Unity Inbox. Note that in version 3.1 and earlier, the Cisco Unity Assistant was known as the ActiveAssistant, or AA; the Cisco Unity Inbox was known as the Visual Messaging Interface, or VMI.)

For the Cisco Unity Administrator, the language selected in the browser must be one of the languages in the Loaded list on the GUI Languages page. If the language that you select in the browser is not among the loaded languages, Cisco Unity uses the default GUI language; for the Cisco PCA, the language selected in the browser must be one of the languages that the Cisco PCA offers.

See the "GUI Languages Settings" section on page 29-7 for more information.

TTY Overview

With Cisco Unity version 4.0(3) and later, a TTY prompt set, available in U.S. English (ENX) only, can be installed and used just like any other supported phone language. When the TTY prompt set is installed, subscribers and outside callers who use TTY can call in to Cisco Unity and use the same features that a hearing caller can use. However, note the following limitations:

G.711 MuLaw must be selected as the message recording and storage codec. The Cisco Unity TTY prompt set is not compatible with G.729a or other message recording and storage codecs.

A dedicated phone number must be set up for use by outside callers with TTY. All greetings, prompts, and subscriber names accessible from this number must be created with the TTY prompt set.

TTY is a TUI language only. At the present time, there is no compatible Text to Speech (TTS) language for TTY. The TTY prompt set is also not suitable for use as a GUI language.

TTY tones are not available for use in navigating through the Cisco Unity conversation. Some TTY phones do not have the capability to send DTMF tones. In this case, TTY users may need to use the phone keypad for system navigation.

Due to recording and playback limitations, the TTY prompt set can not be used in interview handlers.

See the following sections for information on setting up and using the Cisco Unity TTY prompt set:

Setting Up Cisco Unity to Use the TTY Prompt Set

Disabling Cisco Unity Comfort Noise

Using the TTY Angel

Using NTS for Advanced TTY Features

Setting Up Cisco Unity to Use the TTY Prompt Set

To set up Cisco Unity for TTY, do the following tasks.

1. Obtain a dial-in number that will be used exclusively for outside callers with TTY to call in to Cisco Unity. Set up the phone system and integration as required.

2. Install TTY devices for subscribers, as needed. For information about using Nix products with Cisco Unity and Cisco CallManager, see the "Using NTS for Advanced TTY Features" section.

3. Install the ENX language on the Cisco Unity server.

4. Confirm that G.711 is selected as the Cisco Unity message recording and storage code.

5. Disable Cisco Unity comfort noise. See the "Disabling Cisco Unity Comfort Noise" section.

6. Create a TTY subscriber template. This template will be used when creating subscriber accounts for all subscriber who will use TTY. You may also want to create a TTY class of service, on which you disable Text to Speech for these subscribers.

7. Create a routing rule for the TTY dial-in number.

8. Create an opening greeting call handler for the TTY dial-in number.

9. Set up additional TTY call handlers as needed.

10. Record greetings in TTY by using the TTY Angel, or by using the Media Master and a TTY phone as a recording and playback device. You will need to record the following greetings, as applicable: the opening greeting, additional call handler greetings, and subscriber greetings. See the "Using the TTY Angel" section.

11. Test the TTY dial-in number, opening greeting, call handlers, and all subscriber devices to confirm correct operation for both incoming and outgoing TTY calls.

Disabling Cisco Unity Comfort Noise

Comfort noise is low-level background noise generated on a IP device. Its purpose is to simulate the hiss produced in a circuit-switched connection, and it can be generated to help provide reassurance to callers when there is no audio from Cisco Unity, for example, during a transfer or between system prompts.

The Cisco Unity ComfortNoise registry setting is a system-wide setting that controls the ability of Cisco Unity to send comfort noise generation packets to an IP phone, or to a gateway that is enabled to receive and respond to comfort noise generation packets.

If Cisco Unity comfort noise is enabled on a system that is using the TTY prompt set, TTY subscribers may report that characters are occasionally garbled or dropped. Disabling Cisco Unity comfort noise will prevent this problem from occurring.

Disabling Cisco Unity comfort noise should not cause a problem for non-TTY subscribers, but be aware that callers may notice short periods of silence between some Cisco Unity prompts.

To Disable Cisco Unity Comfort Noise


Step 1 Start Regedit.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that for a Cisco Unity failover system, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 2 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 3 Expand the registry key

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Avaudio\Parameters\ComfortNoise.

Step 4 In the Edit Dword Value window, click Decimal.

Set the value to 128.

Step 5 Click OK.

Step 6 Restart the Cisco Unity server.

Step 7 If you are using failover, repeat this procedure to apply the registry setting to secondary server.


Using the TTY Angel

The TTY prompt set includes all system prompts needed to use TTY with Cisco Unity. The TTY Angel application, available in Tools Depot, is used to create custom call handler and subscriber greetings, and subscriber recorded names, in TTY.

You can also create a CSV file containing a list of greetings and subscriber names to be converted to TTY all at once. Refer to the TTY Angel online Help for more information about this option.

To Use the TTY Angel to Create Greetings and Recorded Names


Step 1 On the Cisco Unity desktop, double-click the Cisco Unity Tools Depot icon.

Step 2 In the left pane, expand Administrative Tools, and double-click TTY Angel. The TTY Angel window appears.

Step 3 To create a new greeting or subscriber voice name, in the Output File Name window, enter a location and file name for the new TTY file.

For example, enter C:\TTY Greetings\Opening Greeting.

Step 4 In the Text to Convert to TTY/TDD Wav File window, enter the greeting, subscriber name, or other text as applicable, and click Create Wav File.

The text is converted, displayed in the Diagnostic Output window, and stored in the designated output file and in the clipboard.

Step 5 To paste the TTY WAV file into a call handler or subscriber record, in the Cisco Unity Administrator, browse to the applicable subscriber or call handler page.

Step 6 On the Media Master Control Bar, click the Options menu, and click Paste or Paste From File as applicable. The WAV file is pasted into the record.


Using NTS for Advanced TTY Features

NTS version 4.0 and later, available from NXi Communications, is compatible with Cisco Unity and Cisco CallManager. NTS offers advanced TTY features for business and individual use.