Skip to main content

SMS

SMS configuration is split across three places:

  • System Preferences → Communication → SMS settings — general, system-wide SMS settings (below).
  • System Preferences → Communication → SMS routing — configuring SMS gateways and the routing plans that use them (below).
  • Namespace Editor → Features tab → SMS settings — per-namespace settings, including which routing plan a namespace's users use (see Namespace-level SMS settings).

SMS settings​

Core settings​

  • Enable SMS sending via REST API — enables or disables SMS message sending via the REST API, system-wide.
  • Gateway resiliency enabled — resubmits a message through a secondary gateway when the primary gateway fails, triggered by a delivery report indicating an error.
  • SMS content removal delay — removes the content of SMS messages after this delay, once they have expired. Defaults to Never.

Queue​

Shows any currently queued SMS messages. Pressing Flush queue attempts to send out any unsent messages.

Proxy settings​

A proxy can be enabled for all SMS-related outgoing traffic, configured with a proxy host and port.

Quota settings​

Restricts the number of messages that can be sent to a single mobile number, per hour and per day; each counter resets on its own schedule. Both default to unlimited.

Number patterns​

Number patterns define, via regular expression, mobile numbers that are not otherwise recognised by the system — for example when numbering plans change, or to identify numbers not supported for other reasons, such as machine-to-machine (M2M) numbers. Each pattern is scoped to a region (the country calling code) and matched against the national number, excluding the calling code and any leading zeros — for example, the national number extracted from (+358) 49123456789 is 49123456789, which a pattern such as 49\d{9} would match.

The system has a set of built-in patterns for common M2M and similar ranges; custom patterns can be added alongside them.

SMS routing​

Gateways​

The Gateways tab lists the configured SMS gateways — the external services Trivore ID sends SMS messages through. Each gateway's status can be tested by pressing the Start test button found on the leftmost side of its row.

SMS routing's Gateways tab, listing configured SMS gateways with a Start test button per row

Routing plans​

A routing plan binds one or more gateways to destination regions, so that Trivore ID knows which gateway (or gateways, load-balanced by priority and price) to use for a message to a given region. Each namespace uses exactly one routing plan (see Namespace-level SMS settings below) for all its outgoing SMS.

A routing plan can also restrict which phone numbers it will send to — for example, allowing only mobile numbers, or maintaining a whitelist of allowed numbers — and control how the message's originator address (sender ID) is validated or sanitised.

Namespace-level SMS settings​

A namespace's own SMS settings are configured in its Namespace Editor, under the Features tab's SMS settings section:

  • Enable SMS messages — whether any SMS messages, including system messages such as those required for two-factor authentication, can be sent from this namespace. Disabling it can break user sign-in and password reset flows that depend on SMS.
  • Enable custom SMS messages — whether custom, free-form SMS messages created by users (via the user interface or the REST API) can be sent from this namespace, independently of system messages.
  • Default region — the default region used for parsing and validating mobile numbers in this namespace.
  • Default originator — the default alphanumeric SMS originator address (sender ID) for this namespace.
  • SMS billing plan — which billing plan applies to SMS messages sent from this namespace.
  • Routing plan — which routing plan this namespace's messages use. A namespace has exactly one active routing plan at a time; changing it requires the SMS Admin permission.
Last updated on