ISL Conference Proxy 4.4.2120.112 with modules for Windows and Linux (2022-03-03)

Localhost IP checks are now enforced on all HTTP frontend connections.

In previous versions of ISL Light module argument check was not performed correctly and was now redesigned.

ISL Conference Proxy now supports local non-replicated DT tables.

Settings in Security have been removed:

• "Do not use service public addresses for web pages"
• "Alternate (for CDN) address for web pages"
• "Alternate (for CDN) address for other services"
• "Allow X-Forwarded-For header (for CDN) for IP ranges"

Two new tables were added for storing ISL Groop session info required for reports: "islgroop_session_history", "islgroop_participant_history".
New setting "Update session history interval in seconds" was added to /conf -> Configuration -> ISL Groop, which can be used to modify update interval of end session time (default 300 seconds).

Groop session history is now exposed through existing reports api: "reports/products/usage/get/1".

Reports page for ISL Groop module was added, accessible at Reports -> Web Conference. Report shows:

• graph of daily usage for given span
• aggregated stats (total sessions, durations, participants...)
• list of sessions with details

Sessions can be exported to CSV.

New page was added to ISL Groop reports, where user is able to see details of one session and its participants (how long were they in session, what country are they from and what platform they use).

Participants can be exported to CSV.

New field "Client Description" was added to ISL Light reports. This field is only set for ISL AlwaysOn sessions and contains description of the AON connection used to connect to remote computer.

Support for breakout rooms functionality was added to ISL Groop module:

• Implemented support for persistent breakout room data storage in "islgroop_sessions" table
• Implemented support for storing breakout room status data
• Implemented support for changed data notifications
• Implemented support for breakout room related RPCs (create, modify, delete, assign, start)

Added support for dedicated chat channel for breakout room functionality.

New settings:

• /conf -> Configuration -> Security
  • Enable GRID health api in /health/grid exposes health status with HTTP API on /health/grid
  • GRID health api secret can be used to protect API with secret (if not empty, HTTP API requests need to have secret set in query string)
• /conf -> Configuration -> GRID ->Settings
  • GRID server tags was added where tag for each server can be provided. This tags are then used when checking for number of servers and services per tag. Server can have multiple tags(format: $TAG1$, $TAG2$, $TAG3$)
  • Delay before first GRID health check (secs) can be used to set the delay before first GRID health check is performed after restart of server (before this delay any GRID health issues are not detected or exposed through HTTP API)
  • Minimum number of connected servers in GRID can be used to specify minimum number of connected servers in GRID with enabled load.
  • Minimum number of connected servers per tags is used to provide tag based limits for number of connected servers with load in GRID (format: $TAG$=$MIN_SERVERS$)
• /conf -> Configuration -> GRID -> Load balancing -> Service settings (each service has own settings)
  • Minimum number of servers providing service in GRID specifies minimum number of connected servers that provide given service in GRID
  • Minimum number of servers providing service per tags specifies minimum number of connected servers that provide given service per tag (format: $TAG$=$MIN_SERVERS$)

Implemented GRID health checks:

• check if number of connected servers with load on is above limit set with Minimum number of connected servers in GRID
• check if number of connected servers with load on is above limit for each tag set in Minimum number of connected servers per tags
• check if any disconnected servers that have load on
• for each available service check if number of servers is above limit set with Minimum number of servers providing service in GRID for this service
• for each available service check if number of servers in each tags is above limits set with Minimum number of servers providing service per tags for this service

GRID health check is performed periodically (every minute) and all checks are performed. If any check fails logs are created and error is exposed in /conf.
GRID health check is also performed when manipulating with GRID settings so user should get immediate feedback if setup no longer matches given limitations.
Each of the mentioned checks is exposed with simple web page (response code is set to 200 if check OK, otherwise 500, except if "no_err" query argument is set in request, then 200 is returned on error also):

• /health/grid/overall - Check all
• /health/grid/servers/connected - Minimum connected servers with load in GRID
• /health/grid/servers/tags - Minimum connected servers with load per tags
• /health/grid/servers/disconnected - Disconnected servers with load in GRID
• /health/grid/services/total - Minimum servers with service in GRID
• /health/grid/services/tags - Minimum servers with service per tags

Added new permission "Guests will continue sharing their screens when breakout rooms are opened" to /conf -> ISL Groop -> ISL Classroom. With this permission disabled, guests will automatically stop sharing their screens when breakout rooms are opened.

Two new indexes were created for "c_time" column that replace existing simple index. Index is used by "islalwayson/computer/search/2-3" webapi when searching for last used.

Severity of "connected to server" logs was changed and will be now logged with following log level:

• initial connect - notice
• reconnect - warning

Severity of "disconnected from server" logs was changed and will be now logged with following log level:

• disconnect - warning
• disconnect because of duplicate connection - notice

New setting was added to /conf -> Configuration -> GRID ->Settings: "Health Check when down set log severity Critical after (in minutes)"

Setting can be used to specify the amount of time that individual check needs to be failing for, until the logs are escalated from "warning" to "critical". Setting it to "5" would mean that failing check will be logged with "warning" for 4 minutes and with "critical" from 5th check on (after 5 minutes).

Each successful check will reset delay.

Support for custom breakout room labels was added to ISL Groop module.

ISL AlwaysOn computer update quota was implemented. Maximum 10 updates are allowed, all subsequent updates are skipped.
The counter is reset after 24 hours. New log subsystem "[ISL AlwaysOn] Database Flush" was added.

Added HTTP event message (EVENT=END) for ISL Light sessions. This event is triggered when session has ended.

In previous versions when changing "Title background color" setting, ICP had to be restarted to apply changes. This was now redesigned and restarting ICP should no longer be necessary.

The defect was fixed.

In previous versions on v440 pages, when user had setting "User can create Classroom type meetings" disabled, functionality was still shown. This was now redesigned and button to add new Classroom should not be visible anymore.

The defect was fixed.

Following fixes were added to Administration pages:

• Tooltips are now positioned above sidebar so they are not cut by sidebar.
• "Show More" link is no longer available when creating group (group is not available yet so no info to show).
• "Delete User" link in user sidebar is not available if required webapis are not available.

In previous version click on "Execute" option did not have effect in computer list (single computer action). This was now redesigned and execute dialog should be opened.

The defect was fixed.

In previous versions some of the translation strings in Administration module were not registered in HTML, and strings were not translated. This was now redesigned, translations were registered and strings should now be translated.

The defect was fixed.