On this page
Voice routing groups & routes
Destination matching, priorities, weights, attempts and media selection.
Build a route#
Create a Voice routing group, then add at least one active route and gateway. Assign the group to a Voice client.
Selection rules#
More specific destination prefixes win before less specific prefixes. Within the same specificity, a lower numeric priority is preferred. Weights randomize eligible routes only within an equal prefix/priority tier. A weight of zero is handled as one by the current selector.
| Route field | Behavior |
|---|---|
| Destination prefix | Prefix match; * is a catch-all |
| Priority | Lower number wins within equal specificity |
| Balance weight | Relative selection weight within the same tier |
| Concurrent call limit | 0 means no route-specific limit |
| Maximum attempts | Budget for this route, bounded by the job's remaining attempts |
| On failure | NEXT tries the next eligible route; STOP stops routing |
| Media mode | STATIC IVR or TTS |
| Language | Exact IVR language name or TTS language code |
| Successful DLR at | RINGING, ANSWERED or COMPLETED policy |
| Flash call | Separate ringing/CLI verification mode |
Media requirements#
For static IVR, the configured language and prompts must have compatible runtime variants. For TTS, select a configured provider and voice. CLI and destination patterns alter numbering; verify their exact result before sending real traffic.
Observe attempts#
A submission can have more than one call attempt. Reports use the latest attempt to avoid inflating submission totals. Compare route ID, gateway ID, attempt number and failure reason rather than counting attempts as new customer messages.
Limitations#
The Record call field does not enable a production recording adapter in this release. Transport and authentication limits are described in Voice gateways.
Screenshots show fictional data from the public demo. Your instance may have different records and permissions.