The Unified Communications Reference Architecture for RingCentral is illustrated in the diagram below.
This architecture provides a conceptualization of the possible functionality deployed to support and realize messaging, video, and voice (MVP) unified communication services. It does not illustrate possible multiplicities of functionality at enterprise sites or in terms of connectivity to the RingCentral cloud used in particular enterprise deployments. Wide-area and local-area network components are indicated for the delivery of those services to endpoints, including desk phones and soft clients.
The “RingCentral Global MVP UCaaS Cloud” in the diagram below illustrates Internet telephony service provider (ITSP) and PSTN carrier interfaces, a communication session controller, a media server, and the cloud Application Programming Interface (API). Each of these functions corresponds to globally distributed and connected components or service access points.
The ITSP and PSTN interfaces support voice calls with parties outside the RingCentral cloud domain. The media server facilitates voice and video encoding and connecting call legs for point-to-point and conference calls. The communication session controller handles endpoint registration and orchestrates messaging, video, and voice sessions. The API provides the ability to extract call and quality history reports and billing information from the RingCentral cloud and to externally control communication sessions.
The RingCentral reference architecture operates based on a hub-and-spoke topology; all signaling and media traffic from an endpoint traverses the RingCentral cloud, even for communication between adjacent call participants at a single enterprise site.
Along the path between an endpoint and the RingCentral cloud, traffic must be managed in terms of end-to-end path Quality of Service. This implies that sufficient bandwidth must be available on every link, traffic needs to be properly prioritized if possible, and intermediate and endpoint devices must have sufficient performance. All traffic between endpoints and the RingCentral cloud is encrypted including signaling, messaging, video, and phone media streams, configuration updates, presence status notifications, and API sessions.