Get Call Quality by CDR Id (no domain in path)

Per-direction call quality for one CDR, from the monthly <YYYYMM>_q table.

netsapiens-nqs polls the local voipmonitor database every 30s and publishes each call leg over the sbus cdr_quality channel; netsapiens-cdr writes one row per (cdr_id, side).

The summary numbers are already on the CDR itself — call-audio-quality-orig-mos and call-audio-quality-term-mos, each the worse of that leg's two RTP directions. This endpoint is the detail behind them: both directions of both legs, with jitter, loss and packet counts.

Direction semantics. voipmonitor's a_* stream is caller → called and b_* is the reverse. So for side=orig, call-quality-direction-a is audio from the originating endpoint; for side=term it is audio to the terminating endpoint. call-quality-caller / -called and their IPs are reported per row so a consumer can verify that rather than trusting the convention.

An empty array is a normal answer, not a 404 — the CDR exists and you may read it, there is simply no quality data for it. That is the case for any call that predates the NQS rollout, for a cluster where the scanner (mos_enabled) is still off, and for the ~30s between a call ending and the scanner's next pass.

The rtcp-* metrics are absent until RTCP capture is enabled in voipmonitor. They are omitted rather than reported as 0, because a zero would claim a measurement that was never taken.

Scoping. With no domain in the path there is nothing for the scope_priv tier walk to land on, so the caller is confined against the CDR's own domain: a Super User passes, a Reseller must hold the territory, and a domain-tier token must be on one of the domains involved in the call.

voipmonitor deep links. Each entry carries voipmonitor-url (the capture's own detail page, by voipmonitor-cdr-id) and voipmonitor-search-url (the same GUI filtered by Call-ID over a ±1 day window, which still works when the id is missing). The host is the leg's own nqs-server, so on a multi-probe cluster each leg links to the box that captured it; NsVoipmonitorUrlBase / NsVoipmonitorUrlPath override that. Both need a voipmonitor login — the login-free share form needs voipmonitor's own cdr.calldate, which is not published onto the quality row yet.

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

{ "call-parent-cdr-id": "1780021234567", "call-leg-side": "orig", "call-leg-call-id": "20260921180355019284-6cc082866aafdc5dee7a480c2d339c76", "call-orig-domain": "abbott_inc", "nqs-server": "nqs1.example.com", "voipmonitor-cdr-id": 48210993, "call-quality-caller": "19168475801", "call-quality-called": "2001", "call-quality-caller-ip": "192.81.236.31", "call-quality-called-ip": "10.20.0.44", "call-audio-quality-mos": 3.9, "call-quality-direction-a": { "from": "19168475801", "to": "2001", "mos": 4.3, "jitter-avg-ms": 2.1, "jitter-max-ms": 11, "loss-percent": 0.012, "packets-received": 38734, "packets-lost": 5 }, "call-quality-direction-b": { "from": "2001", "to": "19168475801", "mos": 3.9, "jitter-avg-ms": 6.8, "jitter-max-ms": 57, "loss-percent": 0.431, "packets-received": 38102, "packets-lost": 165 }, "call-quality-recorded-datetime": "2026-09-21T18:04:12+00:00", "voipmonitor-url": "https://nqs1.example.com/cdr.php?cdrId=48210993", "voipmonitor-search-url": "https://nqs1.example.com/admin.php?cdr_filter=%7Bfcallid%3A%2220260921180355019284-6cc082866aafdc5dee7a480c2d339c76%22%2Cfdatefrom%3A%222026-09-20%22%2Cfdateto%3A%222026-09-22%22%7D" }

Get Call Quality by CDR Id (no domain in path)

Request

Responses