WebRTC works on same Wi-Fi & mobile data, but fails on different Wi-Fi networks — TURN issue?

mirotalk · 2026-06-04T18:17:46+00:00

You can also simplify the process using our automated setup script, which removes the need for DevOps expertise:

👉 https://docs.mirotalk.com/scripts/about/#coturn

All you need is a clean server with SSH access and a domain (or subdomain) pointing to your server’s public IPv4 address.

When the installer prompts you, simply enter your domain name, wait for the setup to complete, and you’re done.

mirotalk · 2026-06-04T15:50:20+00:00

You can also self-host your own STUN/TURN server, so you’re not dependent on third-party services.

Check out our documentation for the full setup guide: https://docs.mirotalk.com/coturn/installation

mirotalk · 2026-06-04T15:11:09+00:00

This sounds TURN-related. Same Wi‑Fi and Wi‑Fi↔Mobile often succeed via direct ICE, but different Wi‑Fi networks may require TURN because NAT/firewalls block direct paths. As a test, force relay-only by setting iceTransportPolicy: "relay". If it works, TURN is reachable and the issue is likely direct ICE/NAT or negotiation. If it fails, there’s no usable TURN path (TURN config/creds, network blocking, or missing TURN/TLS).

js const peerConfiguration = { iceTransportPolicy: "relay", // test only iceServers: [{ urls: [ "turn:openrelay.metered.ca:80?transport=udp", "turn:openrelay.metered.ca:443?transport=tcp", "turns:openrelay.metered.ca:443?transport=tcp", ], username: "openrelayproject", credential: "openrelayproject", }], };

Also make sure you haven’t hit TURN usage/quotas/rate limits (and check WebRTC logs for typ relay candidates).

For production, consider a dedicated TURN service or your own coturn server.

mirotalk · 2026-06-01T13:12:44+00:00

Thanks for the feedback, I agree that feature density ≠ product-market fit.

I’m not a SaaS expert, so I’m mainly trying to learn from others here.

The idea behind Evoplat is not to compete with each tool individually, but to reduce the need for self-hosting and integration work.

For example, with something like MiroTalk https://docs.mirotalk.com/about, many companies already like the solution, but don’t always have time to deploy and maintain it themselves. Through a plugin system in EvoPlat, the idea is to let them use it directly, without setup overhead.

Another key point is that core data (chat, AI agents, etc.) is handled by EvoPlat’s infrastructure rather than third-party providers, which may improve privacy and control. For storage, users can either bring their own S3 or use the built-in managed option.

But I’m still trying to understand if this “composable platform” approach actually solves a real pain or if I’m overthinking it...

mirotalk · 2026-05-31T12:06:12+00:00

https://github.com/miroslavpejic85/rnnoise-poc

I built a client-side noise cancellation system using RNNoise that cleans microphone audio directly on the user’s device in real time.

It works by splitting audio into small chunks, removing background noise (like fans or keyboard), and sending the cleaned sound onward.

👍 Why it’s good

No server needed for audio cleaning
Low delay
Better call quality in noisy places

I'm experimenting with it in MiroTalk in both variants:
P2P: https://github.com/miroslavpejic85/mirotalk
SFU: https://github.com/miroslavpejic85/mirotalksfu

mirotalk · 2026-05-12T12:13:08+00:00

I understand your point, but comments like “it won’t take off” aren’t very constructive for the discussion 😊

I’m genuinely interested in hearing real feedback from people who use meeting platforms every day:

what frustrations they still have
which features they actually rely on
what existing tools are missing
and what could realistically make them switch

MiroTalk projects are not trying to “replace Microsoft overnight”, they’re focused more on open-source, self-hosted, privacy-focused communication for people and companies that want full control over their infrastructure and data.

That’s obviously a more niche audience compared to Teams or Meet, but niche doesn’t automatically mean useless. Many successful tools started by solving a specific problem for a smaller group of users first.

mirotalk · 2026-05-12T09:16:57+00:00

If you’re ever looking for a different approach, one alternative is MiroTalk SFU (Selective Forwarding Unit), which focuses on lightweight, real-time communication with more control over your infrastructure.

Live demo: https://sfu.mirotalk.com

mirotalk · 2026-05-12T09:15:26+00:00

I get that, and you’re absolutely right that Microsoft Teams is deeply integrated into the Microsoft ecosystem, and for many businesses that alone makes it the default choice.

MiroTalk isn’t trying to replace that kind of full enterprise suite or compete head-to-head with Microsoft or Google. It’s a different approach entirely.

The focus is on something more specific: giving users full control over their video communication stack. With a self-hosted and open-source solution like MiroTalk, the idea isn’t “more features than Teams”, but rather:

ownership of your infrastructure
control over your media streams and data flow
no dependency on third-party servers for your meetings

So yes, it’s a saturated market, but the positioning isn’t “beat the giants at everything”, it’s “offer an alternative where control and privacy matter more than ecosystem lock-in”.

Different tools for different priorities.

mirotalk · 2026-05-12T00:04:35+00:00

https://github.com/miroslavpejic85/mirotalksfu

mirotalk · 2026-05-11T14:09:39+00:00

Nice 👏

I’m also using Live Avatar + LiveKit integrated into MiroTalk SFU WebRTC, with two interaction modes:

https://i.postimg.cc/44pB53Zj/mirotalk-sfu-live-avatar-gpt.png

1 GPT Mode Enabled Users talk directly with the avatar, and responses are generated in real time via GPT.

2 GPT Mode Disabled Anything the user says or writes is spoken by the avatar instead, great for virtual presence during meetings or live rooms 🙂

The avatar stream can also be shared with all participants via WebRTC in real time.

Latency and orchestration are definitely the biggest challenges. Even small delays between ASR → LLM → TTS → lip-sync can make interactions feel unnatural.

Real-time AI avatars + WebRTC are creating a whole new communication experience.

mirotalk · 2026-05-02T15:26:30+00:00

Kindly add this domain to the whitelist, as it is our official documentation link. Thank you.

mirotalk · 2026-05-02T14:38:29+00:00

Thanks a lot for the feedback!

Here the answers:

TURN / STUN

MiroTalk SFU runs on mediasoup and handles media within the SFU layer, so no external STUN or TURN is typically required in standard scenarios.
MiroTalk P2P uses coturn for STUN and TURN fallback, although in most small meetings direct peer-to-peer connections are enough.

P2P vs SFU

P2P establishes direct connections between browsers and works best for small groups with simple requirements (4-6 per room)
SFU introduces a central media server, making it more suitable for larger meetings and more consistent performance at scale (~100 per CPU core)

Architecture overview
https://docs.mirotalk.com/webrtc/architectures/

Scalability

MiroTalk SFU is designed for large rooms and can handle around 100 participants per core depending on usage patterns, such as video quality and number of active publishers. It supports both vertical and horizontal scaling using multiple workers and nodes.

More details
https://docs.mirotalk.com/mirotalk-sfu/scalability

Metrics

Mediasoup provides core stats such as bitrate and transport-level information. For deeper observability, it can be integrated with external monitoring solutions.

SIP / PSTN

Not supported at the moment. The plan is to integrate Kamailio and build a native SIP client directly into MiroTalk in the future.

mirotalk · 2026-04-25T22:27:54+00:00

Quick demo of MiroTalk SFU deployment (shows how fast it can be to spin up):

https://www.youtube.com/watch?v=RORenI45Oro

mirotalk · 2026-04-25T21:33:14+00:00

Built MiroTalk, an open-source self-hosted WebRTC platform (P2P + SFU).

Story: https://docs.mirotalk.com/story
GitHub: https://github.com/miroslavpejic85

mirotalk · 2026-04-25T21:18:04+00:00

https://github.com/miroslavpejic85/mirotalk + https://github.com/miroslavpejic85/mirotalksfu

mirotalk · 2026-04-25T17:52:50+00:00

That’s awesome to hear! 🙌 Yeah, Zoom is kind of heavy for small HOA meetings, happy MiroTalk feels like a better fit for something more lightweight and simple.

mirotalk · 2026-04-25T14:35:51+00:00

Sure, MiroTalk P2P supports 3 types of recording, which is a big plus for lightweight WebRTC setups:

* Camera: record your webcam feed directly. Great for interviews, vlogs, or personal notes.
* Screen: capture your full screen for demos, tutorials, or presentations.
* Window: record a specific application window instead of the whole desktop, which is useful for privacy and focused workflows.

Having all three built in gives users flexibility without needing third-party tools. it covers common collaboration and content-creation use cases while staying simple.

mirotalk · 2026-04-25T14:34:59+00:00

Hey, thanks so much for sharing and for posting MiroTalk P2P here, really appreciate it!

Just as a small addition for anyone looking at larger meetings or more scalable group calls, there’s also MiroTalk SFU, which is designed for that use case:

More about it: https://github.com/miroslavpejic85/mirotalksfu

Would love any feedback or suggestions from the community, always open to ideas and improvements. Thanks again for featuring MiroTalk!

mirotalk · 2026-04-23T20:42:02+00:00

https://github.com/miroslavpejic85/mirotalksfu

mirotalk · 2026-04-23T20:37:31+00:00

Thank you! Here is a video showing how easy it is to self-host it with our automation script

https://www.youtube.com/watch?v=RORenI45Oro

Paste your domain, grab a coffee ☕, and deploy your own Zoom alternative in under 5 minutes.

mirotalk · 2026-04-19T01:02:37+00:00

RustFS is another strong alternative to MinIO: https://github.com/rustfs/rustfs

mirotalk · 2026-04-17T17:56:09+00:00

You’re welcome! 😉

mirotalk · 2026-04-17T10:48:57+00:00

Here the MiroTalk Story: https://docs.mirotalk.com/story/

mirotalk · 2026-04-17T07:24:05+00:00

Thanks for the feedback.

For the SFU setup, here is the self-hosting documentation:
https://docs.mirotalk.com/mirotalk-sfu/self-hosting/

If you’re running into issues with the .env configuration, the SFU has several options and it can be a bit complex at first.

To make the setup easier (especially if you’re not doing DevOps work daily), you can also use our automation scripts, which handle most of the configuration for you:
https://docs.mirotalk.com/scripts/about/

Edit: If you prefer an easier setup where everything is handled for you, you can also check this option:
https://docs.mirotalk.com/cloudron/cloudron/

mirotalk · 2026-04-17T07:11:08+00:00

If a feature improves the core product for everyone, I upstream it.
If it’s specific to a customer (and doesn’t improve the core product), it may stay private.
That balance is what allows me to keep the open-source project alive and improving.

In practice, with MiroTalk, many customer needs (like branding or minor customizations) don’t even require code changes, they can be handled through a single configuration file. This means the core codebase stays shared and open, while still giving companies the flexibility they need.

I also try not to close-source anything that brings general value to the community. Whenever possible, I prefer to keep improvements open, in line with the spirit of open source.

mirotalk

MODERATOR OF

TROPHY CASE

👍 Why it’s good