Enterprise integration

SMPP

Telecom-standard TCP/IP protocol for direct messaging integrations and enterprise traffic.

Service overview

SMPP is a widely used industry-standard protocol for exchanging SMS messages between SMSCs, routing entities, and application systems, with additional MM4 and MM7 support for MMS-related integration.

Core specifications

Transport
TCP/IP
Delivery reports
Supported
Data coding
ASCII, Latin 1, UCS2, KSC5601
MMS interfaces
MM4 and MM7
Enterprise role
Protocol-level delivery, gateway control, and receipt-driven operations

Protocol details

SMPP is designed to provide a flexible communication interface for transferring SMS messages between SMS centers, routing entities, and external short message systems.

  • Open telecom industry standard
  • Designed for fast and reliable SMS delivery
  • Appropriate for direct integration and operational control

Supported PDUs

CommandCommand
bind_transmittersubmit_sm
bind_receiverdata_sm
bind_transceiverdeliver_sm
unbindenquire_link

Data coding schemes

ValueEncoding
0 or 1ASCII
3Latin 1
8UCS2
14KSC5601

Delivery report format

"id:<message_id> sub:<message_sub> dlvrd:<message_dlvrd> submit date:<message_submit_date> done date:<message_done_date> stat:<message_stat> err:<message_err>"

SMPP and MM4 architecture documentation is available for teams implementing enterprise integrations.

Operational support

Standardized interfaces

SMPP v5, MM4, and MM7 support simplify integration with enterprise systems and carrier-aligned workflows.

PC-based sending tools

PC-based sending programs are available for teams that need Excel-driven or operational sending support.

Receipt-driven control

Delivery-report support helps teams monitor completion, exceptions, and downstream status handling.

Queue and retry handling

SureM also describes queue-based processing, retry and cancel controls, priority assignment, and transmission-time monitoring for heavier operational traffic.

Delivery statuses

DELIVRDUNDELIVREJECTED

What is MM4?

MM4 is the interface used to exchange messages between two MMSCs and is commonly described as the interface between two mobile networks.

  • Also known as the MMSR interface in WAP and OMA standards
  • Used for MMSC-to-MMSC message exchange
  • Typically implemented using SMTP

Protocol example

submit_sm {
  source_addr: "SUREM"
  destination_addr: "+821055551234"
  short_message: "Your code is 483920."
}

Common use cases

  • Direct SMSC integrations
  • Large-scale delivery
  • Platform interoperability
  • Receipt-driven workflows