Changes for Amethyst 1.5.12

[Belinda Frick]

Supervisor

New features
Supervisor can now see the agent screen for AMTClients configured as CTI devices
Live updates of agent screen (no more 10-second refresh)
Search results can now be sorted
Supervisor can now search between two dates (with a pop-up calendar to select dates)
Supervisor will now show a message if AQM questions are missed
Telephone number, destination, duration and reference are now displayed on reviews
Some additional checks for faulty input
Recordings default to AQM status "B" instead of AQM status "A" after first review

Bug fixes
Supervisor comments are no longer lost when using quotes
Prevented possible thread conflicts when two Supervisors are working at the same time
Cleaned up HTML code
Various spelling mistakes fixed
Telephone number is now saved when a new predefined search is created

Web Admin
Moved "Change Password" to Admin screen and not main screen
E-mailed logs are now sent as .txt instead of .log
"Test connection" now writes the results to the webadmin log as well.
Changed lost password feature to require the default password and use a button to prevent abuse.
When configuring Supervisors, no longer allows logins or passwords which are too long to be inserted into the database.

Sweeper
"Configure Sweeper" will create an INI file with default entries if the INI file is blank.
CRITICAL e-mails will now have .txt attachment instead of .log
Added facility to re-process Sweeper's calls if not enough licenses.
Changed display in list of mounts when configuring Sweeper to be correct for first exclusive drive.
Amethyst Server
The cardserver can be "stuck" on a locked recording, due to a channel being down. This version will skip over locked recordings.
Nightly archiving should now work with damaged databases as well.
Verbose logs are turned off after 2 days (48 hours)
Tools
More descriptive error messages when there are NFS errors.
Fewer duplicate error messages if there are errors during the archive process.
Fixed problem where checksum errors are given on NFS archives if the file is not completely written to disk yet.
The archive process won't abort if the database is damaged (critical warnings will still be given).
Fixed bug that could cause archiving to take a long time on very busy sites or sites that have large NFS archive drives.