Routes Asia 2022

Da Nang, Vietnam
• 6 – 8 June 2022

Routes Asia 2022

As the only route development event dedicated to the Asia Pacific region, Routes Asia 2022 will facilitate conversations that will drive recovery and future growth for Asia's route networks.

View Attendees

System Requirements Information

Please view the following system requirements information to ensure you make the most of your digital event meeting experience for Routes Asia.

Firewall requirements

TokBox services require access to specific ports. At a minimum the following requirements must be met:

  • Open TCP port 443
  • Whitelist the following domains:
    *.tokbox.com
    *.opentok.com

Along with the minimum requirements, opening UDP Port 3478 will give you a better experience. UDP is highly recommended over TCP for better quality audio and video. The protocol favors timeliness over reliability which is consistent with the human perceptive preferences; where we can fill in gaps but are sensitive to time-based delays.

This port only accepts inbound traffic after an outbound request is sent. The connection is bidirectional but is always initiated from the corporate network/client so it is not possible for an external entity to send malicious traffic in the opposite direction. For the best possible experience, we recommend opening UDP ports 1025 - 65535.

Whitelist the following HTTPS verification servers for our HTTPS certificate. Not doing so may cause console warnings, but should not affect the session.

  • ocsp.godaddy.com
  • crl.godaddy.com

Proxy requirements

As a general rule, using the latest versions of TokBox and browsers will produce the best results. Most proxies are supported in browsers and mobile apps today. If the only way to access the Internet from your network is through a proxy then it must be a transparent proxy or it must be configured in the browser for HTTPS connections.

WebRTC does not work with proxiesrequiring authentication. Along with these requirements, clients may have the following rules:

  • Chrome
    - although not every option has been tested, recent versions have full support for authentication
    - pre-58 version support NTLM authentication
    - we've found a forwarding proxy setup with Kerberos does notwork

  • Firefox does not support proxiesthat inspect packetsto validate that connections are real TLS connections, because Firefox does not support TURN over TLS

  • Internet Explorer requires the installation of a plugin. Use the latest version of the IE browser when possible.
    - supports basic authentication, and NTLM
    - other authentication algorithms like Kerberos have not been fully tested

  • iOS does not support proxy configurations that use .pac files
Share Page