Detailed documentation for sections covered in this tutorial can be found at:

• Routing
• Advanced Routing
• Routes
• SMSC groups
• Services

Each customer SMPP account uses a service. The service has a routing profile that decides which supplier SMSC groups deliver each message. This tutorial walks through creating a routing profile, choosing a strategy, setting weights, checking a destination with the analyser, and using country default networks.

Before you start

Routing cannot deliver traffic until the supplier side is in place:

1. Add the supplier and SMSC connection (see the Suppliers tutorial).
2. Put the SMSC in an SMSC group.
3. For Net-RR, add coverage and costs for that group in Suppliers > Routes.

Then create the routing profile and attach it to a service in Configuration > Services.

Routing profiles

Go to the Routing section of the SSG Admin Portal.

The table lists each routing profile, its strategy, and behaviour flags. The lower table shows which services use each profile.

Routing profiles

Add a routing profile

Click Add routing profile.

Enter a name and an optional description.

Select the routing strategy:

• RR (Round-robin) — use all SMSC groups in the profile, regardless of destination network.
• Net-RR (Network round-robin) — use only SMSC groups that have the destination network in their coverage (Suppliers > Routes).
• Routing scripts — use a script to choose the SMSC. See Scripts.

Configure behaviour (described under each strategy below), then click Save.

Add routing profile

The new profile has no members yet. Open it in the routing editor (or expand it from the Routing page) to add SMSC groups.

Attach the profile to a service

A profile is used only when a service selects it.

1. Go to Configuration > Services.
2. Click New service (or edit an existing service).
3. Select the routing profile and a pricing plan.
4. Click Save.

Customer SMPP accounts that use this service will now route through the profile.

RR routing strategy

Use RR when every SMSC group in the profile can take any destination, or when you do not yet have network coverage loaded.

Configuring

1. Create or edit the routing profile and set Strategy to RR.
2. Open the routing editor for the profile.
3. Click Add member.
4. Select an SMSC group.
5. Set Weight (RR) (see below). If you leave the weight unset, the platform uses a weight of 1.
6. Click Save / Update.

Repeat for each SMSC group that should share traffic.

RR does not consult Suppliers > Routes when choosing an SMSC. Coverage and cost are still used for reporting, CDRs and margin, but not for SMSC selection.

Weights

Weights control the proportion of messages each SMSC group receives.

If a profile has two members with weights 3 and 1, about 75% of messages go to the first group and 25% to the second.

To change a weight, click the edit control on the weight cell in the routing editor, enter the new integer value, and save. The editor shows the resulting percentage next to each weight.

Net-RR routing strategies

Use Net-RR when different suppliers cover different networks and you want each destination to use only the groups that can reach it.

Configuring

1. Confirm each SMSC group has coverage (and costs) for the networks it can serve. Add or upload these in Suppliers > Routes.

2. Create or edit the routing profile and set Strategy to Net-RR.

3. Set the Net-RR behaviour flags:

   • Net-RR: RR fallback — if the mobile's network is not in the profile's coverage, fall back to RR across all members.
   • RR unknown net — if the network of the MSISDN cannot be identified, use RR.
   • Use default networks — if there is no coverage for the identified network, use the country default network route (see Default networks).

4. Optionally enable:

   • MSISDN cache — look up the network from Configuration > Routing > MSISDN cache.
   • MSISDN block / Prefix block — apply the lists in Configuration > Firewall.

5. Click Save.

6. In the routing editor, click Add member and select each SMSC group that should participate.

Weights

Net-RR weights are per destination network, not a single weight for the whole group.

For a given mobile network:

1. The SMSC group must already have coverage for that network in Suppliers > Routes.
2. In the routing editor, find the network row for that SMSC group.
3. Set the Network weight. If no weight is set, the platform uses 1.
4. The editor shows the percentage of that network's traffic the group will receive.

To apply the same weight to every network in a country for one SMSC group, use Set weight for all networks (same SMSC group & country) in the editor.

Note: Net-RR will not offer an SMSC group for a network unless that group has coverage defined and is a member of the profile.

Routing analyser

Use Routing > Analyser to see how a message to a specific mobile number will be routed for a customer's SMPP account.

Routing analyser

1. Go to Routing > Analyser.
2. Enter the destination MSISDN (digits only, international format without +).
3. Select the customer and the SMPP account (system ID).
4. Click Analyse.

The analyser checks routing, pricing and the customer's account. It highlights problems (for example missing coverage, missing price, or insufficient balance) and shows which SMSC groups are eligible.

Use the analyser whenever:

• a customer reports that submits are rejected
• you have changed routes, weights or a pricing plan
• you are confirming that a new SMSC group is in path for a destination

Default networks

Each country has a default network entry (shown as [DEFAULT <MCC>] in Suppliers > Routes).

Set a cost (and therefore coverage) on the default network when:

• you have a country-wide rate from the supplier rather than per-network rates, or
• you want a fallback cost and route when the specific mobile network is unknown or has no row.

The default network cost is used as the message cost in CDRs and Status > Message lookup when no network-specific cost exists, even if Use default networks is not enabled on the routing profile.

Use default networks on a Net-RR profile additionally allows the default-network route to be selected for delivery when the mobile's network has no coverage.

Inbound (MO) SMS

To deliver inbound SMS to a customer account, configure Routing > Inbound SMS:

• Match specific MSISDN — route one number to one SMPP account. Click Add MSISDN.
• MSISDN matches pattern — route a range of numbers using an ECMAScript regular expression. Click Add pattern.
• Content matches pattern — route by message content.

Lists can be imported and exported, and selected rows can be reassigned or deleted in bulk.

To send MO SMS to a customer's HTTP URL instead of (or as well as) SMPP, configure the MO webhook on the SMPP account. See SMPP accounts — Webhooks.

Troubleshooting

If the issue remains, contact Support with:

• Error code (command status) received by the customer, if any
• Screenshot of Routing > Analyser for the example MSISDN and SMPP account
• Screenshot of the routing editor for the profile associated with that account

Further detail, including a routing flowchart, is in Advanced Routing.