ESME_RINVDLNAME in SMPP

What is ESME_RINVDLNAME?

ESME_RINVDLNAME (Error Code: 0x00000034) is an SMPP error indicating that the distribution list (DL) name provided in the PDU is invalid or not recognized by the SMSC.

Possible Causes

  • The specified distribution list name does not exist on the SMSC.
  • The format of the distribution list name is incorrect.
  • The ESME does not have permission to use the specified distribution list.
  • The SMSC does not support distribution lists.

When Does It Happen?

This error occurs when sending a submit_multi PDU that references an invalid or non-existent distribution list.

Example SMPP PDU Transaction

Incorrect submit_multi PDU (Invalid Distribution List Name)

0000003C (Length)
00000021 (Command ID for submit_multi)
00000000 (Command Status)
00000002 (Sequence Number)
00 (Service Type)
01 (Source Address TON)
01 (Source Address NPI)
31323334 00 (Source Address: "1234")
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")
01 (Number of Destinations)
02 (Destination Flag - Distribution List)
696E76616C69646C00 (Invalid DL Name: "invalidDL")

Response PDU (submit_multi_resp) with ESME_RINVDLNAME

00000010 (Length)
80000021 (Command ID for submit_multi_resp)
00000034 (Command Status - ESME_RINVDLNAME)
00000002 (Sequence Number)

Issue: The distribution list name provided ("invalidDL") does not exist or is incorrectly formatted.

How to Solve It?

  • Verify that the distribution list name is correctly formatted and exists on the SMSC.
  • Ensure that the ESME has the necessary permissions to use the distribution list.
  • Confirm with the SMSC provider whether distribution lists are supported.
  • Check the SMSC documentation for valid naming conventions for distribution lists.
  • Enable debugging logs to inspect the exact values being sent in the PDU.

If the issue persists, contact the SMSC provider to verify the availability and configuration of distribution lists.

More information