Giga Hub 2.0 intermittently interrupts WebRTP video call

Mogsdad
Contributor

I recently upgraded from a Home Hub 3000 because it began to reboot frequently after I obtained a new laptop with Wifi 6. Unfortunately, that upgrade has had severe impact on the stability of video calls that had been rock solid for years prior.

The video calls are managed using Doxy.me, a simple, web-based telemedicine platform that allows healthcare providers to conduct secure video consultations with patients. For privacy, calls are made using WebRTC (aka WebRTP), which is implement on UDP. It can handle dropped packets better than delays.

Immediately after moving to the Giga Hub, we started seeing the audio and video in calls "pausing", and confirmed via chrome://webrtc-internals that round-trip times (a measure of latency) were spiking at a regular cadence - about every minute. If I rebooted the router, a new call would be ok for five to ten minutes, then we'd start to see some stuttering, which would settle into the steady interruption state. Later in the day, we could no longer initiate calls at all.

I called Bell Support, and described the situation. After some rudimentary checks, they said that the migration from the Home Hub had set something up wrong (no details), which they fixed. They noticed in the logs that several devices, including the laptop used for client calls, were continuously disconnecting and reconnecting to Wi-Fi, presumably as they switched between 2.4 and 5 GHz bands. They applied a firmware update to 3.11.6.4 which reduced that switching - they suggested splitting the bands to eliminate that problem. Sadly, we saw no improvement in the issue that prompted our call.

The laptops are now only using 5 GHz - I changed their adapter settings so we could still use Whole Home Wi-Fi. 

Searching around for similar symptoms lead to a Reddit post, Bell Giga Hub 2.0 (Firmware 3.11.3) - Ring cameras, WhatsApp calls & remote access stop working afte.... That was helpful. The underlying tech for WhatsApp and Ring video is WebRTC, just as it is for my case. I enabled "Privacy Mode" for the "Guard" feature, and it reduced the severity of my problem. Since that change, we've never been unable to initiate a call, but we still experience frequent latency spikes at a steady cadence (when they happen).

Here's a screenshot showing the impact on Web RTC:

WebRTC-Internals-10-01-2026_08_59_AM annotated.pngThese are IGMP messages on the network at the same time, captured via WireShark.

No.TimeSourceDestinationProtocolLengthInfo
26732026-10-01 8:47:07192.168.2.1224.0.0.1IGMPv352Membership Query, general
26762026-10-01 8:47:07192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
66702026-10-01 8:49:12192.168.2.1224.0.0.1IGMPv352Membership Query, general
66712026-10-01 8:49:12192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
173572026-10-01 8:51:17192.168.2.1224.0.0.1IGMPv352Membership Query, general
173582026-10-01 8:51:17192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
305622026-10-01 8:53:22192.168.2.1224.0.0.1IGMPv352Membership Query, general
305632026-10-01 8:53:22192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
475602026-10-01 8:55:27192.168.2.1224.0.0.1IGMPv352Membership Query, general
475612026-10-01 8:55:27192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
518542026-10-01 8:57:32192.168.2.1224.0.0.1IGMPv352Membership Query, general
518552026-10-01 8:57:32192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
551562026-10-01 8:59:37192.168.2.1224.0.0.1IGMPv352Membership Query, general
551582026-10-01 8:59:37192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
587602026-10-01 9:01:42192.168.2.1224.0.0.1IGMPv352Membership Query, general
587732026-10-01 9:01:42192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
678702026-10-01 9:03:47192.168.2.1224.0.0.1IGMPv352Membership Query, general
678712026-10-01 9:03:47192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
685152026-10-01 9:04:08192.168.2.1224.0.0.1IGMPv352Membership Query, general
685162026-10-01 9:04:08192.168.2.1224.0.0.1IGMPv352Membership Query, general
685292026-10-01 9:04:08192.168.2.1224.0.0.1IGMPv352Membership Query, general
685302026-10-01 9:04:08192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
685372026-10-01 9:04:09192.168.2.1224.0.0.1IGMPv352Membership Query, general
685382026-10-01 9:04:09192.168.2.1224.0.0.1IGMPv352Membership Query, general
685552026-10-01 9:04:09192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources
715512026-10-01 9:05:52192.168.2.1224.0.0.1IGMPv352Membership Query, general
715522026-10-01 9:05:52192.168.2.31224.0.0.22IGMPv370Membership Report / Join group 224.0.0.252 for any sources / Join group 224.0.0.251 for any sources / Join group 239.255.255.250 for any sources

I'd seen in some other post that there were issues with how the Giga Hub handles IGMP control traffic, but without input from a knowledgeable tech that's only conjecture. The correlation between periodic IGMP messages originating from the router and the resulting impact on UDP traffic over Wi-Fi is suspicious, anyway. In general, though, interactions like this are a known issue in the industry: 

If a consumer router or switch processing IGMP Snooping misbehaves—or experiences 
brief CPU spikes during network queries—the device can temporarily drop a port or
interface from an active group. This triggers a half-second packet starvation gap.
For regular web browsing, this gap is invisible, but for highly sensitive real-time
interactive UDP streams (like a live video call), it results in an immediate
connection freeze or drop.

As a temporary work-around, we have an ethernet cable strung up two sets of stairs to reach the office where client calls take place, in privacy. There's no problem over the ethernet ports, just Wi-Fi.

I called Bell Support again this week, and their advice was to permanently use the wired connection (why do I pay you for Wi-Fi, then?), or put the Giga Hub into bypass mode and set up my own Wi-Fi network.

I've come to the community for some better ideas.

 

Possibly related:

0 4 289
4 REPLIES 4

dks
Community All-Star
Community All-Star

Thank you for your questions and detailed response. While there may be issues with the Giga Hub, I have to ask is there is a correlation with issues starting with your new laptop? Are all the laptop and especially the wireless drivers up to date? Is this a Windows, iOS or Chromebook operating system? Have you attempted troubleshooting from the laptop end, especially when you have no issues with a wired connection? What is the distance between the laptop and the Giga Hub and is there any intervening wall between the two devices? 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

All good questions, I'll supply some more details for completeness.

I've got an "old" and a "new" laptop, and it's the "old" one that is used for daily calls with clients. It worked fine on Wi-Fi when we had the previous Home Hub router. 

The "new" laptop is not a replacement for the "old" one. The Home Hub router started rebooting when the new laptop was added - similar to this previous thread. We upgraded to the Giga Hub to fix this.

The Windows 11 OS and device drivers in both laptops are up to date. 

The problem is independent of the specific machine - I've reproduced it on both our Windows laptops as well as with an iPad. We get the same behaviour in Chrome, Firefox, Edge, and Safari (on the iPad only).

WRT Wireless distance - the office with the "old" laptop is normally about 16m from the router with several walls in between. Locating the device within 2m of the router did not resolve the problem.

The majority of the debugging I've done has been from the laptop - the WebRTC stats are collected there, and I've run Wireshark to monitor broadcast traffic from the router, for example. When using wired Ethernet, we see smaller amounts of cumulative packets lost, which is normal. There is no pattern to those losses, so it's likely that some UDP packets are being dropped due to network congestion. (Packets that arrive out of order get dropped internally by WebRTC, but don't appear in the network stats as "lost".)

I hope that clarifies things a bit, feel free to ask if any other details are needed.

Vanadiel
Community All-Star
Community All-Star

"The laptops are now only using 5 GHz - I changed their adapter settings so we could still use Whole Home Wi-Fi. "

In order to keep the bands split, you have to disable whole home Wi-Fi. As soon as you enable it they are not split anymore and your WiFi adaptors can roam and switch bands.

I am thinking what you are seeing is the result of WiFi adaptor(s) switching bands, since you mentioned you had no issues with wired connections.

I would leave home WiFi disabled and keep the bands separated, then set each WiFi adaptor manually up to ensure it only connects to a set band which should be the highest supported.

As per this guide. 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.


@Vanadiel wrote:

...what you are seeing is the result of WiFi adaptor(s) switching bands...


I considered the possibility, since router logs sometimes showed the new laptop disconnecting and reconnecting multiple times. It turns out that this isn't the solution - the laptops are not switching bands anymore.

As an experiment, I did follow those instructions you point to, to mitigate the possibility of devices switching bands (with a disconnect / reconnect), but wanted to keep some of the "Whole Home Wi-Fi" functionality. Therefore, I ultimately used Windows' device manager to disable 2.4G so the laptops don't switch away from 5G. (The "Preferred Band" setting isn't sufficient to ensure a device uses 5G.)

screenshot - device manager - 2.4G Wireless DISABLED.png