Feature request: support Tunisia (+216) as a call destination

[Hiba-Chaabnia]

Got this rejection calling a +216 (Tunisia) number via the Developer API:

"I recognized the destination as Tunisia and the call language as English, but that region/language combination is not currently supported."

Not in the supported-regions table in the README. Is this planned, and if so is there a timeline or a way to signal demand for it?

[Ray-56]

Triage: P3 feature request.

The reported rejection is consistent with the current supported-regions table: Tunisia (TN, +216) is not advertised as a supported destination. This is not a repository security defect, and the integrations repository cannot enable the route by itself; support depends on the deployed CALL-E telephony/routing configuration and the provider account used in production. I cannot infer a delivery timeline from the repository.

Recommended next action for the product/platform owner:

1. Record the +216 demand and confirm outbound coverage with the production carrier/provider account.
2. Validate regulatory, caller-ID, local-versus-international line, pricing/credit, and billing behavior for Tunisia.
3. Confirm the intended English ASR/TTS path and define any language fallback explicitly.
4. Add a preflight/integration test proving unsupported +216 requests are rejected before carrier dispatch or any chargeable side effect.
5. After the backend route is enabled and verified end to end, update the supported-regions table and any machine-readable capability metadata in the same change.

Until those checks pass, please keep +216 rejected rather than documenting it as available.

[JJasonSun]

English support for Tunisia (+216) is now live. Our test destination rejected the call immediately, so end-to-end validation is still pending. Please retest with an authorized +216 number and let us know whether it connects.

[Hiba-Chaabnia]

Just retested with an authorized +216 number and it's working now — call connected, had an actual conversation, no more region rejection.

Thanks for the fast fix, closing this out on my end.