Field #

Field Name

Description

1

Id

Order ID - the Order ID generated by the AT&T GSMS.

2

Status

AT&T GSMS status of the message

See Message Status Description for further information.

3

To Presentation

If configured in the list as the 'Destination Presentation' field, this will contain the associated field / combination of fields relating to the recipient.

If not configured in the broadcast list, then this will relate to the actual MSISDN

For further information on how to set up the 'To' presentation please see the 'Contacts / Groups / Lists' section.

4

From Presentation

If configured in the list as the 'Destination Presentation' field, this will contain the associated fields / combination of fields relating to the source address of the originating mobile.

If not configured in the broadcast list, then this will relate to the actual MSISDN

For Further Information on how to set up the 'From' presentation please see the 'Contacts / Groups / Lists' section.

5

Client Submit Time

The time that the client submitted / received the message, i.e. the time that the AT&T GSMS received the message for handling.

Standard date format is YYYY-MM-DD HH:MM:SS.###

6

Network Submit Time

The time that the network received / submitted the message, i.e. the time that the SMSC Received the message for handling

Standard date format is YYYY-MM-DD HH:MM:SS.###

7

User

The user who deployed the campaign.

8

Cost Center Label

The cost center or user deploying the campaign.

9

Registered

States whether outbound message requested delivery report / registered delivery:

•True

•False

10

Labels

Applied labels, if any

11

MCC

Mobile country code

12

MNC

Mobile network code

13

To

Recipient address.

This is the address who is receiving the message.

i.e. the MSISDN if the target is a mobile number, or an email address for email outbound campaigns.

For Inbound campaigns this may be a short code or what ever address is set up to receive messages on.

14

From

Originating address.

This is the address who is originating the message.

i.e. the  MSISDN if it is a mobile campaign or an email address for email outbound campaigns.

For Inbound mobile campaigns, this will be the mobile that submitted the message.

15

Order Id

The Order ID generated by the AT&T GSMS.

16

Order Name

The name of the broadcast as provisioned from the web front end.

17

Message Type

The message type example:

•SMS

•Email

•Voice

18

Message

The message content.

For SMS this is the message itself bound by quotes.

Note: If you wish to include double quotation marks (") in the actual displayed text of your message, two double-quotation characters must be used (""). The platform has been configured to automatically carry out this function.

For email this does not carry the message.

19

Client Message Id

For a campaign from the web interface the Client Message ID is the Order ID allocated by SCM. The message will go out with something like client message id e.g. 12345

If it is coming into an Inbound with Order ID 98765, then the Client Message ID will be 12345.98765

Additional purpose of this field is to allow an external application sending via an  API can specify their own Client Message ID as their own reference number.

20

Requires Acknowledgement

Status to depict if the message was sent with the requisite of sending acknowledgement :

•True

•False

21

Acknowledged Time

Time when the message was acknowledged

22

Company

Name of the company

Over time, additional fields may be added onto the report to provide further detail. If ingesting the report content into a automated system, please include the flexibility to add additional field mapping capability.