SIPCAPTURE Homer

SIPCAPTURE Homer is an open-source, self-hosted telecom observability server that captures, stores, and queries SIP signaling and media-quality data for VoIP…

  • Databases
  • Network Services
SIPCAPTURE Homer is an open-source, self-hosted telecom observability server that captures, stores, and queries SIP signaling and media-quality data for VoIP homelabs. It runs as an all-in-one HEP (Homer Enterprise Protocol) capture and API monolith: writer, reader, coordinator, compactor, and query engine, written in Go and powered by DuckDB with a columnar data-lake design for X64 and ARM64 on Linux and macOS. Built for self-hosters and PBX operators who want to monitor, replay, and analyze calls without vendor lock-in, it stays backwards compatible with all HEPv3 agents and adds optional VQRTCP QoS collection and SIPREC signaling recording.

Platform availability

Available on 2 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

68/100 Good

Maintained
100last commit 1 day ago
Popular
662,035 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
1016 GB minimum RAM
Security check
82no serious findings, CI, tests, OpenSSF Scorecard 5.6/10

Availability: platform listings confirmed today

GitHub stars
2,035
Open issues
0
Last commit
2026-11-20
Latest release
11.0.367
Activity
rising

Checked today - source: GitHub (sipcapture/homer)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 8 CPU core(s), 100 GB disk.

Checked today - source: Docker Hub image tags and published docs

First-install notes

  • Set where Homer receives calls Point heplify’s transport setting at your Homer/HEP server and port, for example 127.0.0.1:9060 if Homer is on the same machine. If the host or port is wrong, heplify may run but Homer will not receive any captured SIP or RTCP call data. source
  • Windows needs Npcap and admin On Windows, install Npcap (the network packet-capture helper) first, then run heplify from an Administrator command prompt with your config file. Without Npcap and admin permission, Windows will not let heplify capture network traffic, so no calls will appear in Homer. source
  • Use heplify.json for settings Start heplify with -config heplify.json and treat that file as your main settings list. If you typo the HEP server address, port, or capture options there, heplify may still start but send data to the wrong place or miss the traffic you expect. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should heplify point to a local Homer instance?

Set heplify's transport setting to Homer's HEP host and port, for example 127.0.0.1:9060 if Homer is on the same machine. If the host or port is wrong, heplify may run but Homer will not receive captured SIP or RTCP call data.

Can Homer be put behind a reverse proxy for HTTPS?

Yes, self-hosters often run Homer in Docker and put a reverse proxy in front for HTTPS.

Will existing HEPv3 agents work with Homer 11?

Homer is backwards compatible with all HEPv3 agents. Its ingest accepts HEP packets over UDP, TCP, TLS, HTTP, or HTTPS.

Answers sourced from github.com, github.com, opentools.dev

Community

No community discussions collected yet.