This topic describes
CallPilot uses Secure Socket Layer (SSL) encryption 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.
Encryption is optional. However, Nortel Networks strongly recommends that you establish a secure (encrypted) session if the User ID and Password authentication method is used. Transmission of the user ID and password in the clear is strongly discouraged.
Encryption prevents
password transmission in the clear
eavesdroppers from gaining access to the contents of the message (thereby ensuring user privacy)
To determine whether you need to implement encryption in your CallPilot network, consider the following:
Is encryption needed for secure desktop messaging or My CallPilot logon?
Is encryption required between messaging servers?
Does your network infrastructure
support secure message transmission from end-to-end?
If messages cross a firewall or pass through an intermediate mail relay,
encryption may not be provided end-to-end.
Do you need to upgrade
any systems?
Transmission of an encrypted message to a remote CallPilot system is
pointless if the message is also addressed to another system that does
not support SSL. To do so wastes CPU bandwidth.
Encryption of TCP/IP traffic for SSL requires significant CPU resources. The impact of using SSL depends on
total network traffic (desktop messaging and VPIM Networking)
percentage of traffic that is using SSL
Encryption is enabled and configured independently from SMTP authentication configuration. For information about SMTP authentication, see SMTP security.
SSL configuration consists of the following tasks:
SSL for incoming sessions from desktop messaging or My CallPilot clients and remote messaging systems.
SSL for outgoing message transmission sessions to remote messaging systems.
For each remote server defined in the CallPilot network database, specify the port that the CallPilot server uses to listen for SSL connections, if it is different from the CallPilot default SSL port (465).