Avaya

Modular Messaging Help

 Getting Started 
 Administration 
 Maintenance 
 Reference 
Home   >   MAS Administration   >   Configuring the local Octel Analog Networking node

Configuring the local Octel Analog Networking node

To enable your local Octel Analog Networking node to send and receive messages through the Octel Analog Networking gateway, you must configure properties for the local node. The properties apply to all MASs in the domain.

To configure local Octel Analog Networking node properties:

  1. Start Octel Analog Networking gateway administration.
  2. For more information, see Starting Octel Analog Networking gateway administration.

  3. Click the Local Node tab.
  4. Configure the following fields on the Local Node tab:
    • Serial number  Enter the unique serial number of the Octel Analog Networking system. The serial number is a line item on the Octel Analog Networking certificate included with the Avaya Modular Messaging shipment.
    • Hours before returning a non-delivery report  Enter the number of hours for which the MAS continues to try to send messages to the remote Octel Analog Networking node before returning a non-delivery report. The default is 4. We recommend that you enter a minimum value of 4.
    • Maximum TTS conversion length (mins)  Enter the length of time, in minutes, that is allowed for a text message that has been converted to voice using text-to-speech conversion. If this time is exceeded, the system sends a non-delivery report.
    • Sending Server  Select the MAS that sends voice messages. To locate the MAS in the voice mail domain, click Browse.
    • Only one MAS in a voice mail domain can send voice messages through the Octel Analog Networking gateway. This MAS is marked with the icon. All other MASs are marked with the icon to indicate that they cannot be used to send messages using Octel Analog Networking.

      Note: All MASs can receive Octel Analog Networking messages.
  5. Click OK or Apply.
Note: If the MAS stops before returning a non-delivery report for a message that could not be delivered, the report is not returned until the MAS restarts and the number of hours specified in the Hours before returning a non-delivery report field elapses.