Aizaz_Jahangir
12/30/2025, 8:41 PMAI Evy
12/30/2025, 8:41 PMAI Evy
12/30/2025, 8:41 PMAI Evy
12/30/2025, 8:41 PMinvalid_destination, this represents cases where the destination phone number is invalid.
4. Re-import the Number if Needed
If the configuration is not correct, delete the imported number and re-import it with the correct termination URI and credentials.
5. Check with Twilio
If the above doesn't resolve it, check with your telephony provider (Twilio) to see what error they're showing on their side.
Can you share the specific disconnection reason or SIP error code from your call history? That would help narrow down the exact issue.AI Evy
12/30/2025, 8:41 PMAizaz_Jahangir
12/30/2025, 8:43 PMAI Evy
12/30/2025, 8:43 PMAI Evy
12/30/2025, 8:43 PMAI Evy
12/30/2025, 8:43 PMinvalid_destination error represents cases where the destination phone number is invalid. [(1) ]()
Since you've already enabled Pakistan in Twilio's geographic permissions, here are the next steps to troubleshoot:
1. Verify Phone Number Format
Ensure the Pakistan number you're dialing is in proper E.164 format (e.g., +92 followed by the number without spaces or special characters) . [(2) ]()
2. Check Your Termination SIP URI
- Remove any spaces in your Termination SIP URI [(3) ]()
- Use a localized termination URI that's near your region
3. Verify Twilio Elastic SIP Trunking Permissions
Double-check that you selected "Elastic SIP Trunking" (not just Voice) in Twilio's Voice Geographic Permissions setting. The documentation specifically notes: Search "geo" to find the "Voice Geographic Permissions" setting, then choose "Elastic Sip Trunking" in the selector and select the countries you would like to dial.
4. Re-import the Number
If the configuration is not correct, delete the imported number and re-import it with the correct settings. [(1) ]()
5. Check Twilio Logs
If the above doesn't resolve it, check with Twilio to see what's the error on their side.
The most likely cause here is that the geographic permission was enabled for standard Voice but not specifically for Elastic SIP Trunking in Twilio.AI Evy
12/30/2025, 8:43 PMAizaz_Jahangir
12/30/2025, 8:53 PMAI Evy
12/30/2025, 8:54 PMAizaz_Jahangir
12/30/2025, 8:54 PMAI Evy
12/30/2025, 8:55 PMAI Evy
12/30/2025, 8:55 PMAI Evy
12/30/2025, 8:55 PMinvalid_destination, here are the remaining things to check:
1. Verify the Termination SIP URI in Retell
Check your Termination SIP URI for any spaces and remove them. [(1) ]() Also verify the username and credentials are correct—the username is different from the friendly name that shows in the credential list in Twilio.
2. Re-import the Number
If the configuration is not correct, delete the imported number and re-import. [(2) ]() Right now you'd need to delete and re-import the number to change the configuration. [(3) ]()
3. Check Twilio's Logs
If that does not solve it, please check with your telephony provider to see what's the error on their side. [(2) ]() Twilio's logs may show a more specific SIP error code that clarifies why the destination is being rejected.
4. Verify Phone Number Format
Ensure you're dialing the Pakistan number in proper E.164 format (e.g., +92 followed by the number) . [(4) ]()
The invalid_destination error represents cases where the destination phone number is invalid. [(2) ]() Since your Twilio permissions appear correct, the issue is likely either in the number format, the termination URI configuration in Retell, or something on Twilio's termination side that their logs would reveal.