What is SQmediator?
SQmediator is a multi-user performance management system that supports passive quality monitoring and active testing for a variety of IP network services and applications including Voice over IP, IP videoconferencing, web, email, DHCP and DNS. In passive mode, it collects, analyzes and displays performance metrics sent by IP phones, probes and other media endpoints. In active mode, it uses distributed software or hardware test agents to generate simulated VoIP and video conferencing calls and to test network services and applications.
Do I need special hardware to run SQmediator?
No. SQmediator software runs on standard off-the-shelf Linux server hardware and isn't tied to any specific vendor platform. SQmediator's user interface can be accessed with a standard web browser.
What's included with SQmediator?
SQmediator has three main components: Reporter, Collector and Controller. They are software applications that can be deployed on separate servers or together on a single server, depending on the size and scope of your network.
What is the Reporter?
The SQmediator Reporter provides the web user interface, and optionally the web services API, for the SQmediator system. Its secure UI supports multiple concurrent users, and offers an extensive set of features including configurable per-metric service thresholds, data aggregation by customer and location, and real-time alerts via the dashboard, email and SNMP traps.
What is the Collector?
The SQmediator Collector collects quality reports sent by passive probes and RFC6035-capable endpoints including IP phones and gateways, and stores the data in the system database where it can be accessed by the Reporter. If multiple reports are received for the same call - for example, when both endpoints send an RFC6035 report, or the call is also monitored by a probe - the Collector automatically correlates them into a unified call record.
What is the Controller?
The Controller is a management application used to authenticate and configure active test agents, run tests, and collect and store test results in the system database. It runs invisibly as a background component, while the Reporter provides the user interface for configuring and running tests.