Set up your teams to win
To ensure a smooth experience with Jiminny, we provide a set of requirements for the use of our web applications. Prior to using these, your IT team need to make sure that your environment is suitable for VOIP and streaming video. Failing to check and meet these requirements may result in spotty call connections and poor call/video quality.
All of your teams must be using a supported browser.
Computer Requirements
For best results, ensure that computers have
- a minimum of 4GB of RAM
- a headset if using the web audio
- an Intel i5 dual-core processor or equivalent
- 64bit Windows 10 or macOS 10.2+ installed
If you are experiencing audio or video quality issues, CPU spikes from other apps might be responsible. Check the activity monitor or task manager for any applications that are monopolizing the CPU. You may need to close a few browser tabs.
Network Requirements
As with any real-time web conferencing and VoIP system, Jiminny attempts to compensate and adapt to network conditions and glitches. However, you can help ensure the best results by being aware of what can help the most. Audio and video are sensitive to 4 fundamental metrics of network health: available bandwidth, packet loss, latency, and jitter.
Here's what we have at our Jiminny offices for the absolute best quality:
- Bandwidth: for the most optimal quality, we recommend 2.5 Mbps (uplink) and 4.5 Mbps (downlink) available to each device that will be connecting to a meeting or placing calls. Jiminny will adjust call and video quality based on the amount of bandwidth available
- Packet loss: less than 1.0% link loss at the throughput listed above
- Latency: less than 70 ms one-way latency to the Twilio services (hosts are listed below), with a standard deviation less than 30 ms
- Jitter: less than 30 ms
Audio and video quality will suffer if these conditions are not met. When sharing their screen, users may see a frozen video, low frame-rate, lower image quality. For web audio calls, high lag on the line can be expected.
Network Test
To get a true feel for your network quality, please run these tests when a computer is using Wi-Fi and separately using a wired (Ethernet) connection. Each test should be run 3 times remove any anomalies.
First, complete the Twilio network test to verify your available call bandwidth and firewall passes Jiminny traffic. Remember to run the test during a normal calling time where many users are making calls.
First, complete the Twilio network test to verify your available call bandwidth and firewall passes Jiminny traffic. Remember to run the test during a normal calling time where many users are making calls.
You should expect to see the number of simultaneous connections at least 20 above your number of users set up to call.
Next, run a Speedtest to observe your download/upload. These speeds should match the bandwidth requirements above.
General Suggestions
As additional traffic on the same network can impact audio/video quality, here are other suggestions you should follow as well:
- Use a wired (Cat5e or Cat6 Ethernet) connection rather than a Wi-Fi connection. This will provide a more consistent and better quality network connection.
- If your computer doesn't have an Ethernet port, you can use an Ethernet/USB 3.0 adapter (Windows), Ethernet/Thunderbolt adapter (MacOS) or Ethernet/USB-C adapter.
- Check with your IT team to see if higher Quality of Service is possible for calls.
- Don't run any network-intensive applications on the computers, such as internet radio or streaming video, or run significant uploads or downloads that might compete with your CPU. Close unused desktop apps that might also use CPU or RAM.
- Open required network ports in your router, firewall, and antivirus software (see below).
- If your router includes SIP Application Level Gateway (ALG) function or Stateful Packet Inspection (SPI), disable both of these functions.
- Don't use a VPN as it will most likely affect the audio quality. If you do need to use a VPN, you can exclude the voice traffic using the necessary IP addresses. It is important that the voice traffic does not go over a VPN.
WebRTC Info
WebRTC is the technology we use to provide Web Audio and Video. Whilst it's supported natively in most modern browsers, Jiminny only officially supports specific browsers and versions.
WebRTC usually works without a problem using built-in networking technologies (STUN and TURN).
However, environments with very restrictive firewalls may require some setup, the details below have further information for your IT team.
Our WebRTC client connects using the following details:
Signalling
Address: chunderw-gll.twilio.com
Client Port: Any†
Server Port: 443
Protocol: TCP
Presence
Address: matrix.twilio.com
Client Port: Any†
Server Port: 443
Protocol: TCP
Media (SRTP)
Address: Latest list
Client Port: Any†
Server Port 10,000 - 20,000
Protocol: UDP
Signalling
Address: chunderw-gll.twilio.com
Client Port: Any†
Server Port: 443
Protocol: TCP
Presence
Address: matrix.twilio.com
Client Port: Any†
Server Port: 443
Protocol: TCP
Media (SRTP)
Address: Latest list
Client Port: Any†
Server Port 10,000 - 20,000
Protocol: UDP
The client will select any available port from the ephemeral range. On most computers, this means the port range 1,024 to 65,535.
Jiminny Domains:
- *.jiminny.com
- *.amazonaws.com
- chunderw-gll.twilio.com
- chunderw-vpc-gll.twilio.com
- chunderw-vpc-gll-au1.twilio.com
- chunderw-vpc-gll-br1.twilio.com
- chunderw-vpc-gll-de1.twilio.com
- chunderw-vpc-gll-ie1.twilio.com
- chunderw-vpc-gll-jp1.twilio.com
- chunderw-vpc-gll-sg1.twilio.com
- chunderw-vpc-gll-us1.twilio.com
- matrix.twilio.com
- media.twiliocdn.com
- static.intercomcdn.com
- ws.pusherapp.com
These domains should be excluded from inspection/policing on ports 80 and 443 wherever possible. The domains are hosted on Amazon Web Services. You can find Amazon’s current public ranges by checking here. Amazon changes these ranges often, and services could originate from any address in these ranges.