Status (Report)

Description

DELIVERED

Delivered to the handset

ACCEPTED_BY_CLIENT

Message received by AT&T GSMS for handling by  the AT&T GSMS Inbound service

ACCEPTED_BY_NETWORK_ELEMENT

Message has been submitted towards the Mobile Operator for for delivery to the handset. (If Delivery Receipts were not requested or the Mobile Operator does not support Delivery reports, the message may have been delivered, however the AT&T GSMS has not received any response from the network to say delivered. )

DELIVERED_TO_CLIENT

When forwarding an MM& to an external application

Status (Report)

Description

REJECTED

Message has been rejected by the MMSC

EXPIRED

Message has been determined by AT&T GSMS as expirying before delivery.

Messages can be expired on the AT&T GSMS platform  or from the Operator MMSC. There is no differentiation of where the message has expired

FILTERED

Message delivery has been prevented by a filtering BLACK LIST or WHITE LIST.

INVALID_SOURCE_ADDRESS

The Mobile  Operator rejected the request due to an incorrect Source address being provided.

SUBMIT_MULTI_SPLIT

Status (Report)

[Error Code OR ErrorCode]

Description

Error Code = 307

Possible Issues:

•

Action to Take:

•

Error Code = 336

Possible Issues:

•

Action to Take:

•

Error Code = 710

Possible Issues:

•

Action to Take:

•

1000

Possible Issues:

•None

This code indicates that the request was executed completely (successfully)

1100

Possible Issues:

•None

No Issue, this is a partial success response. This code indicates that the request was executed partially but some parts of the request could not be completed.

Lower order digits and the optional Details element may indicate what parts of the request were not completed.

ErrorCode = 2000

Possible Issues:

•Client error

•Client made an invalid request

ErrorCode = 2001

Possible Issues:

•Operation restricted

•The request was refused due to lack of permission to

execute the command.

Error Code = 2002 or

ErrorCode = 2002

Possible Issues:

•Operation restricted - The request was refused due to lack of permission to execute the command.

•Address Error, The address supplied in the request was not in a recognized format or the MMS Relay/Server ascertained that the address was not valid for the network because it was determined not to be serviced by this MMS Relay/Server. When used in response-result, and multiple recipients were specified in the corresponding push submission, this status code indicates that at least one address is incorrect.

Action to Take:

•Check the address before trying again.

ErrorCode = 2003

Possible Issues:

•2003 Address Not Found The address supplied in the request could not be located by the MMS Relay/Server. This code is returned when an operation is requested on a previously submitted message and the MMS Relay/Server cannot find the message for the address specified.

ErrorCode = 2004

Possible Issues:

•2004 Multimedia content refused The server could not parse the MIME content that was attached to the SOAP message and indicated by the Content element or the content size or media type was unacceptable.

ErrorCode = 2005

Possible Issues:

•Message ID Not found This code is returned when an operation is requested on a previously submitted message and the MMS Relay/Server cannot find the message for the message ID specified or when the VASP receives a report concerning a previously submitted message and the message ID is not recognized.

ErrorCode = 2006

Possible Issues:

•2006 LinkedID not found This code is returned when a LinkedID was supplied and

the MMS Relay/Server could not find the related message.

Error Code = 2007

ErrorCode = 2007

Possible Issues:

•Message format corrupt An element value format is inappropriate or incorrect.

Action to Take:

•You may be sending with a content type that is not supported. Please check this before trying again. If the problem continues please raise this issue to your support agency.

Error Code = 3000

Possible Issues:

•Server Error The server failed to fulfil an apparently valid request.

Action to Take:

•Check your addressing, your message format (including content) and your SMIL template before sending again. If the problem continues please raise this issue to your support agency.

Error Code = 3001

Possible Issues:

•Not Possible The request could not be carried out because it is not possible. This code is normally used as a result of a cancel or status query on a message that is no longer available for cancel or status query. The MMS Relay/Server has recognized the message in question, but it cannot fulfil the request because the message is already complete or status is no longer available.

Action to Take:

•Please raise this issue to your support agency.

Error Code = 3002

Possible Issues:

•Message rejected Server could not complete the service requested.

Action to Take:

•MMSC rejected the request. Please raise this issue to your support agency.

Error Code = 3003

Possible Issues:

•Multiple addresses not supported The MMS Relay/Server does not support this operation on multiple recipients. The operation MAY be resubmitted as multiple single recipient operations.

Action to Take:

•You are possibly sending to multiple recipients. Try again with a single recipient. If this continues please raise it with your support agency.

Error Code = 4000

Possible Issues:

•General service error

•4000 General service error The requested service cannot be fulfilled.

Action to Take:

•This is a generic error, check your addressing, your message format (including content) and your SMIL template before sending again. If the problem continues please raise this issue to your support agency.

Error Code = 4001

Possible Issues:

•4001 Improper identification Identification header of the request does not uniquely

identify the client (either the VASP or MMS Relay/Server).

Action to Take:

•You could not be authorized, please check your username and password. If the problem continues please raise this issue to your support agency.

Error Code = 4002

Possible Issues:

•4002 Unsupported version The version indicated by the MM7 Version element is not supported.

Action to Take:

•Update your request to provide a lower version of the MMS  MM7 schema.

Error Code = 4003

Possible Issues:

•4003 Unsupported operation The server does not support the request indicated by the MessageType element in the header of the message.

Action to Take:

•The interface did not support the action that you were trying to implement. Please check your message, its content and addressing before trying again.

Error Code = 4004

Possible Issues:

•4004 Validation error The SOAP and XML structures could not be parsed, mandatory fields are missing, or the message-format is not compatible to the format specified. Details field may specify the parsing error that caused this status.

Action to Take:

•Message formatting was incorrect. Please check your SMIL before trying again.

Error Code = 4005

Possible Issues:

•4005 Service error, The operation caused a server (either MMS Relay/Server or VASP) failure and should not be resent.

Action to Take:

•Permanent failure occurred, please contact your support agency

Error Code = 4006

Possible Issues:

•Service unavailable, This indication may be sent by the server when service is

temporarily unavailable, e.g. when server is busy

Action to Take:

•May be an issue with your service provisioning.

•Service may be experiencing congestion, please wait a moment before trying again.

Error Code = 4007 or

ErrorCode = 4007

Possible Issues:

•Service denied, possibly: Maximum allowed message size exceeded!

•Service denied, possibly: The client does not have permission or funds to perform the requested operation.

Action to Take:

•Check your message size and try again.

Status (Report)

Description

ENROUTE_IN_CIQ

MM7 Interface from 3rd Party Application. Message has been received by AT&T GSMS, but could not be processed, most likely due to malformed message

ENROUTE_IN_COQ

Message could not be delivered to 3rd Party MM7 Application. Most likely that the application is not successfully receiving requests

ENROUTE_IN_NOQ

Message is in the Queue for delivery to the Network (MMSC)