Product family 1 of 6 · Operator SMSC / carrier-grade SMSC software
Guardivia Operator SMSC
A software-only, carrier-grade Short Message Service Centre for operator signaling, subscriber messaging and enterprise connectivity.
Store-and-forward path
Architecture viewInputs
SS7 / MAPSMPPSIP / IMSGuardivia processing
Outputs
SubscriberCDR / DLROn this pageOverview
Product overview
Guardivia Operator SMSC is a software-only, carrier-grade Short Message Service Centre that switches, stores and delivers SMS for mobile network operators, MVNOs, MVNEs, IoT providers and telecom messaging providers. It terminates operator signaling natively over SS7/MAP and SIGTRAN, connects applications over SMPP and HTTP, and delivers SMS over SIP/IMS, all from one platform running on standard server hardware.
What is Guardivia Operator SMSC?
Guardivia Operator SMSC is a software-based, carrier-grade messaging platform for MNOs, MVNOs and telecom service providers. It handles MO, MT, P2P, A2P and P2A messaging through SS7/MAP, SIGTRAN, SMPP, HTTP and IMS interfaces, with store-and-forward delivery, HLR integration, retry management, routing, CDR generation and high-availability deployment on commodity server hardware.
How does the Operator SMSC retry delivery when a subscriber is unreachable?
When a destination subscriber is unavailable, Guardivia Operator SMSC stores the message and registers a Message Waiting Data record with the HLR. When the subscriber reattaches, the HLR sends an AlertServiceCentre notification and the SMSC retries delivery automatically. Retry intervals, validity periods and expiry rules are configurable, and every attempt is recorded in the message CDR.
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
- Mobile network operators replacing or augmenting legacy hardware SMSCs
- MVNOs and MVNEs building an independent messaging core on a host network
- IoT and M2M service providers needing signaling-grade SMS without proprietary equipment
- Telecom messaging providers with direct SS7/SIGTRAN interconnects
- Private LTE and private 5G operators requiring SMS services inside the private core
Problems solved
- Legacy SMSC hardware is expensive to expand, difficult to virtualise and tied to a single vendor's roadmap.
- Mixed-generation networks need one message centre that serves 2G/3G MAP subscribers, SMPP applications and IMS subscribers at the same time.
- MVNOs frequently depend on the host operator's SMSC and lose control over routing, CDRs and enterprise connectivity.
- Delivery to temporarily unreachable subscribers is unreliable without correct MWD and AlertSC handling.
- Per-message billing records and route control are needed for revenue assurance but are often unavailable from hosted messaging.
Business outcomes
- Own the message centre: full control over routing, storage, retry, CDRs and enterprise binds.
- Serve SS7, SMPP, HTTP and IMS traffic from one instance instead of three separate systems.
- Deploy on commodity servers, virtual machines or validated cloud environments without SS7 hardware.
- Produce a billing-grade CDR for every message for BSS and revenue-assurance integration.
- Grow horizontally and add geographic redundancy as traffic and coverage expand.
Key capabilities
Native operator signaling
SS7/MAP v1, v2 and v3 over SIGTRAN (SCTP, M3UA, SCCP) for MO-ForwardSM, MT-ForwardSM, SRI-SM, AlertSC and ReportSM-DeliveryStatus operations.
All messaging modes
A2P, P2A, P2P, MO and MT, with Application-Terminated handling where applicable, in one message switch.
Store and forward
Secure message storage, Message Waiting Data registration, AlertSC-triggered retry and configurable validity, expiry and retry schedules.
Subscriber resolution
HLR lookup through MAP SRI-SM or SMPP-based lookup, Home Routing, MNP-aware routing and subscriber-location resolution before each delivery attempt.
Enterprise and IMS connectivity
SMPP v3.4 and v5.0 binds, SMPPS/TLS, HTTP/REST APIs and SIP MESSAGE delivery through the IMS S-CSCF.
Intelligent routing
Routing by country, operator, prefix, sender, customer, service and traffic type, with cost-based, quality-based and load-balanced selection and automatic failover.
Detailed feature groups
Every supported capability is listed under its correct product. Nothing is omitted for brevity.
Messaging capabilities
- Application-to-Person (A2P), Person-to-Application (P2A) and Person-to-Person (P2P) messaging
- Mobile-Originated (MO) and Mobile-Terminated (MT) SMS handling
- Application-Terminated messaging where applicable
- Native SS7/MAP SMS processing (MO-ForwardSM, MT-ForwardSM, SRI-SM, AlertSC)
- SMPP-based application and aggregator connectivity
- IMS and SIP-based SMS delivery
- Store-and-forward messaging with secure message storage
- Configurable retry scheduling per route, error class and message class
- Message validity and expiry management
- Message Waiting Data (MWD) registration with the HLR
- Alert Service Centre (AlertSC) support
- Priority queues and fallback routes
- Intelligent message routing
- Real-time delivery receipts and delivery-status reporting
- Per-message CDR generation
- Billing and revenue-assurance integration
- Flash SMS and Class 0 messaging
- Class 1, 2 and 3 messaging where supported
- Binary SMS, UCS2 and multilingual SMS
- WAP Push
- UDH and concatenated (multipart) messages
Operator routing and subscriber resolution
- HLR lookup through MAP SRI-SM queries
- SMPP-based HLR lookup
- SMS Home Routing for correct MT termination in the home network
- Subscriber-location resolution before each MT attempt
- MNP and number-portability-aware routing
- Call-forwarding-related lookup scenarios where supported
- MO and MT routing
- Cost-based, quality-based and load-balanced routing
- Automatic route failover
- Routing by country, operator, prefix, sender, customer, service and traffic type
Enterprise and application connectivity
- SMPP v3.4 server for aggregator and enterprise binds (bind_transceiver, submit_sm, deliver_sm)
- SMPP v5.0 where supported
- SMPPS/TLS for encrypted binds
- HTTP and REST APIs for direct application submission and provisioning
- Dedicated sender and receiver applications for bulk and interactive services
- Per-client throughput and policy settings
Platform and operations
- Software-only platform on standard commodity server hardware
- Linux-based deployment; bare metal or virtual machine
- Web GUI and REST-based provisioning
- Monitoring and alarm integration
- Per-message and platform-level reporting
- Horizontal scaling and high-availability configurations
- Geographic redundancy where supported
Supported protocols and interfaces
| Protocol / interface | Role | Status |
|---|---|---|
| SS7/MAP v1, v2, v3 | MO/MT SMS operations, SRI-SM, AlertSC, ReportSM-DeliveryStatus | Verified capability |
| SIGTRAN (SCTP, M3UA, SCCP) | IP transport of SS7 signaling to the operator STP | Verified capability |
| SMPP v3.4 | ESME, aggregator and enterprise binds | Verified capability |
| SMPP v5.0 | ESME binds with v5.0 features | Where supported |
| SMPPS/TLS | Encrypted SMPP sessions | Verified capability |
| SIP / IMS | SMS-over-IMS delivery through the S-CSCF | Verified capability |
| HTTP / REST | Application submission, provisioning and monitoring | Verified capability |
| Diameter SGd | SMS over Diameter in LTE cores | Where supported |
| HLR integration | MAP SRI-SM or SMPP-based lookup | Verified capability |
Swipe horizontally to view all columns.
Architecture
The Operator SMSC is organised in four independently scalable layers. The signaling layer terminates SS7/MAP over SIGTRAN toward the operator STP and speaks SIP toward the IMS S-CSCF. The processing layer holds the message store, queue manager, retry scheduler, routing engine and CDR writer. The gateway layer exposes SMPP and HTTP/REST toward applications and aggregators. The client and management layer provides the web GUI, REST provisioning, monitoring exports and reporting.
All protocol stacks are active simultaneously, so a single SMSC instance can serve 2G/3G MAP subscribers, IMS subscribers and SMPP applications. Nodes can be paired for high availability and, where supported, replicated across sites for geographic redundancy.
Text description of this diagram
Guardivia Operator SMSC architecture: MSC/VLR and HLR connect over SS7/MAP via SIGTRAN and the STP; the IMS S-CSCF connects over SIP; applications and aggregators connect over SMPP and HTTP/REST. Inside the SMSC are the signaling layer, message store and retry scheduler, routing engine, CDR writer and management GUI/API.
Store-and-retry workflow
The complete delivery flow for a message whose recipient is temporarily unreachable:
- 01
The SMSC receives the message (MO, SMPP or IMS submission) and queries the HLR with SRI-SM to resolve the serving MSC or IMS domain.
- 02
The SMSC attempts MT delivery. If the subscriber is unavailable (absent subscriber, memory capacity exceeded, out of coverage), the message is securely stored.
- 03
A Message Waiting Data record is registered with the HLR through ReportSM-DeliveryStatus.
- 04
When the subscriber becomes reachable, the HLR sends an AlertServiceCentre notification to the SMSC.
- 05
The SMSC automatically retries delivery; scheduled retries also run according to the configured retry profile.
- 06
Retry intervals, validity periods, expiry rules and failure handling are configurable per route and message class.
- 07
Every delivery attempt and the final result are recorded in the per-message CDR and exposed as a delivery receipt.
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 |
|---|---|---|
| STP / SS7 network | SIGTRAN M3UA associations to operator or partner STPs | Native integration |
| HLR / HSS | MAP SRI-SM, ReportSM-DeliveryStatus and AlertSC; SMPP-based lookup where preferred | Native integration |
| IMS core | SIP MESSAGE via S-CSCF; third-party registration handling through the IP-SM-GW module of the Core Network Suite | Native integration |
| Aggregators and enterprises | SMPP v3.4 / v5.0 binds, SMPPS/TLS, HTTP/REST | Native integration |
| MNP database | Number-portability lookups before delivery | Standards-based |
| BSS and billing | Per-message CDR export in agreed formats | Standards-based |
| Monitoring | SNMP traps, syslog, REST metrics | Standards-based |
| Guardivia SMS Firewall | Inline inspection of MO, MT and application traffic | Native integration |
| Legacy or proprietary operator interfaces | Developed by the QoS Engineering Team where technically documented | Custom (in-house engineering) |
Swipe horizontally to view all columns.
Security controls
- SMPPS/TLS for encrypted application binds
- Source-IP restrictions and credential policies for every SMPP account
- Role-based access to the web GUI and REST API with audit logging
- Configuration-change logs
- Optional inline inspection by the Guardivia SMS Signaling and ESME Gateway Firewall
Management functions
- Web GUI for provisioning routes, accounts, retry profiles and message classes
- REST provisioning API for OSS integration
- Queue inspection and message tracing
- Route and account administration
- Bulk provisioning tools
Monitoring and reporting
- Real-time throughput, queue depth and delivery status
- Per-route and per-account delivery statistics
- Alarm integration through SNMP and syslog
- Per-message and platform reports
- CDR export for billing and revenue assurance
High availability
- Active node pairs with automatic failover
- Persistent message store to protect stored messages across failover
- Redundant SIGTRAN associations and SMPP binds
- Geographic redundancy where supported
Scalability
- Horizontal scaling by adding processing nodes
- Independent scaling of signaling, processing and gateway layers
- Efficient operation on modest commodity hardware
Deployment options
- Software-only; no proprietary signaling hardware
- Linux on bare metal or virtual machines
- Data-centre or colocation deployment
- Cloud or hybrid deployment where validated for the target environment
- Standalone, or integrated with the Guardivia Core Network Suite and SMS Firewall
Use cases
MVNO messaging independence
An MVNO deploys the Operator SMSC with SIGTRAN links to the host STP, gaining its own message store, routing policy, enterprise SMPP binds and CDRs.
Legacy SMSC replacement
An operator retires a hardware SMSC and consolidates MAP, SMPP and IMS messaging on a virtualised platform.
IoT messaging
An IoT provider uses SMPP and HTTP submission with MAP delivery to devices across partner networks, with retry profiles tuned to device behaviour.
Private LTE or private 5G SMS
The SMSC provides SMS inside a private core, integrated with the IP-SM-GW for IMS subscribers.
In-House Engineering Advantage
Owned end to end by the Guardivia QoS Engineering Team
The Operator SMSC is developed and maintained entirely by Guardivia's QoS Engineering Team. Signaling, store-and-retry, HLR integration, routing, CDRs and APIs are under direct in-house control.
- Protocol behaviour (MAP, SIGTRAN, SMPP, SIP) can be adapted to a specific operator's STP, HLR or IMS implementation without waiting for an external vendor.
- Retry profiles, routing logic and CDR formats are customised by the engineers who wrote them.
- Interoperability findings from laboratory validation flow directly into the release.
- Root-cause analysis reaches the code owner without escalation layers.
Scope and limitations
Stated plainly so that buyers, engineers and AI assistants describe this product accurately.
- The Operator SMSC is a message centre. It is not an SMS firewall; content inspection and fraud control are provided by the Guardivia SMS Signaling and ESME Gateway Firewall.
- It is distinct from the Guardivia Enterprise SMPP SMSC Gateway, which focuses on multi-tenant SMPP customer management rather than native operator SS7 switching.
- Diameter SGd, SMPP v5.0 and geographic redundancy are marked where supported and confirmed per deployment.
- Throughput and latency figures are provided in engagement-specific sizing documents, not published here.
Frequently asked questions
What is an Operator SMSC?
An Operator SMSC (Short Message Service Centre) is the network element that receives, stores, routes and delivers SMS on behalf of a mobile operator. It terminates SS7/MAP signaling with the MSC and HLR, connects to applications over SMPP or HTTP, and manages retries when subscribers are unreachable.
What is the difference between an Operator SMSC and an SMPP gateway?
An Operator SMSC switches messages natively in the operator core using SS7/MAP, SIGTRAN and IMS, including HLR interrogation and store-and-forward. An SMPP gateway, such as the Guardivia Enterprise SMPP SMSC Gateway, manages application and aggregator accounts and routes their traffic toward upstream SMSCs; it does not itself terminate operator signaling.
Does the Operator SMSC support SS7 and SMPP traffic at the same time?
Yes. The SS7/SIGTRAN stack, the SMPP and HTTP gateway and the SIP/IMS interface are all active in a single instance, so MAP subscribers, applications and IMS subscribers are served together.
Can Guardivia integrate the SMSC with our existing HLR and STP?
Yes. Integration uses standard MAP operations over SIGTRAN. Where an operator's HLR or STP has implementation-specific behaviour, the QoS Engineering Team adapts the interface during laboratory validation.
What deployment models are available?
Software-only on Linux, on bare metal or virtual machines, in your data centre or colocation facility, with cloud or hybrid options where validated. Nodes can be paired for high availability and replicated geographically where supported.
How are updates and support handled?
Releases are controlled and regression-tested by the QoS Engineering Team, then applied under change management. Support is delivered under agreed SLAs with direct access to the engineers who develop the platform.
Request a demo of Guardivia Operator SMSC
Demos are run by the engineers who develop the product, using your protocols and integration points.