Feature Request: RFC 7198 RTP Stream Duplication for Broadcast Resilience #3707
broadcasty4201
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Request for RFC 7198 (Duplicating RTP Streams) support in baresip, to enable resilient SIP audio connections to broadcast infrastructure that already supports this standard.
We are using baresip as a SIP contribution codec connecting to professional broadcast infrastructure — specifically Tieline Gateway units used for radio outside broadcasts and studio contributions. These Tieline Gateways are fully RFC 7198 compliant and advertise dual stream support in their SDP.
For broadcast contribution use, packet loss resilience without increased latency is critical. RFC 7198 achieves this by sending duplicate RTP streams. The receiver reconstructs from whichever copy arrives intact. This is now standard in the broadcast SIP codec market (Vortex CallMe, Tieline, AETA all support it), but we have no way to take advantage of it from baresip.
Is there an existing or planned mechanism to hook the RTP send path from a module, or would this require changes to
stream.c?Is there any existing work on RFC 7198 or related stream duplication in any branch?
Would a contribution implementing this be welcome as a pull request?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions