|
Variable-length addressing allows Modular Messaging systems to
address messages to subscribers on other remote machines in the
network using a number other than the network address. These alternate
numbers are called numeric addresses.
The typical method of addressing messages to remote subscribers
is to use the network address, which provides a unique address to
all subscribers. The network address is required to be a fixed length
for all subscribers in the Message Networking network, and it typically
has a length of 10 digits. Numeric addresses do not have to be a
fixed length for all subscribers and can range from 3 to 32 digits
in length.
Although Avaya Modular Messaging senders enter the numeric address,
the email address of the recipients are still the fixed length network
address in the Avaya Message Networking domain. Message Networking
does not accept variable-length network address values from non-Avaya
Modular Messaging systems. It only supports a fixed length of 3
to 10 digits as a recipient value from non-Avaya Modular Messaging
systems.
The Numeric addressing feature of Message Networking functions
similarly to the Message Networking dial plan mapping feature and
provides two ways for you to configure variable length addressing:
- On an individual subscriber basis, by modifying the Numeric
Address field on the Subscriber Parameters
Administration page.
- On a remote machine basis, by administering numeric address
mapping. The mapping is then used to generate numeric addresses
for those subscribers based on either their mailbox number or
their network address. The numeric address mapping functions similarly
to the Message Networking dial plan mapping feature. However,
unlike the dial plan mapping feature, no specific length is enforced
for numeric addresses and you can specify multiple numeric address
maps using different lengths.
Note: Numeric addresses for subscribers on Modular
Messaging and other Message Networking remote machines are provided
to the local Message Networking system through LDAP updates.
When you administer numeric address mapping for a remote machine,
the numeric address can be left blank or it can be calculated from
either the mailbox ID or the network address. The address used to
calculate the numeric address is called the base address. You specify
the modifications to be made to the base address much the same as
when you administer the system's dial plan mapping. You specify
a From field, which is used to match a portion of the base addresses.
A base address matches when the From value is the same as the beginning
portion of the base address. When a match is made, the portion of
the base address that was matched is stripped, and the To value
you specify is added to the beginning of the stripped base address
to create the numeric address.
In Message Networking, there are a number of areas in which subscriber
records are created or modified. The following table lists these
areas and describes if and how numeric address mapping applies to
each area:
|
Message Networking feature |
Application
of numeric addressing |
| Bulk add
from FTP file |
Apply the
mapping (numeric addresses cannot be specified in the FTP file). |
| Bulk change
from FTP file |
Leave the
numeric address unchanged. |
| Bulk add
by range |
Apply the
mapping. |
| Auto-add
of sender |
Apply the
mapping. |
| Dynamic
update of sender during messaging |
Leave the
numeric address unchanged. |
| Self-registration/add
subscriber |
Apply the
mapping. |
| Self-registration/change
subscriber |
Leave the
numeric address unchanged. |
| Full update/add
subscriber |
Apply the
mapping.
Note: Do not take this action for subscriber
additions made via LDAP. |
| Full update/change
subscriber |
Leave the
numeric address unchanged.
Note: This does not exclude an LDAP update
changing the value. |
| Delta add/add
subscriber |
Apply the
mapping.
Note: Do not take this action for subscriber
additions made via LDAP. |
| Delta update/change
subscriber |
Leave the
numeric address unchanged.
Note: This does not exclude an LDAP update
changing the value. |
| Subscriber
Parameter Administration page/add subscriber |
If the
numeric address is changed on the screen, update the subscriber's
address. |
| Subscriber
Parameter Administration page/change subscriber |
If the
numeric address is changed on the screen, update the subscriber's
address.
|
| Numeric
Addressing Administration page |
Apply the
mapping. |
Note the following considerations related to numeric addressing:
- The numeric address cannot be sent to an Interchange system
because the field does not exist in Interchange.
- The numeric address should not be generated for any subscribers
associated with another Message Networking server, including servers
running Message Networking 1.0. However, numeric addresses present
for other subscribers from other remote machine should be sent
to other Message Networking servers, including those running Message
Networking 1.0, as part of the standard subscriber updates.
- The numeric address should not be generated for any subscribers
associated with an Modular Messaging. However, numeric addresses
present for subscribers from other remote machines should be sent
to Modular Messaging as part of the standard subscriber updates.
- Failure messages generated by the Avaya Message Networking refer
to the network address of the recipient instead of the numeric
address. However, the voiced name of the recipient is identified
in the message, if available.
Top of page
|
