ESME_RINVBCASTMSGCLASS in SMPP

What is ESME_RINVBCASTMSGCLASS?

ESME_RINVBCASTMSGCLASS (Error Code: 0x0000010B) indicates that the broadcast message class specified in the SMPP PDU is invalid or not supported.

Possible Causes

  • Invalid or unknown message class specified in the broadcast_sm request.
  • Incorrectly formatted message class value in the PDU.
  • The SMSC does not support the specified broadcast message class.

When Does It Happen?

This error occurs when an ESME submits a broadcast_sm message with an invalid or unsupported message class.

Example SMPP PDU Transaction

Request PDU (broadcast_sm) Sent by ESME

00000034 (Length)
00000111 (Command ID for broadcast_sm)
00000000 (Command Status)
00000006 (Sequence Number)
00 (Service Type - Default)
01 (Source Address TON - International)
01 (Source Address NPI - ISDN)
31323334 00 (Source Address: "1234")
01 (Destination Address TON - International)
01 (Destination Address NPI - ISDN)
39383736 00 (Destination Address: "9876")
00 (ESM Class)
00 (Protocol ID)
00 (Data Coding Scheme)
00 (Priority Flag)
00000000 (Schedule Delivery Time - Not Set)
00000000 (Validity Period - Not Set)
00 (Replace If Present Flag)
00 (Sm Default Msg ID)
0005 (Message Length)
48656C6C 6F (Message: "Hello")
001E (Broadcast Message Class TLV Tag)
0001 (TLV Length)
FF (Invalid Value - Unsupported Message Class)

Response PDU (broadcast_sm_resp) Indicating ESME_RINVBCASTMSGCLASS

00000010 (Length)
80000111 (Command ID for broadcast_sm_resp)
0000010B (Command Status - ESME_RINVBCASTMSGCLASS)
00000006 (Sequence Number)

How to Solve It?

  • Ensure that the broadcast message class is valid and supported by the SMSC.
  • Verify the correct encoding and format of the message class in the PDU.
  • Consult the SMSC documentation for a list of allowed broadcast message classes.

To resolve this issue, correct the broadcast message class in the PDU and resubmit the request.

More information