mirror of https://github.com/OpenVidu/openvidu.git
adfd19c8fa
The 14 srtIngress* tests had been commented out with three notes: SRT pull does not work when the ingress runs in a container, AAC fails alongside video, and a single OPUS stream fails. All 14 pass now. The first note was the networking. The listener ran on the bridge network testcontainers uses and the test handed the ingress a container IP that the deployment's own network cannot reach. Moving it to the host network is not enough on its own: host.docker.internal resolves to the gateway of Docker's default bridge, while the ingress sits on another network, so a listener bound to 0.0.0.0 answers the handshake from whatever source address routing picks for that network, and libsrt drops a reply that comes from an address it never contacted. TCP is immune, which is why RTSP never had the problem. The listener now binds the very address the ingress calls, taken from the Docker API, on a free UDP port. The second note does not reproduce: H264 + AAC and MPEG-4 + AAC pass unchanged, so it was a casualty of the networking problem. The third was a real product bug, in the ingress rather than here, and is fixed there. Both helpers now run mediamtx with RTSP over TCP and every other server off. On the host network its defaults collide with the deployment (1935 is the ingress RTMP port) or with another mediamtx (8000/8001 for RTP, and the MoQ server on 8892, which 1.21 extends to 8893), and the container exits. mediamtx moves to 1.21.0 in the same step. The RTSP AC3 test stays disabled, with the cause it actually has: ffmpeg's RTP muxer cannot payload AC-3, so the publisher never produces the stream. Verified against a local deployment: the 44 tests that use the mediamtx image, 30 RTSP and 14 SRT, all pass except that disabled one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .github | ||
| openvidu-components-angular | ||
| openvidu-deployment | ||
| openvidu-livekit@f2e5cda2b3 | ||
| openvidu-test-browsers | ||
| openvidu-test-e2e | ||
| openvidu-test-integration | ||
| openvidu-testapp | ||
| .gitignore | ||
| .gitmodules | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| NOTICE | ||
| README.md | ||
README.md
openvidu
Visit openvidu.io
What is OpenVidu?
OpenVidu is a platform for building real-time video conferencing applications. It's built on top of LiveKit and mediasoup, and is developed by a team with over a decade of experience building WebRTC systems.
- Self-hosted: deploy it on your own infrastructure (AWS, GCP, Azure, Oracle, DigitalOcean, on-premises) or use it as a managed service.
- API-compatible with LiveKit: use any LiveKit client/server SDK unchanged.
- OpenVidu Meet: a fully-featured video conferencing app that ships on top of this platform, ready to use or embed.
- Advanced media features: recording, RTMP/streaming egress, AI agents (transcription, translation), virtual backgrounds, and more.
Getting started
- 📖 Documentation
- 🚀 Try it locally
- 💻 Tutorials
- 🎥 OpenVidu Meet — the reference app
Community Forum
Visit OpenVidu Community Forum
Contributors
This project exists thanks to all the people who contribute.
Backers
Thank you to all our backers! 🙏 [Become a backer]
Acknowledgments
OpenVidu has been supported under project "CPP2021-008720 NewGenVidu: An elastic, user-friendly and privacy-friendly videoconferencing platform", funded by MCIN/AEI/10.13039/501100011033 and by the European Union-NextGenerationEU/PRTR.
Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
