sip-exporter is an open-source Linux eBPF sensor that converts observed SIP signaling and correlated RTP traffic into Prometheus metrics and Grafana dashboards. It captures IPv4 SIP over UDP and exposes traffic, session, RFC 6076 performance, voice-quality, RTP, RTCP, fraud, and diagnostic measures at `/metrics`. RTP analysis includes jitter, packet loss, packet-delay variation, and E-model MOS; RTCP statistics include loss, jitter, and round-trip time correlated by SSRC. Documented fraud indicators include registration scans, INVITE bursts, account takeover after a registration country change, and False Answer Supervision. The repository includes a Grafana dashboard with 11 sections, Prometheus alert-rule examples, and Alertmanager examples for Slack, PagerDuty, and email. Metrics are documented for Prometheus, VictoriaMetrics, Grafana Cloud, and compatible scrapers. Deployment is available as a single container, but it requires privileged access and host networking. The sensor must see both SIP signaling and the related RTP/RTCP path on the same call path. It does not store packets or audio, though userspace RTP snapshots may include a small payload prefix. Anonymous telemetry is enabled by default and can be disabled with SIP_EXPORTER_TELEMETRY set to false.

Who it is for

sip-exporter suits Linux operators who can place a sensor where it sees both SIP signaling and related RTP/RTCP traffic, and who use Prometheus-compatible metrics or Grafana. Its protocol and network restrictions make it a narrower fit for monitoring environments.

What is good

Reports RTP jitter, packet loss, and E-model MOS.
Includes a Grafana dashboard and alert-rule examples.
Metrics work with Prometheus-compatible scrapers.
Does not store packets or audio.
Anonymous telemetry can be opted out of.

What to know first

SIP over TCP or TLS is not captured.
IPv6 and fragmented UDP are unsupported.
Deployment requires privileged access and host networking.
The sensor must see signaling and media on the same path.

Verdict

sip-exporter offers detailed SIP and voice-quality monitoring with Grafana and Prometheus-oriented outputs. Its IPv4/UDP capture limits and privileged, host-networked deployment requirements should be checked against the network environment first.

sip-exporter plans and pricing

All plans

AGPL-3.0 open-source Free Free for personal and educational use; free for commercial use with conditions under AGPL-3.0 github.com · 5 Oct 2026

Compared on VoIP monitoring software

Free plan: Yes
MOS scoring: Yes
Jitter tracking: Yes
Packet-loss tracking: Yes

Best sip-exporter alternatives

See all 19

Obkio Lesson 18.1 Dotcom-Monitor Lesson 27.2 HOMER Lesson 37.1 CallMeter Lesson 46.9 ServicePilot VoIP Monitoring Lesson 56.9 VoIP Spear Lesson 66.8

The record

Purpose

sip-exporter is an open-source eBPF sensor that turns SIP signaling and correlated RTP traffic observed on a Linux host into Prometheus metrics and Grafana dashboards.

Capture method

An eBPF socket filter selects IPv4 SIP packets over UDP for userspace processing; SIP over TCP or TLS is not captured.

SIP and RTP metrics

The exporter reports SIP traffic and session metrics, RFC 6076 performance metrics, and RTP quality metrics including packet loss, jitter, and MOS.

RTCP support

It reports RTCP receiver and sender statistics, including loss, jitter, and round-trip time, correlated by SSRC.

Fraud signals

Documented fraud signals include registration scans, INVITE bursts, account takeover after a registration country change, and False Answer Supervision.

Grafana dashboard

The repository includes a Grafana dashboard with 11 sections and documented Prometheus alert-rule examples.

Integrations

The Prometheus-format metrics are documented as compatible with Prometheus, VictoriaMetrics, Grafana Cloud, and other Prometheus-compatible scrapers.

Deployment

The project provides a single-container deployment and says the container must run privileged with host networking to access eBPF and the network interface.

Supported traffic

Capture support is IPv4/UDP SIP and RTP/RTCP; SIP over TCP/TLS, IPv6 traffic, and fragmented UDP are listed as unsupported.

Network placement

For full metrics, the sensor must run on a host that sees both SIP signaling and RTP media on the same call path.

Data handling

The project says it does not store packets or audio; its RTP processing parses the fixed RTP header and does not inspect or persist audio.

Telemetry

Anonymous usage telemetry is enabled by default and can be opted out of by setting SIP_EXPORTER_TELEMETRY to false.

License

The project is licensed under AGPL-3.0 and says modified network-accessible versions must offer users the corresponding source under the license terms.

Support

The project directs users to GitHub Issues for support, bug reports, and feature requests, and to its security policy for private vulnerability reports.

Price from

Free