Your local site consists of the local messaging server and the local prime switch location. The local server and local prime location are automatically added to the network tree during CallPilot installation. You must configure the local messaging server and local prime switch location so they can communicate with remote sites.
For the local messaging server, you specify identification information and enable or disable options for sending or receiving information, as follows:
The server type for the local messaging server is always CallPilot and cannot be changed.
The Site ID is mandatory. All servers in the messaging
network must have a unique ID.
Prior
to CallPilot Release 2.0, the site ID was mandatory only if the Enterprise
Networking protocol was used on the local server. If you upgraded your
server to CallPilot 2.0, the site ID could be blank. You must manually
configure it for all networking protocols.
If you are using Enterprise Networking, you can
enable the Names Across the Network (NAN)
feature. NAN automatically adds temporary remote users
to the local network database and maintains them.
You must coordinate with the network administrator
of each remote site with which you want to enable NAN. NAN only works
with remote sites that use Enterprise or VPIM Networking, and must be
enabled on both the local messaging server and the remote servers.
If you are using VPIM Networking, the NAN
feature is automatically enabled, and cannot be disabled.
You can enable or disable broadcast message transmissions between the local server and all remote servers. Broadcast messages include the following:
network broadcast messages (messages that are sent to all users at each local and remote site)
location broadcast messages to and from all locations associated with each local and remote site (these are messages that are sent to all users at a single location)
If
users associated with the local server are using My CallPilot and you
change the server name, fully
qualified domain name,
or both, the My CallPilot web server does not automatically detect the
changes. You must run the My CallPilot Administration Utility on the My
CallPilot server to adjust the settings; otherwise, My CallPilot users
may not be able to log on to their mailboxes.
Messaging > Message Network Configuration
In the Local Server tree,
click the local server, and then click Show
Details.
The Local Server Properties page appears.
To change the name of
the local server, type a new name in the Name
box.
The name is mandatory. It cannot be left blank. The name can be up
to 30 characters in length.
Default: Untitled
In the Description
box, type details about the local server.
Maximum length: 255 alphanumeric characters
Choose
a Site ID.
The Site ID is mandatory. 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.
Choose the required options:
Send Messages
to all Other Servers: Check this option to enable your local messaging
server to send messages to the remote sites in your messaging network.
This option is checked by default.
If
you disable this option, messages cannot be sent to the remote sites that
are defined in your network database. However, messages can still be sent
to open sites.
This check box is cleared only in unusual circumstances.
Add/Update Remote Users on this Server: If
you are using Enterprise Networking, check this option to enable the Names
Across the Network (NAN) feature.
This
option is automatically enabled for VPIM Networking. It cannot
be disabled.
Send Network Broadcast: Check this option
to allow the transmission of network broadcast
messages
to all sites in the network. (See also When to disable
broadcast messages.)
AMIS
Networking does not support network broadcast messages. If only AMIS Networking
will be used in your network, leave the check box blank.
Receive Network Broadcast: Check this
option to allow the receipt of
network broadcast messages from all other sites in the network. (See also When
to disable broadcast messages.)
AMIS
Networking does not support network broadcast messages. If only AMIS Networking
will be used in your network, leave the check box blank.
If Enterprise Networking will be used to exchange messages with any remote server, check the Receive Message Text Info option to allow desktop messaging users to receive subject headers in the messages sent by all remote sites that are enabled to send message subject headers. Subject headers are created when messages are sent from desktop messaging. A subject header significantly increases a message's transmission time. If your site incurs charges for incoming messages, or if you have limited voice channel capacity, consider clearing this option.
In the SMTP/VPIM section,
type the fully qualified domain
nameof the local server in the FQDN
box.
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 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
Click Save.