rtsp-streaming-server icon indicating copy to clipboard operation
rtsp-streaming-server copied to clipboard

Add support for TCP interleaved clients

Open slyoldfox opened this issue 7 months ago • 2 comments

Just polling how you feel about this PR. After my last commit, looked into TCP support and it seems like adding support for TCP/interleaved clients was reasonably straightforward.

This does depend on an open PR https://github.com/watson/rtsp-stream/pull/7 which filters interleaved packets from the rtsp-stream Decoder. A TEARDOWN request would error if the interleaved packets weren't filtered out for the Decoder.

The commit which fixes this (https://github.com/watson/rtsp-stream/pull/7/commits/7971c9942cc7f5b04f285d8125c495a0ba27e397) has been around since 2018, I just kicked off the PR to see if @watson merges it.

I have created a forked version 1.0.1 which incorporates that commit: https://www.npmjs.com/package/@slyoldfox/rtsp-stream

This also explain the need for the overrides inside the package.json inside this PR.

The whole thing has been forked in a 2.1.0-interleaved version at https://www.npmjs.com/package/@slyoldfox/rtsp-streaming-server?activeTab=versions in case the PRs don't come through.

Been testing this for a little while for my project (https://github.com/slyoldfox/c300x-controller) and it seems like interleaving successfully works through a NAT port-forwarding setup for my doorbell.

slyoldfox avatar Jul 06 '24 20:07 slyoldfox