Hi Daniele! There aren't any SmarterMail-specific WebRTC performance settings that I'm aware of, but there are some steps you can take to help improve connectivity and video consistency for sure! First, I recommend making sure the domain you're testing against is set up to use a STUN and/or TURN server in the area pictured below. STUN/TURN allows your Online Meeting user's computers and devices to coordinate the correct port and address details to ensure smooth connectivity:

STUN/TURN will dynamically sort out these details even in the presence of NAT (Network Address Translation) and poor connectivity. Google and other providers offer publicly available STUN/TURN servers you can use freely, but it is also relatively easy to get your own STUN/TURN server set up in-house as well. Beyond that there may be device or browser specific changes you can implement as well for performance improvements overall. I had ChatGPT put together a couple of suggestions on that front since it can vary from device to device:

Since WebRTC runs mostly through your browser, start there:

1. Enable Hardware Acceleration

Chrome/Edge/Brave: Settings > System > Use hardware acceleration when available

Firefox: Settings > General > Performance > Use recommended performance settings > Enable hardware acceleration

This offloads video decoding to your GPU, freeing up your CPU.

2. Use Latest Browser Version

Always update your browser—WebRTC gets performance updates frequently.

3. Flags (Advanced Users)

In Chrome, type chrome://flags and look for:

WebRTC Echo Canceller 3: Try enabling for better audio processing

WebRTC H.264 Video Codec: Can improve performance on some hardware

⚠️ Flags are experimental, so tweak carefully and test results.

1. Network Configuration

Prefer wired Ethernet over Wi-Fi for stable bandwidth.

On Wi-Fi, use 5GHz instead of 2.4GHz if possible.

2. Firewall & Antivirus

Make sure they're not blocking or throttling WebRTC traffic (UDP ports especially).

Some strict firewalls can delay peer connections or cause them to fail.

3. CPU & Background Tasks

Close unnecessary programs during calls—especially ones using CPU/GPU or bandwidth.

1. Open chrome://webrtc-internals (Chrome) during a call to see real-time performance stats.

2. Look at packet loss, jitter, bandwidth usage, and codec types.

3. Check Task Manager (Windows) or Activity Monitor (macOS) to see what's hogging resources.

Hi Kyle, thank you for your reply.

I've been working on SmarterMail online meetings for two months, I've set up a TURN server on my datacenter using eturnal with success. I've enabled UDP and TCP connection mode (also adding ?transport=tcp at the end of the urns).

To reduce the impact of users firewall restrictions, I've enabled TURN also on TCP ports like 80 and 443, in addition to the standard 3478 (udp and tcp).

Bandwidth available for the server is about 500 Mbps, and the max load for online meetings is about 6 or 7 users.

TURN is reachable from two different internet link, and each public IP is set on SmarterMail's domain TURN configuration.

Well: everything is almost fine.

There are two main issues that I'm not able to control and improve:

1- video quality is really low for about 20% of online meeting users, also if they have a good internet connection. webRTC on SmarterMail doesn't seem to re-improve quality during the connection and the only way is to re-connect to the online meeting. This is annoying for many users who give up and remain at low quality.

2- there is a browser or driver issue on many many many many devices that starts the camera at 640x480 or however at 4:3 resolution. Deactivating the camera and reactivating it after some seconds, it runs at HD 16:9 res. This occours on Chrome, Edge, Firefox, Vivaldi... often on Android and Windows, but never on iOS. I'm sure is not a SmarterMail issue because on Google Meet, MS Teams or webcamtests.com sites you've the same behaviour, but I'm asking why this was never fixed by anyone.

These issues are the reason for my question about hidden settings. I was hoping on some hidden tweaks to enforce "something" on the client side to get better at least with the video quality.

Thanks for any thoughts!

Daniele