Subscriber capabilities

The following lists the subscriber capabilities of a Message Networking system:

• The Message Networking system allows a uniform dial plan (the number of digits used when addressing a message), which consists of from a 3-digit to a 10-digit network address. It allows from a 0-digit to a 21-digit prefix for an INTUITY AUDIX system. The sum of the network address and prefix cannot exceed 24 digits. A 10-digit network address dial plan is recommended.
• Message Networking supports variable-length addressing, which allows Modular Messaging subscribers to address messages to subscribers on other remote machines using an alternate numbering. See Administering numeric address mapping for more information.
• A subscriber must be administered on a Message Networking system so that Message Networking can accept messages for delivery.
• Messages sent by digitally networked mailboxes to subscribers on any supported remote machine can be addressed using the number or name of the subscriber, if the subscriber name has been administered or registered.

  Note: Data must have been previously downloaded to the remote digital sending machine from the Message Networking system.

• Messages sent to digitally networked mailboxes from subscribers on any type of end node are treated as though they are coming from another digitally networked mailbox. Recipients hear "Message from voice or extension" as they usually would when receiving a message from local subscribers.

  Note: For VPIM V2 end nodes, this capability depends on the features of the VPIM end node.

• AMIS Analog subscriber messages can optionally contain the "private/priority" designation and voiced name of the sender as part of the actual message being sent.
• Messages delivered to VPIM V2 digital subscribers include the sender's name in the appropriate sender's voice name field in the ADPCM form if the name is stored on the Message Networking system.
• VPIM V2 digital subscriber messages can optionally contain the "private/priority" designation and voiced name of the sender as part of the actual message being sent.

  Note: When Aria senders send a mixed private and/or priority message to multiple Serenade or VPIM V2 digital recipients on the same remote machine, the message is marked Priority and/or Private for all recipients, even if only one recipient is marked as such. The sender is not notified that this has happened.

• AMIS Analog and Octel Analog Networking subscribers can be administered through any of the following ways:
• Administration screens
• Bulk files
• Sending a message through the Message Networking system (Octel Analog Networking only)
• Demand Remote Update (Octel Analog Networking only)
• Sending a message to a predefined subscriber registration mailbox on the Message Networking system
• Professional Services Organization (PSO)
• Aria Digital and Serenade Digital subscribers can be administered through any of the following ways (refer to Appendix H, Directory Population, in Message Networking Administration for further information about how and when subscribers are added to the Message Networking system):
• NameSend from Aria or Serenade Digital .

  Note: For existing subscribers who were migrated from an Aspen system to Aria Release 2.05 or later, NameSend does not work until each subscriber rerecords a spoken name on the Aria.

• For Aria, Demand Remote Update from the Message Networking system is supported as follows:
• Can be done by all extensions or an extension range.
• Takes an average of 2 seconds per subscriber.
• Is less efficient than Aria NameSend.
• Aria/Serenade Digital automatically informs the Message Networking system when a new subscriber is added; this is similar to AUDIX directory updates.
• Duplicate names from the same Serenade system have Node #D# appended to the name to make it unique.
• Message Networking supports only one mailbox length per remote machine.
• VPIM V2 and SMTP/MIME (that do not use LDAP-based updates) subscribers can be administered in any of the following ways:
• Administration screens
• Bulk files
• Sending a message through the Message Networking system
• Self-registration
• For subscribers residing on AUDIX Digital remote machines, a delivered status means the message was successfully delivered to the Message Networking system. This message can be returned to the sending subscriber if the Message Networking system cannot successfully deliver the message to the receiving subscriber for some reason.
• A scheduled message status for AUDIX indicates that delivery has not been successfully completed, nor has it failed yet.
• Senders receive notification of failed messages in two ways, including:
• An error message indicating each mailbox that failed to receive the sent message. This can be an optional Priority message.
• A copy of the failed original message from the Failed Message Delivery Manager.


• For AUDIX, failed message IDs can be viewed using INTUITY Message Manager.
• Notification of failure to deliver a message component because the recipient is not enabled to receive a component type (voice, fax, text, or binary) is the same as on the INTUITY AUDIX Release 4 system. The component that could not be delivered is stripped, and the following is prefixed to the original message: "One or more components could not be delivered, please contact the sender <pause><voice message>."
• Accessed status indicates that the subscriber has received and accessed a message for both the Message Networking and INTUITY AUDIX systems.
• For AUDIX, the machine name of the receiving machine in INTUITY Message Manager is that of the Message Networking system delivering the message.
• The ASCII name for remote subscribers contains a suffix of from two to eight characters at the end of the name field, indicating the Message Networking node ID for the remote machine on which that subscriber resides.

Top of page