Reference section - SMPP

Message Submission TLVs

SMPP Message Submission TLVs

SMPP v5

Message Submission Request TLVs

This section lists TLVs that may be used for message submission operations.

TLV NameDescriptionRef.
alert_on_msg_deliveryRequest an MS alert signal be invoked on message delivery.4.8.4.2
billing_identificationBilling information passed from ESME to MC.4.8.4.3
callback_numA call-back number associated with the short message.

This parameter can be included a number of times for multiple call-back addresses.
4.8.4.15
callback_num_atagAssociates a displayable alphanumeric tag with the call-back number.

If this parameter is present and there are multiple instances of the callback_num parameter then this parameter must occur an equal number of instances and the order of occurrence determines the particular callback_num_atag which corresponds to a particular callback_num.
4.8.4.16
callback_num_pres_indDefines the call-back number presentation and screening.

If this parameter is present and there are multiple instances of the callback_num parameter then this parameter must occur an equal number of instances and the order of occurrence determines the particular callback_num_pres_ind which corresponds to a particular callback_num.
4.8.4.17
dest_addr_np_countryE.164 information to the operator country code.4.8.4.20
dest_addr_np_information Number portability information for the destination address.4.8.4.21
dest_addr_np_resolution Number portability query indicator.4.8.4.22
dest_addr_subunitThe subcomponent in the destination device for which the user data is intended.4.8.4.23
dest_bearer_typeThe correct bearer type for delivering the user data to the destination.4.8.4.24
dest_network_id Identification of destination network.4.8.4.25
dest_network_type The correct network for the destination device.4.8.4.26
dest_node_id Identification of destination node.4.8.4.27
dest_subaddress The sub-address of the message destination.4.8.4.28
dest_telematics_id The telematics identifier associated with the destination.4.8.4.29
dest_portIndicates the application port number associated with the destination address of the message. This parameter should be present for WAP applications.4.8.4.30
display_timeProvides the receiving MS with a display time associated with the message.4.8.4.31
its_reply_typeThe MS user’s reply method to an SMS delivery message received from the network, is indicated and controlled by this parameter.4.8.4.33
its_session_infoSession control information for Interactive Teleservice.4.8.4.34
language_indicatorIndicates the language of an alphanumeric text message.4.8.4.35
message_payloadContains the extended short message user data. Up to 64K octets can be transmitted.

Note: The short message data should be inserted in either the short_message or message_payload fields. Both fields should not be used simultaneously.

The sm_length field should be set to zero if using the message_payload parameter.

Note: In the case of data_sm, the message_payload TLV is the only means of specifying text.
4.8.4.36
more_messages_to_sendIndicates that there are more messages to follow for the destination SME.4.8.4.38
ms_msg_wait_facilitiesThis parameter controls the indication and specifies the message type (of the message associated with the MWI) at the mobile station.4.8.4.40
ms_validityIndicates validity information for this message to the recipient MS.4.8.4.41
number_of_messages Indicates the number of messages stored in a mail box.4.8.4.43
payload_typeDefines the type of payload (e.g. WDP, WCMP, etc.).4.8.4.44
privacy_indicatorIndicates the level of privacy associated with the message.4.8.4.45
qos_time_to_live Time to live as a relative time in seconds from submission.4.8.4.48
sar_msg_ref_numThe reference number for a particular concatenated short message.4.8.4.46
sar_segment_seqnumIndicates the sequence number of a particular short message fragment within the concatenated short message.4.8.4.49
sar_total_segmentsIndicates the total number of short message segments within the concatenated short message.4.8.4.50
set_dpfIndicator for setting Delivery Pending Flag on delivery failure.4.8.4.52
sms_signalIndicates the alerting mechanism when the message is received by an MS.4.8.4.53
source_addr_subunitThe subcomponent in the destination device, which created the user data.4.8.4.54
source_bearer_typeThe correct bearer type for delivering the user data to the destination.4.8.4.55
source_network_id Identification of source network.4.8.4.56
source_network_typeThe correct network associated with the originating device.4.8.4.57
source_node_id Identification of source node.4.8.4.58
source_portIndicates the application port number associated with the source address of the message. This parameter should be present for WAP applications.4.8.4.59
source_subaddressThe sub-address of the message originator.4.8.4.60
source_telematics_id The telematics identifier associated with the source.4.8.4.61
user_message_reference ESME assigned message reference number.4.8.4.62
user_response_codeA user response code. The actual response codes are implementation specific.4.8.4.63
ussd_service_opThis parameter is used to identify the required USSD Service type when interfacing to a USSD system.4.8.4.64

Message Submission Request TLVs

The following table contains TLVs that can be returned in a submit_sm_resp or data_sm_resp PDU. All TLVs are relevant to transaction message mode only (ref. 4.2.10.4).

TLV NameDescriptionRef.
additional_status_info_textASCII text giving a description of the meaning of the response.4.8.4.1
delivery_failure_reasonInclude to indicate reason for delivery failure.4.8.4.19
dpf_resultIndicates whether the Delivery Pending Flag was set.4.8.4.32
network_error_codeError code specific to a wireless network.4.8.4.42

Find out more...

Please provide your name.
Please provide a valid company name.
Please type your message.
Please provide a valid email address.