Tag Length Values, also known as TLVs, are optional parameters that can be defined by the aggregator. When using Vibes, you can use these TLVs to define carrier code, specify an alternate route upon message failure, and more. For a full list of our TLVs, please reference our complete protocol PDF.

Carrier Codes

This tag is used to identify the carrier in both incoming (MO) messages and outgoing (MT)) messages.

Message Payload

This field is part of the SMPP 3.4/5.0 Specification and is used in place of the short_message fields to send messages up to 900 characters or 1500 bytes. Note that messages must be 900 characters or less and not exceed 1500 bytes. Byte size per character will vary based on encoding used.

The message_payload parameter contains the user data. Its function is to provide an alternative means of sending texts above the limit of the short_message field. Applications, which need to send messages longer than 140 bytes, should use the message_payload tag.

When used in the context of a submit_sm PDU, the sm_length field must be set to zero.

❗

Length limitations

An error ESME_RINVMSGLEN (0x00000001) - Message Length is Invalid will be returned if the user data is greater than 1500 bytes or if the encoded message exceeds 900 characters.

Long Message Segment Info

If a message has been split into multiple parts, this tag identifies which part of a long message segment the DLR is referring to. For example, if a long message is sent in 3 parts, the tag will show if the DLR is referring to part 1, 2, or 3.