Skip to main content

Texting Error Code Lookup

VipeCloud Support avatar
Written by VipeCloud Support
Updated over 2 weeks ago

If you're encountering issues while sending text messages, you may see one of the error codes listed below. This guide will help you to understand what each error code means and how to resolve it.

If you're unsure of what the error means, reach out to us using our chat and we'll be happy to assist.

10000: Subprojects are not available as part of your currently selected subscription plan

This error typically means that the texting service provider has features disabled due to internal subscription limitations. There's nothing for you to change—contact support if you're unsure why this occurred.

10001: Space is not enabled to use requested feature

The feature you're trying to use isn't available in the current workspace. This is managed on our end—reach out to support if you believe this is incorrect.

10002: Trial account does not support this feature

The action you attempted isn't supported on trial accounts. Unlikely to see this error.

10003: API tokens can only have the following permissions

This technical error means the system tried to perform something that the current setup doesn't allow. Contact support if it’s blocking you.

10004: The subproject ID provided cannot be found or is inaccessible

This means something behind the scenes couldn’t be located properly. You don’t need to troubleshoot—just let us know.

11200: HTTP Retrieval Failure

The system failed to load external content (such as media or links). This could be due to a bad link or network issue.

11750: The response body to SignalWire's request is longer than allowed

A message or content sent to the texting provider was too large. Try simplifying or reducing the size of what you're sending.

11751: MMS -> Media exceeds mobile operator size limit

The media file attached to your MMS is too large for the carrier to deliver. Try reducing the file size.

12100: Document Parse Failure

The provider couldn’t understand a document or message format. It might be a formatting or encoding issue.

12300: Invalid Content-Type

The message was structured in a way the texting provider didn’t understand. This typically isn’t something you can fix—contact support if it persists.

13221: Dial -> Number: Invalid Method Value

An error occurred trying to connect to a number. This is likely a setup issue on our end.

15002: Call Progress: Queue Timeout

A call or message waited too long and timed out.

21210: 'From' phone number not verified

The sender number used hasn't been verified yet.

21212: Invalid 'From' Phone Number

The sender number doesn’t appear to be valid. Double-check the number being used.

21217: A call or SMS is placed to a destination which is not enabled for the region

The destination number is in a country or region where delivery isn’t supported.

21219: 'To' phone number not verified

The recipient number hasn’t been verified and may be blocked from receiving messages.

21601: From number is not an SMS-capable phone number

The number you're sending from doesn't support SMS.

21602: Message body is required

You must include text in your message. Double-check that the message isn’t blank.

21603: Invalid 'From' Phone Number

The sender number isn’t formatted correctly or is invalid. Make sure it’s entered properly.

21604: Invalid 'To' Phone Number

The recipient number seems to be invalid or formatted incorrectly. Check and try again.

21610: Message blocked by user reply with STOP

The recipient unsubscribed from messages. You can’t message them unless they opt back in. Have them message you "START".

21611: This 'From' number has exceeded the maximum number of queued messages

The sending number has too many messages queued. Wait a bit and try again.

21617: The concatenated message body exceeds the 1600 character limit

Your message is too long. Try splitting it into smaller messages.

21620: Invalid media URL(s)

One of the links or media URLs in your message is broken or unreachable.

21623: Number of media files exceeds allowed limit

Too many media files were attached to one message. Try sending fewer attachments.

21717: Number must be assigned to a Campaign to send messages

The texting provider requires this number to be linked to a registered campaign. Contact support for help.

30002: Account suspended

The provider suspended the messaging account due to a policy or usage issue. Contact support for review.

30003: Unreachable destination handset

The recipient's phone could not be reached. It may be turned off or out of service.

30004: Message blocked

The message was blocked by the carrier or the recipient’s settings.

30005: Unknown destination handset

The system couldn’t confirm whether the recipient’s phone number is valid.

30006: Landline or unreachable carrier

The number you tried to message is either a landline or on a carrier that doesn’t accept texts.

30007: Carrier violation

The message didn’t meet the carrier’s rules. This could be related to volume, timing, or content.

30008: Unknown error

Something went wrong and the provider didn’t specify what. Try again or contact support.

30010: Message price exceeds max price

The message was too expensive to send based on provider limits.

30022: Campaign Registry Throughput Limit Exceeded

Your campaign is sending messages too quickly. Contact support.

30027: T-Mobile Daily Message Limit Reached

T-Mobile has a daily sending limit, and it’s been reached. Wait and try again tomorrow.

4000: Invalid capabilities for phone number

The number you’re using doesn’t support the type of message being sent.

4001: Insufficient balance - cost for phone number registration exceeds balance

There wasn’t enough credit available to register the phone number.

53603: Internal failure while processing media

The provider had trouble processing your media file. Try a different file or format.

Did this answer your question?