Problem
A developer is experiencing persistent RTM connection issues with users behind strict firewalls, particularly on their guest WiFi networks.
Through extensive testing and detailed log analysis, the developer has observed that all RTM connections are attempting to use ports 9593 or 9591, but there is no fallback to port 443 as expected.
The issue was encountered using SDK version "agora-rtm-sdk": "^1.6.0-205", and the developer wants to know how to ensure an immediate fallback to TCP 443 for a more reliable connection.
Root Cause
The reason there was no fallback to TCP 443 during their test is that they were using RTM 1.x, which does not support fallback to TCP 443, even with Cloud Proxy enabled.
Additionally, in Agora RTM 2.2.1, fallback did not occur because Cloud Proxy was not enabled. To ensure fallback to TCP 443 in RTM 2.2.1, Cloud Proxy must be enabled.
Solution
They need to use the latest version of the RTM 2.2.x SDK (Web) and set cloudProxy to true in the rtmConfig parameter. This will enable Cloud Proxy, ensuring that traffic is routed directly through TCP 443.