Support data sovereignty in Saudi Arabia

Saudi telecom regulators require that PSTN signaling and media stay inside the Kingdom. LiveKit offers a Saudi SIP edge for that purpose, but there is no agent hosting region or static IP range there today. Use the steps below to keep compliant without getting surprised by unsupported features.

Choose the Saudi SIP hostname

Point your trunks at the region-specific endpoint documented in the firewall guide:

• <your-subdomain>.sa.production.livekit.cloud

That hostname locks traffic to the Saudi POP. If the region becomes unavailable, calls will not fail over automatically; decide whether regulatory requirements outweigh redundancy and communicate that trade-off to customers.

What runs inside Saudi (and what does not)

• SIP termination and media relay: Provided locally so PSTN traffic never leaves the country when the above hostname is used.
• LiveKit Agents / managed compute: Not available in Saudi Arabia. Agent sessions still run in the closest supported region (typically EU or US), so do not rely on Agents for PSTN-first Saudi workloads unless regulations allow cross-border media.
• Static IPs: Not offered for Saudi POPs. The LiveKit Cloud firewall reference confirms static IP blocks exist only for EU, India, and US today. You must allow traffic by domain name; if carriers insist on IP pinning, deploy your own SBC in-country and proxy LiveKit traffic through it.

Media anchoring expectations

The compliance playbook mirrors India:

• Outbound PSTN: Your server that initiates SIP toward LiveKit or your carrier must sit in Saudi Arabia to keep signaling in-country.
• Inbound PSTN: App servers/WebHooks that answer SIP INVITEs should also be hosted domestically.
• Conferences: Avoid bridging PSTN audio with WebRTC legs in the same session; local carriers treat that as exporting media and may tear down the call.

If any leg leaves the country, expect call failures or enforcement actions from the Communications, Space and Technology Commission (CST).

Number provisioning and carrier coordination

Work with your Saudi carrier (or Plivo partner) to provision numbers. They typically request:

• Commercial registration plus proof of address inside the Kingdom.
• A written description of the IVR or agent use case.
• Emergency-contact details for abuse reports.

Provisioning can take weeks, so start paperwork well before go-live.

Firewall planning without static IPs

Because Saudi POPs do not expose dedicated IP blocks, plan firewall rules around DNS:

• Allow egress to *.sa.production.livekit.cloud
• Cache DNS with short TTLs so failovers inside the Saudi POP continue to resolve.
• Monitor the LiveKit Cloud firewall reference for new regions or hostname changes.

Combine DNS-based allow lists with in-country SBCs if your compliance team requires a single fixed IP surface.