The Askia software on the following stations in your interviewing center can be updated automatically:
To perform an update, the system administrator simply needs to provide the latest set-up files to CCA. The update is then distributed automatically when users log in to their supervisor, CATI or Face stations.
Updates are sent by Askia to the system administrator. The supervisor and CATI updaters will have filenames supervisor_update [version number].exe or cati_update [version number].exe respectively (for example supervisor_update 5.1.5.0.exe).
The following notes apply to AskiaField agent, but a similar update process applies to Supervisor and AskiaFace.
In order for the installation to occur, the system administrator should place the updaters in a special folder, where CCA will detect them and handle the distribution. The location of this folder depends on your system installation, and is specified in the registry key HKEY_CURRENT_USERSoftwarePeter HolmesCcaAutoUpdater.
When an agent logs into askiafield agent, the service checks the registry key in LatestInstalledVersion at HKEY_LOCAL_MACHINESOFTWAREPeter HolmesCatiSettings, and compares it with the cati-update v5.1.x.x.exe file version on the askiafield CCA server.
If a newer version is found on the server, the updater will automatically download from the CCA and install the newest version on the askiafield agent machine with no human intervention required. EXE and DLL files are updated as necessary. The update could concern any of the following files: cati.exe, askiaclient.exe, askcmn.dll or other dlls used for voice over IP (metaphor.dll or allegory.dll).
At the end of the update, AskiaField agent will restart automatically, and the agent will be presented with the logon window.
On Windows NT-based systems (including XP and Vista), the service ContactCenterUpdaterService runs under system/administrator rights and waits for a request for an update. When an application (AskiaField agent, CCA or supervisor) wants to update itself, it places the update in the appropriate folder, requests an update from the service and terminates itself. The updater runs the setup with administrator rights, deletes the update file, and restarts the calling application with the restricted user account.
On Windows 95/8/ME, because services do not operate in the same way, the application just starts the updater and exits (hoping that all goes well).
Here is an example of the configuration for automatic CATI updates:
Create an update directory somewhere, and add the setup files there. Example: C:AskiaUpdatesCATIupdate_5.1.5.0.exe
Create the following registry entries (in HKEY_CURRENT_USERSoftwarePeter HolmesCcaAutoUpdater):
CATI update path -> C:AskiaUpdatesCATI
CATI update arguments ->
CATI update style -> 0/1/2
0: Ask if we should install update (yes/no), Cati will start normally if 'no' is chosen.
1: Warn if we should install update (ok/cancel), Cati will exit if 'cancel' is chosen.
2: Install update without question/warning.