
				Facilities			Products


	Convoq ASAP

Firewall Friendliness

« Browser Compatibility | Main | Setup - Installation »

To properly communicate across firewalls ASAP needs ports 5051, 1935, 443, and 80 for outbound traffic to any server in the convoq.com domain or - if IP addresses are required - the address block 38.113.16.0/24 (38.113.16.xxx).

Convoq also provides a very handy test page in which you can see if such ports in your firewall are accessible. Go to the Port Test page and test yourself.

If you receive a "Connection Error Encountered" message, which prevents you from connecting to an ASAP meeting you can open port 443 (HTTPS) and 80 (HTTP) to *.convoq.com (38.113.16.xxx), although this will result in decreased performance.

When ports 5051 and 1935 are not available, ASAP attempts to tunnel using common port 80. Tunneling on port 80 is designed to enable users to participate in meetings when dedicated ports are not available.

Tunneling does cause meeting performance to decrease, but allows you to work around the port restriction.

If tunneling through port 80 does not work, try turning off HTTP 1.1 in the Internet Explorer Advanced options (Tools > Internet Options > Advanced > HTTP 1.1 Settings).

If the above conditions are met ASAP has no problem in powering live meetings where multiple users are behind a corporate firewall or router NAT.

As mentioned above, Convoq ASAP uses HTTP tunneling only when necessary, sidestepping completely any possible problem relating to firewalls or router NATs.

Cons:

HTTP tunneling adds a significant amount of delay to all communication and collaboration features. This is particularly noticeable in the video and audio performance in which there can be between 2 to 6 seconds of delay:

"Estimated ASAP Delays Using HTTP Tunneling and/or Meeting Encryption
The performance implications of encrypted meetings and use of HTTP tunneling when using a broadband connection are very similar. The following list indicates the incremental delays when using either HTTP tunneling or meeting encryption:

Meeting Console: 2 to 4 seconds longer to update

Text chat: 2 to 4 seconds

Video: 3 to 6 seconds

Audio: 2 to 4 seconds (intermittent). Expect more audio dropouts, especially for multiparty audio transmissions.

Screensharing: 5 to 10 seconds additional delay.

Presentations: 5 to 10 seconds, especially when first loading a presentation

Annotations: 2 to 4 seconds"