r/WebRTC • u/enthusedclues • 11h ago
r/WebRTC • u/Ok-Willingness2266 • 3d ago
How we ingest NDI sources directly and play them over WebRTC (no RTMP/SRT encoder in between)
I work on the team at Ant Media, and we just published a walkthrough on getting an NDI source from a LAN into a browser over WebRTC without converting it to RTMP or SRT first.
The idea is to skip the intermediate encoder or app that most NDI-to-web setups need. The server discovers NDI sources over mDNS, ingests the feed directly, and you can then play it back as WebRTC (or HLS/LL-HLS if you need broader compatibility).
The guide covers:
Enabling mDNS discovery (avahi-daemon on Ubuntu, UDP 5353)
Sending NDI from an Android camera app, NDI Tools Test Patterns, OBS (DistroAV plugin), or an NDI-enabled PTZ camera or switcher
Adding the NDI source as a live stream and playing it with WebRTC
Options for NDI over a WAN (Discovery Server, NDI Bridge, VPN), since default mDNS discovery doesn’t cross networks
A short troubleshooting checklist for missing sources, broadcasting problems, and WebRTC playback failures
Full guide: https://antmedia.io/ndi-to-webrtc/
Note that NDI ingest is an Enterprise Edition feature, and there’s a 14-day trial if you want to test it.
I’d like to hear from anyone running NDI in production. How are you getting NDI feeds to web viewers today, and what has been the biggest pain point: discovery, WAN, or latency?
r/WebRTC • u/AdFew177 • 5d ago
After 10 years of backend VoIP development, I finally completed the frontend with AI assistance — Meet AiPBX (Open-Source Asterisk 22 UC Platform + Live Demo)
Hi everyone, I’ve been developing the core telecom logic and backend architecture behind AiPBX for over 10 years. As a VoIP systems engineer, my bottleneck was always turning a decade of dialplan and infrastructure work into a clean, modern web interface. With the help of AI tools, I finally built and polished the entire frontend portal, and I’m releasing the complete platform as 100% free, open-source software (MIT License) with zero paywalls or per-seat limits.
⚡ Cutting-Edge Architecture & Capabilities
Single-Port 443 ALPN Multiplexing: Browser WebRTC softphone (DTLS-SRTP), Go-powered real-time team chat, SIP over TLS, and HTTPS are all multiplexed over port 443 — zero fragile high ports exposed through the firewall.
Native Mobile Mobility & Passwordless Auth: Android (Kotlin) and iOS (SwiftUI + CallKit) apps featuring native Apple PushKit (APNs) and Google FCM wake-up notifications, paired with Passkeys (WebAuthn / FIDO2) and QR provisioning.
On-Premise & Cloud AI Stack (x86_64 & ARM64): Run local Whisper STT, Piper TTS, and Ollama LLMs directly on your PBX hardware (or hook into OpenAI-compatible APIs) with a strict Cloud AI Lock and automated Luhn/PII redaction.
Sandboxed Plugin Engine & REST API (
mahirgul/aipbx-plugins): Extend the portal with one-click SHA-256 verified plugins — including multi-carrier SMS/MMS messaging, embeddable Website WebRTC Call Widgets, Auto-Dialer with AMD, and MS Teams Direct Routing.Automated Network & Telephony Provisioning: Zero-touch LAN phone discovery daemon, multi-site Phone Regions with automated Let's Encrypt SAN renewals, sub-microsecond AstDB spam blacklisting, and multi-DID T.38 Virtual Fax Units.
Self-Healing Atomic Updates (
aipbx-update): Live-reloads Asterisk without dropping active calls, defers core library restarts to a zero-call night window, and automatically rolls back code, configs, and DB migrations if background smoke tests fail.
🚀 One-Line Install (Ubuntu 26.04+, Debian 13+, Raspberry Pi / ARM64)
GitHub: https://github.com/mahirgul/AiPBX
Website & Docs: https://aipbx.bid
🖥️ Interactive Live Demo: https://aipbx.bid/demo
r/WebRTC • u/OfficialWaveOK • 8d ago
💚 More Than Just Chat — Here's What We're Building with WaveOK
r/WebRTC • u/reb_2020 • 10d ago
TFile: peer-to-peer file sharing in the browser, with readable links, passwords and a torrent-style "share for later" mode
Hi! I'm the developer of TFile, a free tool for sending files straight from one browser to another. Files go over an encrypted WebRTC connection between your devices, so they aren't uploaded to anyone's cloud first. No account, no app, no cookies, no ads, no tracking.
I've just shipped a big update and would love feedback.
⚡ Send now (live, two people)
- Open the site, get a link like tfile.io, which you can actually read out over the phone, or scan the QR code.
- When the other person opens it, drop files, whole folders, text or a pasted screenshot.
- No fixed size limit: big files are written to the browser's storage on disk as they arrive, so free disk space is the real limit.
- Folders can be saved as one .zip, and received files can be saved automatically.
- If the connection drops for a moment (a phone switching networks, a laptop waking up), the transfer continues where it stopped.
- Both of you see a security code. If the codes match, nobody, not even my server, is sitting in the middle.
- New: an optional password. Your browser turns it into the room ID, so the password never leaves your device.
🔗 Share for later (new, works like a torrent)
- Pick files or a folder and get a link. Anyone who opens it sees the list, ticks what they want, and downloads it straight from your browser whenever they like.
- People downloading pass pieces on to each other. Once someone has the files, others can still get them from that person while their tab is open, even after you close yours.
- Every piece is checked against a fingerprint in the link, so a peer sending corrupted data is caught and dropped.
- Optional password, plus limits: how many people can download at once, how many in total, and how long the link works (1 hour, 1 day or 7 days).
Honest limitations
- It's peer to peer, so a tab with the files has to stay open: yours, or the tab of someone who already downloaded them.
- With Share for later, others on the same link can see your IP address, just like a torrent. Downloaders can opt out of passing files on, and links with limits never pass them on.
- Some strict company or school networks block direct connections. TFile then falls back to a relay server, which carries the encrypted data but can't read it or store it.
Why I built it: I was tired of uploading a file to some cloud service just so the person next to me, or on the other side of the world, could download it again.
It's free. I'd really like to hear what breaks, especially on phones and in Safari or Firefox. 🙏
r/WebRTC • u/yasirtug • 10d ago
Built an ephemeral browser Discord
It's [gipcord.xyz](http://gipcord.xyz)
Built for ease of use. You can create a room, share a screen and friends can hop in with 1 click. Its also good for P2P file sharing.
Great for when you have the bandwidth and want to share your screen in higher quality, or to give people quick remote support.
Everything costly happens P2P so no reason for me to monetize this etc.
r/WebRTC • u/desarrolladorNODE • 10d ago
Acabo de lanzar la versión 1.0.0 de mi plataforma de streaming 100% descentralizada (IPFS + WebRTC + Nostr) sin servidores centrales. ¡Busco testers!
r/WebRTC • u/Real_Pumpkin7083 • 11d ago
Release v1.6.0 — rete Freenet · blue-terminal/freenet-android
github.comr/WebRTC • u/vprogramming • 11d ago
I need help finding a peerjs alternative
im working on a web based game which uses a peer to peer 1 host multiple party members style of connection
i was trying to ussee peerjs but only to learn TURN wasnt working and then that TURN for peerjs was discontinued
I cannot pay for anything even anything that suggest meetering (looking at you cloudflare) just in case of exploitation costing a ton off money i dont have
what alteernatives would be available to me?
r/WebRTC • u/PhysicsExtreme • 12d ago
We took the pose server off a 2D street and left Yjs holding the map
r/WebRTC • u/Lucky-Bad-9436 • 12d ago
Lessons from building a phone-as-camera studio on LiveKit: hold frames, endless reconnect and packet loss
We built StudioFlow, a browser-based control room where phones send camera and screen via WebRTC (LiveKit SFU) and a director switches scenes into a 16:9 output page.
A few things we learned:
Mobile browsers drop out constantly (screen lock, network switch). We keep the last decoded frame on the output and reconnect endlessly, so the program never goes black
A wake lock plus a recovery path on the phone matter more than any codec tuning
With 5 % loss, a loss-dependent playout buffer and an early keyframe request keep freezes under 2 s per minute
With 20 % loss we still see single freezes of up to ~6.5 s. Ideas we're weighing: request the keyframe sooner, or drop to the lowest simulcast layer as soon as loss is high
How do you handle heavy loss on phone uplinks? Anything we're missing?
Code (MIT): https://github.com/OPTEN/StudioFlow
r/WebRTC • u/Ok-Willingness2266 • 12d ago
Auto-provisioned media servers for WebRTC conferencing: has anyone tried this approach?
Disclosure: I’m on the marketing team at Ant Media, but this is about a technical approach I’d like opinions on.
Our dev team put together a conferencing sample where the client doesn’t connect to a fixed server. It calls a single HTTPS endpoint (a Lambda behind a CloudFormation template), and that spins up a media server instance on demand. The SDK waits for it to come up, then opens the WebSocket and carries on as usual. When the room is empty, the instance goes away, so there’s no idle cost.
What I found interesting is how little the client code changes. The only difference from a normal self-hosted setup is one option:
// auto-managed
new ConferenceClient({ httpEndpointUrl: 'https://your-lambda-url/' })
// self-hosted
new ConferenceClient({ websocketURL: 'wss://your-server:5443/live/websocket' })After that, publish / play / screen share / data channel messaging are identical in both modes.
Trade-offs I can see:
First connection waits for an EC2 instance to boot (roughly 20-60s)
You’re tied to AWS for the auto-managed route
In return, there’s no TURN, SSL or scaling setup, and no paying for idle servers
For people who’ve built conferencing products:
How do you handle idle cost vs. instant join? Warm pool, scheduled rooms, something else?
Would a cold start of 20+ seconds be a dealbreaker for your use case?
Writeup with the full code and a repo you can run locally: https://antmedia.io/build-a-webrtc-conference-room-quickly-with-ams-sdk-v2/
Happy to pass technical questions to the dev who built it.
Serverless multiplayer (no signal/stun/turn servers) via webrtc/camera/barcode
This project is mainly about the serverless technique used and the simple game merely provides an end-to-end explanation.
r/WebRTC • u/Real_Pumpkin7083 • 13d ago
Release v1.4.4 - Fix overlay a schermo intero · blue-terminal/freenet-android
r/WebRTC • u/Real_Pumpkin7083 • 14d ago
Da ora in poi, puoi effettuare videochiamate
r/WebRTC • u/jsprogrammer • 16d ago
My AI agent's P2P browser game merged 7 batches in a day: spatial audio, hearing skills, dead-reckoned poses (408 vs 1,607 B/s per client in its sim), and a blank-phone-screen fix
Meridian is an MIT-licensed persistent browser world with no authoritative server, built with Grok's Build mode. A small "lighthouse" server only introduces browsers; game traffic goes peer to peer over WebRTC. The walk view is a WebGL2 ray pass that falls back to a software (CPU) renderer when WebGL2 isn't available. There's a solo demo on GitHub Pages that runs on desktop and phones: https://blakelapierre.github.io/meridian/tools/view/index.html
What merged today (no PRs are open now):
**Sound:** other players' shots, digs and steps are heard by distance and side through the character's hearing sense. There's an ambient soundscape placed in the world (surf, gusts, birds, night insects, grass, distant AI players), plus hearing skills that get better at noticing and placing sounds, with on-screen cues.
**Senses:** the minimap reveals as far as your character can see and draws a ring at that edge. There are new perception skills, skill tooltips, ability-unlock notices and an abilities log.
**Foveation fix:** the sharpest rays go where your character looks. The old version stepped through blur bands, which showed as rings. It's now a continuous per-pixel blur with dithered sampling.
**Trampled paths:** grass wears to dirt and then to a packed path where people walk. Terrain cells are now 25 cm, and old saves migrate.
**Wire v2:** change-only poses and footprints derived from poses. The PR's capture (3 browsers + an archive) measured 79% fewer bytes in total. Older peers keep working because every v2 encoding rebuilds the signed v1 frame byte for byte.
**Wire v3:** per-receiver interest tiers plus dead reckoning, with no view adverts on the wire. In a headless sim with 25 clients and 1% loss, upload went from 1,607 to 408 B/s per client.
**Phone bug:** the demo showed a blank screen on Android Chrome while reporting 60 fps. The cause was a CSS background on the canvas covering the WebGL layer. It's fixed, and a red banner plus the CPU fallback now covers real GL failures.
**Phone camera:** pinch zoom, two-finger orbit and a first/third-person toggle, plus fullscreen and a "reset everything" button.
**Scaling bench:** grows from 2 to 50 iframe clients driven by wander bots and stops at the first failure.
**Tests:** 241 total, 236 pass, 0 fail, 5 skipped (the two-browser tests need headless Chromium).
What doesn't work yet: the demo is solo right now because the public lighthouse is off. The bench has only been run to 4 clients (movement only), since the agent's browser blocks WebRTC. The phone fix was checked in emulation, not on a real device. On my own split-screen test, no keeper block was mined on camera, so no dig became official.
For people who've done P2P games over WebRTC: how far did you get with full-mesh before you needed relays or interest management?
r/WebRTC • u/Infamous-Library-702 • 17d ago
I made NEXUS, a communication sandbox, with a codec built from scratch and a custom streaming pipeline in c++
Solo dev here. NEXUS is a free communication sandbox: chat, voice, calls with camera and screen sharing, encrypted DMs, group calls and streaming coupled with remote play at high fps, low latency so your friends can play on your PC
it basically combines parsec and zero-tier (or hamachi for the older gentleman) with discord
Windows, Android, browser and the Microsoft Store: https://zenisosoftworks.com/nexus
I'd love to hear some feedback.
r/WebRTC • u/desarrolladorNODE • 17d ago
Últimamente estoy probando hasta dónde se puede llevar la descentralización en el streaming.
galleryr/WebRTC • u/Low_Ferret6101 • 17d ago
[Bug] Intermittent 1-way video call bug in Discord Web/Desktop — WebRTC inbound-rtp receives packets but no codecId is assigned (0 frames decoded)
reddit.comr/WebRTC • u/Decent-Lime-9185 • 18d ago
Multi-viewer Pi/Jetson streaming with shared control via Cloudflare SFU
A Pi or Jetson publishes video and a control DataChannel to the SFU, so multiple people can watch the same stream from their browsers and take turns controlling the device. The Worker handles session setup, so you don't need to run your own signaling server.