Using Stunner for a webrtc broadcaster #166
Unanswered
nunoribeiro-tw
asked this question in
Q&A
Replies: 1 comment 9 replies
-
My understanding is: you can connect to your broadcast app in k8s via STUNner from device A. Pods inside your cluster can reach the broadcast app too. The problem is, a webbrowser outside on the cluster cannot reach the broadcast app via STUNner. If that's the situation, my first assumption is there is an error in the ICE process at your browser side. I recommend to check your ICE candidates with webrtc-internals ( Last but not least, if it is not a secret, mind to tell a bit about your use case. Thanks! |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to run the following setup
A device A is sending video to a cluster on device B. On this cluster we have a stunner running and a webrtc broadcast that receives the incoming stream from device A and broadcasts it to whomever connects to it afterwards. Currently we have 2 pods in the cluster connecting to the broadcast and consuming the stream without problem. However when we try to add a browser (either on device A or a device C) to consume from the broadcast there are some issues where the stunner doesnt seem to be able to provide a viable path for the ice connection to be established.
Am I missing something in how the stunner is supposed to work? Should this scenario be doable or is there something that makes this undoable?
kubernetes setup:
I am working on a Arm Mac so I am using multipass with kubeadm to run the cluster and portforwarding the service ports for local network access
Beta Was this translation helpful? Give feedback.
All reactions