An IP-SM-GW (IP Short Message Gateway) is the IMS network function that lets SMS travel over IP between VoLTE or VoNR devices and an operator’s existing SMSC. It receives text messages sent as SIP requests from IMS devices, converts them into the MAP signaling the SMSC understands, and does the reverse for incoming messages. For operators retiring 2G and 3G, the IP-SM-GW is what keeps SMS working as voice and messaging move onto IMS in 4G and 5G networks.
SMS is still the delivery channel for one-time passcodes, account alerts, emergency notifications, visual voicemail signaling and machine-to-machine traffic. Losing it during a network transition is not an option.
What “5G messaging” means for operators
The term “5G messaging” is used loosely in the industry. In practice it covers three related capabilities:
- SMS over IMS: SMS carried as SIP messages for devices registered on IMS for VoLTE or VoNR. This is where the IP-SM-GW operates.
- SMS over NAS in the 5G core: SMS carried in control-plane signaling through the AMF and a dedicated SMS Function (SMSF), without requiring IMS.
- RCS: Rich Communication Services, defined by the GSMA Universal Profile, offering chat-style messaging, media sharing, group chat and business messaging over IP.
All three usually coexist. Operators need SMS to work for every device type, including legacy phones, IoT modules and inbound roamers, while rich messaging layers on top for capable devices.
How SMS over IMS works
In 2G and 3G, SMS travels through the circuit-switched core: the MSC delivers messages to the handset and exchanges MAP signaling with the SMSC. In an IMS network there is no circuit-switched path for that device, so 3GPP’s SMS over IP specifications define a different method. The SMS payload is encapsulated inside a SIP MESSAGE request and routed through the IMS core.
Mobile-originated SMS
- The device sends a SIP MESSAGE containing the encapsulated SMS to the P-CSCF.
- The S-CSCF applies the subscriber’s filter criteria and routes the request to the IP-SM-GW.
- The IP-SM-GW extracts the SMS and forwards it to the subscriber’s SMSC using MAP.
- The SMSC accepts the message, returns a report, and delivers it toward the recipient as usual.
Mobile-terminated SMS
- The SMSC queries the HLR or HSS for routing information for the recipient.
- If the recipient is registered on IMS, the response points to the IP-SM-GW serving that user.
- The SMSC sends the message to the IP-SM-GW using MAP, exactly as it would to an MSC.
- The IP-SM-GW performs domain selection and delivers the message as a SIP MESSAGE through the S-CSCF.
- If IMS delivery fails, the IP-SM-GW can attempt another domain, such as circuit-switched or SMS over SGs, or return the failure so the SMSC can retry later.
What an IP-SM-GW does in the IMS network
The IP-SM-GW sits between the IMS core and the legacy messaging core. Its main responsibilities are:
- IMS registration awareness: it receives third-party registration from the S-CSCF and informs the HSS that it is serving the user for SMS, so terminating messages are routed to it.
- Protocol interworking: it translates between SIP on the IMS side and MAP over SIGTRAN on the SMSC side.
- Domain selection: for terminating traffic, it decides whether to deliver over IMS or fall back to another available domain.
- Delivery reports: it carries status reports in both directions so senders and the SMSC get accurate delivery results.
- Charging and policy hooks: it provides points where messaging can be rated and controlled in line with the operator’s billing and service rules.
Transport-level versus service-level interworking
3GPP describes two modes. In transport-level interworking, the SMS is carried intact inside SIP and the IP-SM-GW simply moves it between domains. This is the mode most operators deploy for VoLTE SMS. In service-level interworking, the IP-SM-GW converts between SMS and native IMS messaging formats, which can help bridge IP messaging clients and SMS-only users.
SMSC interworking: keep the core you have
One of the strongest arguments for an IP-SM-GW is that it protects existing investment. To the SMSC, the IP-SM-GW looks like another serving node reachable through MAP. That means:
- The SMSC remains the single store-and-forward point for all subscribers, whatever access they use.
- Routing rules, retry schedules and delivery policies continue to work unchanged.
- A2P traffic, OTP delivery, broadcast and emergency alerting keep running through established platforms.
- Value-added services that depend on SMS, such as visual voicemail notifications, continue to reach devices after they move to VoLTE.
The main integration points to plan are the HSS (for registration and routing), the S-CSCF (for filter criteria that steer SMS to the IP-SM-GW), the SMSC (MAP over SIGTRAN), and charging systems.
SMS delivery options compared
Most operators run several of these methods at once during a transition. The right mix depends on device base, roaming partners and network roadmap.
| Method | Network | How the SMS is carried | Key elements | Typical use |
|---|---|---|---|---|
| SMS over CS | 2G / 3G | Circuit-switched signaling via the MSC | MSC/VLR, HLR, SMSC | Legacy devices, 2G/3G roamers |
| SMS over SGs | 4G with CS fallback | LTE signaling via the MME, relayed to an MSC | MME, MSC, SMSC | LTE devices without IMS registration |
| SMS over IMS | 4G VoLTE / 5G VoNR | SIP MESSAGE through the IMS core | P-CSCF, S-CSCF, IP-SM-GW, HSS, SMSC | IMS-registered smartphones |
| SMS over NAS | 5G standalone | 5G control-plane signaling via the AMF | AMF, SMSF, UDM, SMSC | 5G devices, including IoT without IMS |
| RCS | 4G / 5G data | IP messaging per GSMA Universal Profile | IMS core, RCS platform | Rich chat and business messaging, with SMS fallback |
RCS and where SMS still fits
RCS brings features users expect from OTT apps: typing indicators, read receipts, high-resolution media, group chat and branded business messaging. Android devices have supported RCS for some time, and iPhone support has more recently been added, though availability still depends on operator support and configuration.
RCS does not remove the need for SMS. When a recipient is not RCS-capable, out of data coverage, or roaming on a network without RCS interconnect, messages fall back to SMS. Enterprise senders also continue to rely on SMS for its reach. For operators, RCS is best treated as a layer on top of a reliable SMS foundation, and the IP-SM-GW is part of that foundation for IMS devices.
Migrating from 2G/3G: a practical path
Operators in many regions have shut down 2G or 3G networks or announced plans to do so. Messaging is one of the services most likely to break if the migration is rushed. A typical sequence looks like this:
- Inventory SMS dependencies: consumer handsets, IoT and M2M devices, A2P traffic, roaming partners, voicemail notifications and emergency alerting.
- Deploy SMS over IMS with an IP-SM-GW for VoLTE subscribers, integrated with the existing SMSC and HSS.
- Keep fallback paths such as SMS over SGs or circuit-switched delivery available while non-IMS devices remain on the network.
- Test device behavior across popular handset models, since IMS SMS support depends on device and operator configuration.
- Address roaming: inbound roamers without VoLTE roaming agreements may lose voice and SMS if circuit-switched access disappears.
- Plan for 5G standalone, including SMS over NAS through an SMSF for devices that will not register on IMS.
- Align charging so messaging over every path is rated consistently in the prepaid and postpaid systems.
How Primal Technologies helps
Primal Technologies has delivered messaging and value-added services to mobile, landline and cable operators since 1997. Its messaging portfolio includes SMSC, IP-SM-GW for LTE and IMS, MMS, USSD and Broadcast Manager for emergency SMS alerts, alongside converged OCS/prepaid billing. These run on Primal’s microservice-based Open Services Environment (OSE) and support the TCAP, ISUP, SIP, DIAMETER and SIGTRAN signaling that SMS interworking depends on.
Because SMS underpins other services, Primal can look at the whole picture. Its Visual Voicemail platform relies on messaging to notify devices, so keeping SMS working through a VoLTE migration protects that service too. Primal’s professional services team handles consulting, deployment, support, NFV and containerization, and Primal Cloud offers a hosted option built on OpenShift, Rocky Linux and Kubernetes.
Primal works with operators across North America, the Caribbean, Africa, Europe and the Pacific Rim.
Frequently asked questions
What is the difference between an SMSC and an IP-SM-GW?
The SMSC stores and forwards SMS and manages retries and delivery. The IP-SM-GW connects IMS devices to the SMSC by converting between SIP and MAP. Most operators need both: the SMSC as the messaging core, and the IP-SM-GW for IMS access.
Do I need an IP-SM-GW if I already have VoLTE?
If you want SMS delivered natively over IMS to VoLTE devices, yes. Without it, VoLTE devices typically depend on SMS over SGs, which requires keeping an MSC in the network.
Does 5G standalone need an IP-SM-GW?
5G standalone also supports SMS over NAS through an SMSF. Devices using VoNR on IMS can still send SMS over IMS through an IP-SM-GW. Many operators support both, depending on their device base.
Is RCS replacing SMS?
Not in the near term. RCS adds rich features for capable devices, but it falls back to SMS when the recipient or network cannot support it. SMS also remains the main channel for OTPs and alerts.
Can an IP-SM-GW run in the cloud?
Yes. Modern IP-SM-GW platforms can be deployed on virtualized or containerized infrastructure, in private or public cloud environments, as part of an NFV strategy.
If you are planning a 2G/3G sunset, launching VoLTE or preparing for 5G standalone, Primal Technologies can help you keep SMS reliable on every path. Request a demo to talk with our messaging team.