---
title: Routing groups and route testing
url: https://help.telecomsxchange.com/buyers/routing-groups-and-route-testing/
audience: For Buyers
summary: "Go to Routing \u2192 Routing Groups, click Add New Routing Group, pick a\
  \ policy, then add your purchased routes to the group. Dial the group's 444 tech\
  \ prefix and the group picks the route for each call."
updated: '2026-10-23'
verified_commit: 83b4ebc96d0081a25213776d5a8871bd04941125
---

# Routing groups and route testing

> Go to Routing → Routing Groups, click Add New Routing Group, pick a policy, then add your purchased routes to the group. Dial the group's 444 tech prefix and the group picks the route for each call.

## How a routing group picks a route

1. **Your call**: Dialed with the group's tech prefix
2. **Routing rules** (via `444101#447700900123`): First CLD or CLI prefix match wins
3. **Routing policy** (via rule or group default): LCR, Failover Order or Load Balancing
4. **Purchased route** (via chosen route): Failover stops on a hunt stop code

When you've bought more than one route to a destination, a routing group chooses between them for each call. You dial one tech prefix and the group's policy does the rest.

## Before you start

- [Buy at least one route](https://help.telecomsxchange.com/buyers/find-and-buy-routes/). A group can only use routes you have purchased.
- Log in as the main user or a default-role web user. Finance-role web users don't see **Routing Groups**.

## What is a routing group?

A routing group puts several of your purchased routes behind one tech prefix. Group prefixes are `444`, three random digits and `#`, for example `444101#`. Dial `444101#447700900123` and the group decides which route carries the call.

![The Routing Groups list with each group's tech prefix, sellers, entries, rules, policy and type](https://help.telecomsxchange.com/assets/screenshots/buyer-routing-groups.jpg)

The list shows each group's **Group Name**, **Tech Prefix**, **Sellers** (hover to see their names), **Entries**, **Rules**, **Policy** and **Type** (Voice or SMS). A group without routes shows **0 — no routes** under **Entries**.

## How do I create a routing group?

1. Go to **Routing → Routing Groups** and click **Add New Routing Group**.
2. Under **Protocol**, choose **Voice (SIP)** or **SMS (SMPP)**. You can't change this later.
3. Enter a **Name**.
4. Choose a **Routing Policy** (see the list below). **Least Cost Routing** is preselected; **AI Smart Routing (IDR)** is shown as coming soon and can't be chosen yet.
5. Click **Add Routing Group**.

The new group appears in the list with its own `444…#` tech prefix and 0 entries. Add routes before you use it.

These are the routing policies:

- **Least Cost Routing (LCR)**: tries the cheapest route first, then fails over to the next lowest cost.
- **Failover Order**: calls always start at route #1 and move down your order.
- **Load Balancing**: splits traffic by weight. Weights 1 and 3 send about 25% and 75% of calls.

## How do I add routes to a group?

1. In **Routing → Routing Groups**, click the cogwheel in the group's **Action** column. The group page shows its tech prefix at the top with a copy button.
2. Under **Your Purchased Routes**, click a route, or drag it into the group. Use the search box to find a route or seller.
3. Arrange the routes for the policy:
    - **Failover Order**: use the up and down arrows. The first route is **Primary**, the next are **Failover 1**, **Failover 2** and so on. A new route is added at the end.
    - **Load Balancing**: type a weight from `1` to `100` and click **Set**. You'll see "Weight updated successfully" and each route's share of traffic.
    - **Least Cost Routing**: no order needed. Each route shows **auto**.

You'll see the message "Route added to this group", and the route is listed under **Active in Routing Group**. To take a route out, click its remove icon and confirm; you'll see "Route removed from this group".

!!! warning
    A group with no routes can't carry calls. Everything sent with its tech prefix fails until you add a route, so don't remove the last route from a group that has traffic. Removing the last route asks you to confirm that calls sent with the group's tech prefix will fail.

To change the name, policy or hunt stop codes, edit them under **Settings** and click **Save Changes** or **Save & Close**. Switching to Failover Order numbers the routes 1 to N; switching to Load Balancing resets every weight to 1.

**Hunt stop codes** (voice groups and voice rules) are SIP codes from 400 to 699 that stop failover to the next route. They sit in a collapsed **Hunt stop codes** row under the policy; open it to type codes separated by commas or click the chips **486 Busy**, **404 Not Found**, **603 Decline** and **604 No Such User**. New voice groups start with `486,404,604`. Codes outside 400 to 699 are dropped when you save.

## How do I route specific dial codes differently?

Routing rules override the group's default routing for particular dial codes (CLD prefixes), callers (CLI prefixes) or both. Each rule has its own routes, policy and hunt stop codes. One group can, for example, send most traffic by LCR, send UK mobiles (`447`) by Failover Order across two premium routes, and send calls without caller ID somewhere else. Rules are available in voice groups.

The group page is split into two parts, with jump links at the top: **Default routing**, which applies to every call sent with the group's tech prefix that doesn't match a rule, and **Routing rules · overrides**.

![A routing group's Routing rules section with the prefix filter, the Add Rule button and three rules: CLD 447 on Failover Order, CLD 44 on LCR, and CLI EMPTY with no routes yet](https://help.telecomsxchange.com/assets/screenshots/buyer-routing-rules.jpg)

### How is a call matched to a rule?

- **CLD** is the dialled number after the group's tech prefix, in E.164 without `+` or `00`. A call to `444101#447700900123` is matched on `447700900123`, so the CLD prefix `447` matches it, and so do `44` and `4477`.
- **CLI** is the caller ID as your switch sends it. `EMPTY` matches calls that arrive without caller ID. Send caller IDs in E.164 without `+`, or a digit prefix won't match.
- A rule with both prefixes matches only calls where both match. A rule with only one prefix ignores the other.
- Rules are checked in **Priority** order, from 1 down, and **the first match wins**. It is not the longest match, so put specific prefixes above broader ones: `447` above `44`, or the UK mobile rule never sees a call.
- A call that matches a rule uses only that rule's routes, policy and hunt stop codes. It never falls back to the group's default routing, so give every rule its routes before you send traffic.

| Rule | CLD prefix | CLI prefix | Catches |
|---|---|---|---|
| UK mobiles | `447` | | Every call to a UK mobile number |
| All UK | `44` | | Every other UK call (keep it below `447`) |
| One caller to Germany | `49` | `14165551234` | Calls to Germany from that caller ID only |
| No caller ID | | `EMPTY` | Calls sent without a caller ID |

### How do I add a rule?

1. Open the group from **Routing → Routing Groups** and click **Routing rules** at the top, or scroll to it.
2. Click **Add Rule**. The **Add a routing rule** window opens.
3. Enter a **CLD (Destination) Prefix**, a **CLI (Caller) Prefix**, or both: digits only, up to 15. For the CLI you can also enter `EMPTY`.
4. Click **Add Rule** in the window, or **Cancel** to close it.

![The Add a routing rule window with CLD (Destination) Prefix 49, an empty CLI (Caller) Prefix, and the Cancel and Add Rule buttons](https://help.telecomsxchange.com/assets/screenshots/buyer-routing-rule-add.jpg)

The rule is added at the bottom of the list (lowest priority), and the portal opens it straight away so you can give it routes.

### How do I set up a rule's routes and policy?

A rule's page says which calls it handles: **Routing rule in** the group, **Calls matching CLD 447**. It has the same parts as a group: **Rule settings** with the two prefixes, the **Routing Policy** and the **Hunt stop codes**, then the routes.

1. Add routes from **Your Purchased Routes**, as for a group.
2. Choose the policy. New rules start with **Least Cost Routing**; pick **Failover Order** or **Load Balancing** if the rule needs it.
3. Change the prefixes or the hunt stop codes if needed, then click **Save Changes**, or **Save & Close** to go back to the group.

![A routing rule's page: Back to Routing Group UK-LCR, Calls matching CLD 447, the CLD and CLI prefix fields, the routing policy cards with Failover Order selected, and the hunt stop codes](https://help.telecomsxchange.com/assets/screenshots/buyer-routing-rule.jpg)

Click **Back to Routing Group** to return to the group.

### How do I manage rules?

The **Routing rules** table on the group page lists each rule's **Priority**, **CLI**, **CLD**, **Policy** and **Sellers**. A dash means that prefix isn't used.

- **Sellers** shows how many sellers the rule's routes use; hover to see their names and the route count. **No routes yet — add** means matching calls have nowhere to go: click it to add routes.
- **Edit rule** opens the rule.
- The up and down arrows change its priority ("Routing Rule moved up" / "Routing Rule moved down").
- The bin deletes it after you confirm ("Routing Rule deleted"). The rules below it move up.
- With many rules, type a CLD or CLI prefix in **Filter rules by prefix (CLD or CLI)** to show only the matching rules.

Two rules in a group can't have the same CLD and CLI pair. `44` and `447` are fine, but a second `44` rule isn't.

!!! tip
    A common setup: the group's default routing on **LCR** for everyday traffic, plus a rule for your premium destination prefix on **Failover Order** across your two best routes.

## How do I use a routing group for SMS?

An SMS (SMPP) group works like a voice group: send messages with its `444…#` tech prefix. To use the group without a prefix:

1. Click **Accounts** in the sidebar, open the SMPP account's **Actions** menu and choose **Edit Account**.
2. Under **Default Routing Group**, choose the group. The default is **NOT SET (Use direct route from purchased routes)**.
3. Click **Update Account**.

Messages sent from that account without a tech prefix now go through the group. Choosing a group clears any **Default Route** set in the account's purchased routes list, and clicking **Make Default** on a purchased route there resets **Default Routing Group** to **NOT SET**. See [send SMS](https://help.telecomsxchange.com/buyers/send-sms/) for the SMPP side.

## How do I test a route?

**Routing → Route Test** opens the **Web Callback Service**. TelecomsXchange calls your phone first, then connects you to the destination, each leg through a route you choose.

1. Go to **Routing → Route Test**.
2. Under **First Call Leg**, enter **Your Phone Number**, the **CLI (Caller ID)** to show, and choose **Seller Route 1**.
3. Under **Second Call Leg**, enter the **Destination Number**, its **CLI (Caller ID)**, and choose **Seller Route 2**.
4. Choose the **Billing Account**. The list shows each account's balance. It must have purchased both routes.
5. Click **Initiate Callback**. **Clear Form** empties the fields.

![The Web Callback Service with both call legs and the billing account filled in, and the Recent Callback Requests list](https://help.telecomsxchange.com/assets/screenshots/buyer-route-test.jpg)

You'll see "Test call has been initiated". Your phone rings within a few seconds, for up to 120 seconds, from "TelecomsXchange" with the CLI you entered; when you answer, the destination is called, and you can judge audio quality and caller ID delivery. Each test is listed under **Recent Callback Requests** with its **Account**, **Your Number / CLI**, **Route 1**, **Destination / CLI**, **Route 2**, **Callback Time** and **Status** (**initiated**, or **failed** if the first leg could not be placed).

[HLR Lookup](https://help.telecomsxchange.com/buyers/hlr-lookup/) checks whether a mobile number is valid and which network it belongs to. This helps when you investigate failed calls.

## What if something goes wrong?

| You see | What to do |
|---|---|
| Please enter a name for the routing group. | Type a name before you save. |
| A routing group with this name already exists - choose a different name. | Use a name you haven't used for another group. |
| You can only add routes you have purchased in the Market. | Buy the route first, then add it. |
| This route is already in this group. | The route is in the group already. Pick another one. |
| Weight must be a whole number between 1 and 100. | Enter a weight from `1` to `100`. |
| Enter at least one prefix: CLD (destination) or CLI (caller). | Fill in at least one prefix for the rule. |
| CLD prefix may contain digits only. | Remove spaces, `+` and letters from the CLD prefix. |
| CLI prefix may contain digits only, or the special value EMPTY. | Remove spaces, `+` and letters, or enter `EMPTY`. |
| A prefix can be at most 15 digits. | Shorten the prefix. |
| A rule with this CLD/CLI prefix already exists in this group. | Open the existing rule instead, or change one of the prefixes. |
| No rules match that prefix. | Clear the **Filter rules by prefix** box to see all rules. |
| Calls to a dial code use the wrong routes | A broader rule above it matched first. Move the more specific rule up (for example `447` above `44`). |
| Calls matching a rule fail | The rule has no routes (**No routes yet — add** in the table), or all of its routes failed. A matched call never falls back to the default routing: add routes to the rule. |
| A CLI rule never matches | Your switch sends the caller ID with `+` or a national format. Send it in E.164 without `+`, or match on CLD instead. |
| rouing group not found | The **Default Routing Group** you chose for the SMPP account no longer exists. Pick another group or **NOT SET**. |
| Selected account does not have a purchased for selected route(s), please choose other combination or purchase selected route(s) on this account | Choose a billing account that bought both routes, or buy them on that account. |
| CLD format error | Enter both phone numbers as digits only. |

## Frequently asked questions

**Q: What routing policies can a group use?**

A: Least Cost Routing (LCR) tries the cheapest route first. Failover Order always starts at route #1 and moves down your order. Load Balancing splits traffic by weight, so weights 1 and 3 send 25% and 75% of calls.

**Q: What are hunt stop codes?**

A: SIP response codes from 400 to 699 that stop failover to the next route. New voice groups start with 486, 404 and 604. Voice routing rules have their own hunt stop codes.

**Q: Can I add a route I haven't bought?**

A: No. A routing group only accepts routes you have purchased in the market, of the same type as the group (voice or SMS).

**Q: How do routing rules work?**

A: A rule matches a CLD (destination) prefix, a CLI (caller) prefix or both, and has its own routes, policy and hunt stop codes. Rules are checked in priority order and the first match wins; calls that match no rule use the group's default routing.

**Q: Can I route one dial code differently inside a routing group?**

A: Yes. Add a routing rule with that CLD prefix, for example 447 for UK mobiles, and give it its own routes and policy. The CLD is the number after the group's tech prefix, so 444101#447700900123 matches 447.

**Q: Does a call fall back to the default routing if a rule's routes fail?**

A: No. A call that matches a rule uses only that rule's routes. Give every rule its routes, and put more specific prefixes (447) above broader ones (44).

**Q: Can SMS use a routing group without a prefix?**

A: Yes. Open the SMPP account from Accounts → Edit Account and choose the group under Default Routing Group. Messages sent without a tech prefix then go through that group.

**Q: How do I test a route before sending traffic?**

A: Use Routing → Route Test. TelecomsXchange calls your phone through one route, then connects you to the destination through another, so you can hear the call yourself.