Message Detail Record (MDR) Field Descriptions

Follow

Emma Bradley

Updated

What is a Message Detail Record (MDR)?

A Message Detail Record (MDR) is a report that documents the details of the SMS and MMS messages that you send and or receive.

 

How can I gain access to MDRs?

Navigate to the ‘Reports’ tab of the Bandwidth Dashboard to get started. Check out our video demonstration on How to Download Message Detail Records (MDRs) on the Bandwidth Learning Lab! 

 

What data is provided in MDRs?

The table below describes the fields available in the MDR export file:

*All times will be in UTC (Coordinated Universal Time)

 

Field

Description

Detailed Description

Example Value

AccountId

Customer Service Account ID

This is the Account ID associated to your Bandwidth Dashboard service account. MDRs are aggregated by individual service accounts.

200001

MessageType

Type of message

This is the type of messaging channel being used. This will be populated as SMS or MMS as Bandwidth currently supports SMS and MMS messaging.

SMS/ MMS

MessageID

Message Identifier

This is a unique identifier given to each segment of a message which aids in identification of the message segment if needed. For example, this may be used during troubleshooting to identify the message throughout Bandwidth’s systems.

00000000-0000-0000-000000000000

CallDirection

Message Direction

You will see two values here to represent the direction of the messaging: inbound or outbound.

INBOUND/ OUTBOUND

SourceTn

From Number

The number that initiated the message. This number will follow E.164 format.

15555551234

DestinationTn

To Number

This is the number that is receiving the message. It will follow the E.164 format.

525556667777

TimeStamp

Time Bandwidth Received the Message

Date and time a message was received by Bandwidth.

2018-11-01T00:07:45.622Z

ErrorCode

Success Error Code

This is a historical field used to reflect the success response code, you will see either a blank or 200 here. Please reference the MessageStatus attribute for a concise friendly status description on the success or failure of the message.

200

IntlZone

Zone Reach

This is the Zone associated with the reach of your SMS message. Toll Free, MMS and Short Code reach are not currently divided into Zones.  


Based on the Destination Carrier and Country, SMS messages reach to the specific zone listed in this field.  For more information about Bandwidth’s Messaging Reach, visit this page.

1 - 5

MessageDate

Message Date

This date is used for billing purposes to associate a given message to a particular service period based on the date listed here.  

Since each record represents a segment, a segmented message could have different service periods for billing.

12/1/2018

GlobalAccountID

Global Customer Account Number

This is the Global Account Number associated with you as the customer. If you have multiple service accounts, this allows you to be identified as a single customer.

BW-0000000

ReceivedTimestamp

Time Bandwidth Received the Message

This represents the date and time a message was received by Bandwidth. 

2018-11-01T00:07:45.622Z

SentTimestamp

Message Sent Time (Initial)

This represents the date and time the message was first attempted to be sent by Bandwidth.

2018-11-01T00:07:45.622Z

CompletedTimestamp

Time of Final Acceptance of Message

When Bandwidth sends a message, it may not always succeed on the first attempt. This is the date and time when a message has finally been accepted or timeout has occurred.

2018-11-01T00:07:45.622Z

MessageSegments

Message Segments

The quantity of segments the long message is broken into when sent or received.

A single message may be broken into multiple segments for delivery as dictated by the underlying messaging protocol. The number of characters at which segmentation occurs is variable depending upon the type of characters used in the message body.

See this page for information on character encoding.

1

SegmentNumber

Segment Number

This is the segment number of the long message.

You can use this field and the attribute MessageSegments to determine which segment this record represents ex: 2 of 2, 1 of 2

1

MessageLength

Message Length

For SMS messages, this is the count of characters in a message, including spaces.

Currently for MMS Messages, this is the overall size of the message. In the future this will be blank for MMS messages and a new messaging attribute, Messaging Size, will reflect message size.

160

Billable

Message Billed

The field reflects if the message will be considered for billing by the Bandwidth billing system. These records show all messages associated to your account, depending on the status of the message Bandwidth may not charge you for that message.

Bandwidth bills for Outbound Messaging on the successful attempt to deliver your message. For Inbound Messaging, Bandwidth bills on a successful attempt to deliver the message to you.

Yes/No

SourceCountry

Source Country

The country of the text message sender. This is the country of the “from” number, or the message sender.

United States

SourceState

Source State

The state of the text message sender. This is the state of the “from” number, or the message sender.

NC

SourceLATA

Source LATA

The Local Access Transport Area (LATA) of the "Source" number. This is the LATA of the “from” number, or the message sender.

426

DestinationCountry

Destination Country

This is the country of the “to” number, or the message recipient. The “to” number is the DestinationTN.

United States

DestinationState

Destination State

This is the state of the “to” number, or the message recipient.

NC

DestinationLATA

Destination LATA

The Local Access Transport Area (LATA) of the "Destination" number. This is the LATA of the “to” number, or the message recipient.

426

MessageClass

Message Class

This field is specific to A2P messaging. If you are contracted and approved to run Local A2P campaigns, this is the message class that’s assigned to your campaign.

A, B, C, P

CampaignID

Campaign ID

This field is specific to A2P messaging. If you are contracted and approved to run Local A2P campaigns, this is the CampaignID that’s assigned to your campaign. This field will be blank if it does not apply to you.

user-specific

DLRCode

Delivery Receipt Response Code

This is a code returned in a delivery receipt (DLR) by the Bandwidth platform. It provides information describing the success or failure of delivering the message to the end user or downstream system. This attribute is applicable to outbound messages only.

Note: DLRs are always requested for V2 Messaging API users, but SMPP customers must request it. Please refer to this page for a list of HTTP V2 error codes.  SMTP error codes are here.

0 - Success

902 - Timeout

470 - SPAM Detected



MdrID

MDR Identifier

This is a unique identifier for this message detail record.  Note that each segment of a message has an individual MDR.

00000000-0000-0000-000000000000

MessageStatus

Message Status

This field will show the summary status of a message. Bandwidth summarizes the status of the message across 9 status values as shown below.  Each status has a Y or N to designate whether this status is considered billable. 

 

  1. REJECTED-CUSTOMER: May include messages which failed to be accepted by the customer for a variety of reasons. (N)
  2. REJECTED-PROVIDER: A downstream destination carrier has rejected the message. There are several reasons for this, common reasons may be - malformed to number, carrier unavailable, carrier application error. (N)
  3. REJECTED-BW: Bandwidth rejected the message.  This could be due to improper formatting, authorization violations or systems failures. (N)
  4. REJECTED-BW-SPAM: Bandwidth rejected as SPAM. (Y)
  5. REJECTED-PROVIDER-SPAM:  Provider rejected as SPAM. (Y)
  6. FAILED: Message could not be transmitted to customer or to a provider. (N)
  7. ACCEPTED: Message was accepted by the Customer or the Provider and no DLR was requested. (Y)
  8. DELIVERED: Message was accepted and a successful DLR was provided. (Y)
  9. DELIVERY-FAIL - Message was accepted, but DLR code indicated delivery failure or Bandwidth timed out waiting for the receipt of the DLR. (Y)

REJECTED-CUSTOMER

REJECTED-PROVIDER

REJECTED-BW

REJECTED-BW-SPAM

REJECTED-PROVIDER-SPAM

FAILED

ACCEPTED

DELIVERED

DELIVERY-FAIL



Article is closed for comments.