How to Integrate mediamtx with stunner for WebRTC ICE/TURN?

[CheSauRie]

Hello everyone,

I'm currently working on deploying both mediamtx and STUNner in a Kubernetes environment. While I have managed to deploy each component separately, I'm facing challenges in configuring them to work together—particularly for proper ICE/TURN functionality with WebRTC clients.

Has anyone come across a tutorial or guide that provides a step-by-step approach to integrating mediamtx with STUNner on Kubernetes? I’m looking for details on:

• Deployment Practices: Best practices for deploying both mediamtx and STUNner on a Kubernetes cluster.

• Configuration Details: How to correctly configure mediamtx to communicate with STUNner (e.g., setting up ICE servers, handling NAT traversal issues).

• Troubleshooting: Common pitfalls or issues encountered during integration and any tips on resolving them.

Any pointers to existing resources, examples, or personal experiences would be greatly appreciated. Thanks in advance for your help!

Best regards,

[CheSauRie]

I use chatgpt for this discussion, actually I want a tutorial on how to combine mediamtx with stunner and deploy on kubernetes

[levaitamas]

Hi @CheSauRie,
We do not have an official tutorial per se. @CodeDing made a great demo on setting up MediaMTX w/ STUNner without Kubernetes: #82 As for the K8s installation, I would recommend to check the docs: https://docs.l7mp.io/en/stable/ A good start is the installation guide, followed by experimenting with the examples.

[levaitamas]

I hope so, but it is not on our agenda.

[dbason]

Hey @CheSauRie, we currently have MediaMTX running with Stunner, and I'm also the one who authored the commit in MediaMTX to allow it to operate in asynchronous ICE mode with Stunner. Were there any specific issues you were having? It should be as simple as configuring the external IP address of Stunner in Mediamtx:

webrtcICEServers2:
- url: turn:stunner-ip:port
  username: user
  password: password
  clientOnly: true

Or if you wanted to use ephemeral auth

webrtcICEServers2:
- url: turn:host:port
  username: AUTH_SECRET
  password: shared_secret
  clientOnly: true

[CheSauRie]

Thank you, everyone. I’ve now configured MediaMTX with Stunner. Previously—when running MediaMTX with networkhost: true (without Stunner)—I could support up to 300 clients with no lag. But as soon as I enable Stunner, the client count tops out at just over 100. I’d appreciate any suggestions or help!

[dbason]

You should be able to scale out the stunner dataplane, particularly if you're using the clientOnly flag.

[CheSauRie]

Currently in my k8s cluster I have Istio as gateway for HTTP requests, how can I use Istio and Stunner in parallel without adding another public IP