On 30th of January the following was released: :
- ISL Conference Proxy 4.1.2 for Windows 32bit (Platform=win32, Revision=38749, release_date=2014-11-21, os_version=0x5020000-0x7fffffff)
- ISL Conference Proxy 4.1.2 for Windows 64bit (Platform=win64, Revision=38749, release_date=2014-11-21, os_version=0x5020000-0x7fffffff)
- ISL Conference Proxy 4.1.2 for Linux 32bit (Platform=linux, Revision=38749, release_date=2014-11-21)
- ISL Conference Proxy 4.1.2 for Linux 64bit (Platform=linux64, Revision=38749, release_date=2014-11-21)
- ISL Groop 4.1.2 (release_date=2014-11-21, revision=38690 )
All updates have release date set to 2014-11-21. Your ESS will need to be same or higher to be able to update your server. This release is available to all countries except Japan.
Upgrading to new version
This are server side updates so hosted service users do not need to do anything.
Server license users please check Upgrading Server License
ISL Conference Proxy
ISL Conference Proxy - Core - vcredist does not install under user islcp, module startup fails (DEFECT) [ISLCONFPROXY-618] More
Users who installed ISL Conference Proxy 4.1.0 or 4.1.1 on their Windows computer for the first time experienced an error of PostgreSQL module failed to load. The issue was that vcredist 2010sp1 was not installed with ISL Conference Proxy and this is needed in order to start PostgreSQL module. Installation process was redesigned, when installing ISL Conference Proxy, vcredist 2010sp1 is also installed. This fixes the issue of PostgreSQL module failure to load.
Users with the above error should update to ISL Conference Proxy 4.1.2 and open /conf page then navigate to PostgreSQL installation and click on remove notification and try again. PostgreSQL module should start correctly after restarting ISL Conference Proxy.
The defect was fixed.
ISL Groop - Module - Owner Reauthenticode will make session stop (DEFECT) [ISLGROOP-553] More
If users had ISL Groop application stored on desktop and the included authentication token was expired then started the meeting (user had to be session owner and session not started yet ), got kicked out of the meeting after 30 seconds. The issue was that once the user had authenticated he was not removed from join user queue. Users in user queue have 30 seconds to join the session otherwise the connection timeouts. Authenticating user was redesigned, once user is authenticated, the user gets removed from join user queue thus eliminating being kicked out of the session due to 30 seconds join timeout.
The defect was fixed.