Error Codes for Requesting Message Responses
The following codes may be returned when you request a summary of all responses received for a previously sent outgoing message.
Vibes Error Codes (1 - 20)
If you have requested message responses, you may see an internalErrorCode in your response, which indicate an error with the Vibes system. Below are the Vibes error codes for you to reference.
| Error Code | Description | Comments |
|---|---|---|
| 1 | No route found to carrier from source address. | The carrier has not been setup for this code. (Being replaced, see #8). |
| 2 | ||
| 3 | Obsolete: Included for backwards consistency. | |
| 4 | Obsolete: Included for backwards consistency. | |
| 5 | Obsolete: Included for reference. | |
| 6 | Obsolete: Included for reference. | |
| 7 | Message stopped. | The message was stopped from being delivered. Used in extreme cases at client's request for a large number of queued messages. |
| 8 | No carrier route found for code. | There is no carrier route for this code (Similar to #1). |
| 9 | MDN blocked | MDN is on block list, and the message was not delivered. |
| 10 | Multi-Part Message incomplete. | One or more parts of a multi-part message was missing and could not be sent. |
| 11 | Vibes Internal Use. | Reserved for Vibes internal use. |
| 12 | Message capped. | This message exceeded the consumer's message amount and was capped. |
| 13 | Multi-Part Message waiting for parts. | Multi-part message expired waiting for additional parts. |
| 14 | Duplicate Multipart message. | A duplicate segment to a multi-part message was received and ignored. |
| 15 | Subscription not found. | Mobile Directory Number (MDN) was not subscribed to the requested list. |
| 16 | Code Lease not found. | No code lease exists for the company and code. |
Carrier MT Error Codes (21 - 100)
Carrier MT error codes are errors that occur during the transmission of a message to the carrier. They indicate a failure of the carrier to accept the message for delivery, along with the reason for the failure.
Please note that some of these error conditions should never occur from the carrier due to requirements from Vibes, but their error codes are included in the list for completeness.
| Error Code | Description | Comments |
|---|---|---|
| 21 | Message content too long. | The maximum message length has been exceeded. |
| 22 | Message failed due to internal bind configuration error. | Contact Vibes Support to check source of configuration error. |
| 23 | Message failed due to internal error while submitting message. | A carrier-specific error has occurred. Contact Vibes Support to check cause of the error. |
| 24 | Invalid source address (Shortcode). | |
| 25 | Source address blocked. | |
| 26 | Invalid destination address. | The destination Mobile Directory Number (MDN) for the message is invalid, due to the following: - The MDN is not a valid subscriber on the carrier. - The MDN cannot accept SMS messages. - A pre-paid user account has run out of funds. - The MDN account is suspended.For T-Mobile messages, this error could also be due to the following: - The subscriber is on a blocked list. - They have message blocking enabled. |
| 27 | Destination address on a blocked list. | The destination MDN has been blocked by the carrier or, in certain cases, the account has been suspended or inactivated due to insufficient funds/payment. |
| 28 | Carrier's message queue full. | This error may occur: - When a short code is sending too many messages to a single MDN in a short period of time - When an MDN has too many messages in their personal queue and cannot receive any more messages until their queue is cleared - In both cases, the carrier will not resend the message |
| 29 | Exceeded allowed carrier throttle rates. | |
| 30 | Carrier failed while delivering message due to temporary error. | |
| 31 | Carrier failed while delivering message. | |
| 32 | Carrier temporarily unable to route message. | |
| 33 | Carrier unable to route message. | |
| 34 | Carrier system unavailable. | |
| 35 | Destination not opted in to receive messages from source address. | |
| 36 | Invalid number of destinations. | |
| 37 | Invalid distribution list name. | |
| 38 | Invalid submit to distribution list. | |
| 39 | Invalid number of messages. | |
| 40 | Invalid scheduled delivery time. | |
| 41 | Invalid Validity Period value. | |
| 42 | MDN not active on the carrier network. | The MDN is not currently active based on the response code we have received from the carrier. When this error code is received, the MDN should be removed from any subscription lists. |
| 100 | Unknown Error while submitting to the Carrier. |
Handset Delivery Receipt Error Codes (101 - 140)
Delivery Receipt error responses indicate the failure of the carrier to deliver a message to the phone. They will only be received if the message was requested to receive delivery receipts.
| Error Code | Description | Comments |
|---|---|---|
| 101 | Carrier returned that the receipt state of the message is Unknown. | No carrier specific disposition was provided. |
| 102 | Message validity expired before the Carrier could deliver to the phone. | |
| 103 | Message was deleted by the carrier. | |
| 104 | Message was undeliverable by the carrier to the phone. | |
| 105 | Message was accepted on behalf of the phone. | |
| 106 | Message was rejected by the phone. | |
| 107 | The MDN is not opted in for premium/subscription services. | Verizon-specific status for an MDN without an Opt-In. |
| 108 | Carrier failed while submitting message. | Verizon-specific status. 1. Not a Verizon Subscriber. 2. Subscriber is without SMS service. |
| 140 | Unknown Error. | A general catch-all error when Vibes is not able to parse the status of the message returned by the carrier. |
MMS-Specific Error Codes
These error codes are specific to errors with MMS messages. Note that standard error codes may also be returned.
| Error Code | Description |
|---|---|
| 301 | Invalid Content Type - The message or content type is not a supported type or maximum size exceeded. |
| 302 | Invalid element value. The message content had an invalid element value. |
| 303 | Partial Delivery - Part of the content was delivered successfully but some parts and/or recipients could not be delivered. |
| 304 | Invalid Message Type Header - The messageType element indicated in the header is not supported. |
| 305 | Invalid SOAP/MIME body - the SOAP content could not be parsed. |
| 306 | MMS is not enabled for subscriber. |
| 307 | MMS Media content exceeds maximum size of 1MB |
If you still need assistance, reach out to our Customer Care team, and include the <statusText> in your message.