SMPP Global SMS
MT command status codes
This topic describes both the standard status codes returned for MT messages and status codes returned for OpenMarket custom TLVs.
Search this page for a specific code or description:
submit_sm_resp command status codes
Status Code |
Description |
---|---|
0x00 |
No error. The MT was accepted. The ticket ID is included in the submit SM response. |
0x01 |
Message length is invalid. The message text is not included or exceeds the maximum length allowed for the destination carrier, supplier, or operator. |
0x02 |
Command length is invalid. The command length in the submit_sm header is invalid. |
0x03 |
Invalid command ID. The Command ID in the submit_sm header is invalid. |
0x04 |
Incorrect BIND status for given command. |
0x06 |
Invalid priority flag. |
0x07 |
Invalid registry flag. |
0x08 |
System error. You may retry submitting the MT if you receive this error. |
0x14 |
Message queue full. You may retry submitting the MT if you receive this error. |
0x15 |
Invalid service type. The service type value is longer than the allowed length in the PDU definition. |
0x43 |
Invalid esm_class field data. The esm_class contains a value which OpenMarket does not support in the submit_sm. 0x40 is supported as the UDH indicator (UDHI); 0x00 is supported as the default. |
0x45 |
submit_sm failed. |
0x48 |
Invalid source address TON. Only 0x01, 0x03, and0x05 are supported. |
0x49 |
Invalid source address NPI. OpenMarket only supports 0x00 and 0x01. |
0x50 |
Invalid destination address TON. Only 0x01 is supported. |
0x51 |
Invalid destination address NPI. Only 0x01 is supported. |
0x58 |
Throttling error. The message exceeded the configured throttle limit of messages per second. |
0x61 |
Invalid schedule delivery time. |
0x62 |
Invalid message validity period. |
0x63 |
Predefined message invalid or not found. A value was submitted for the optional predefined message parameter. This parameter is not supported. |
OpenMarket submit_sm_resp command status codes for custom TLVs
OpenMarket custom TLV command status codes fall within a 0x400 range.
OpenMarket submit_sm command status codes
Status Code |
Description |
---|---|
0x406 |
Invalid data coding scheme. |
0x407 |
Message payload and short message cannot both contain data. |
0x409 |
Invalid user data header format. |
0x42E |
An OpenMarket TLV included in the MT has an invalid value. This occurs if the value for the following OpenMarket TLVs is invalid—for example, too long or empty:
|
0x43B |
The account is not provisioned for global one- or two-way SMS. |
0x43D |
Account is blocked in the SMS provisioning database. |
0x43E |
Invalid request. The campaign ID value is invalid. The TLV value is greater than the allowed maximum length, or is empty. |
0x43F |
Invalid request. The promotional value is invalid. The TLV value is greater than the allowed maximum length or is empty. |
0x440 |
Invalid request. The note 1 value is invalid. The TLV value is greater than the allowed maximum length or is empty. |
0x441 |
Invalid request. The note 2 value is invalid. The TLV values is greater than the allowed maximum length or is empty. |
0x442 |
The TLV value is not one-way or two-way. |
0x443 | Account not enabled for SMPP. |