ESME_RINVNUMDESTS in SMPP

What is ESME_RINVNUMDESTS?

ESME_RINVNUMDESTS (Error Code: 0x00000033) is an SMPP error indicating that the number of destinations specified in the PDU is invalid.

Possible Causes

  • The number_of_dests field in a submit_multi PDU is set to an invalid value (e.g., zero or exceeding allowed limits).
  • One or more destination addresses in the dest_address field are incorrectly formatted or invalid.
  • The SMSC has a restriction on the maximum number of destinations allowed per request.
  • The PDU is incorrectly structured, leading to parsing errors at the SMSC.

When Does It Happen?

This error occurs when sending a submit_multi PDU, and the SMSC detects an issue with the number of destination addresses.

Example SMPP PDU Transaction

Incorrect submit_multi PDU (Invalid Number of Destinations)

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")
00 (Number of Destinations - Invalid)

Response PDU (submit_multi_resp) with ESME_RINVNUMDESTS

00000010 (Length)
80000021 (Command ID for submit_multi_resp)
00000033 (Command Status - ESME_RINVNUMDESTS)
00000002 (Sequence Number)

Issue: The number of destinations is either zero or exceeds the allowed limit.

How to Solve It?

  • Ensure that at least one valid destination address is provided.
  • Check if the number of destinations exceeds the maximum limit allowed by the SMSC.
  • Verify the formatting of the destination addresses in the PDU.
  • Consult the SMSC provider for the supported number of destinations per request.
  • Enable debugging logs to inspect the exact values being sent in the PDU.

If the issue persists, contact the SMSC provider to verify system restrictions and resolve any configuration issues.

More information