MM7_DeliveryReport

Receive Delivery Reports for previously submitted MT

Skycore sends delivery reports using the MM7 Delivery Report message type i.e., “DeliveryReportReq”. The delivery report indicates the current state of the original submit request message. We will send a delivery report to your platform only when the appropriate information is available. If the delivery report message is accepted or rejected then respond with an “DeliveryReportRsp”, including a status that indicates why the delivery report was accepted/rejected. For information about the status codes returned for Delivery Reports, please See Delivery report status.

MM7_DeliveryReport.REQ

MM7 delivery report request elements

Element Description Returned
TransactionID This identifies the DeliveryReportReq/DeliveryReportRsp pair. It is Skycore generated ID. Always
DeliveryReportReq Identifies the message as an MM7 Delivery Report. Always
MM7Version Identifies the MM7 Version.
See all supported MM7 Versions & Namespaces
Always
Recipient The mobile phone number of the end user. This must be a valid mobile number in international format without a leading + symbol; for example: 12515550123 (US) and 447700900750 (UK). Always
Sender Your shortcode. This should match the same information that is linked in the MT configuration, and generally to the service you are providing. Always
MessageID Skycore generated ID linked to the submitted message. This ID was returned to your system in the initial response (SubmitRsp) to your MT MMS request. Always
Date The date and time of the submission of the multimedia message (timestamp). Value is in UTC. Always
MMStatus A code that indicates whether the MT message was delivered successful or failed. For information about the status codes returned for Delivery Reports, please See Delivery report status. Always
UACapabilities Also known as MMS User Agent capabilities. This describes the capabilities of the MMS User agent of the mobile handset. Only when provided by mobile operator

See Unsupported elements

Example

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
   <TransactionID xmlns=
   "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" 
   soap-env:mustUnderstand="1">10000001</TransactionID>
</soap-env:Header>
<soap-env:Body>
   <DeliveryReportReq xmlns=
   "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4">
      <MM7Version>6.8.0</MM7Version>
      <MessageID>369500617770864640</MessageID>
      <Recipient>
         <Number>16175550123</Number>
      </Recipient>
      <Sender>
         <Number>111122</Number>
      </Sender>
      <Date>2015-03-16T14:03:51.749Z</Date>
      <MMStatus>Retrieved</MMStatus>
      <StatusText>Success</StatusText>
      <UACapabilities UAProf="Samsung Galaxy" />
   </DeliveryReportReq>
</soap-env:Body>
</soap-env:Envelope>

MM7_DeliveryReport.RES

MM7 delivery report response elements

Your system should respond to the delivery report request with a delivery report response containing the elements described in the following table. Returning any HTTP response other than HTTP 200 will trigger a retry.

Element Description Required
TransactionID Identifies the DeliveryReportReq/DeliveryReportRsp pair. It is part of the SOAP header. You must return the same transaction that was passed in the request or the transaction will not be accepted. No
DeliveryReportRsp Identifies the message as an MM7 Delivery Report Response. If you do not provide this element it will not be considered a valid response. Yes
MM7Version Identifies the MM7 Version.
See all supported MM7 Versions & Namespaces Typically you would return the MM7 Version passed in the request.
No
StatusCode A code that indicates whether you received the MO message request successfully. The status code for success is 1000. Any other status code other than 1000 will trigger a retry. Yes
StatusText Your human readable description of the status. This is informational only and not required. No


Example

<?xml version="1.0" encoding="UTF-8" ?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
   <TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" soap-env:mustUnderstand="1">1000001</TransactionID>
</soap-env:Header>
<soap-env:Body>
   <DeliveryReportRsp xmlns=
   "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4">
      <MM7Version>6.8.0</MM7Version>
      <Status>
         <StatusCode>1000</StatusCode>
         <StatusText>Successfully Received MMS.</StatusText>
      </Status>
   </DeliveryReportRsp>
</soap-env:Body>
</soap-env:Envelope>

Delivery Report Full Example

Request

POST / HTTP/1.1
SOAPAction: "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4"
Content-Type: multipart/related; type="text/xml"; 
Host: api.skycore.com
Content-Length: 2546
X-Skycore-Carrier-Id: 0001890
Connection: Keep-Alive

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
   <TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" soap-env:mustUnderstand="1">10000001</TransactionID>
</soap-env:Header>
<soap-env:Body>
   <DeliveryReportReq xmlns=
   "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4">
      <MM7Version>6.8.0</MM7Version>
      <MessageID>369500617770864640</MessageID>
      <Recipient>
         <Number>16175550123</Number>
      </Recipient>
      <Sender>
         <Number>111122</Number>
      </Sender>
      <Date>2015-03-16T14:03:51.749Z</Date>
      <MMStatus>Retrieved</MMStatus>
      <StatusText>Success</StatusText>
      <UACapabilities UAProf="Samsung Galaxy" />
   </DeliveryReportReq>
</soap-env:Body>
</soap-env:Envelope>

Response

HTTP/1.1 200 OK
Server: Apache
Content-Type: text/xml; charset=utf-8
Content-Length: 539
Date: Mon, 16 Mar 2015 14:03:32 GMT

<?xml version="1.0" encoding="UTF-8" ?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
   <TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" soap-env:mustUnderstand="1">1000001</TransactionID>
</soap-env:Header>
<soap-env:Body>
   <DeliveryReportRsp xmlns=
   "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4">
      <MM7Version>6.8.0</MM7Version>
      <Status>
         <StatusCode>1000</StatusCode>
         <StatusText>Successfully Received MMS.</StatusText>
      </Status>
   </DeliveryReportRsp>
</soap-env:Body>
</soap-env:Envelope>

MM7_DeliveryReport.REQ

Element Description
ApplicID This information element indicates the identification of the application that the delivery report is intended for. If a Reply-Applic-ID was indicated in the corresponding original MM, the recipient MMS Relay/Server shall set its value to that Reply-Applic-ID value. Otherwise, the recipient MMS Relay/Server shall set its value to the Applic-ID value that was indicated in the corresponding original MM
AuxApplicInfo If present, this information element indicates additional application/implementation specific control information. The recipient MMS Relay/Server shall insert it if Aux-Applic-Info was indicated in the corresponding original MM, in which case its value shall equal that Aux-Applic-Info value
MMSRelayServerID Identifier of the MMS Relay/Server
ReplyApplicID If present, this information element indicates a “reply path” to this delivery report, i.e. the identification of an application to which reply-MMs are addressed. The recipient MMS Relay/Server shall insert it into the MM1_DeliveryReport.REQ if the values of Applic-ID and Reply-Applic-ID in the corresponding original MM differ, in which case its value shall equal the Applic-ID value that was indicated in the corresponding original MM