Desktop messaging requires appropriate configuration of CallPilot server components that interact with desktop messaging.
In addition, the features and options available to users are determined by the privileges you assign to mailbox owners. For more information, see User access rights.
Ensure the following components are configured correctly on CallPilot server for desktop messaging.
|
Component |
Description |
|
Desktop messaging uses domain name resolution for the CallPilot FQDN. If you do not have a Domain Name System (DNS) server, you must use an alternative method to identify the CallPilot server address. | |
|
IMAP service lets desktop messaging users retrieve CallPilot messages from the CallPilot server. | |
|
If some of your users require access to their office or external e-mail account using Web Messaging or Email-By-Phone, you must specify the e-mail servers they are permitted to access. | |
|
LDAP service lets desktop messaging users access the CallPilot address book. | |
|
SMTP service lets desktop messaging users send CallPilot messages. You can enable and disable SMTP service. SMTP service options are configured as a part of messaging network configuration. | |
|
SMTP supports both authentication and encryption options. | |
|
You must define an SMTP/VPIM prefix (VPIM network shortcut) for the local site and any NMS satellite switch locations. This prefix is required for desktop messaging, even if you are not implementing NMS on the CallPilot server. |