The YateSMSC server fulfills all the functions of a conventional Short Message Service Center, forwarding, storing and delivering SMSs in GSM, UMTS and LTE networks.
YateSMSC description and API configuration
YateSMSC for GSM, UMTS and LTE networks
-
General information about what YateSMSC is and does.
-
General information about the JSON API.
-
Using JSON API to schedule, hurry and cancel SMSs.
-
Call Flow Example on YateSMSC Equipment
-
Using the JSON API to configure YateSMSC.
-
Instructions on how to use the JSON API to retrieve information about node statistics, request delivery of messages and more.
-
Instructions for configuring an API for a multi tenant YateSMSC & YateHSS
-
Generic information about licensing system.
-
Information and configuration of YateSMSC as SMPP server/client.
-
Message handle priorities in YateSMSC components
Settings for YateSMSC equipment
Various usage scenarios and settings for YateSMSC
-
Easily track the life-cycle of SMS being submitted.
-
Radius protocol usage for MO SMS authorization and charging.
Miscellaneous YateSMSC features
-
Example of routing SMS of HTTP with adding of custom authentication header
Latest Changes
| Tag number | Date | Release notes |
|---|---|---|
| 6009 | 02.09.2026 | Use existing dialog application context for subsequent MAP MT SMS. |
| 6008 | 28.07.2026 | Fixed function call and message handler filter bugs. |
| 6007 | 27.07.2026 | Fixed mo sms: allow imsi to be missing (align with old bahavior). |
| 6006 | 27.01.2026 | Added support to accept (after authorization) MO SMS without IMSI. |
| 6005 | 27.10.2025 | Use mariadb command instead of mysql on Mageia greater than 8: it was deprecated and will be removed. |
