Ogave SS7: Your own SMSC, straight into mobile networks over SS7 (On request)
Ogave SS7 takes the SMPP traffic of Ogave Core and delivers it as MT-SMS over SS7 (SIGTRAN / MAP) through your own SMSC, with real network delivery receipts. Add-on module, available on request.
What it does
SMPP in, SS7 out
Ogave Core sends to the SMSC like to any supplier. The SMSC asks the HLR where the number is and hands the SMS to the operator's network (SRI-for-SM and MT-ForwardSM).
Your own SS7 identity
M3UA links over SCTP to your SS7 carrier, with your own global title and point code. MAP version 3 with fallback to version 2.
Real delivery receipts
The receipt comes from the network's answer — delivered, phone off, unknown number — with the error code mapped for your customers.
Retries for phones that are off
The message waits and is retried, and goes out as soon as the network reports that the phone is back.
Long messages and Unicode
GSM 7-bit, Unicode and concatenated messages, with every part kept together.
Secure link to Ogave Core
SMPP over TLS between Ogave Core and the SMSC.
Nothing lost on a restart
The queue is kept on disk: a restart or a crash does not lose what was waiting.
Monitoring and alerts
SS7 link, queue and counters in the portal, and Telegram alerts when the link drops or the queue gets stuck.
Other platform modules
Talk to a technical team
We're a technical team. You'll talk to someone who understands SMPP, wholesale routing, and carrier interconnects. Technical proposal in under 24 hours.
Technical email: 