The Dolby.io Communications APIs currently operate in five regions:
- au: Australia
- ca: Canada
- eu: Europe
- in: India
- us: United States
Dolby.io uses AWS Route53 Geo-latency based resolution to determine a client or server application's geo-location. Non-media traffic is routed to one of the Dolby.io regions based on the proximity.
Routing of the media traffic depends on the region of where the conference is created. Media traffic refers to video, audio, and screenshare data. By default, the conference is created based on the conference creator's geo-location and proximity to one of the Dolby.io regions. The conference creator can be either a client or server-side app. For example, a client SDK in Spain creates a conference and that conference is automatically hosted in the Europe data center; a client from the US in the same conference will send its media traffic to the European data center even though its non-media traffic is still routed to the US region. In the event of a data center failure, we will attempt to route traffic to the next closest data center.
Note: Recording files are created in the region where the conference is hosted.
Regional media zones let you restrict media and recordings to specific geographical regions, by pinning an application key to a specific region, thus bypassing the conference creator's geo-latency based resolution. The servers will not change to another region even for load or failover. This is particularly useful for various compliance regulations, such as GDPR and HIPAA. Please contact the Dolby.io Sales team to enable the Regional Media Zone capability through backend configuration.
You can bypass proximity-based conference creation, and create a conference in a particular region on the server-side using REST APIs. You can specify the region for media traffic routing by prefixing the regional code to the REST API endpoint URL, for example using eu.comms.api.dolby.io instead of comms.api.dolby.io to enforce traffic routing to the Europe data center.
Updated 6 months ago