-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Change outbound UDP stream to accepting inbound UDP connections #24
Comments
Can you be more specific about what you're trying to do? What do you mean
by connecting to a UDP server?
There are four modes of operation:
1. UDP input to SRT output (Caller)
2. UDP input to SRT output (Listener)
3. SRT input (Listener) to UDP output
4. SRT input (Caller) to UDP output
where UDP can either be unicast or multicast
…On Wed, Feb 5, 2025 at 12:30 PM ahbosch ***@***.***> wrote:
Is there a way to change the outbound UDP stream, to accept inbound UDP
connections so clients can connect to a UDP server?
—
Reply to this email directly, view it on GitHub
<#24>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ3YIOBG3RIOYIZXKLLPWT2OJKE3AVCNFSM6AAAAABWRXTBGKVHI2DSMVQWIX3LMV43ASLTON2WKOZSHAZTGNRXGMYDKNA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sure, Currently, it's set up as SRT input (Listener) to UDP inbound on port 10001 (as an example) Where the UDP client can connect to the OpenSRTHub on port 10001. Hope this makes sense. (Or if there is another solution that can take an inbound UDP connection and make it available to multiple UDP clients that would ) |
Hmmm.. almost sounds like you are looking for an RTSP type relay server
that can serve multiple clients via UDP?
…On Wed, Feb 5, 2025 at 1:08 PM ahbosch ***@***.***> wrote:
Sure,
Currently, it's set up as SRT input (Listener) to UDP output, but I have
a different use case and need something that could be:
SRT input (Listener) to UDP inbound on port 10001 (as an example)
Where the UDP client can connect to the OpenSRTHub on port 10001.
Hope this makes sense.
(Or if there is another solution that can take an inbound UDP connection
and make it available to multiple UDP clients that would )
I looked at the multicast, but that's also an outbound connection.
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ3YIOI4F6WVAZOO7J74PD2OJOTFAVCNFSM6AAAAABWRXTBGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZXG44TQNRZGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
That sounds about right, didn't know the possibility of the OpenSRTHub to be able to do it, maybe it can as a one-stop shop. Thinking of writing a Python app to run alongside it to do that, but not sure how functional that would be. |
It's not really a one stop shop unfortunately. It was really only intended
as a lightweight SRT server/client with a management layer and user
interface on top. You may have better luck with something like this:
https://github.com/bluenviron/mediamtx
…On Wed, Feb 5, 2025 at 1:51 PM ahbosch ***@***.***> wrote:
That sounds about right, didn't know the possibility of the OpenSRTHub to
be able to do it, maybe it can as a one-stop shop. Thinking of writing a
Python app to run alongside it to do that, but not sure how functional that
would be.
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ3YIPGVSUC3CARGFEQN7L2OJTV5AVCNFSM6AAAAABWRXTBGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZXHA4DSMBXGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Is there a way to change the outbound UDP stream, to accept inbound UDP connections so clients can connect to a UDP server?
The text was updated successfully, but these errors were encountered: