|
This topic provides information on general considerations related
to SMTP/MIME remote machines.
Note: For specific considerations related to Modular
Messaging systems that use SMTP/MIME, see Modular
Messaging remote machine considerations.
The following are general considerations related to SMTP/MIME remote
machines:
- The following are standard methods of encoding audio messages
in a compressed format. Message Networking can directly process
audio files of these types when they are received as .wav files
that are part of an SMTP/MIME message:
- GSM: In the Windows Sound Recorder, this file type
has an audio format of GSM 6.10 8.000 kHz, Mono.
- A-law: In the Windows Sound Recorder, this file type
has an audio format of CCITT A-Law 8.000 kHz, 8 Bit, Mono.
- Mu-law: In the Windows Sound Recorder, this file
type has an audio format of CCITT u-Law 8.000 kHz, 8 Bit,
Mono.
- In cases where a sent SMTP/MIME message is larger than a receiving
non-SMTP/MIME machine can handle, the message is failed with a
large message failure code.
- Message Networking does not support Group 4 fax transcoding.
- The Message Networking VPIM module does not support variable-length
mailbox IDs on the same SMTP/MIME mail server.
- Message Networking supports a maximum mailbox ID and network
address length of 10. In addition, Message Networking supports
a uniform dial plan whereby the length of the network address
must be the same number of digits (from 3 to 10) network-wide.
None of the Avaya message servers that Message Networking supports
can have a mailbox ID or network address greater than 10 digits.
However, Message Networking does support variable-length addressing
for Modular Messaging systems. Therefore, numeric addresses can
be administered on Message Networking for subscribers on non-Modular
Messaging remote machines. If you do not administer numeric address
mapping, note that Message Networking supports E.164 conformance
addressing from SMTP/MIME senders in the format of user id@domain.
The user ID is alphanumeric and can be greater than 10 in length.
Message Networking can then take this address and map it to a
network address whose length cannot exceed 10.
- Certain sending SMTP/MIME systems can generate what is known
as a multistrip fax that Message Networking does not support.
Specifically, a multistrip fax is a fax with one or more pages
each stored as multiple strips of image data. An example of a
system that can generate a multistrip fax is Microsoft Exchange
2000.
- Message Networking does not support the ability to change a
remote machine administered as AMIS or Octel Analog (such as Unified
Messenger with MS Exchange) to SMTP/MIME. The remote AMIS/Octel
Analog machine must be deleted and readministered as an SMTP/MIME
remote machine on the Message Networking system.
- Virus detection and are virus detection software server-specific.
Fortunately, virus infection is generally limited to binary attachments
intended to execute in a PC environment. Current Avaya message
servers that support binary files do not attempt to run any
binary attachments on the server, so the risk of infection occurs
only in the client environment. There is NO virus detection support
on Message Networking. Virus detection support should be applied
at the binary file detach operation on the client. Because Message
Networking is provisioned as an email receiver, customers must
ensure that a firewall exists between Message Networking and the
Internet. In addition, customers should deploy a virus detection
solution, such as a standalone server that sits on the LAN between
the Message Networking server and any incoming email. This kind
of solution adds an extra transmission, but filters out viruses
from incoming email. Most large corporations are already running
a similar service at their publicly accessible incoming email
gateway. See Virus and worm protection
for more information on protecting the remote messaging system.
-
If SMTP messages being sent via a sound card have static, check
the users' microphone settings. You might need to adjust the
microphone settings.
-
Note the following considerations for voiced and ASCII names
on non-LDAP-based systems:
- Messages delivered to SMTP/MIME recipients from Message
Networking include the ASCII name, but not the voiced name,
in the appropriate sender's name field. How the names are
presented to the recipient (if at all) depends on the receiving
SMTP/MIME vendor's implementation. When the ASCII name is
received by Message Networking, that sender's directory entry
is updated, if necessary.
- Message Networking can register the SMTP/MIME subscriber's
voiced name in the directory using the Self-Registration Agent
feature. Once recorded on the Message Networking system, the
voiced name can then be presented to the rest of the network.
These considerations do not apply to Avaya Modular Messaging
systems because they use LDAP-based utilities for subscriber directory
updates, which occur automatically (similar to AUDIX TCP/IP and
including ASCII and voiced name).
Top of page
|
