# Geolocation enable Twilio

## Enable calling to UAE & Saudi Arabia (Programmable Voice)

1. **Open the Geo/Dialing Permissions page**\
   Twilio Console → **Programmable Voice → Settings → Geo (Dialing) Permissions**. From there, enable **United Arab Emirates (AE)** and **Saudi Arabia (SA)**, then **Save**. citeturn0search5turn0search6
2. **(If you use Elastic SIP Trunking)**\
   Also enable countries under **Voice Dialing Geographic Permissions** for SIP Trunks (it’s a separate toggle path in the Console). citeturn0search5
3. **(Optional) Enable via API**\
   You can programmatically manage permissions using the **Dialing Permissions API** (Countries & Settings resources). Handy for CI/automation. citeturn0search10turn0search22
4. **Retry your call**\
   After saving, place another call to confirm routing. If it still fails, check the notes below.

***

### Country-specific gotchas

#### United Arab Emirates (AE)

* **You cannot place outbound calls using a UAE geographic number as the caller ID** (regulatory rule). Use a non-UAE number (e.g., EU/US/KSA) as your outbound CLI. citeturn0search0turn0search7

<figure><img src="https://885185803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWu0Bf4ztMRcYFAREHSWo%2Fuploads%2FpTWjrx9EKxg5Yh0S7LKp%2Fuae%20twillio%20geo%20permissions.png?alt=media&#x26;token=ea3a0bc7-709d-4a37-b432-d92882f04144" alt=""><figcaption></figcaption></figure>

#### Saudi Arabia (SA)

* Voice works once Geo Permissions are enabled; just ensure your caller ID is valid E.164 and not a restricted/premium destination. (SMS has extra rules, but that doesn’t affect voice here.) citeturn1search0

***

<figure><img src="https://885185803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWu0Bf4ztMRcYFAREHSWo%2Fuploads%2F5ByM8Z0qX2GpRlSVod6m%2Fsaudi%20geopermissions.png?alt=media&#x26;token=1e16c37b-27b0-4ee9-a627-0deb6a0b215f" alt=""><figcaption></figcaption></figure>

### Troubleshooting checklist (if calls still don’t go through)

* **Confirm the correct product’s permissions:** You must enable **Voice** (not just Messaging/Verify). The Voice troubleshooting & Geo Permissions docs are the ones you need.&#x20;
* **Caller ID (CLI):** Use a compliant, verified number as your `From`—and for UAE, never a UAE geo number as outbound CLI.
* **High-risk prefixes blocked:** Some premium/satellite routes are blocked by default; stay on standard mobile/landline ranges. (Managed via Dialing/Geo Permissions.)
* **Subaccounts & Trunks:** If you’re using subaccounts or SIP Trunks, set permissions at the correct level (account vs. trunk).

***

### Official links (for your bookmarks)

* **Voice Dialing Geographic Permissions (how-to + Console paths):**&#x20;
* **International Voice Dialing Geo Permissions (overview):**&#x20;
* **Troubleshooting Voice (international permissions reminder**
* **Dialing Permissions API (Countries):**
* **Dialing Permissions API (Settings)**
* **UAE Voice Guidelines / Restrictions:**&#x20;
* **Saudi Arabia Regulatory Guidelines (country page):**&#x20;

***

### Quick “what to click” summary

* Console → **Programmable Voice → Settings → Geo (Dialing) Permissions** → **Enable AE & SA** → **Save**.
* If using SIP Trunks: Console → **Elastic SIP Trunking → Settings → Geo Permissions** → **Enable AE & SA** → **Save**. citeturn0search5

If you want, tell me whether you’re calling via **Programmable Voice API** or **Elastic SIP Trunking**, and what “From” number you’re using—I can pinpoint the exact toggle(s) for your setup.