Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forward rtp stream to multiple receivers #116

Open
hupan-seu opened this issue Oct 13, 2020 · 3 comments
Open

Forward rtp stream to multiple receivers #116

hupan-seu opened this issue Oct 13, 2020 · 3 comments
Labels
feature request New Cool Features

Comments

@hupan-seu
Copy link

In some SIP cases, one SIP INVITE will be forked and sent to more than one receivers. After the SIP 183 code, the caller will send early media to the receivers. So the early media need to be copied and sent to multiple receivers by Server, too. Does rtpproxy support this? I saw the Recording/Copy control command(https://github.com/sippy/rtpproxy/wiki/RTPProxy-Command-Protocol), but there is not a clear example about how Copy command use. Could the Copy command make more client join the RTP session and receive the early media RTP data?

@sobomax
Copy link
Member

sobomax commented May 20, 2021

Hi @hupan-seu. Such functionality is not currently supported unfortunately, however we have been receiving requests to make it possible several times over the past few years, so it's definitely on the drawing board. As such, I'll re-categorize your report as a "feature request" and keep it open until it's available.

Thanks for your interest and best regards.

@sobomax sobomax added the feature request New Cool Features label May 20, 2021
@greenbea
Copy link

A typical scenario is sending a doorbell's early media to multiple receivers. I also would like to have this feature.

@sobomax
Copy link
Member

sobomax commented Oct 26, 2023

@hupan-seu @greenbea yes, I was thinking about that as well. The idea there perhaps is to convert record/copy functionality into its own module and hook it into the packet processing using a new packet pipeline mechanism in 3.0. This would allow multiple independent "copy" sessions. I will look into this for 3.1, hopefully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New Cool Features
Projects
None yet
Development

No branches or pull requests

3 participants