ISL Conference Proxy 4.1.5 for Windows and Linux (2015-04-10)

General Information

On 10th of April the following was released: :

• ISL Conference Proxy 4.1.5 for Windows 32bit (Platform=win32, Revision=39735, release_date=2014-11-21, os_version=0x5020000-0x7fffffff)
• ISL Conference Proxy 4.1.5 for Windows 64bit (Platform=win64, Revision=39735, release_date=2014-11-21, os_version=0x5020000-0x7fffffff)
• ISL Conference Proxy 4.1.5 for Linux 32bit (Platform=linux, Revision=39735, release_date=2014-11-21)
• ISL Conference Proxy 4.1.5 for Linux 64bit (Platform=linux64, Revision=39735, release_date=2014-11-21)

Update availability

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

Improvements

ISL Conference Proxy - Core - add cmd_reset_web_access_filter (FEATURE) [ISLCONFPROXY-672] More

Description

Support for resetting web access filter setting was added to ISL Conference Proxy.

On linux execute the following command in terminal : confproxyctl resetwebaccessfilter

On Windows run cmd_reset_web_access_filter.bat located in ISL Conference Proxy installation folder

Both support also the following option: create file called cmd_reset_web_access_filter inside ISL Conference Proxy installation folder and restart ISL Conference Proxy

ISL Conference Proxy - Core - add xmlmsg file commands (FEATURE) [ISLCONFPROXY-673] More

Description

ISL Conference Proxy now supports XMLMSG through file commands. Commands are read at start of ISL Conference Proxy. In order to execute a command users will have to do the following:

1. Create a file called cmd_xmlmsg inside ISL Conference Proxy installation directory

2. Add XMLMSG call inside cmd_xmlmsg

3. Restart ISL Conference Proxy

4. After restart original cmd_xmlmsg will be deleted, new file cmd_xmlmsg_reply will be created which shows success or failure of the call.

Access password in XMLMSG message is not required. If users plan to execute multiple XMLMSG calls they have to create multiple files with a number extension ( example - cmd_xmlmsg.1 , cmd_xmlmsg.2 , cmd_xmlmsg.3 and so on ).