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.

For best results, ensure that computers have

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.

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 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:

Audio and video quality will suffer if these conditions are not met. When sharing their screen, users may see frozen video, low frame-rate, lower image quality. For web audio calls, high lag on the line can be expected. 

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.

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 speed should match the bandwidth requirements above.

As additional traffic on the same network can impact audio/video quality, here are other suggestions you should follow as well:

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:
​
​Signaling
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:

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.