ESME_RINVSERTYP in SMPP
What is ESME_RINVSERTYP?
ESME_RINVSERTYP (Error Code: 0x00000015) is an SMPP error indicating that the service type provided in the PDU is invalid or not supported by the SMSC.
Possible Causes
- The
service_type
field contains an invalid or unrecognized value. - The SMSC does not support the requested service type.
- There is a typo or incorrect formatting in the
service_type
field. - The ESME does not have permission to use the specified service type.
When Does It Happen?
This error occurs when sending a submit_sm
, deliver_sm
, or data_sm
PDU with an invalid service_type
.
Example SMPP PDU Transaction
Incorrect submit_sm
PDU (Invalid Service Type)
00000033 (Length) 00000004 (Command ID for submit_sm) 00000000 (Command Status) 00000001 (Sequence Number) 696E7661 6C696400 (Invalid Service Type: "invalid") 01 (Source Address 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_RINVSERTYP
00000010 (Length) 80000004 (Command ID for submit_sm_resp) 00000015 (Command Status - ESME_RINVSERTYP) 00000001 (Sequence Number)
Issue: The service_type
provided ("invalid") is not recognized by the SMSC.
How to Solve It?
- Ensure that the
service_type
is set to a valid value as per the SMSC's specifications. - Check for typos or incorrect encoding in the
service_type
field. - Verify with the SMSC provider which service types are supported.
- Consult the SMPP specification to use standard service types like
"CMT"
,"CPT"
,"VMN"
, etc. - Enable debugging logs to inspect the exact values being sent in the PDU.
If the issue persists, contact the SMSC provider to clarify supported service types and resolve configuration issues.