Avaya

Message Networking Help

Home | Search  
Print | Back | Fwd | Close
  
Getting Started Admin Maintenance Reference
Home >  Administration > Remote machine administration > Add or modify a remote machine: Modular Messaging/Exchange or UM Analog

Add or modify a remote machine: Modular Messaging/Exchange or UM Analog

Use the Add New Machine: UM Analog page to add a new Modular Messaging/Exchange using OAN or UM analog remote machine to the Message Networking system or to modify an existing machine.

This page contains the following fields.

New Machine Name: Type a unique name for the remote machine you are adding. The machine name can be up to 23 alphanumeric characters:

  • Enter uppercase letters as uppercase.
  • Enter lowercase letters as lowercase.
  • Use a hyphen (-) or an underscore (_).
  • These names cannot start with a number.
  • There can be no blank spaces.

Note: The name must be unique on both the local Message Networking network as well as any other Message Networking systems in the network. To ensure that you are using a unique name, check the Remote Machines List on all Message Networking systems in your network.

Machine Type: Select UM Analog to add a Modular Messaging/Exchange using OAN or UM Analog remote machine.

Bridged Machine: Specify whether this remote machine is to be used as a bridged machine. Bridged machines are used by Message Networking to pass messages between nonbridged remote machines. Select yes to indicate that this remote machine is to be used as a bridged machine. If this remote machine is not being used as a bridged machine, select no. The number of remote machines that can be used as a bridge is specified by the Number of Bridged Nodes field on the Customer Options page.

Note: The Bridged Machine field does not appear if the Number of Bridged Machines on the Customer Options page is set to 500 (the maximum).

Send FAX Messages?: Specify whether fax messages are allowed for the remote machine. Select Yes to allow fax messages or No to restrict fax messages.

Note: Modular Messaging/Exchange systems using Octel Analog Networking require a separate fax server to support fax components.

Dial String: Type the gateway telephone number of the remote machine, up to 30 characters. The Message Networking system uses the dial string to contact and send messages to the remote machine. The dial string typically consists of the dial-access code needed to reach the network, followed by a pause interval, followed by the telephone number of the remote machine.

You can enter the following characters in the dial string field: 0 - 9, P, #, *, and ". To make the Message Networking system pause for a specific length of time, type "P" (including the quotes) in the dial string. Include a single "P" to cause the system to pause approximately 1.5 seconds. Include a "P" followed by a digit from 1 to 9 to cause the system to wait the specified number of seconds.

Mailbox ID Length: Type the number of digits in mailbox IDs on the remote machine, up to 10 digits.

Note: To change the Mailbox ID Length after initial system administration, see Changing a remote machine's mailbox number length for the steps you must complete to successfully change this field.

Default Language: Use this field to specify the default language on the remote machine. If more than one language is installed on the system, select the language from the drop-down menu. The default for this field is en-US (US English).

If you change the Default Language after initial remote machine administration, subscribers that you subsequently add to the remote machine are assigned the new Default Language as their default Language ID. However, the Language IDs of existing subscribers on the remote machine do not change.

Failed Msg. Notification Priority?: Indicates whether to mark failed message notifications with priority status. Select yes to mark failed message notifications with priority status. Select no if you do not want to mark failed message notifications with priority status. The default for this field is no.

Msg ID?: Specify whether to include the original message ID in failed message notifications. Select yes to include the original message ID. Select no if you do not want to include the original message ID in failed message notifications. The default for this field is no.

Send Message for EAW?: Specify whether the original message is sent back to a subscriber after that subscriber has sent a message from this machine to an Aria machine that has the Extended Absence Greeting (EAG) warning activated. This message return is in addition to the message indicating the actual EAG warning condition. Select yes to return the original message. Select no if you do not want to return the original message. The default for this field is no.

Default NameNet Type: Specify the default NameNet type, set up on the remote machine, that is used for aging purposes by the remote machine. Type p if directory entries are permanent. Type u if entries are usage-based, which indicates that directory entries are temporarily available based on the network traffic of a particular remote machine. The default for this field is u.

Organization: Use this field to provide a description of the organization using Message Networking, up to 64 characters. This field is optional and for informational purposes only.

Organization Unit: Use this field to provide a description of the organization unit using Message Networking, up to 64 characters. This field is optional and for informational purposes only.

Node ID: Unique node ID for this remote machine. This field is display-only and cannot be modified.

Comments: You can optionally type any comments about this remote machine, up to 68 alphanumeric characters. This field is optional and for informational purposes only.

Default Community ID: Community identifier for all subscribers added to this remote machine. An integer of 1 through 15.

Subscriber Updates Type: Leave this field at the default, dynamic. This field does not apply to UM Analog and Modular MM/Exchange using OAN systems because they cannot request remote updates from Message Networking and Message Networking cannot push remote updates to these remote machines.

Updates In: Specify whether the Message Networking system can receive updated user database information from this remote machine. Select yes if this Message Networking system accepts updated user information from this remote machine. Select no if this Message Networking system does not accept updated user information from this remote machine. The default for this field is no.

Updates Out?: Leave this field at the default, no. This field does not apply to UM Analog and Modular MM/Exchange using OAN systems because Message Networking cannot push remote updates to these remote machines.

Voiced Names for Dynamic?: Leave this field at the default, yes. This field does not apply to UM Analog and Modular MM/Exchange using OAN systems because Message Networking cannot push remote updates to these remote machines.

ASCII Name Confirmation?: Specify whether the ASCII name is verified when a subscriber sends a message using NameNet. If the name does not match, the Message Networking system requests an update. Select yes to verify the ASCII name. Select no if you do not want to verify the ASCII name. The default for this field is yes.

Admin Mode?: Specify that when Message Networking delivers a message to a remote machine using the Octel Analog Networking gateway, Message Networking automatically requests a subscriber update for the receiving subscriber. Select yes to automatically request a subscriber update. Select no if you do not want to automatically request a subscriber update. The default for this field is no.

Octel Analog Serial Number: Type the serial number of the analog remote machine, either 4 or 5 digits.

Dynamic Sub Expiration Days: Type the number of days a dynamically-added subscriber can exist without performing any activity (without sending or receiving messages). This number must match the number of aging days administered on the remote machine. The default for this field is 90. The minimum for this field is 1. The maximum for this field is 999.

Record Delay (Sec): The Record Delay is a timing parameter used by the Octel Analog Networking protocol that specifies the number of seconds before recording begins. The default for this field is 3. If clipping occurs at the beginning of a message received by an Octel Analog Networking remote subscriber, increase this value to eliminate clipping. If silence occurs at the beginning of a message received by an Octel Analog Networking remote subscriber, decrease this value to eliminate the silence.

Maximum Simultaneous Connections: Maximum number of ports that will simultaneously handle outgoing traffic for this machine. Enter an integer of 1 through 9 The default for this field is 1.

Voiced Name Delay (Sec): The Voiced Name Delay is a timing parameter used by the Octel Analog Networking protocol that specifies the number of seconds before a remote subscriber's name is voiced. The default for this field is 3. If clipping occurs at the beginning of a message received by an Octel Analog Networking remote subscriber, increase this value to eliminate clipping. If silence occurs at the beginning of a message received by an Octel Analog Networking remote subscriber, decrease this value to eliminate the silence.

System Mailbox ID: This field specifies the system mailbox number used by the protocol for the remote machine, up to 10 digits. The default for this field is 0. This mailbox address must match the system mailbox set up on the remote machine.

If you are modifying an existing machine, click Save to save your changes. If you are adding a new machine, click Next Step to save the remote machine and administer Dial Plan Mapping, or click Add this Machine if you do not want to administer Dial Plan Mapping at this time:

  • If you click Next Step, the Administer Dial Plan Mapping page displays.
  • If you click Add this Machine, a message displays that the parameters have been saved. Click OK.

Top of page

Home | Search | Print | Back | Fwd | Close
©2006 Avaya Inc. All rights reserved.
Last modified 8 February, 2006