On this page
SMPP provider gateways
Configure outbound provider connections and diagnose bind failures.
Match the provider contract#
Create a gateway in SMPP Gateways. A reachable TCP port alone does not establish a working SMPP bind. The system ID, password, system type, bind mode and permitted source IP must match the provider.
Connection settings#
| Field | Use |
|---|---|
| Description | Recognizable provider and route label |
| IP / port | Provider destination; default client-mode port is 2775 |
| Connect mode | Outgoing client connection or configured server-side mode |
| IP authentication | Enforce the mode's configured IP identity checks |
| Username / password | Provider bind identity; password validation is 3–8 characters |
| TON / NPI | Address type and numbering plan expected by the provider |
| DLR timeout | Receipt timeout in minutes, not a throughput or concurrency limit |
| Server outbound command | deliver_sm or the configured server-mode command |
| Enabled | Whether the gateway can participate |
Verify bind state#
After enabling a prepared connection, inspect Bind and Bind error. A network timeout points to reachability or firewall configuration; an SMPP bind rejection points to the provider contract. Confirm the exact provider error code before retrying.
Route membership#
A direct client can select this gateway. A routing-group client needs the gateway added to its group. An enabled gateway without a matching selection does not automatically receive every submission.
Maintenance#
Disable a gateway before retiring it. Check group membership and clients assigned directly to it. Compare outgoing message IDs and final receipts in CDRs when investigating provider behavior.
Screenshots show fictional data from the public demo. Your instance may have different records and permissions.