← Back to home
Comparison · Meetings

HOMER vs rtpengine

A side-by-side editorial comparison of HOMER and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.

HOMER vs rtpengine: at a glance

FeatureHOMERrtpengine
SectorMeetingsMeetings
Velocity score5.05.0
Sparks · 30d00
Top themesvoip monitoring, security, sip-i, duckdbwebrtc, media-proxy, srtp, backports
Last editorial update1d ago9d ago
WebsiteVisit →Visit →

What is HOMER?

HOMER 11 closes an open mTLS listener and stops dropping ISUP from SIP-I calls.

HOMER's 11.0 pre-releases keep pairing security fixes with SIP-I decoding. 11.0.384 makes HEP and HTTPS ingest with mutual TLS and no CA refuse to start, where before they accepted any client, and runs all-in-one node reads in the DuckDB sandbox. It also stops the Decode window from dropping the ISUP part of multipart SIP-I INVITEs. 11.0.382 and 11.0.381 had already required tokens for the live SIP stream and admin rights for alert changes.

Read the full HOMER trajectory →

What is rtpengine?

rtpengine backports a DTMF header-extension fix to mr26.0 and mr26.3.

Sipwise's rtpengine shipped a batch of SRTP, ICE, Opus and Redis fixes to four branches on November 2. Two days later, mr26.0.1.28 and mr26.3.1.3 carry a single fix that leaves room for the RTP header extension when adding DTMF packets.

Read the full rtpengine trajectory →

HOMER vs rtpengine: editorial side-by-side

H
HOMER
MEETINGS
5.0

HOMER 11 closes an open mTLS listener and stops dropping ISUP from SIP-I calls.

◆ Current state

HOMER's 11.0 pre-releases keep pairing security fixes with SIP-I decoding. 11.0.384 makes HEP and HTTPS ingest with mutual TLS and no CA refuse to start, where before they accepted any client, and runs all-in-one node reads in the DuckDB sandbox. It also stops the Decode window from dropping the ISUP part of multipart SIP-I INVITEs. 11.0.382 and 11.0.381 had already required tokens for the live SIP stream and admin rights for alert changes.

◆ Where it's heading

Three releases in a week closed access gaps, which suggests a security review of the 11.0 line before a stable release. Alongside it, the work on SIP-I and ISUP decoding points at carrier and telco users who bridge SS7 and SIP.

◆ Prediction

Expect more fail-closed defaults and sandboxing in the next 11.0 builds, and possibly a published advisory for the mTLS issue.

R
rtpengine
MEETINGS
5.0

rtpengine backports a DTMF header-extension fix to mr26.0 and mr26.3.

◆ Current state

Sipwise's rtpengine shipped a batch of SRTP, ICE, Opus and Redis fixes to four branches on November 2. Two days later, mr26.0.1.28 and mr26.3.1.3 carry a single fix that leaves room for the RTP header extension when adding DTMF packets.

◆ Where it's heading

The project ships fixes in synchronized batches across every supported branch and reserves new behaviour for the newest line. Recent work clusters on encryption correctness, ICE negotiation edge cases and Redis-backed call recovery.

◆ Prediction

Follow-up builds on these branches within days are likely, as after the October 16 batch, along with further mr26.3 builds.

Alternatives to HOMER and rtpengine

Other Meetings products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either HOMER or rtpengine.

See all HOMER alternatives → · See all rtpengine alternatives →

Recent activity from HOMER and rtpengine

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoHOMERHOMER 11.0.384 keeps SIP-I ISUP parts and fails closed on bad mTLS
  2. 5d agoHOMERHOMER 11.0.382 requires a token for the live SIP stream
  3. 6d agoHOMERHOMER 11.0.381 restricts subscription and alert changes to admins
  4. 8d agoHOMERHOMER 11.0.378 adds B2BUA legs to Session Info and IPv6 search
  5. 8d agoHOMERHOMER 11.0.377 brings back tshark decoding of captured messages
  6. 8d agoHOMERHOMER 11.0.376 keeps SIP-I bodies intact and decodes ITU-T ISUP
  7. 9d agortpenginemr26.0.1.28: DTMF packet header-extension fix
  8. 9d agortpenginemr26.3.1.3: DTMF packet header-extension fix
  9. 11d agortpenginemr26.0.1.27: SRTP, ICE and Redis restore fixes backported
  10. 11d agortpenginemr13.5.1.31 fixes a WebSocket disconnect deadlock
  11. 11d agortpenginemr26.2.1.6: SRTP, ICE and Redis restore fixes backported
  12. 11d agortpenginemr26.3.1.2: SRTP, ICE, jitter buffer and kernel fixes

Frequently asked questions

What is the difference between HOMER and rtpengine?

They serve adjacent needs but don't currently overlap on shipped themes. HOMER and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is HOMER better than rtpengine?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.

What are the best alternatives to HOMER?

Top HOMER alternatives in Meetings are ranked by recent ship velocity. Browse the "HOMER alternatives" section above for the current picks, or visit /alternatives/homer-voip for the full list with editorial commentary on each.

What are the best alternatives to rtpengine?

Top rtpengine alternatives in Meetings are ranked by recent ship velocity. Browse the "rtpengine alternatives" section above for the current picks, or visit /alternatives/rtpengine for the full list with editorial commentary on each.