Our application runs entirely inside of your browser.
Our Azure based webserver is just a delivery mechanism.
When you open the page, we download a framework into your browser.
That framework first connects to RingCentral for authentication.
Once you have logged in, RingCentral passes back a token that is used to communicate with RingCentral.
After initial launch and authentication, all communications is between your browser and RingCentral.
If you have enable the Microsoft or Google features, those will also be engaged directly via you browser.
All communications between your browser and our webserver happens over HTTPS (TCP/443).
Once running, communications to RingCentral are governed by the following firewall requirements.
If some firewall ports are blocked, call handling will be unpredictable when the app accesses one of the blocked ports.
If this is a home office, you will need review the config on the router/firewall connecting you to the internet.
You can review this list for firewall ports from RingCentral.
Also, you can study the troubled call in RingCentral’s Call Analytics for more clues.
We utilize RingCentral’s WebRTC API for audio.
Summarized from