Adding and configuring a remote server

Add all remote sites in your messaging network to the network tree in Messaging Network Configuration. When you add a remote site, CallPilot automatically creates the site's prime switch location.

If you are using a Network Message Service (NMS), you can add satellite switches as required.

Much of the information that you provide when configuring the remote messaging server and remote switch location must be coordinated with the network administrator of the remote site. Modifications to the configuration should be done only if agreed upon by the remote sites.

You can add up to 499 remote sites. Remote sites are automatically listed in alphabetical order.

Note/Tip  If your CallPilot server does not have networking installed, you cannot add any remote servers to the network database.

To configure a remote server

Messaging > Message Network Configuration

  1. Do one of the following:

IF you want to

THEN

add a new server

click New Server.

The Server Properties page appears.

modify the configuration for an existing server

  1. In the Remote Server Maintenance tree, click the name of the remote server you want to modify.

  2. Click Show Details.
    The Server Properties page appears.

  1. In the Name box, type the name of the remote messaging server.
    The name is mandatory. It cannot be left blank. The name can be up to 30 characters in length.

    Note/Tip  You should type the name that was assigned to the remote server by its local network administrator. This correspondence in site naming makes the network easier to administer and maintain, because all network administrators use the same names for the same sites.
    Example

    If a remote server calls itself Toronto, you should name it Toronto when you add it to your Remote Server Maintenance tree.

  1. From the Server Type list, choose the type of system used at the remote site:

    Server type

    Description

    CallPilot

    CallPilot, any release

    MMNG

    Meridian Mail Net Gateway (connected to
    Meridian Mail Release 11)

    Meridian Mail

    Meridian Mail Release 8 or later

    Norstar

    Norstar Voice Mail, any release

    Other

    Any other vendor’s voice messaging system

  2. In the Description box, enter details about the remote server.
    Maximum length: 255 alphanumeric characters

  3. Choose the Site ID.
    The Site ID is mandatory for each remote server. All servers in the messaging network must have a unique ID. Choose a number that has not been assigned to any other site, between 1 and 500.

    Caution The site ID you specify here for the remote site must match the local site ID in the remote site's network database.

  1. Choose the following options, as required:

Note/Tip  By default, the Send Network Broadcast and Receive Network Broadcast options are enabled for VPIM and Enterprise Networking. If the network protocol between the local and remote server is AMIS Networking, then these options are not available because network broadcast and location broadcast are not supported by the AMIS protocol.

  1. If Enterprise Networking will be used to exchange messages with this remote server, choose the following options, as required:

  1. Type the remote server’s fully qualified domain name (FQDN) in the Server FQDN box.
    Note/Tip  You must specify the FQDN even if you are not using VPIM Networking, because it is required for desktop messaging and My CallPilot. The FQDN also facilitates the delivery of VPIM messages to recipients at sites that do not use the VPIM protocol.

    The FQDN must match the host and domain name defined in the DNS configuration on the CallPilot server. If you do not know the FQDN, type a placeholder, such as "FQDN_goes_here."
    Maximum length: 255 alphanumeric characters

  2. Choose the network protocol from the Network Protocol list box.

  3. Define the connection information for this server, as required.

  4. Click Save.

  5. Configure the remote prime switch location.

Back to top


Planning Tools    Remote Server Procedures    Switch Location Procedures    Overviews