Configuring VPIM Networking security options

You can secure the VPIM Networking connection to each remote server by

Go to task list.

Secure Socket Layer (SSL)

CallPilot uses Secure Socket Layer (SSL) to encrypt message transmissions between CallPilot and

When SSL is used to encrypt message traffic between messaging servers, users are provided with privacy over the network.

Caution!  Total privacy is only obtained under the following circumstances:

SMTP authentication password

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.

SMTP authentication failures counter

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.

Controlling message receipts from the remote server

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.

To configure the VPIM security options

Messaging > Message Network Configuration

  1. In the Remote Server network tree, select the remote server that you want to modify.

  2. Ensure that VPIM is selected in the Network Protocol box.

  3. In the VPIM Security section, configure the following:

    1. 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
      Note/Tip  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.

    2. 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

    3. 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.
      Note/Tip  After you resolve the cause of SMTP authentication failures from the remote server, click Reset Count to set the counter back to 0.

    4. 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.

    5. Receive messages from this server: Choose Enabled from the list box to allow the local server to receive messages from this remote server.

  1. Click Save.

Back to top


Related Procedures    Overview    See Also