Description / Use Case:
Currently, UK customers using default BT and EE Wi-Fi routers (such as the EE Smart Hub) experience severe uplink packet loss (up to 25%), freezing, and "Unstable Connection" errors during RC Video meetings, specifically when sharing their screen.

While Engineering has identified the BT/EE router hardware as the bottleneck, competitor applications like Microsoft Teams handle video routing and screen sharing flawlessly on the same routers without packet loss.

The request is to improve RCV's network resilience and packet handling (e.g., adaptive bitrates, alternative port tunneling, or UDP fallback mechanisms) so that it can natively bypass or tolerate the traffic shaping/limitations of BT/EE routers, just as our competitors do.

Business Impact (Why this is needed):
High risk of churn. BT/EE is one of the largest ISPs in the UK. Telling enterprise customers they must purchase and install third-party network hardware just to use RingCentral Video is an unacceptable workaround, especially when MS Teams works out of the box on their existing network. Implementing a software-side, router-agnostic fix will prevent lost accounts and improve the RCV experience for a massive segment of UK users.

Current Workaround:
Customers are currently forced to use a different network, a mobile 5G hotspot, or purchase/install a third-party router (none of which is a viable long-term enterprise solution).

Target Audience:
All UK RingCentral Video users, specifically those on BT and EE networks.