You can secure the VPIM Networking connection to each remote server by
configuring the remote server's SMTP authentication password
enabling or disabling message receipts from the remote server
Go to task list.
CallPilot uses Secure Socket Layer (SSL) to encrypt message transmissions between CallPilot and
desktop messaging and My CallPilot clients
another messaging server
When SSL is used to encrypt message traffic between messaging servers, users are provided with privacy over the network.
Total
privacy is only obtained under the following circumstances:
The message originates from a phoneset, or SSL is used between the desktop messaging or My CallPilot client and the CallPilot server.
SSL is used end-to-end between messaging servers.
The SSL transaction is successful.
Message transmissions can be authenticated to prevent toll fraud and security breaches in your messaging network. If you plan to implement SMTP authentication, then you must define the SMTP password sent by the remote server to the local server.
The Failed attempts from this server field displays the number of times SMTP authentication failed from the remote server. If the number of failures reaches the maximum number of failures defined on the local server, CallPilot will disable incoming VPIM message transmissions from this remote server, if configured. For more information, see Configuring the authentication options on the local server.
When you resolve the cause of SMTP authentication failures from the remote server, you can click Reset Count to set the counter back to 0.
You can control the receipt of messages from the remote server by enabling or disabling message receipts. When message receipts from the remote server are disabled, CallPilot rejects all incoming VPIM messages from that server (both authenticated and unauthenticated). This prevents hackers from trying all the possible password combinations, and eventually obtaining the correct SMTP password.
Messaging > Message Network Configuration
In the Remote Server network tree, select the remote server that you want to modify.
Ensure that VPIM is selected in the Network Protocol box.
In the VPIM Security section, configure the following:
SSL port
number: If encryption will be used, type the port number designated
as the Secure Socket Layer
port on the remote messaging server.
Default: 465
When
the SSL port is specified, and if the Connect
to server with SSL for Outgoing SMTP Sessions option is enabled
in Message Delivery Configuration, CallPilot attempts to establish an
encrypted connection with this port when connecting to this remote server.
Server password:
Type the SMTP authentication password
that the remote server must send when the local CallPilot server requests
SMTP authentication.
Maximum length: 30 alphanumeric characters
Failed attempts
from this server: This box displays the number of failed SMTP authentication
attempts that have occurred to date. If this value reaches the maximum
number of failures defined on the local server (specified in the System Maximum box, below), CallPilot
will disable incoming VPIM message transmissions from this remote server,
if configured. For more information, see Configuring
the authentication options on the local server.
After
you resolve the cause of SMTP authentication failures from the remote
server, click Reset Count to set
the counter back to 0.
System Maximum: This box displays the maximum number of SMTP authentication failures that the local server will tolerate from this server. For more information, see Configuring the authentication options on the local server.
Receive messages from this server: Choose Enabled from the list box to allow the local server to receive messages from this remote server.
Click Save.