0 | Message sent | OpenMarket successfully sent the message to the carrier's network. | Retry Prohibited | SMS Messaging | No |
1 | Processing request |
| Retry Prohibited | SMS Messaging | No |
2 | Message accepted |
|
| SMS Messaging | Conditional |
3 | Message buffered with carrier and waiting for a response |
| Retry Prohibited | SMS Messaging | No |
4 | Message delivered | The carrier successfully delivered the message to the end user. | Retry Prohibited | SMS Messaging | No |
301 | Only one top level request element is permitted |
| Retry Prohibited | SMS Messaging | No |
303 | The required version attribute of the request element was not found in the request |
| Retry Prohibited | SMS Messaging | No |
304 | The required protocol attribute of the request element was not found in the request |
| Retry Prohibited | SMS Messaging | No |
306 | The XML POST parameter cannot be empty |
| Retry Prohibited | SMS Messaging | No |
307 | The request was an ill-formed XML document | Common cause would be setting a url_encoded content-type, missing parameters or incorrect syntax in the XML | Retry Prohibited | SMS Messaging | No |
321 | Invalid request version |
| Retry Prohibited | SMS Messaging | No |
322 | Invalid request protocol |
| Retry Prohibited | SMS Messaging | No |
323 | Invalid request type |
| Retry Prohibited | SMS Messaging | No |
339 | Carrier ID is not an integer. | The carrier ID is not an integer, or the carrier ID attribute was submitted with a null value. | Retry Prohibited | SMS Messaging | No |
341 | Transaction failed; Carrier ID does not exist | Verify the carrier ID used in the message submitted to OpenMarket. | Retry Prohibited | SMS Messaging | No |
345 | Unable to determine carrier ID from destination address | Number not associated with a carrier our system supports. Verify from MO SMS if possible. Please contact OpenMarket support for further information. | Retry Prohibited | SMS Messaging | No |
349 | Destination address contains non-numeric characters | Double check your numbers for improper input | Retry Prohibited | SMS Messaging | No |
350 | A destination address is required | Check the destination address against the OpenMarket Deactivated Numbers Reports; if the number is listed you cannot resubmit the billing to the destination address unless you receive an opt-in from a wireless subscriber | Retry Prohibited | SMS Messaging | No |
351 | Transaction failed: Invalid destination address value | Error 351 occurs in two general scenarios: 1. The 351 error is returned in the response to an MT submit. In this scenario the destination address in the message was not provided or was not properly formatted. 2. The 351 error is returned in a delivery receipt or in response to a Query API call. In this scenario, the 351 error can have multiple meanings, some of which are dependent upon the destination mobile operator: * The destination address does not belong to the mobile operator. * For US operators AT&T, T-Mobile, and MetroPCS, the error may also mean the phone number belongs to a prepaid user who does not have sufficient credits to receive an SMS message. * For US operator T-Mobile, the error may mean the end user is not provisioned to receive SMS from all short codes or specific short codes. Additionally, T-Mobile US does not deliver short code SMS to any of its resellers' numbers. You will receive this error if you attempt to send a short code MT to a T-Mobile reseller number. A reasonable course of action would be to retry using a US long code as the MT source address. * For US destination addresses, it is possible the phone number is deactivated. Check the "Deact" reports on Customer Center. * Global SMS: In most cases OpenMarket does not receive information from global operators to further refine the error case. | In general, mobile operators do not want SMS senders to retry MT messages, which have failed with OpenMarket error 351. However, given the range of different possible root causes, OpenMarket does not think is it unreasonable to retry. For example, retry once every day over the course of 7 days. The first check you should make for US and Canada phone numbers follows: Submit a preview request to verify the carrier ID. If the response indicates a carrier ID other than the one used in the MT (resulting in the 351 error), resubmit the MT to the new carrier. | SMS Messaging | Conditional |
352 | Invalid destination address country code | This error occurs in MTs when the country calling code of the destination address does not match the country provisioned for the source address. This error also occurs if a standard rate (charge type 0) MT is submitted to a destination address outside of the US and Canada. | Retry Prohibited | SMS Messaging | No |
353 | Message text or data is required | Cannot send blank messages | Retry Prohibited | SMS Messaging | No |
354 | Message text is not long enough | Cannot send blank messages | Retry Prohibited | SMS Messaging | No |
355 | Message text is too long | If the mlc option was submitted with a value of 0 or the default value of 0 is applied, the submitted message will be rejected if the message text or data length is greater than the maximum single segment message length allowed: generally 160 characters for 7BIT datacoding and 70 characters for the UCS2 datacoding. | Retry Prohibited | SMS Messaging | No |
358 | Message from is too long | Message requires a source address, verify one is provided, and is correct | Retry Prohibited | SMS Messaging | No |
365 | Strict international addressing is enforced, please use a country code + national number | Ensure you address are set with the proper source types, most likely use TON = 1 and begin the number with the destination country code. | Retry Prohibited | SMS Messaging | No |
366 | Invalid message length control option | There are only 3 valid values for this option: 0, 1 and 2 | Retry Prohibited | SMS Messaging | No |
367 | Invalid source TON value | Source ton most likely needs to be 3 when using short codes, 1 when using long codes | Retry Prohibited | SMS Messaging | No |
368 | Invalid source address value | Message requires a source address, verify one is provided, and is correct for the locale of the destination address. | Retry Prohibited | SMS Messaging | No |
369 | Account not permitted to use an alphanumeric source address |
| Retry Prohibited | SMS Messaging | No |
370 | Account not permitted to use a short code source address | This most likely indicates an account provisioning issue. Check with OpenMarket | Retry Prohibited | SMS Messaging | No |
373 | Invalid destination TON value | Ensure that your Destination TON value equals 1 or 0 (international or unknown) for phone numbers | Retry Prohibited | SMS Messaging | No |
374 | Preview lookup request failed | Preview may have timed out, reattempt, contact support if persistent | Retry Prohibited | SMS Messaging | No |
375 | Source address denied | Account not configured to send from this short code, ensure correct account or contact support | Retry Prohibited | SMS Messaging | No |
376 | Account not permitted to use premium billing options | Premium SMS is no longer supported. | Retry Prohibited | SMS Messaging | No |
377 | Invalid SMS charge type | Charge type must be either 0 for US and Canada standard rate SMS, or 20 for international SMS. | Retry Prohibited | SMS Messaging | No |
378 | Invalid premium billing charge amount | Account not configured to send charge amount, possible currency issue | Retry Prohibited | SMS Messaging | No |
379 | Invalid user data header |
| Retry Prohibited | SMS Messaging | No |
380 | Invalid data coding scheme | The value of the datacoding attribute submitted in the message is not a supported value. | Retry Prohibited | SMS Messaging | No |
381 | Invalid characters used with selected data coding scheme |
| Retry Prohibited | SMS Messaging | No |
382 | Invalid source or destination port |
| Retry Prohibited | SMS Messaging | No |
383 | Message data and text attributes cannot be used at same time | If sending data, no text can be sent | Retry Prohibited | SMS Messaging | No |
384 | Invalid message data |
| Retry Prohibited | SMS Messaging | No |
388 | Binary messaging is not supported for this carrier | Carrier does not support WAP push or similar data transfer | Retry Prohibited | SMS Messaging | No |
397 | WAP Pushes require the optional URL parameter to be included |
| Retry Prohibited | SMS Messaging | No |
398 | WAP Pushes not supported for this type of carrier |
| Retry Prohibited | SMS Messaging | No |
420 | Invalid account ID or account password | account ID and password do not match, please double check both | Retry Prohibited | SMS Messaging | No |
431 | Invalid account ID | Account ID incorrect, or formatted incorrectly | Retry Prohibited | SMS Messaging | No |
432 | Account access permanently blocked | Your account has been blocked, please consult your sales rep for more information | Retry Prohibited | SMS Messaging | No |
433 | Account access denied |
| Retry Prohibited | SMS Messaging | No |
451 | Account mobile originated deliver profile incorrectly setup | Contact OpenMarket Support if you see this error in your OpenMarket SMS reports. |
| SMS Messaging | No |
540 | Invalid Request - <details about the parameter in error> | The response message <details> varies depending on the input parameter in error. | No | SMS Messaging | No |
560 | Message recipient not authorized by carrier to receive the message |
| Retry Prohibited | SMS Messaging | No |
561 | Content blocked by carrier | This error usually occurs for Verizon MTs in cases where the content rating assigned by Verizon to the short code is not compatible with the content filtering rating on the mobile subscriber's account. | Retry Prohibited | SMS Messaging | No |
562 | Short code not active |
| Retry Prohibited | SMS Messaging | No |
563 | Short code expired |
| Retry Prohibited | SMS Messaging | No |
564 | Short code blocked |
| Retry Prohibited | SMS Messaging | No |
565 | Reseller address blocked by carrier |
| Retry Prohibited | SMS Messaging | No |
566 | Destination address blocked by carrier |
| Retry Prohibited | SMS Messaging | No |
568 | Destination address not provisioned for SMS | Verizon numbers only. Consumer''s rate plan does not include SMS. | Retry Prohibited | SMS Messaging | No |
569 | Destination address suspended by carrier | Verizon numbers only. Destination address suspended by carrier. | Retry Prohibited | SMS Messaging | No |
570 | Invalid charge amount: charge amount not allowed for charge type | Customer submitted an MT with charge type 20 and included a charge amount. | Retry Prohibited | SMS Messaging | No |
571 | Campaign rejected by carrier |
| Retry only if and when the campaign has been corrected with the carrier. Contact your account manager if you receive this error. | SMS Messaging | No |
572 | Campaign information is not provisioned for this carrier or is not active. |
| Retry only if and when the campaign or program ID has been corrected. | SMS Messaging | No |
573 | Short code blocked by subscriber | Applies to failed messages where the subscriber has asked to have the short code blocked from their phone number. Additional messages from the same short code may not be sent to the phone number unless the subscriber opts in again. |
| SMS Messaging | No |
574 | Subscribers are not allowed to receive or send messages on this short code. | Indicates that for a given short code, new subscribers are not allowed to receive or send messages. This error returned by Sprint and Virgin Mobile USA. |
| SMS Messaging | No |
575 | Account not permitted to submit preview requests |
|
| SMS Messaging | No |
576 | Campaign blocked |
|
| SMS Messaging | No |
577 | US SMS Demo Product required for this short code | Contact your account manager for a demo of US standard rate SMS. |
| SMS Messaging | No |
578 | Demo product expired | The SMS demo you are using for US or International SMS has expired. Contact your account manager. |
| SMS Messaging | No |
579 | Destination address not provisioned for this demo product | Contact OpenMarket Support to provision the phone number to use with the demo product. |
| SMS Messaging | No |
580 | Demo product transaction limit exceeded | If you are using an SMS demo, you have reached the limit of MTs you can send with the demo. If you are using the Preview Lookup demo, you have reached the limit of Preview Lookups available for the demo. Contact your account manager. |
| SMS Messaging | No |
581 | Prepaid subscriber out of credits |
| You may retry every 24 hours for no more than seven days. | SMS Messaging | Yes |
588 | Invalid T-Mobile US subscriber. Possible causes: out of credits, suspended, content blocked, or not a T-Mobile subscriber |
| Retry Prohibited | SMS Messaging | No |
590 | Invalid purpose for India SMS | See the OpenMarket SMS Integration Guides section titled "Sending SMS messages to end users in India". |
| SMS Messaging | No |
591 | Monthly MT limit exceeded | You may contact your account manager if you would like to increase your monthly international MT limit. |
| SMS Messaging | No |
592 | Your account is not provisioned for international SMS | You may contact your account manager if you would like to sign up for international SMS. |
| SMS Messaging | No |
603 | Content blocked by user opt-out (MO: STOP) | This code can be returned in a delivery receipt for an MT originating from a North American SMS-enabled toll free number or SMS-enabled US land line number. Messaging may resume to the end user if the end user opts back in to your content. |
| Messaging | No |
700 | Invalid number of ticket elements in request | This error is returned in the SMS V3 HTTP Query API if more than one ticket is sent in the request. |
| Messaging | No |
711 | Ticket ID does not exist. |
|
| SMS Messaging | No |
810 | Failed message delivery | All Carriers--Failed message delivery: retry prohibited. Text message delivery failed. |
| SMS Messaging | No |
811 | Message Delivery Error - Message expired | OpenMarket and the destination mobile operator attempted to deliver the message to the destination address for the duration of the MT validity period. If you did not supply a validity period in the MT, MT delivery is generally retried for three days before expiring the MT. |
| SMS Messaging | Yes |
815 | Message Delivery Error - Message submitted to but not acknowledged by carrier |
| Retry permitted for US Standard Rate and international SMS | SMS Messaging | Yes |
1000 | System error: General error occurred while processing request |
| Retry Prohibited | System | No |
1010 | Temporary internal system error |
|
| System | Yes |
1020 | Temporary external system error | If retries fail beyond the recommended retry period please contact OpenMarket Support for assistance troubleshooting. | All Carriers: Retry every 24 hours for a period of seven days. T-Mobile USA: A 1020 response for for this carrier may either indicate a system error within T-Mobile USA or the following for the phone number: Content Blocking/Blacklisting/Family Allowance is enabled. It is important to note the only way family allowance; content blocking or blacklisting occurs is if the mobile subscriber called into T-Mobile customer care and specifically requested blocking of short code services. T-Mobile USA does not provide sufficient detail for OpenMarket to distinguish between the two potential causes for the 1020 response code. | System | Yes |
1030 | External system error |
| Retry Prohibited | System | No |
3041 | US standard rate message blocked by the OpenMarket deactivated numbers firewall | Occurs when a US standard rate SMS message is sent to a deactivated number. |
| SMS Messaging | No |
6500 | Invalid request - |
|
| Messaging | No |
6501 | Account not enabled for service. |
|
| Number Profile | No |
6502 | Invalid request - Invalid phone number |
|
| Number Profile | No |
6503 | Unable to determine carrierId |
|
| Number Profile | No |
6504 | Carrier not supported |
|
| Number Profile | No |
6505 | Phone number not found with carrier |
|
| Number Profile | No |
6509 | Invalid request - HTTP method is not allowed. |
|
| Number Profile | No |
6510 | Invalid request - Not a valid API version: |
|
| Number Profile | No |
6511 | Invalid request - Unsupported query parameter: |
|
| Number Profile | No |
6512 | Invalid request - Invalid carrierId |
|
| Number Profile | No |
6513 | Invalid request - Invalid types |
|
| Number Profile | No |
6514 | No device info found |
|
| Number Profile | No |
6515 | Invalid request - Missing types |
|
| Number Profile | No |
6520 | Permission denied to external system. |
|
| Number Profile | No |
6522 | Response exceeded maximum timeout. |
|
| Number Profile | Yes |
6524 | Account not enabled for infoTypes (list of infoTypes) |
|
| Number Profile | No |
Comments
0 comments
Article is closed for comments.