MCS supports two primary testing modes, both powered by the same engine and satellites.
A user reports an issue. IT sends a test link or triggers a test from the dashboard. Results come back immediately. Ideal for troubleshooting, one-off assessments, and support-initiated diagnostics.
Satellites run scheduled tests between any endpoints: every 5 minutes, every hour, or 24/7. Establishes baselines, catches intermittent issues, validates SLAs, and generates trend data unattended.
Learn moreDeploy branded, customizable test portals that customers or employees access from any browser. The BCS plug-in enables non-native browser testing including VoIP, route, firewall, quality, DHCP, and efficiency tests.
Test to private network egress gateways and ingress application services to isolate whether a problem is on the internal network or the public ISP path. Pinpoint exactly where responsibility lies.
Every MCS deployment follows the same pattern, whether you're testing 10 sites or 10,000.
The central hub. Runs on Linux or Windows Server with its own built-in web server and WAF. Manages all satellites, stores all test data, and serves the dashboard. No Apache or IIS dependency. Java 11+ required.
Distributed test endpoints deployed at every location that matters. Hardware appliances or software agents. Each acts as both I-point (initiator) and E-point (endpoint), enabling any-to-any testing.
End users run tests from Chrome, Edge, Safari, or Firefox with no software to install. The lightweight BCS utility unlocks full VoIP, capacity, route, and firewall testing from the browser.
By design, only the MCS management server stores persistent test result data. NCS satellites (hardware and software) do not store or maintain any persistent data. There is no requirement for persistent files or filesystem access on the host OS.