Skip to main content

​
Outbound country coverage matrix for agents

Every agent’s Outbound coverage page shows a per-country matrix of outbound voice destinations with a status for each: enabled, regulated, or disabled. Open it before you configure an agent’s outbound calling so a blocked destination surfaces while you’re still in setup — not as a provider-level SIP rejection on the first live call. Base path: GET /api/v1/voice/country-coverage Base surface: dashboard — open an agent, then Voice settings → Outbound coverage.

​
What the matrix is

The matrix is a pre-configuration advisory. Each destination country carries one of three statuses:
  • Enabled — outbound calls to the country proceed normally.
  • Regulated — the country carries regulatory conditions (for example, calling-hours limits or disclosures). A note and a regulator reference link spell out what applies.
  • Disabled — outbound calls to the country are subject to sanctions or regulatory restrictions.
Search by country name, ISO code, or dialing prefix, and filter the table by status.

​
Read it before wiring outbound

When a destination shows regulated or disabled, the outbound guard logs a structured advisory as the call dispatches so the flag is visible in your logs. Whether the call proceeds is a tenant-level decision: country restrictions on Devotel Orbit are your workspace’s policy, not a platform-wide gate. Set that policy where you manage compliance, and use the matrix to know which destinations carry a flag before you commit them to an agent’s call list. The matrix is informational only — it never picks a provider. Every outbound call routes over the same Devotel wholesale softswitch; the page applies policy, it does not steer carriers.

​
The coverage API

The same data is readable over the public API under the voice:read scope:
Each row returns countryIso, countryName, dialingPrefix, status (enabled | regulated | disabled), an optional regulatoryNote, and an optional citationUrl to the regulator source. Rows with no country match are treated as enabled, so an unknown destination never blocks a call that your own compliance configuration would allow.

​
When a destination needs pre-clearance

For a destination flagged regulated, complete the pre-clearance step in your workspace’s compliance configuration before you put the country on an agent’s outbound list. See country requirements for what each flagged destination needs — those controls are yours to own per tenancy.