Avaya

Avaya™ Message Networking Help

Home | Search the Help  
Print | Back | Fwd | Close  

Getting Started Admin Maintenance Reference
Home > Administration > Administering remote machines > Checklists for administering new remote machines > Checklist for adding a new VPIM remote machine

Checklist for adding a new VPIM remote machine

The following table lists the procedures for adding a new VPIM remote machine to the Message Networking system. The procedures appear in the sequence in which they are performed.

Note: The following list assumes a scenario in which remote subscribers address mail messages to VPIM subscribers using the same telephone number that is used to call VPIM subscribers. This approach is usually the easiest for subscribers to learn.

Completed Task
  Obtain the completed planning worksheet for the remote machine. You will use the information from this worksheet when you configure the remote machine parameters for the new VPIM machine.
  Obtain the Dial Plan Mapping requirements for the remote machine from your account representative. You will use these requirements to determine how to map the new system's dial plan.
  Administer the remote machine parameters for the new VPIM remote machine.
  Administer the Dial Plan Mapping for the remote machine, using the Dial Plan Mapping requirements you obtained.
 

Use one of the following methods to administer subscribers on the Message Networking system (in order of preference):

  • Use FTP to add subscribers.
  • Use self-registration to add subscribers' voiced names.
  • Send a message from the new subscriber.
  • Register through the Administration page.
  • Initiate Bulk Add by Range from the Message Networking system.
  Verify that the remote machine has been added to the Message Networking system:
 

Administer the Message Networking system as a VPIM network node on the VPIM system. You'll need the following information:

  • The fully qualified domain name and IP address of the Message Networking system. The VPIM system uses this information to send messages to the Message Networking system. You can find this information on the General Parameters page on the Message Networking system.
  • The Message Networking network address length. You can find this number on the General Parameters page on the Message Networking system.
  • The Message Networking network address ranges for other messaging systems in the network. Depending on the specific VPIM system, the address ranges that are required might extend just to the area code or the local area code + exchange prefix. In other cases, you might need all digits of the address ranges.

Note: The VPIM system must pass to Message Networking only those addressing digits used in the Message Networking network. When using telephones, subscribers on the VPIM system might have to dial additional digits to address messages to remote subscribers on the Interchange network. These digits might be required for the following reasons:

  • The VPIM system can identify the addressee as a remote subscriber.
  • The VPIM system can identify the remote system where the remote subscriber resides (in this case, the Message Networking system).

Do not administer the VPIM system to pass any other digits to the Message Networking system. Instead, administer the VPIM system so that it strips off these additional addressing digits when it passes the message to the Message Networking system. Only addresses within the ranges specified for Message Networking remote machines (specified in the Dial Plan Mapping) are to be sent to the Message Networking system.

  Perform a remote machine connectivity test.
  Verify the subscriber updates by viewing the Subscriber List by Machine Name on the Message Networking system.
  Update existing remote machines in the Message Networking network for subscribers on the new VPIM system. The Adding and updating subscribers overview provides information on how subscribers are updated for the different types of remote machines.

 

Top of page

Home | Search the Help | Print | Back | Fwd | Close

©2003 Avaya Inc. All rights reserved. Last modified 3 March, 2003