# Hosted SMSC at carrier scale for MVNOs, operators and enterprises. - Canonical URL: https://www.broadnet.me/operators/smsc-gateway - Language: en - Last updated: 2026-10-20 - Publisher: BroadNet (https://www.broadnet.me) - Markdown version of the page above, generated from the rendered page. SMSC Gateway · Hosted multi-tenant Multi-language hosted SMSC with 1,000+ direct operator connections, unlimited SMS connections, advanced user management, and detailed reporting. Full SMS infrastructure — without the CAPEX, the hardware, or the 24/7 operations team. Deployed at enterprises and operators across MENA, backed by a 99.99% SLA. [Request SMPP connectivity](https://www.broadnet.me/contact?topic=smpp-connectivity&product=smsc-gateway) [Discuss bind requirements](https://www.broadnet.me/contact?topic=bind-requirements&product=smsc-gateway) GSMA Associate Member ISO 27001 30,000 SMS/sec per node ![The BroadNet snow leopard beside a hosted messaging core where message streams converge and fan out](https://www.broadnet.me/marketing/art/op-smsc-gateway.webp) BroadNet · SMSC gateway Carrier messaging core 30,000 SMS/sec per node 1,000+ operator connections 99.99% SLA In production ## A core measured in nines, not features. Built on the same messaging infrastructure BroadNet has run for Google, Meta, and Uber since 2003 — now a multi-tenant hosted SMSC for enterprises and operators across MENA, with a 99.99% SLA and no CAPEX. THROUGHPUT 30,000 SMS per second per node, sustained UPTIME 99.99% hosted SLA, credit-backed CONNECTIVITY 1,000+ direct operator interconnects REACH 200+ countries covered How traffic flows ## From SMPP bind to operator handset, in 5 hops. One SMSC core, five named stages. Every submit_sm is queued, deduped, lane-scored, charged, and forwarded across SS7 to the destination MSC — with sub-second median end-to-end on direct interconnects. 1. 01 · Bind Customer SMPP Enterprise senders and aggregators connect over SMPP 3.4 / 5.0 binds (TX/RX/TRX) with TLS. HTTP submit also supported. TLS bind < 80ms 2. 02 · Core SMSC core Submit_sm queued, deduped, content-screened. Store-and-forward up to 72h. Active-active across geo-redundant nodes. queued · deduped 3. 03 · Route Routing engine Five-lane policy: Direct, Premium, Partner, Fallback, Greylist. Cost · quality · SLA per destination. decision < 50ms 4. 04 · Egress Operator SS7 SIGTRAN M3UA or SMPP egress to the destination MSC / SMSC. MAP MT-ForwardSM with SRI-SM cache. MT submit < 800ms 5. 05 · Charge CDR · OCS Per-message CDR / EDR streamed to Kafka, file, or REST. OCS / OFCS hook for prepaid balance & refund. CDR < 30ms 6. ← DLR · CDR · OCS refund 01 · Bind Customer SMPP Enterprise senders and aggregators connect over SMPP 3.4 / 5.0 binds (TX/RX/TRX) with TLS. HTTP submit also supported. TLS bind < 80ms 02 · Core SMSC core Submit_sm queued, deduped, content-screened. Store-and-forward up to 72h. Active-active across geo-redundant nodes. queued · deduped 03 · Route Routing engine Five-lane policy: Direct, Premium, Partner, Fallback, Greylist. Cost · quality · SLA per destination. decision < 50ms 04 · Egress Operator SS7 SIGTRAN M3UA or SMPP egress to the destination MSC / SMSC. MAP MT-ForwardSM with SRI-SM cache. MT submit < 800ms 05 · Charge CDR · OCS Per-message CDR / EDR streamed to Kafka, file, or REST. OCS / OFCS hook for prepaid balance & refund. CDR < 30ms Platform ## Everything a physical SMSC delivers — hosted. Six capabilities that define a hosted, multi-tenant SMSC — global reach, unlimited connections, multi-language encoding, and the reporting operators run their business on. ### Unlimited SMPP bindings Per-customer SMPP 3.4 and 5.0 binds — separate TX, RX, and TRX sessions, with HTTP REST as an alternative. No cap on the number of connections a customer can hold. SMPP 3.4 SMPP 5.0 HTTP REST ### Fully hosted, no CAPEX Full SMS infrastructure with no hardware to buy and no ops team to staff. Geo-redundant, monitored 24/7 by the BroadNet NOC, and backed by a 99.99% SLA. No CAPEX 24/7 NOC 99.99% SLA ### Intelligent routing Country-wise and operator-wise routing with cost, quality, and SLA enforced per destination. Direct, premium, partner, and fallback lanes keep delivery high and margin intact. Country-wise Operator-wise Failover ### Detailed reporting Campaign, delivery, and performance reports with real-time DLR and EDR export. Per-route and per-vendor breakdowns, live TPS monitoring, exportable to CSV, PDF, or Excel. EDR export TPS monitor CSV/PDF/Excel ### Global connectivity 1,000+ direct operator connections, with direct binds in 86 countries and 200+ countries reachable. Country-wise and operator-wise routing to the correct destination network, every time. 1,000+ operator connections 200+ countries Direct ### Revenue assurance & billing Revenue assurance built in. Prepaid, postpaid, and hybrid wallets with real-time balance check, per-customer rating, and refund-on-failure — per tenant, from submit to invoice. Prepaid Postpaid Refund on fail Multi-tenant by design · not bolted on ## Four tiers. One platform. Native white-label. The hierarchy ships with the core — not as an integration project. Each tier inherits policy, branding and billing from the level above, with strict isolation so a tenant can never see another tenant's traffic, wallet or audit trail. Tier 01 ### Super Admin Platform-wide control Operator-level governance: tenant provisioning, global compliance posture, cross-tenant audit, RBAC root, system-wide rate plans, and the master billing ledger. Tier 02 ### Reseller White-label business unit A complete sub-platform under its own brand and domain. Resellers configure their own pricing, throttles, sender-ID lists and analytics — without ever touching the underlying platform. Tier 03 ### User Enterprise sender The end customer. Sends traffic via SMPP, HTTP or the web console. Sees only their own wallet, their own templates, and their own EDRs — multi-tenant isolation enforced at every layer. Tier 04 ### Sales Account & quota ops Per-sales-rep visibility for portfolio, quota and recovery actions. Scoped reporting and a clean handoff to the User tier — never granted production traffic rights. Stand up a new reseller sub-brand without re-platforming Billing models · native ## Prepaid, postpaid, hybrid — without a side-car. The wallet engine is part of the core, not a third-party add-on. Each tenant chooses the model that matches its commercial relationship, and the platform enforces the policy from submit_sm to invoice. ### Prepaid wallet Top-up before send. Real-time balance check at submit_sm, hard stop at zero. Ideal for retail enterprise senders and tightly controlled MVNO sub-brands. Real-time debit Hard stop Refund on failure ### Postpaid wallet Accrue volume, invoice on cycle. Per-period quotas, soft-warn at thresholds, configurable credit limit per tenant. Standard for banks, governments and Tier-1 enterprise. Volume accrual Soft warnings Credit limit ### Hybrid wallet Prepaid floor with a postpaid ceiling. Customers pre-fund a minimum, with overspend metered on the postpaid line. Common for resellers serving mixed-tier downstreams. Floor + ceiling Mixed downstream Auto-cutover Cost-optimisation engine ## Cheapest route only if it actually delivers. The router weighs four signals on every submit — cost, DLR success rate, latency, and complaint rate — and re-evaluates per destination, per time-band, per traffic class. No more cost-only routing that quietly destroys quality, and no more quality-only routing that quietly destroys margin. Re-scored every minute · per destination & class ### Cost / SMS Per-route, per-destination, per-time-band cost data refreshed from the rate file. ### DLR rate Live delivery-success ratio per route, sliding window of the last 24 hours. ### Latency Submit-to-DLR latency per route, p50 and p95, weighted to deprioritise stale routes. ### Complaint rate Quality signal — subscriber complaints, spam-trap hits and operator pushbacks per route. Send workflows ## Four workflows. Every tenant tier. The same workflow surface is exposed from Super Admin down through Reseller and User — each tier seeing only its own audit trail and its own dispatch ledger. ### Quick Send Single-message dispatch from the operator portal or a sales-team console. Audit-tagged to the sender, with full delivery telemetry. ### Bulk Campaign-grade dispatch with per-campaign throughput envelopes, opt-out enforcement and per-segment DLR aggregation. ### Personalised Variable-substitution templates with per-recipient parameters, segmented by language, locale and consent class. ### Auto-Schedule Schedule by absolute time, recurring window, or trigger event. Time-zone-aware, with regulator quiet-hours enforced per market. Event Detail Records ### EDR analytics, at carrier-grade depth. Every event in the message lifecycle — submit, dedup, route selection, MAP forward, DLR, refund — is captured as a typed EDR. Streamed in real time over Kafka, file or REST, with reference parsers for the BSS stacks operators already run. The same EDRs feed finance, fraud, capacity planning and the regulator export. Per-event typed Kafka · file · REST Reference parsers Regulator export Stream lag <100ms Retention 7+ years HLR + MNP · native ### HLR and MNP lookup, inside the core. Number-state validation before submit_sm acceptance — HLR for reachability and serving MSC, MNP for the real owning operator after port-out. Cached, batched and rate-limited so it never costs you a roaming budget surprise. Routes pick the correct destination operator, every time. HLR cache MNP cache Per-tenant policy Batch + on-demand Lookup p99 <350ms Cache hit >94% Capacity envelope ## The numbers operators actually plan against. 30,000 SMS / second per node Sustained throughput per node. 300M+ Messages / day Across the BroadNet platform. SMPP 3.4/5.0 + HTTP / HTTPS Operator and enterprise interfaces. 99.99% Hosted SLA Credit-backed availability. SMPP v3.4 + HTTP / HTTPS — operator and enterprise interfaces For your SMSC engineers ## The config, the PDU, the CDR. The exact bind file your operations team will paste into source control, the submit_sm PDU layout they'll capture on the wire, and the Kafka CDR consumer that feeds revenue assurance. prod · SMPP 3.4 / 5.0 Example ``` 1# Operator-side SMPP bind configuration2# /etc/broadnet/smsc/binds/mno-acme.conf3 4[bind:mno-acme-tx]5type = transceiver6host = 7port = 27758system_id = mno_acme_prod9password = ${MNO_ACME_SECRET}10system_type = SMPP11interface_version = 0x34 # SMPP 3.412tls = required13window_size = 25614throughput_tps = 500015 16[lane:mno-acme]17priority = direct18quality_score = >0.9219cost_band = tier-120fallback = partner > greylist21sri_sm_cache = 24h ``` Architecture ## Four tiers. Each replaceable, observable, audited. A clean separation between application bind, routing, carrier egress, and charging — so each layer can be scaled, swapped, or audited independently. L1 ### Application layer SMPP 3.4 / 5.0 binds, HTTP submit, customer portal, multi-tenant auth. SMPP 3.4 SMPP 5.0 HTTP REST Portal API L2 ### Routing engine Lane selection, throttling, retries, store-and-forward, sender-ID policy. Lane policy Throttling Retry Store & forward L3 ### Carrier interconnects SS7 SIGTRAN, SMPP egress to MNO SMSCs, partner aggregators, premium routes. SS7 SIGTRAN SMPP egress Aggregators Greylist L4 ### Charging & billing Real-time CDR / EDR stream, rating, OCS integration, revenue assurance. CDR stream EDR export OCS hook Rate plan Deployment ## Three operating models. One platform. The SMSC core ships in the topology your security, regulator, and network team can defend. Operator-owned ### On-prem Installed inside the operator's core network. BroadNet engineering supports day-2, you retain custody of all CDRs and subscriber data. - Core-network install - Operator owns data - BroadNet day-2 support BroadNet-operated ### Managed Hosted in BroadNet data centres, operated 24/7 by our NOC. SMPP and HTTP endpoints, customer portal, monitoring, DR — all included. - BroadNet DCs - 24/7 NOC - Multi-tenant SaaS Split-stack ### Hybrid Application layer on-prem for sovereignty, with managed routing, monitoring, and analytics in BroadNet cloud. Best of both with clean boundaries. - On-prem application - Cloud routing & analytics - Sovereign data plane Who runs it ## What a hosted SMSC looks like in production. GCC enterprise group Enterprise · GCC AE A GCC enterprise group retires its own message-centre hardware and moves campaigns, OTP and alerts onto BroadNet's hosted SMSC — one multi-tenant core, per-team credentials and delivery reporting, with nothing left to rack or patch. Enterprise messaging · illustrative scenario 1,000+ Operator connections 99.99% Hosted SLA Multi-market operator group Operator · MENA SA KW BH JO Several markets share one multi-tenant SMSC instead of separate stacks — unified user management, per-customer routing and sender-ID control, and a single reporting view across every opco. Group messaging platforms · illustrative scenario 200+ Countries reachable 99.99% Group SLA SMS aggregator Aggregator · North Africa MA An aggregator resells BroadNet capacity under its own brand — unlimited SMPP connections for downstream customers, per-reseller pricing and throttles, and reports each customer sees only for its own traffic. Wholesale messaging · illustrative scenario Unlimited SMPP connections 30,000 SMS/sec per node 24/7 NOC coverage Compliance ## Audited where it matters for carrier teams. The certifications procurement, security, and the regulator will actually ask for — current, audited, and renewed on schedule. GSMA Associate Member Associate Member of the GSMA operator community ISO 27001 Information security management ISO 9001 Quality management ISO 22301 Business continuity Operator due diligence ## Eight answers for your SMSC evaluation. A hosted, multi-language Short Message Service Center for enterprises and operators that need full SMS infrastructure without operating their own physical SMSC. It includes campaign management, DLR tracking, EDR export, performance reports, real-time TPS monitoring, and global connectivity through 1,000+ direct operator interconnects — all backed by a 99.99% SLA. An SMS API is enough for application-driven sending — your code generates the message and our API delivers it. A hosted SMSC is what you need when you want the SMSC features themselves: store-and-forward, delivery scheduling, retry logic at the SMSC layer, multi-tenant routing, multi-operator failover within one namespace, and direct SMPP connections from your own customers' applications. SMPP 3.4 and SMPP 5.0 bind support, plus an HTTP REST interface. Unlimited SMS connections per account, with separate transmit (TX), receive (RX), and transceiver (TRX) sessions. Global connectivity runs through BroadNet's 1,000+ direct operator connections, with direct binds in 86 countries and 200+ countries reachable. Campaign reports with delivery statistics and DLR breakdown, batch-level analysis, and schedule tracking. Delivery reports with real-time DLR, latency, error-code analysis, per-message logs, and EDR (Event Detail Record) export. Performance reports for user and client metrics, route and vendor efficiency, SMSC health KPIs, and TPS monitoring — exportable to CSV, PDF, or Excel. Full GSM 03.38 and UCS-2 Unicode encoding, so Arabic, Hindi, Chinese, and every other non-Latin script route as Unicode automatically. The portal itself is multi-language for operators' staff and their customers, and per-message billing accounts for Unicode segment limits. Yes. The SMSC supports unlimited customer-side SMPP connections, each with its own credentials, throughput limits, sender-ID assignments, and routing rules. Every customer sees only their own traffic in their portal view. Real-time TPS tracking per customer, per operator route, and per SMSC node, with configurable TPS caps. Peak throttling protects downstream operators, burst handling is queued, and the dashboard shows current TPS, peak TPS, and historical patterns. Hosting in BroadNet data centres, SMPP and HTTP endpoints, and a customer portal with reports and configuration. The platform is monitored 24/7 by the BroadNet NOC with automatic alerting, performance and security monitoring, backup and disaster recovery, and SLA-backed availability. Need the SMPP bind contract or a working session with our SMSC engineers? [Request SMPP connectivity](https://www.broadnet.me/contact?topic=smpp-connectivity&product=smsc-gateway) ![Real-time operator network protection](https://www.broadnet.me/marketing/generated/viz-security.png) Operator-grade ## Protect and monetize at the signaling layer. In-network SMS and SS7 firewalls stop grey routes and fraud at line rate while legitimate traffic flows untouched. <5ms Inspection 99.99% Uptime 1,000+ MNO links [Talk to our carrier team](https://www.broadnet.me/operators/contact) Carrier engineering · direct line ## Talk to carrier engineering. We'll walk the design with your team, share an SMPP test harness, and scope onboarding — typically live in days, with no CAPEX and no hardware to run. No marketing call, no slide deck. [Request SMPP connectivity](https://www.broadnet.me/contact?topic=smpp-connectivity&product=smsc-gateway) [Discuss bind requirements](https://www.broadnet.me/contact?topic=bind-requirements&product=smsc-gateway) $ smpp bind --host --port 2775 --system-id mno_prod Related guides & answers Go deeper on the concepts behind this product. [What is an SMSC Read](https://www.broadnet.me/answers/what-is-smsc) [What is SMPP Read](https://www.broadnet.me/answers/what-is-smpp) [How does the SMPP protocol work Read](https://www.broadnet.me/answers/smpp-protocol) [SIGTRAN — SS7 over IP explained Read](https://www.broadnet.me/answers/what-is-sigtran)