Routing groups
A routing group is the routing table of an account: an ordered list of entries, each pairing a vendor Connection with a Termination Route, and a policy that decides in which order the matching entries are tried. Accounts and customers of the root customer get a routing group directly; resellers’ accounts inherit it unless extended routing gives them their own. See Routing.
Where to find it
Section titled “Where to find it”Open Vendors → Routing Groups in the left sidebar. The URL is /routing_groups.php. The screen requires system management rights; Add needs the add and edit rights, Delete the delete right.
What you see
Section titled “What you see”| Column | Meaning |
|---|---|
| Name | The group’s name, linking to the form |
| Policy | The active policies in order, for example Prefix Length/Route Preference; None when no policy is set |
| Description | Free text |
The filter takes a Name with is like / is not like. Delete appears only for groups that are not assigned to any account, customer or authentication rule.
Create a routing group
Section titled “Create a routing group”Before you start you need at least one vendor with a connection and one termination route; otherwise the entries editor is disabled with the message You cannot manage Routing Entries as Vendor Connections or Termination Routes have not been setup yet.
- Click Add.
- Enter Group Name.
- In the entries table select Vendor, then Connection and Termination Route, and click Add Row. Repeat for every connection the group may use.
- Open Routing Policy and click the policies you want in the order they should apply. New groups start with Prefix Length → Route Preference.
- Click Save & Close.
Routing entries
Section titled “Routing entries”| Column | Meaning |
|---|---|
| Vendor, Connection | The gateway the call is sent to. A struck-through connection is Blocked on the vendor’s side and is skipped |
| Termination Route | The prefix list with the vendor’s prices used for this connection. Only prefixes in it are routed to the connection |
| Activation Date, Expiration Date | When the entry is in effect. now and Never by default |
| STIR/SHAKEN | Required, Preferred, Supported or Disabled, stored only when STIR/SHAKEN is enabled for the group |
| Order # | Position in the list: First, After n or Last. Used by the Routing Entries Order policy |
| Weight | Share of traffic for Weighted Distribution. No Value keeps the entry out of the distribution |
Edit in a row changes it in place; Delete removes it after a confirmation. Both take effect when the group is saved.
Routing policy
Section titled “Routing policy”The policies are chips you switch on and drag into order. Each active policy sorts the matching routes; the next one breaks ties.
| Policy | Order |
|---|---|
| Least Cost | cheapest termination price first, estimated with the tariff’s Avg. Call Duration |
| Prefix Length | longest matching prefix first |
| Route Preference | highest Preference of the route first |
| Routing Entries Order | lowest Order # first |
| Weighted Distribution | random, in proportion to the entries’ Weight |
A common wholesale setup is Least Cost alone; a quality-first setup is Route Preference → Least Cost. See Weighted distribution for how weights interact with the other policies.
Advanced Parameters
Section titled “Advanced Parameters”| Field | Meaning |
|---|---|
| Media Relay | Relay for the group’s calls; [ from Connection ] uses the connection’s own setting |
| Final 2xx Timeout, sec | How long the last entry may ring before the call fails, 300 by default. The other entries use the route’s 2xx Timeout. Must be above 0 |
| Enable LRN, LRN Translation Rule | Look up the ported number before routing and rewrite the result. See LRN dipping |
On-Net Routing
Section titled “On-Net Routing”Use Connection turns on calls between your own accounts: [ Default ] delivers them through the built-in registrar, a specific Vendor / Connection sends them to an external registrar, [ Disabled ] routes every call through the entries. With on-net routing on, Voicemail Connection chooses where unanswered calls go, On-Net Scope limits who can reach whom (All Accounts, Reseller and Sub-Resellers, Reseller Only), and Reply Timeout, sec, 1xx Timeout, sec and 2xx Timeout, sec apply to on-net legs. See On-net routing.
STIR/SHAKEN
Section titled “STIR/SHAKEN”Shown when the STIR/SHAKEN module is installed. Enabled makes the per-entry STIR/SHAKEN mode effective for attestation handling.
Delete a routing group
Section titled “Delete a routing group”Delete in the list removes the group after a confirmation. The button is hidden while anything is assigned to the group; move those accounts, customers and authentication rules to another group first.