Reading the connect.adversus.io result
Run the test on the affected agent's computer, on the same network and with the same headset they use for calls.
Overall diagnostic score
| Score | Meaning | Next |
|---|
| 90–100 | The network is fine | Look at device, browser and settings |
| 50–89 | Borderline — problems likely at busy times or under load | Check the lowest sub-test values, then fix the network |
| 0–49 | The network is the problem | Fix the network |
Top of the page
- Local IP (e.g.
192.168.x.x) — the computer's private address inside your network. It's not your public IP.
- Microphone device (e.g.
Default - Jabra Link 390) — check it's the headset the agent actually uses.
Sub-tests
Each should end with Done. A test that hangs or errors counts as failed.
| Test | Good | If it's bad |
|---|
Echo call – PCMA
Test call with the default codec (A-law/U-law = PCMA) | Latency < 100 ms · jitter < 20 ms · packet loss < 1% · MOS ≥ 4.0 | Fix the network |
Echo call – Opus
Same test call with OPUS | Same limits | PCMA bad, Opus good → switch the codec to OPUS |
Throughput – UDP (Sound)
Audio bandwidth, shown as how many agents can call at once | "Agents" figure above the number of agents on that connection — also at its lowest value | Bandwidth bottleneck → wired, fewer devices, check the subscription |
Throughput – TCP (Data)
Bandwidth for the web app | — | Slow app loading; rarely audio |
Firewall
Adversus services reachable | Done | Send the port list; check Windows profile and SIP ALG |
Microphone
Accessible microphone | Done, correct device | Microphone step in Path B |
Read the worst value, not just the headline. The small values under each measurement appear to be the spread across the test (lowest / average / highest). A big gap means an unstable connection — e.g. UDP speed 14.23 Mb/s, but a low of 2.07 Mb/s.
Example — a healthy result
| PCMA | Opus |
|---|
| Latency | 4.40 ms | 5.59 ms |
| Jitter | 3.50 ms | 2.56 ms |
| Packet loss | 0.00% | 0.00% |
| MOS | 4.22 | 4.30 (lowest 3.87) |
| UDP capacity | 114 agents (lowest 17) | 228 agents (lowest 33) |
Verdict: the network is fine — look at device, browser and settings.
Network ports & IP ranges
Give this to your IT department or internet provider.
| Purpose | Port(s) | Protocol |
|---|
| Media server (RTP/RTCP) | 10000–60000 | UDP |
| WebRTC (RTC/STUN) | 10000–60000, 443, 8089 | UDP + TCP |
| Web (HTTPS) | 443 | TCP/UDP |
| Journeys/Webhooks (outgoing) | 443 | TCP/UDP |
IP ranges
62.69.152.0/28 — media / WebRTC / web (worldwide)75.2.73.2, 13.248.176.31 — WebRTC46.30.124.219 — outgoing webhooks
Watch for SIP ALG, DPI, SPI, IDS/IPS, web proxies and VPNs on the gateway. Windows: the network profile must be Private, not Public.
Browser & device support
- Chrome / Firefox: supported.
- Safari: not recommended — missing functionality, known problems.
- Brave: blocks WebRTC audio unless Shields are disabled for the site.
- Mobile devices: not supported — "something went wrong" error.
- AirPods / Bluetooth headsets: known audio issues — use wired headsets.