Skip to main content
Geo‑fencing allows you to restrict inbound and outbound calls based on the caller’s geographic location. It ensures that SIP traffic is routed only through approved geographic regions, helping maintain compliance, security, and regional telephony rules. Users connect to a specific regional Zero Runtime server based on the geoRegion value they set. In this example, even though some users are located in India, a user who sets geoRegion to ‘US’ is routed through the US server, and all users are then bridged together inside the same Zero Runtime room.
videosdk.live is expected here. Zero Runtime runs on VideoSDK’s real-time infrastructure, so its SIP, media, and API endpoints are served from the videosdk.live domain. Use the hostnames and URLs exactly as shown.

​
Inbound Calls

For inbound calls, Geo-fencing lets you choose which regional SIP server should handle the call. This can be configured using the SIP URI or through the Zero Runtime Dashboard.
You can specify the region directly in the SIP Inbound Gateway URI:
Replace $YOUR_ORG_ID with your actual Zero Runtime organization ID and <region> with one of the supported region codes.Available region codes:
  • in001 → India
  • us002 → United States

​
Outbound Calls

When making outbound calls, you can control the SIP server region via the Dashboard or the API Request.
You can control the SIP server region via the geoRegion property in the API request. If geoRegion is omitted, Zero Runtime selects the region automatically based on the dialed number’s location.