SMPP Gateway
The SMPP Gateway bridges external SMPP peers to the messaging core. External applications and interworking partners — ESMEs (External Short Message Entities) — connect over SMPP either as clients the gateway dials out to or as servers the gateway accepts binds from, and the gateway carries their short messages to and from the SMSC. Each connection is an SMPP bind (transceiver, transmitter or receiver), and the gateway's job is to keep those binds up, authenticate and police them, and hand traffic on to the messaging core. OmniWeb surfaces the live bind status, the configured client and server peers, and the gateway's logs.
The SMPP Gateway is a per‑instance element page reached from the sidebar when one runs in the site's inventory, with a fleet view where several are deployed. All traffic goes through the OmniWeb backend proxy to the gateway's API, so it stays behind the single authenticated gateway. The documentation link in the page header (the in‑context help button) opens this page. It is organised into tabs.
Overview
A single‑screen health read: the aggregate bind statistics — the total number of binds and the connected / disconnected breakdown split across client (outbound) and server (inbound) binds. It is the quickest way to confirm the gateway is up and that its peers are bound, and to spot at a glance if any expected connection has dropped.
Bind Status
Every enabled bind — client and server — with its current connection status, the underlying session details and per‑bind metrics. This is the live view of who is bound right now. From here an operator can act on a bind:
- Drop an active bind — for a client bind this terminates the outbound connection; for a server bind it disconnects all active client connections. Use it to clear a stuck or misbehaving connection.
- Reconnect a client bind — forces a client (outbound) bind to redial its remote host, which is the quickest way to bring an outbound peer back after a network blip.
Client Peers
The configured outbound SMPP client connections — the peers the gateway dials out to. Each shows its name, the remote host and port, the system ID it binds with, and the bind type (transceiver, transmitter or receiver). Client peers are fully editable here: an operator can add a peer, edit an existing one (host, port, credentials, bind type, enquire‑link interval, TPS limit and the other bind parameters), and delete one that is no longer needed. Enabling a peer brings its outbound bind into service; disabling it takes the peer out without discarding its configuration.
Server Peers
The configured inbound SMPP server authorisations — the credentials and rules for peers that bind into the gateway. Each entry defines a system ID and password, the allowed bind types, and the guard rails that police an inbound bind: an IP whitelist of permitted source addresses and a source‑address whitelist of permitted originating‑address patterns, plus a TPS limit. Server peers are editable here in the same way — add, edit and delete — so an operator can onboard a new inbound partner, tighten its whitelists, or revoke it. Enabling and disabling an authorisation controls whether that partner is allowed to bind.
Logs
The Logs tab tails the gateway's live log output for troubleshooting a single gateway — bind failures, authentication rejects and dropped connections — without leaving OmniWeb.
Monitoring
Message rates, throughput and other time‑series for the SMPP Gateway are presented as Grafana dashboards, reached from the element page — OmniWeb does not duplicate those charts natively.
Related
- The SMSC is the messaging core the gateway hands short messages to and from.
- The IP‑SM‑GW carries SMS over IMS for VoLTE devices, complementing the SMPP path to external peers.