Delivery Status Service#

Service Setup#

The Service Provider sends a message delivery report to the Partner’s URL configured to send delivery statuses.

The URL for statuses is set in the integration settings when enabling the service, it can also be sent in notifyUrl parameter. The URL sent in the parameter is deemed priority, and if the parameter is not sent or an incorrect URL is sent, the message delivery report is sent to the URL specified when the connection was configured.

HTTP method: POST.

Delivery Report#

 1 {
 2   "id":"8770599",
 3   "mtNum":"107930572",
 4   "status":2,
 5   "type":"SMS",
 6   "doneDate":"2019-05-05T10:20:35+0300",
 7   "submitDate":"2019-05-05T10:19:55+0300",
 8   "sourceAddr":"SOURCE",
 9   "destAddr": "72101234567",
10   "text":"message_text",
11   "partCount":"001",
12   "errorCode":"0",
13   "mccMnc":"25012",
14   "trafficType":0
15 }

Delivery Statuses#

Код

Delivery status

Description

0

SEND

Sent to the operator, the final status is not known yet.

2

DELIVERED

Delivered to the operator, after delivery it is possible to wait for the status of reading by the subscriber.

5

UNDELIVERED, REJECTED

Rejected by the operator/undelivered to the operator. The reason of non-delivery is specified in the errorCode parameter. It is the final status, no further statuses are expected.

9

READ

Status indicating the message is read by a subscriber. For all messages except FLASHINGCALL and SMS. It is the final status, no further statuses are expected.

Description of Error Codes#

The section provides a description of the reasons for the non-delivery of messages of various types (parameter status=5).

Code

Error message

Error description

1

unknown

An error unknown to the platform occurred during the message delivery process, or the operator did not provide an error in the delivery report.

2

absent-subscriber

The subscriber’s device was turned off or it was out of network coverage during entire attempt to deliver the message.

3

call-barred

The subscriber’s device is blocked, either the subscriber has the ban on receiving messages enabled or the subscriber is in roaming with the ban on receiving messages while roaming enabled.

4

failure

An error occurred at the transport layer of the signaling network during message delivery.

5

memory-capacity-exceeded

The subscriber’s phone memory is full.

6

teleservice-not-provisioned

The subscriber doesn’t have the message receiving service activated.

7

timeout

The switching equipment on which the subscriber s registered is not responding.

8

unknown-subscriber

The subscriber’s phone number is incorrect, or the subscriber’s phone has been switched off for a very long time.

9

duplicated

A message was discarded by the platform as the function cutting duplicate messages was activated.

10

filtered

The message was discarded by the platform because one of the message filters, such as a spam filter, was triggered.

11

unrouted

Routing error at the platform configuration.

12

oper-blacklisted

Subscriber’s number is on the operator’s blacklist.

13

oper-invsrcaddr

Message sending from a sender’s name that is not registered by the operator.

14

oper-spamfiltered

On the operator’s side, a SPAM filter was activated based on the text of the message.

16

busy

At the time of SMS message delivery, the phone was busy either receiving or transmitting another short message.

18

bad-params

When sending a message, one or more SMS message parameters were specified incorrectly, or mandatory parameters were not included.

20

consumer-phone-not-found

The subscriber’s phone does not accept SMS messages.

28

provider-error

The SMS message was sent to a number belonging to another mobile operator.