Product family 4 of 6 · Enterprise SMPP gateway / A2P SMSC gateway
Guardivia Enterprise SMPP SMSC Gateway
Multi-tenant SMPP messaging, routing, customer management, delivery optimisation and embedded ESME security for aggregators, CPaaS providers and enterprises.
Enterprise message path
Architecture viewInputs
EnterpriseAggregatorResellerGuardivia processing
Outputs
Upstream SMSCDLR / reportOn this pageOverview
Product overview
Guardivia Enterprise SMPP SMSC Gateway is a multi-tenant SMPP messaging platform that manages ESME customer accounts, routes their traffic across multiple upstream SMSC connections, optimises delivery, enforces delivery receipts, resends failed traffic and applies an embedded ESME firewall. It serves SMS aggregators, CPaaS providers, MVNOs, enterprises, banks, fintechs, government messaging platforms, bulk providers, OTT and application providers and resellers. It is an SMPP and application messaging platform, not a native SS7 operator SMSC.
What is Guardivia Enterprise SMPP SMSC Gateway?
Guardivia Enterprise SMPP SMSC Gateway is a multi-tenant SMPP messaging platform for aggregators, CPaaS providers, MVNOs and enterprises. It manages ESME accounts and binds (TX, RX, TRX), routes traffic across upstream SMSC groups by country, operator, prefix, sender or account, enforces delivery receipts, resends failed messages by filter, monitors delivery quality and applies an embedded ESME firewall with AI-assisted content classification.
What is the difference between the Enterprise SMPP SMSC Gateway and the Operator SMSC?
The Guardivia Enterprise SMPP SMSC Gateway is an application-side platform: it manages SMPP customers and routes their traffic to upstream SMSCs and suppliers. The Guardivia Operator SMSC is a network-side message centre that terminates SS7/MAP, SIGTRAN and IMS signaling and delivers directly to subscribers. Aggregators typically deploy the gateway; operators deploy the SMSC, often with the gateway in front of it.
Last reviewed 2026-09-12 by the Guardivia QoS Engineering Team. Product facts on this page describe current capabilities; items marked “where supported”, “optional”, “integration” or “consultancy” are confirmed per deployment.
Target customers
- SMS aggregators and wholesale messaging providers
- CPaaS providers offering SMS APIs
- MVNOs offering enterprise messaging
- Enterprises, banks, fintech companies and government messaging platforms with direct SMPP binds
- Bulk-messaging providers, OTT and application providers, and resellers
Problems solved
- Customer binds, routes and supplier connections are managed in separate tools with no unified policy.
- Route quality changes hourly; failed traffic is not automatically rerouted or resent.
- Delivery receipts are inconsistent across suppliers, obscuring true delivery performance.
- OTP abuse, promotional and political content and international sender-ID misuse expose the provider to operator blocks.
- Resellers and sub-accounts need isolation, per-user routing and per-user reporting.
Business outcomes
- One platform for ESME accounts, upstream SMSCs, routing, DLRs and reporting.
- Higher delivery rates through quality monitoring, intelligent rerouting and targeted resending.
- Policy enforcement on every bind through the embedded ESME firewall.
- Reseller hierarchies with per-user policies, routing and reports.
- Direct engineering control over binds, throttling and routing behaviour.
Key capabilities
SMPP customer management
ESME account creation, system IDs, secure passwords, source-IP whitelisting, dedicated ports, expiry, block/unblock, roles and activity logs.
Upstream SMSC and route management
Multiple supplier SMSCs, TON/NPI controls, enforced DLR, TPS throttling, SMSC groups with percentage distribution and country/operator/prefix/sender/account routing.
Delivery optimisation
HLR-assisted routing, intelligent rerouting, delivery-quality routing, automatic failover and traffic holding when quality falls below policy.
Resend engine
Targeted resending by message-ID range, user, date range, country, operator, error and message status, with rerouting to a new SMSC.
Embedded ESME firewall
Sender, content and prefix rules, regex and multilingual keyword filtering, OTP-spam and repeated-OTP control, international sender-ID restrictions and AI-assisted classification.
Performance monitoring
Delivery-rate thresholds per SMSC, operator or sender with email, SMS and webhook alerts and optional automatic traffic hold.
Detailed feature groups
Every supported capability is listed under its correct product. Nothing is omitted for brevity.
SMPP and customer management
- SMPP client and server connectivity
- ESME account creation with system-ID and secure password management
- Source-IP restriction and whitelisting; dedicated account ports
- Account expiration; account blocking and unblocking
- Admin and normal-user roles; reseller administration
- User activity logs; multi-tenancy
- Per-user policies, per-user routing and per-user reporting
- Bind transmitter, bind receiver and bind transceiver (TX, RX and TRX modes)
- Manual bind, unbind and rebind; bind-status monitoring; bind-failure alerts
- SMPPS/TLS where supported
SMSC and route management
- Multiple upstream SMSC connections and SMSC vendor management
- System type; TON and NPI controls (STON, SNPI, DTON, DNPI) with enforce or default modes
- Enforced DLR; hexadecimal response options where supported
- Configurable TPS and throttling per connection
- SMSC grouping with percentage-based traffic distribution; load balancing and redundancy
- Country-based, operator-based, prefix-based, sender-based, account-based and SMSC-group routing
- HLR-assisted routing with a designated HLR lookup connection
- Intelligent rerouting and delivery-quality-based routing
- Cost-based routing where supported
- Automatic failover and traffic holding when route quality falls below policy
Messaging and delivery functions
- A2P messaging; P2A messaging where supported
- Enterprise and bulk messaging; OTP and 2FA; transactional; campaign traffic
- Message submission and queue management
- Message status tracking and delivery receipts; DLR enforcement
- Retry management
- Targeted message resending and rerouting of failed messages
- Resending by message-ID range, user, date range, country, operator, error and message status
Embedded ESME firewall
- Sender-pattern, content-pattern and prefix rules with block and allow actions
- Global rules and user-specific rules
- Regex filtering and multilingual keyword filtering
- OTP-spam detection and repeated OTP control (threshold of messages, window, distinct-destination ratio, block duration)
- International sender-ID restrictions and sender-ID variation detection
- Promotional and political-content controls; spam and phishing filtering
- AI-assisted content classification with Verified Content AI levels per user
- User-specific security profiles
- HLR-enabled verification per account
- Regulatory-policy enforcement
Performance monitoring and reporting
- Delivery-rate thresholds with minimum-submission thresholds and monitoring windows
- Sender-specific, operator-specific and SMSC-specific monitoring
- Delivered and failed-status monitoring
- Email, SMS and URL/webhook alerts; optional automatic traffic hold
- Submitted, processed, delivered, pending, failed and blocked KPIs
- SMSC errors, user errors and per-user error percentages
- Rule-block and AI-block statistics
- Customisable dashboard widgets with bar and pie visualisations, filtered by user and SMSC
- Advanced reports by user, date, destination, message ID, SMSC and block name, with optional AI-content detail
- CSV, PDF and Excel reports
Supported protocols and interfaces
| Protocol / interface | Role | Status |
|---|---|---|
| SMPP v3.4 | Customer binds and upstream SMSC connections | Verified capability |
| SMPP v5.0 | Where supported by the peer | Where supported |
| SMPPS/TLS | Encrypted binds | Where supported |
| HTTP / REST | Application submission, DLR callbacks, administration | Verified capability |
| HLR lookup | Routing verification through a designated lookup connection | Verified capability |
| SMTP, SMS, webhooks | Alerts | Verified capability |
Swipe horizontally to view all columns.
Architecture
ESMEs (enterprises, aggregators, resellers) bind to the gateway's SMPP server over TX, RX or TRX sessions. The account layer authenticates each bind, applies IP restrictions, security profiles and throttling. The embedded ESME firewall evaluates each submission against global and user rules and the AI content classifier. The routing engine selects an upstream SMSC or SMSC group by country, operator, prefix, sender or account, optionally consulting HLR lookup, and applies percentage distribution within the group.
The delivery layer manages queues, retries and DLR enforcement, feeds performance monitors and exposes the resend engine. Dashboards, reports and alerts are served from the same event store.
Text description of this diagram
Enterprise SMPP SMSC Gateway architecture: enterprises, aggregators and resellers bind over SMPP TX/RX/TRX to the account and security layer; submissions pass the embedded ESME firewall and AI classifier; the routing engine selects an upstream SMSC group (with percentage distribution and HLR-assisted lookup); the delivery layer tracks DLRs, retries and resends; dashboards, reports and alerts consume the event store.
Submission-to-delivery workflow
- 01
An ESME binds (TX, RX or TRX) with its system ID, password, allowed source IP and dedicated port.
- 02
A submit_sm is checked against the account's throttling, expiry and security profile.
- 03
The embedded ESME firewall applies sender, content, prefix, regex, OTP and AI rules: allow or block.
- 04
The routing engine selects the route by country, operator, prefix, sender or account, optionally after HLR lookup, and picks an SMSC within the group by percentage.
- 05
The message is submitted upstream with enforced TON/NPI and DLR settings; status is tracked.
- 06
Performance monitors compare delivered and failed ratios against thresholds; alerts fire and traffic can be held automatically.
- 07
Failed traffic is rerouted or resent by message-ID range, user, date, country, operator, error or status.
- 08
Dashboards and CSV, PDF and Excel reports summarise the outcome per user and SMSC.
Integrations
Integration types are stated explicitly. Custom integrations are delivered by Guardivia’s in-house QoS Engineering Team, not by an external vendor. See the full integration catalogue.
| System | Detail | Type |
|---|---|---|
| Upstream SMSCs and suppliers | SMPP v3.4/v5.0 connections with per-SMSC settings | Native integration |
| Guardivia Operator SMSC | Direct SMPP bind for operator termination | Native integration |
| HLR lookup providers | Designated lookup connection for routing verification | Standards-based |
| Customer applications | SMPP and HTTP/REST with DLR callbacks | Native integration |
| Alerting | Email, SMS and webhook endpoints | Standards-based |
| Billing and reconciliation | Report export; custom exports by the QoS Engineering Team | Custom (in-house engineering) |
Swipe horizontally to view all columns.
Security controls
- Per-account source-IP whitelisting, dedicated ports and expiry
- SMPPS/TLS where supported
- Role separation between admin (reseller) and normal users
- User activity logs
- Embedded ESME firewall on every submission
Management functions
- User management with HLR status, role, port, IP, status and Verified Content AI level per account
- SMSC management: bind, unbind, rebind, edit connection, TON/NPI settings, alert settings
- SMSC group management with percentage members totalling 100%
- Network configuration: country code, operator, MCC, MNC and prefix lists
- Routing administration by user, country and operator with HLR SMSC selection
Monitoring and reporting
- Dashboard: message status, user message status, SMSC errors and types, user errors, error percentage, rules blocked and users blocked
- SMSC performance alerts by SMSC, operator, sender, percentage, minimum submissions, status and duration
- Delivery summary: submitted, processed, delivered, pending, other; firewall blocks, AI blocks and breakdowns
- Advanced delivery reports with CSV, PDF and Excel export
High availability
- Redundant gateway nodes
- SMSC groups for supplier redundancy
- Automatic failover and traffic holding
Scalability
- Per-connection TPS controls
- Horizontal addition of gateway nodes
- Multi-tenant partitioning for resellers
Deployment options
- Linux on bare metal, virtual machines or validated cloud
- Standalone, or in front of the Guardivia Operator SMSC
- Hosted or managed options
Use cases
Aggregator hub
Hundreds of customer binds routed across supplier SMSCs with percentage distribution, quality monitoring and automated resends.
Bank OTP delivery
Dedicated binds with enforced DLRs, HLR-assisted routing and repeated-OTP protection.
Reseller platform
Admin (reseller) accounts manage their own users, routes and reports in isolation.
MVNO enterprise messaging
The gateway fronts the Operator SMSC so enterprise customers connect over SMPP with policy enforcement.
In-House Engineering Advantage
Owned end to end by the Guardivia QoS Engineering Team
Binds, routing, throttling, customer management, delivery optimisation and firewall policies are all under the direct control of Guardivia's engineers.
- Supplier-specific SMPP quirks are handled in the gateway code, not worked around in configuration.
- New routing criteria or report layouts are added on request.
- Firewall rule types and AI classification levels evolve with customer traffic.
- Performance monitors and alert channels are extended internally.
Scope and limitations
Stated plainly so that buyers, engineers and AI assistants describe this product accurately.
- The gateway does not terminate SS7/MAP signaling; operator termination is provided by the Guardivia Operator SMSC or upstream suppliers.
- P2A, SMPPS/TLS, SMPP v5.0, hexadecimal responses and cost-based routing are marked where supported.
- Throughput figures are established by sizing per deployment.
Frequently asked questions
Is this the same as the Operator SMSC?
No. The Enterprise SMPP SMSC Gateway manages application customers and routes their traffic to upstream SMSCs; the Operator SMSC is the network-side message centre with SS7/MAP and IMS signaling.
How does resending work?
Operators filter messages by user, message-ID range, date range, country, operator, error or status, select a target SMSC and submit; the gateway reprocesses the selection.
Can the gateway hold traffic automatically?
Yes. A performance alert can be configured with a delivery-percentage threshold, minimum submissions and window; when breached it notifies by email, SMS or URL and can hold traffic until reviewed.
What does the repeated-OTP feature do?
It counts OTP-like messages per source within a window and compares the share sent to distinct destinations against a threshold; sources below the threshold are blocked for a configurable period.
Does it support resellers?
Yes. Admin (reseller) accounts manage their own users, routing and reports within a multi-tenant environment.
Can Guardivia customise routing or reports?
Yes. Because the gateway is developed in house, routing criteria, report layouts and alert channels can be extended by the QoS Engineering Team.
Request a demo of Guardivia Enterprise SMPP SMSC Gateway
Demos are run by the engineers who develop the product, using your protocols and integration points.