Note: Prior to release of ISL Conference Proxy 4.1.0 the ISL Conference Proxy processes were running as root (administrator). With release of ISL Conference Proxy 4.1.0 the root privileges are needed only for binding ports (confproxy_service) and for the first installation of ISL Conference Proxy. After that the ISL Conference Proxy will run in unprivileged mode (confproxy_server). When ISL Conference Proxy is installed it will also add a new user (islcp) under which the ISL Conference Proxy is running.
Note: Upgrading from old version of ISL Conference proxy will add user islcp to the system and change the permissions of files in ISL Conference Proxy folder.
Note: We detected that change of permissions on Windows can take long time on large number of files (multiple hours for big ICP installations ~30GB). We recommend that you try upgrading first on test server with production database (copy production ISL Conference Proxy folder to new machine and run new ISL Conference Proxy 4.1.0 installer).
NT version 6.0 and above:
- Microsoft Windows Server 2016
- Microsoft Windows 10 (32-bit and 64-bit)
- Microsoft Windows Server 2012 R2
- Microsoft Windows 8.1 (32-bit and 64-bit)
- Microsoft Windows Server 2012
- Microsoft Windows 8 (32-bit and 64-bit)
- Microsoft Windows Server 2008 R2
- Microsoft Windows 7 (32-bit and 64-bit)
- Microsoft Windows Server 2008
- Microsoft Windows Vista (32-bit and 64-bit)
Note: ISL Conference Proxy 4.2.9 was the last version to support Windows Server 2003. With release of ISL Conference Proxy 4.3.0 the support for Windows Server 2003 was dropped.
Note: ISL Conference Proxy 3.4.5 was the last version to support Microsoft Windows 2000 and XP.
Note: Windows Server 2003 is not supported anymore, because it lacks SRW locks API.
Note: Windows XP is not supported anymore, because it lacks 64-bit atomics API.
Note: We support 32-bit versions of OS and ISL Conference Proxy installations, but for new installations we strongly suggest 64-bit OS and ISL Conference Proxy.
Important: Avoid running antivirus clients on your Windows servers!
If you have an antivirus program installed on your Windows server, consider uninstalling it in order to prevent any interference with the ISL Conference Proxy operation and achieve best performance.
Many antivirus programs add hooks for various system calls (file access, network send/receive etc.) which can have an impact on performance or even cause slowdowns/issues during operations.
If you are not able to run your Windows server without an antivirus client you should add the ISL Conference Proxy directory (C:\Program Files\ISL Conference Proxy) to the white list and disable all real-time scanning for that directory and all subdirectories within it.
- Linux Kernel 2.6.23 or newer and glibc 2.3.2 or newer
Note: ISL Conference Proxy 4.4.1816.71 was the last version to support Linux Kernel 2.6 and CentOS 5.
Note: ISL Conference Proxy 3.5.0 was the last version to support Linux Kernel 2.4.
- Minimum: INTEL or AMD 1.4 GHz (x86 processor or x64 processor)
- Recommended: Multi-core CPUs, x64 processor, 3 GHz or faster
- Minimum: 2 GB RAM
- Recommended: 4 GB RAM (standard) or 8 GB RAM (Corporate Server License)
Available disk space
- Minimum: 10 GB
- Recommended: 20 GB (standard) or 100 GB (Corporate Server License)
We also support virtualization environments (such as Hyper-V, Xen, VMware) with one of the supported operating systems installed.
- Minimum: 256 Kbps DSL
- Recommended: 1 Mbps + 200 Kbps per active remote desktop session + 1 Mbps per active web conferencing sessions
Please check ISL Light, ISL AlwaysOn, ISL Groop and ISL Pronto manuals for exact bandwidth usage of specific features (like video streaming, desktop sharing, etc.).
- Public IP address with direct access to ports 7615, 80, 443
Local Area Network (LAN)
If you plan to use ISL Conference Proxy within your LAN (intranet) only, there is no need for a public IP address. You only need a private address in the ranges for private networks (as specified in RFC 1918).
ISL Conference Proxy 4.0.0 and later includes support for reverse proxy. If you plan to position the server behind an existing enterprise network security device such as F5 or a similar reverse proxy, please refer to the Reverse Proxy Manual.
IPv6 for the loopback interface
With ISL Conference Proxy 4.4.1721.9 version, it is required to have IPv6 enabled for the loopback interface, since modules that use module SDK (such as Core Login) bind address ::1 by default, port range from 7640 to 7660. These ports are used for internal communication between ISL Conference Proxy and those modules.
If you do not have IPv6 enabled for the loopback interface, ISL Conference Proxy 4.4.1721.9 startup will fail.
Please consult your server's operating system documentation on how to check the status of IPv6 for the loopback interface and how to enable it if it is currently disabled.
Starting with ISL Conference Proxy 4.4.1721.26, this behaviour has been altered, ISL Conference Proxy will now try IPv4 127.0.0.1 address as well, if binding ::1 address fails.