-
Notifications
You must be signed in to change notification settings - Fork 40
MySQL: smpp_route column meanings
Kurt Neo edited this page Apr 12, 2017
·
6 revisions
| column | meaning |
|---|---|
| route_id | Not used by ksmppd, just useful primary key for a route |
| direction | 1 = Outbound (to process submit_sm PDUs), 2 = Inbound (MO's from bearerbox) |
| regex | Regular expression to match for this route (see examples below) |
| cost | Cost of this route (used in prepaid billing) |
| system_id | System-id this route belongs to (source for MT, target for MO) |
| smsc_id | Target SMSC ID for outbound routes |
| source_regex | If the receive regex matches this regex is checked as well to ensure allowed sender. Leave blank/null for any sender |
| priority | Order in which routing will execute, higher numbers execute first |
Example regular expressions:
^(1800) - any number that starts with 1800
^(1800|1900) - any number that starts with 1800 or 1900