ESME_RINVSRCTON in SMPP

What is ESME_RINVSRCTON?

ESME_RINVSRCTON (Error Code: 0x00000048) is an SMPP error indicating that the source TON (Type of Number) value provided in the PDU is invalid or not supported by the SMSC.

Possible Causes

  • The source TON field contains an incorrect or unsupported value.
  • The SMSC does not recognize the specified TON.
  • The source TON is not correctly mapped to the source address.
  • Using a reserved or undefined TON value.

When Does It Happen?

This error occurs when an ESME sends a submit_sm, deliver_sm, or similar PDU with an invalid source TON value.

Example SMPP PDU Transaction

Incorrect submit_sm PDU (Invalid Source TON)

0000002F (Length)
00000004 (Command ID for submit_sm)
00000000 (Command Status)
00000001 (Sequence Number)
00 (Service Type)
FF (Invalid Source TON)
01 (Source Address NPI)
31323334 00 (Source Address: "1234")
01 (Destination Address TON)
01 (Destination Address NPI)
39383736 00 (Destination Address: "9876")
00 (ESM Class)
00 (Protocol ID)
00 (Priority Flag)
00000000 (Schedule Delivery Time - Not Set)
00000000 (Validity Period - Not Set)
00 (Registered Delivery)
00 (Replace If Present Flag)
00 (Sm Default Msg ID)
0005 (Message Length)
48656C6C 6F (Message: "Hello")

Response PDU (submit_sm_resp) with ESME_RINVSRCTON

00000010 (Length)
80000004 (Command ID for submit_sm_resp)
00000048 (Command Status - ESME_RINVSRCTON)
00000001 (Sequence Number)

Issue: The source TON field is set to an invalid value (0xFF), which is not recognized by the SMSC.

How to Solve It?

  • Use a valid source TON value based on SMPP specifications:
    • 0x00 - Unknown
    • 0x01 - International
    • 0x02 - National
    • 0x03 - Network Specific
    • 0x04 - Subscriber Number
    • 0x05 - Alphanumeric
    • 0x06 - Abbreviated
  • Confirm with the SMSC which source TON values are supported.
  • Ensure the source TON matches the format of the source address.
  • Review and correct the SMPP PDU construction before sending.

If the issue persists, enable debug logs and contact the SMSC provider for further troubleshooting.

More information