Skip to main content
Skip table of contents

Delivery receipts (DLRs)

Delivery receipts and intermediate notifications have the following format and are contained in the short_message field of the deliver_sm:

CODE
	id:IIIIIIIIII sub:SSS dlvrd:DDD submit date:YYMMDDhhmm done date:YYMMDDhhmm stat:DDDDDDD err:EEE text:
  • id: message ID returned in submit_sm_resp (up to 64 characters in length)

  • sub: number of messages originally submitted (set to 001)

  • dlvrd: number of messages delivered (000 or 001)

  • submit date: When message was submitted by ESME

  • done date: When message reached final state

  • stat: State of message (see Name field below)

  • err: Error encountered during delivery (if any)

Additionally, the following TLVs are present in the delivery receipt:

TLV

Description

receipted_message_id

MC message ID of message being receipted. Should be present for MC Delivery Receipts and Intermediate Notifications.

message_state

Delivery state as shown in below table.

network_error_code

Error code specific to a wireless network (see error codes below).

Message states

State

Meaning

Name

Description

0

Scheduled

SCHEDLD

The message is scheduled. Delivery has not yet been initiated. (Intermediate)

1

Enroute

ENROUTE

The message is in enroute state. (Intermediate)

2

Delivered

DELIVRD

Message is delivered to destination. (Final)

3

Expired

EXPIRED

Message validity period has expired. (Final)

4

Deleted

DELETED

Message has been deleted. (Final)

5

Undeliverable

UNDELIV

Message is undeliverable. (Final)

6

Accepted

ACCEPTD

Message is in accepted state. (Final)

7

Unknown

UNKNOWN

Message is in invalid state.

8

Rejected

REJECTD

Message is in a rejected state. (Final)

9

Skipped

SKIPPED

The message was accepted but not transmitted or broadcast on the network. (Final)

Error codes

Values returned as error codes are those values returned in DLRs from supplier SMSCs.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.