How do I enable MMS Delivery Receipts when sending messages?

Follow

Emma Bradley

Updated

MMS Delivery Receipts changes for V2 API users

Beginning July 31, 2020, Bandwidth will support MMS Delivery Receipts (DLRs) when sending messages.

If you use our HTTP interface to send messages, you’ll need to enable this functionality during this initial beta phase. To request this, please reach out to your Bandwidth Support Team.

Once this is enabled on your account, Bandwidth will automatically request DLRs when you send MMS or Group messages. As a result, you'll need to support all three possible callback events for Messaging: Message Delivered, Message Failed, and Message Queued

Screen_Shot_2020-07-29_at_11.41.39_AM.png

New callback messaging events

Bandwidth is introducing a new callback event for MMS. A message-queued callback event indicates the message has been sent to the downstream carrier and is waiting on the return of the requested DLR. This event will be sent before the message-delivered event on successful message authorization of MMS message. If the downstream provider doesn't return or support DLRs, you'll only receive this event to indicate the message was acknowledged by the downstream carrier but they provided no additional delivery information. 

The message-delivered event will now reflect a true message delivery for MMS and Group Messages, effectively representing an acknowledgement from the downstream provider that they've received the message. 

Note: Wireless carriers don't support handset DLRs on local numbers. When sending local messages, the delivery event you receive will represent delivery to the wireless carrier only. Where available from the carrier, toll-free and short code messages will reflect a delivery to the handset.

When the carrier responds to the request for a DLR with a failed status and error code, you may receive a message-failed callback event. This callback will also include an error code that indicates why the message wasn’t deliverable. Please review our list of error codes or visit our support articles about troubleshooting messages if you need help resolving the error. 

What if I don’t want to enable DLRs for MMS?

If you don’t request the MMS DLRs to be enabled on your account, you’ll continue to receive a message-delivered event callback as you do today. This event will continue to indicate that  Bandwidth received the message, but it won’t reflect whether the downstream carrier confirmed the receipt of this message. With the release of this beta phase, we’ll update the following warning message to indicate that MMS DLRs are now available. 

mms_dlr_warning.png

Note: If you don’t enable the MMS DLRs, you’ll continue to receive a callback without true delivery information.

For more information about the message delivered events, please see our developer documentation. 

New MMS HTTP messaging errors

Note: There will be new messaging delivery error codes specific to MMS. For the full list of errors codes, please see our developer documentation. 

Delivery error code

Error code description

Explanation of error

4300

malformed-message

This error indicates the message is formatted incorrectly. 

4410

media-unavailable

There was an error retrieving the media from the media web server. Check the media URL and try to access directly to see if the media can be fetched successfully.

4411

rejected-size-limit

The total size of MMS message media/attachments exceeded the max file size supported.

4412

media-content-invalid

The message failed because the media content type isn't supported. 

4420

rejected-carrier-does-not-exist

The upstream provider doesn't exist in our configuration.

4421

rejected-forbidden-no-destination

The destination is considered forbidden when the account isn't provisioned for that destination. 

4435

forbidden-too-many-recipients

The maximum limit of 10 participants in a Group has been exceeded. 

Article is closed for comments.