This package contains:

1. PEP Number: CP300S00G09S


2. Problem Description:
-----------------------
Q00859007-01
The current design to handle the SSL connection requires that client must 
authenticate the server certificate.  These steps requires certain permissions 
for the cmd.exe and requires to configure a domain for the CallPilot server. 
For 2003 OS the security has been increased, which results is the failure to 
perform necessary steps.
To overcome these problems knowing that CallPilot clients do not really need
 to authenticate the certificate of the CallPilot server, the SDK library has been 
modified to allow the clients to connect over SSL to the server without 
authenticating the server certificate. The cpmgr code has been updating to 
skip importing the server certificate. 

Q00966310-02
When a user's password is about to expire and they log on to CallPilot via
the desktop client, they should receive a password expiry warning with the
option to change their password. However, on CallPilot systems configured
with international (non-North American English) mailboxes, the user
receives an "Invalid credentials" message and they fail to logon.
When the CallPilot server detects that a user's password is about to expire,
it attempts to load an internal password expiry string from the North American
version of IMAP_LNG.TXT. However, if the default code page of the CallPilot
server is not North American English and the mailbox is not North American
English, it fails to load the string. 
The imap server was modified to always load the North American English version
of IMAP_LNG.TXT. This should ensure that the correct internal string is always
loaded. The internal, hard-coded string was also updated to remove the bad
formatting that was causing the crash.

Q00987148-01
IVR channels are not correctly displayed in Channel Monitor

Q00991166-01
A process was consuming 100% CPU on CallPilot. 2 messages were found
to be stuck in the incoming folder which were  causing IMA to go into an infinite 
loop. It appears that these files were not intended for any user on the CallPilot 
system and were relayed from some other system. After removing these messages 
from the folder, CPU usage went back to normal.
The condition leading to the loop, is that the last MIME header 
line starts from blank or tab symbol. As the matter of fact a correct MIME 
header will never conform that condition, but CallPilot should not be confused
so much facing it any way.

Q01002510-01
When rebooting the server after running configuration wizard, before logging on with the ngensys
account the following error is displayed ;
The instruction at 0x006d5efb referenced memory at 0x261ddb8'.
This impacts  the MWI service, which will not start up automatically. CallPilot can take calls (although the popup window say CallPilot can not take calls), but MWI will not be updated. However, the MWI service can be started manually.


Q01017361-01
There was an analysis added into 'AddBackupDevice' function which examines the path of backup devices and does not allow adding devices with incorrect path. There is a small bug there therefore there is no possibility to add a backup device with subfolders. It is necessary to originate a CR to fix it. If it is a GA blocking problem it can be fixed right now. 
 

3. List of CRs that are fixed by this PEP: 
-------------------------------------------
Q00859007-01       	Unable to log in to CallPilot when SSL is activated
Q00966310-02	Can not login to Desktop messaging when password due to expire 
Q00987148-01	IVR channels are not correctly displayed in Channel Monitor
Q00991166-01	IMA service is consuming 100% CPU usage
Q01002510-01	High/nbnot.exe memory error appears after 201i server reboot
Q01017361-01	Minor/Cannot use the Remote Disk Backup to Subfolders
Q00999036-01	Unable to open locked applications

4. How to install this PEP
---------------------------
Make sure you are installing this PEP on a server that has 
been installed with, or upgraded to CallPilot 03.03.06.02 

In order to install the PEP:

- Launch the runme.exe to start the installation of the PEP.
  The runme executable can be found in the PEP's root directory.

- A reboot is required before the server can be brought back into service.

Uninstall:
----------
Go to Start>Programs>CallPilot>System Utilities>PEP Maintenance 
Utility. Click Show PEPs.  Select CP300S00G09S and click Remove.


