Allow legacy end-to-end certificates
When enabled, the client accepts end-to-end certificates generated by older ISL Light releases for backward compatibility. Does not affect server/TLS certificates.
Boost specific transport. Value is list of transports separated by ‘,:’.
Select which type of transport has priority when a connection is being established. If the entered transports are unavailable (or don't exist), then the most appropriate transport will be automatically selected.
The following transports are available:
- direct
- wstun-direct
- wstun-proxy
- wsstun-direct
- wsstun-proxy
- wininet-http
- wininet-https
- httpt-direct
- httpt-proxy
- https-direct
- https-proxy
Transports are described in more detail here: Transports
Destination address in form of “host[:port[,port2[,port3]]]”.
Set the server address to be used along with the ports.
Connect timeout
Set the timeout time for establishing a connection.
Force specific transport. Value is list of transports by ‘,:’. Note: make sure transports exists.
Similar to the Boost Specific Transport option, the transport(s) entered will be used or the connection won't be established. Make sure that the transport(s) you entered exist and are available (you can check if they are available with the ISL Connection Tester). Supported transports are described in more detail here: Transports
Use HTTP connections. If set port 80 will be used.
Only try to establish a connection with the transport types that use the HTTP connections.
HTTP Proxy server address in form of “host:[port]”.
Enter the address of the http proxy server you wish to redirect the connection through.
HTTP Proxy pac.
Enter the address where ISL Light Client can find your PAC (Proxy Auto Configuration) file. This enables ISL Light to get the appropriate proxy server address for this connection.
You can either specify a web address e.g.:
http(s)://www.my-site.com/files/proxy.pac
or a local file location on your disk e.g.:
file://C:\Users\Tim\Documents\proxy.pac
HTTP Proxy password
Enter the password for the proxy server you listed.
HTTPS Proxy server address in from of “host:[port]”.
Enter the address of the https proxy server you wish to redirect the connection through.
HTTP Proxy username
Enter the username for the proxy server you listed.
Use HTTPS connections. If set port 443 will be used.
Only try to establish connections with the transport types that use the HTTPS connections.
Direct port to be used
List direct ports to be used for connection (7615 is the preferred port for ISL Light Client).
Use specific server
Force the connection through a specific ISL Online server. A list with all ISL servers and their IP addresses can be found on our list of servers (the list is updated automatically and IP addresses can occasionally change, so check back for any changes). This is mostly a troubleshooting option, as ISL Light Client connects you through the most appropriate server depending on current server loads and the geographical location of both participants.
Try to send packets of this size
If this is set then ISL Light will try to send fixed-size packets.
Connect to ISL Conference proxy using HTTP/HTTPS ports only
Prevent ISL Light Client from trying to establish a connection with transports using a direct connection.
Disable web sockets httpt transports
Prevent ISL Light Client from trying to establish a connection with transports using web sockets.
Don't use wininet connection
Prevent ISL Light Client from trying to establish a connection with transport using Wininet connection.
Number of retries between reconnects
Set how many times the session tries to be re-established once the connection is lost.
Retry intervals between reconnects
Enter interval (in seconds) after which the ISL Light Client will try to reestablish the connection.
Use wininet with html
Use WinINet API to establish a connection with the server via HTML.
Transports
Here is a quick overview of available transports (values) to choose from when you wish to boost or force a certain type of transport in Advanced settings:
- direct
- wstun-direct
- wstun-proxy
- wsstun-direct
- wsstun-proxy
- wininet-http
- wininet-https
- httpt-direct
- httpt-proxy
- https-direct
- https-proxy
If you are thinking about forcing or boosting a certain transport type, it is advisable to check out the Storing Connection Settings in the ISL Connection Tester Manual. After selecting the Find Best Transport option, the connection tester will list all available transports and their speeds, allowing you to choose the best transport still suitable for your needs. A few different types are listed below.
Direct (TCP Connection)
If possible (and not prevented through settings) the ISL Light will try to establish a connection to the server through a direct TCP connection as this offers the best performance and minimizes the latency. The preferred TCP connection port for ISL Online is 7615, as having a specific port for ISL Online is the most convenient -> makes it easy to set up an exception if your computer is behind a proxy/firewall or if you have to follow a certain company policy. If you can't use the port 7615 you can list additional ports for ISL Light to try and establish a direct connection above (default ports are: 7615,443,80). Additional information on port 7615 can be found here: More on port 7615.
Wstun-direct (WebSocket Connection)
Creates a WebSocket connection to the server. WebSocket protocol is a TCP-based protocol that creates a full-duplex communication over a single socket between a client and a server through TCP port 80. This option comes in handy when only standard ports are open (eg. 80,443,...) as it upgrades the http connection to the server to WebSocket connection enabling communication via port 80 (privileged port, <1024).
Wstun-proxy
Similar to the case above, except that the connection is established via a proxy server instead of connecting directly.
Wsstun-direct (Secure WebSocket connection)
Similar to WebSocket connection, but established the WebSocket connection over port 443 and adds an additional level of encryption with TLS/SSL.
Wsstun-proxy
Similar to the case above, except that the connection is established via a proxy server instead of connecting directly.
WinINet-http (WinINet HTTP tunnel)
Tunnels through http port 80.
WinINet-https (WinINet HTTPS tunnel)
Tunnels through https port 443.
Httpt-direct (TCP connection tunneled by http encapsulation)
TCP connection is established by tunneling TCP packets through port 80 by encapsulating them into http packets.
Httpt-proxy
Similar to the case above, except that the connection is established via a proxy server instead of connecting directly.
Https-direct
Tunnels through https port 443.
Https-proxy
Similar to the case above, except that the connection is established via a proxy server instead of connecting directly.