Message Networking supports the ability to specify the language
in which system announcements are voiced. Announcements are of two
types:
- Announcements sent back to the originator of the message.
- Announcements sent/attached to the recipient's message.
Installing or updating languages on Message Networking
The languages supported for Message Networking are provided on
a separate languages CD that can be installed on top of the standard
Message Networking 2.0 software (US English is always installed
on the system). See Installing switch
connection software and language packages for detailed steps
for installing and updating languages. The list of languages supported
for use with Message Networking is provided on the Avaya support
web site. Go to http://www.avaya.com/support and then navigate to the Message Networking page.
Deleting languages from Message Networking
You can delete individual languages from the Message Networking
system if necessary. For detailed information on deleting languages
from the Message Networking system, see Removing
software packages.
Note: Do not remove the US English language software
package from the system as it is the default language that is used
when a subscriber's preferred language is unavailable.
Assigning languages to remote machines and subscribers
Each remote machine defined on the Avaya Message Networking system
has a default language, which you specify in the Default Language
field when you administer a remote machine.
Initially, all subscribers administered on a remote machine are
assigned the remote machine default language as their preferred
language. However, you can modify an individual subscriber's language,
either by changing the Language ID field on the Subscriber
Administration page or through bulk
administration by file (except Avaya Modular Messaging and remote
Avaya Message Networking systems, which use LDAP-based directory
updates).
The language id is used and displayed in the following locations
in the Message Networking application:
- The Default Language field on the Remote
Machine Parameters Administration page.
- When subscribers are added
or modified in bulk using FTP files.
- The Lang ID field in the Subscriber
List reports (by Name, by Network Address, by Mailbox ID,
and by Remote Machine Name).
- The Language ID field on the Subscriber
Parameter Administration page.
- The Language ID field on the Subscriber
Parameter Display page.
Determining the language used to generate announcements
When determining the language in which to generate an announcement,
Message Networking applies the following criteria, in order of preference:
- If the subscriber's assigned Language ID is available on the
Message Networking system, that language is used.
- If the assigned Language ID is not available, but a variant
of the language is available, the language variant is used. For
example, if fr-CA is the subscriber's assigned Language ID and
fr-FR is installed but fr-CA is not, then fr-FR is used. If more
than one variant is available, the variant that comes first alphabetically
is used.
- If neither the Language ID nor a variant is available, en-US
(US English), which is always available, is used.
General considerations
Note the following considerations associated with Message Networking's
language support:
- Interchange 5.4 and Avaya Message Networking 1.0 support US-English
only. Therefore, US-English will be the systemwide language for
each remote Interchange 5.4 or Message Networking 1.0 system administered
on the local Message Networking 2.0 system. In addition, US-English
will be the only language available for all subscribers on Interchange
5.4 and Message Networking 1.0 systems.
- The following are available in US English only:
- The voice names associated with system mailboxes.
- The existing system mailboxes have a voiced name of "The
Network." The system mailboxes (reserved in number from
0000000000-0000000010) are those mailboxes that Avaya Message
Networking-generated messages originate from (for example,
failure notification).
- Announcements sent as messages originating from an Interchange
5.4 system or an Avaya Message Networking Release 1.0 to an
Avaya Message Networking Release 2.0. The only scenario where
full language support is available is in a multi-hub environment
where all systems are Avaya Message Networking 1.1 or 2.0
versions.
Top of page
|