ySMSC

ySMSC – SMPP / MAP Short Message Service Center

ySMSC (aka YATE Short Message Service Center) is yREMORA’s carrier-grade SMSC (Short Message Service Center) solution, engineered for modern telecommunications networks requiring SMS delivery across SMPP, SS7/MAP and HTTP interfaces. Built on the robust open-source YATE (Yet Another Telephony Engine) framework, ySMSC delivers carrier-class store-and-forward messaging. Most vendors sell a rigid box; ySMSC adapts to your network, not the other way around.

---

Key Capabilities

Flexible Deployment Models

Deploy ySMSC in containerized environments (Docker), virtualized infrastructure (VMware, KVM, OpenStack), or directly on bare-metal servers. Choose the architecture that fits your operational requirements.

Multi-Protocol Messaging Interfaces

Submit and receive SMS across every interface a modern operator needs, in a single engine:

• SMPP v3.4 and v5.0: ESME connectivity for A2P, aggregators and application gateways, as both server and client (submit_sm / deliver_sm, MO and MT)
• SS7 / MAP over TCAP: MO-ForwardSM, MT-ForwardSM, SRI-SM (with informServiceCentre), AlertServiceCentre and ATI subscriber interrogation towards HLR/MSC
• HTTP / JSON: message submission and delivery-receipt callbacks to orchestrators and business systems

Complete SS7 / SIGTRAN Stack with Automatic MAP Version Negotiation

A full in-engine SS7 stack (MTP2/MTP3, SCCP for both ITU and ANSI point codes, and TCAP) with SIGTRAN adaptation over SCTP (M2PA and M3UA) makes ySMSC a self-contained signaling end point that connects to your STP over M2PA or M3UA, with no separate SS7 stack or signaling gateway to integrate. MAP v1/v2/v3 is selectable per destination, and optional automatic version negotiation learns each peer’s preferred MAP version so dialogs are built correctly on the first attempt instead of failing over after a retry. An optional TCAP handshake (3GPP TS 33.204) hardens signaling against spoofing.

Native SMS Short-Code Handling

Short numeric SMS codes are recognized natively and routed to their destination application without E.164 country-code normalization, so A2P and A2A services (parking payments, banking alerts, voting and similar) reach the correct endpoint. Enabled per deployment through configurable short-number rules.

Store-and-Forward Scheduling

Reliable message queuing against a MySQL/MariaDB backend with configurable retry, validity-period and expiry handling. Absent-subscriber retries, delivery scheduling and automatic archival keep traffic flowing without message loss.

Number Portability (MNP / NPDB)

Resolve ported numbers before delivery via a local NPDB (SQLite or MySQL) with custom per-country queries that mirror the national MNP database, or a remote HTTP NPDB service with per-query caching and sequential endpoint failover. Portability results feed routing so messages reach the subscriber’s current network.

Full Encoding and Concatenation Support

Complete Data Coding Scheme handling per 3GPP TS 23.038: GSM 7-bit (packed and unpacked), UCS-2, 8-bit binary, Latin-1, Cyrillic and Hebrew, plus national-language shift tables (including Turkish), with SAR / UDH multipart concatenation for correct long and non-Latin message delivery.

Delivery Receipts and Charging

End-to-end delivery-receipt (DLR) correlation and status-report regeneration across protocol boundaries. Optional MO and MT authorization and charging via RADIUS (with RFC 5176 CoA/Disconnect and RFC 5997 Status-Server) or an HTTP OCS bridge, with configurable fail-open behavior so a charging outage need not block delivery.

Intelligent Regex-Based Routing

Powerful regular expression pattern matching enables sophisticated routing logic with granular control over message flows:

• E.164 addressing and alphanumeric originators
• Home-routing, MO/MT direction and per-destination policy
• GTT (Global Title Translation) and E.214 for SS7 destination resolution
• Portability-aware routing
• Per-connection encoding and charging policy

Horizontal Scalability and High Availability

Scale out node by node (smsc1, smsc2 … smscX) behind a MariaDB Galera multi-master cluster or an application-plane cluster, with heartbeat and quorum gating for active-active resilience. Per-table storage-engine choice (InnoDB, MyRocks, ColumnStore) tunes the queue for throughput or analytics.

Dynamic Provisioning

Real-time configuration and route updates without service interruption via API provisioning. Modify routing policies, subscriber records, or traffic patterns on-the-fly without impacting active messaging sessions.

RESTful API Management

Comprehensive JSON-over-HTTP(s) API for configuration, provisioning, monitoring, and management, enabling automation, integration with various systems, and any time control of messaging policies.

Custom Implementations

Because the application layer is open and scriptable, ySMSC accommodates bespoke routing, encoding and integration logic when a deployment needs something the standard feature set does not cover.

Open-Source Foundation

Leveraging the proven YATE framework (github.com/yatevoip) ensures transparency, community-driven innovation, and freedom from vendor lock-in while maintaining enterprise-grade reliability.

---

Ideal For

Perfect for mobile operators (MNO), MVNOs, A2P and messaging aggregators, interconnect providers, and enterprises requiring reliable SMS infrastructure with modern deployment flexibility.

---

Commercial Competition Analysis