|
This topic provides information on performing remote updates, which you perform to send and receive subscriber record updates from some remote machine types. Perform remote updates during initial system administration or after a significant
number of subscribers have been added. Do not perform this procedure
during prime system hours.
There are two types of remote updates:
- Demand Remote Update allows subscriber records, including ASCII
and voiced names, to be pulled over from INTUITY AUDIX, DEFINITY
AUDIX, Serenade Analog, IP600, Aria Digital, DEFINITY ONE, Message
Networking, and Avaya Modular Messaging remote machines on to
the Message Networking system. Demand Remote Updates are only
used for INTUITY AUDIX, DEFINITY AUDIX, IP600, Aria Digital, and
DEFINITY One systems. Demand Remote Updates are not supported
for Serenade Digital, Unified Messenger, Aria Analog, AMIS Analog,
VPIM V2, or other SMTP remote machines.
- Demand Remote Push allows subscriber records, including ASCII
and voiced names, to be pushed from an Avaya Message Networking
to Octel Analog Networking or Aria Digital and Serenade Digital
remote machines. Demand Remote Push updates are not supported
for Octel 100, VPIM v2, INTUITY AUDIX, and SMTP/MIME, including
Avaya Modular Messaging and Avaya Message Networking remote machines.
Note: NameSend is the recommended procedure to use for
updating names in Aria Digital and Serenade Digital. Names can be
updated by range or by using the option for all.
The following tasks are associated with remote updates:
Remote updates are one method of updating subscriber records on the system. But, as noted earlier in this topic, remote updates are not supported for all remote machine types. The following table summarizes the cases in which subscriber updates
occur automatically for each type of remote machine.
| Protocol
|
Remote
machine updates
Message Networking |
Message
Networking
updates remote machine |
| AMIS |
- N/A
for adds and changes.
- When
Message Networking attempts to deliver to a nonexistent
subscriber on an AMIS remote machine, it fails the messages
and deletes that subscriber from the Message Networking
directory.
|
N/A |
| AUDIX
Digital |
When a
subscriber is added, changed or deleted through administration,
the Message Networking system is automatically notified. |
When Message
Networking detects an add, change or delete of a subscriber,
it pushes out the update to the AUDIX Digital remote machine.
|
| Octel
Analog Networking |
- When
Message Networking delivers a message to the remote machine,
it does an ASCII match of the recipient (if ASCII Name Confirmation
is set to Yes).
- If
the recipient does not match, it fails the message and immediately
requests a pull from the remote machine (when Updates In
is set to Yes for that remote machine on the Remote Parameters
page in Message Networking and the remote remote machine
itself is administered for remote updates).
- If
the ASCII name is a default on the Message Networking system,
a comparison is not performed by Message Networking, the
message is delivered, and the pull is immediately requested
(when Updates In is set to Yes for that remote machine on
the Remote Parameters page in Message Networking and the
remote machine itself is administered for remote updates).
- If
the subscriber does not exist on the remote machine but
does on the Message Networking system, then the message
is failed. The Message Networking defaults the ASCII name
and nulls the voiced name of the subscriber.
- For
any name pull to work, the remote machine must be set to
Protocol Level 2 or 3.
|
- When
the remote machine delivers a message to the Message Networking
system, it does an ASCII match on the recipient.
- If
the recipient does not match, it fails the message and deletes
the entry; the next time that subscriber is messaged, it
requests a pull from Message Networking.
- If
the ASCII name is a default on the Message Networking system,
Message Networking always accepts the message (that is,
it does not perform a name comparison); the Message Networking
system then schedules a name pull.
- If
a subscriber does not exist on the Message Networking system
and that subscriber sends a message through Message Networking,
the Message Networking system adds the subscriber as a default
and then schedules a name pull.
- When
Message Networking detects an add or change (not a delete)
of a subscriber, it pushes out the update.
|
| Aria Digital
|
- When
Message Networking delivers a message to the remote machine,
it requests that the remote machine perform an ASCII match
on the recipient.
- If
the recipient does not match, the remote machine fails the
message, and Message Networking requests a pull from the
remote machine.
- If
the ASCII name is a default on the Message Networking system,
a comparison is not requested, the message is delivered,
and the pull is requested.
- If
the subscriber does not exist on the remote machine but
does on the Message Networking system, then the message
is failed by the remote machine. Message Networking defaults
the ASCII name and nulls the voiced name of the subscriber.
- Aria
Digital can automatically push an add, change, or delete
of a subscriber when the update occurs.
|
- When
the remote machine delivers a message to Message Networking,
the Message Networking system does an ASCII match on the
recipient.
- If
the recipient does not match, Message Networking fails the
message and the remote machine deletes the entry; the next
time that subscriber is sent a message, it requests a pull
from the Message Networking system.
- When
Message Networking detects an add, change, or delete of
a subscriber, it pushes out the update.
|
| Serenade
Digital |
- When
the Serenade Digital system delivers a message to the Message
Networking system, it automatically pushes the sender's
ASCII and voiced names (if the voiced name exists).
- The
Serenade Digital system can automatically push an add or
change, but not a delete, of a subscriber when the update
occurs.
- When
Message Networking delivers a message to the remote machine,
it does an ASCII match of the recipient (if the ASCII Name
Confirmation flag is set to Yes).
- If
the recipient does not match, Message Networking fails the
message, defaults the ASCII name, and then nulls the voiced
name.
- If
the ASCII name is a default on the Message Networking system,
a comparison is not performed, and the message is delivered.
- If
the subscriber does not exist on the remote machine but
does on the Message Networking system, the message is failed.
Message Networking then defaults the ASCII name and nulls
the voiced name of the subscriber.
|
- When
Message Networking delivers a message to the Serenade Digital
system, it automatically pushes the sender's ASCII and voiced
names (done only when a voiced name exists).
- When
Message Networking detects an add or change (not a delete)
of a subscriber, it pushes out the update.
- When
the remote machine delivers a message to the Message Networking
system, it does an ASCII match on the recipient if addressed
alphabetically.
- If
the recipient does not match, the Serenade fails the message
and deletes the entry.
|
| VPIM V2
Digital |
Each time a VPIM sender sends a message through Message
Networking, the sender's record is updated on the Message
Networking system. Note that this update occurs only if the
ASCII name/voiced name has changed and the sending system
supports this information. |
Each time a Message Networking sender sends a message to
a VPIM system, the sender's record is updated on the receiving
VPIM system. Note that this update occurs only if the ASCII
name/voiced name has changed and the receiving system supports
this information. |
| SMTP/MIME
(LDAP-based) |
When the
subscriber is added, changed or deleted through administration,
Message Networking is automatically notified. |
When Message
Networking detects an add, change or delete of a subscriber,
it pushes out the update to the LDAP-based remote machine. |
| SMTP/MIME
(non-LDAP-based) |
Each time an SMTP/MIME sender sends a message through Message
Networking, that subscriber's record is updated on Message
Networking. Note that this update occurs only if the ASCII
name (not voice name) has changed and the sending system supports
this information. |
Each time a Message Networking sender sends a message to
an SMTP/MIME system, the sender's record is updated on the
receiving SMTP/MIME system. Note that this update occurs only
if the ASCII name (not voice name) has changed and the receiving
system supports this information. |
Note: LDAP updates (between Modular
Messaging and Message Networking systems and between Message Networking
systems) can impact system performance, including delay of administration
page displays and report results. Note that while the LDAP update
is in progress between the two systems, messages are not transmitted
between them. The length of time to complete an LDAP update depends
on:
- The type of Modular Messaging system (Standard or High Availability)
- The number of MASs in the system
- The size of the system's database
- The number of subscribers to be updated and the voice name message
lengths
- The number of updates occurring at the same time (multiple updates
running slow the update rate)
It is recommended that remote updates of more than approximately
4,000 subscribers with voiced names be scheduled during non-prime-time
hours, and that remote updates of 50,000 subscribers or more be
scheduled over a weekend.
For Modular Messaging system updates, Standard Availability systems
and systems with multiple MASs will take longer to update. The following
numbers are provided to help estimate the total time required for
a remote update. The update rate on a Standard Availability system
with one MAS is approximately 4,000 subscribers updated per hour.
The update rate on a High Availability system with one MAS is approximately
9,000 subscribers updated per hour.
For Message Networking to Message Networking updates, the update
rate for the S3210 server is from 5,000 to 7,000 subscribers updated
per hour. For Message Networking to Message Networking updates,
the update rate for the S3400-H server is from 14,000 to 15,000
subscribers updated per hour.
Top of page
|
