Below are the minimum workstation and network requirements to interact with the SingleComm platform.
- Pentium, Celeron (no Atom processors) or greater
- Admin console: at least Intel i5
- 16GB or greater
Per station network requirements (ACD)
- 128kbit/s will be used while on a call
- The default G.729 codec requires packet loss far less than 1 percent to avoid audible errors. Ideally, there should be no packet loss for VoIP.
- The ITU G.114 specification recommends less than 80 millisecond (ms) one-way end-to-end delay for high-quality real-time traffic such as voice.
- Jitter buffers (used to compensate for varying delay) further add to the end-to-end delay, and are usually only effective on delay variations less than 100 ms. Jitter must therefore be minimized.
- Chrome 102+ - Fully supported
- IE10 - Partially supported (must support TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 cipher) External script pop/embed only.
- IE11 - Fully supported, however you must not run our page in compatibility mode. External script pop/embed only.
- Chrome M45+ - Fully supported.
- TLS 1.2 is required on all connections. Use the testing tool to verify. A passed test will look like this:
- Any desktop OS, see browser section. (Mobile operating systems are not supported, this includes iOS and Android)
- Any headset will work with SingleComm, however be sure your system allows you change the audio input and output settings when a headset is plugged in.
- Suggestion: Using a 3.5mm jack headset is easier for most operating systems as it automatically switches input settings bypassing the restrictions in the OS (some hardware).
- System should be checked for malware and viruses. Automatic updates should be scheduled for a time when the agent is not taking calls.
- A SingleComm agent interaction (on a call) consumes approximately 128kb/s.
- Internet Connection latency must be lower than 50ms on average. Any spikes above 80ms will cause bad call quality, anything above 100ms will cause the call to disconnect. Any interruption in Internet Connection will cause the call to disconnect.
- An Internet Connection with a guaranteed uptime and throughput is highly recommended although not required. Running a station over a LTE or 3G connection will not work as the latency varies wildly and causes jitter.
- IPv6 must be disabled on the workstation (Windows instructions)
- Wireless connections should be avoided as jitter can be introduced.
- TLS 1.2 is required for all API calls
- We only support modern ciphers, for a list of ciphers we support please check here (use the modern profile)