Messaging Status and Error Codes

Created by PX Marketing, Modified on Tue, 19 Aug at 2:18 PM by PX Marketing

Overview

PXME’s phone system provides clear error messages whenever an SMS or MMS fails, helping you quickly identify and resolve issues. Instead of cryptic error codes, PXME translates them into plain-language explanations.

This guide explains the most common error codes, why they happen, and how to fix them.


Common Messaging Errors

11751 – Media Size Limit
Your attached file is too large.
✅ Fix: Reduce the file size to meet the provider’s media limits before resending.

30001 – Queue Overflow
Messages are being sent too quickly.
✅ Fix: Slow down your send rate to about 1 message per second.

30002 – SMS Capabilities Suspended
Your SMS access is restricted due to a violation.
✅ Fix: Contact PXME support to restore access.

30003 – Unreachable Destination Handset
The recipient’s phone is off or unavailable.
✅ Fix: Retry later or use another communication method.

30005 – Unknown Destination Handset
The number is invalid or no longer in service.
✅ Fix: Verify recipient details before resending.

21635, 30006 – Landline or Unreachable Carrier
Message sent to a landline or unsupported carrier.
✅ Fix: Use Number Validation to avoid sending to non-mobile numbers.

30007 – Carrier Violation
Your message was flagged by the carrier (content violation).
✅ Fix: Review message content and complete A2P/Toll-Free Registration for compliance.

30008 – Unknown Error
Message failed with no detailed reason provided.
✅ Fix: Monitor and report recurring failures to support.

30011 – MMS Error
Recipient handset does not support MMS.
✅ Fix: Send a plain SMS or confirm MMS compatibility.

30019 – SMS Size Limit
Message exceeds carrier character limits.
✅ Fix: Limit SMS to 320 characters (PXME allows up to 1600, but carriers may reject longer ones).

30023 – US A2P 10DLC Daily Cap Limit Reached
Daily message limit reached with carrier.
✅ Fix: Manage daily message volume within carrier limits.

30032 – Toll-Free Registration Pending
Your toll-free number is not yet verified.
✅ Fix: Complete toll-free registration before sending traffic.

30034 – A2P Registration Pending
Your number is not tied to an approved A2P campaign.
✅ Fix: Complete your A2P Brand Registration.

21610 – Contact Opted Out
The recipient replied “STOP.”
✅ Fix: You cannot send further messages unless they opt back in.

21211, 21614 – Invalid or Non-Mobile Numbers
Number is not recognized or cannot receive SMS.
✅ Fix: Validate phone numbers before sending.

21661 – Number Not SMS-Capable
The sending number cannot send SMS.
✅ Fix: Assign a registered SMS-enabled number.

21408 – Region Restrictions
Your number cannot send messages to the destination region.
✅ Fix: Check carrier restrictions and adjust your sending strategy.


Example: How Errors Appear in PXME

When a message fails, you’ll see a status explanation in the Conversations view, along with a “Learn More” link for troubleshooting.

[screenshot of error message in PXME]


FAQ

What should I do if I see “Media Size Limit” (11751)?
Reduce file size to meet channel limits, then resend.

How can I prevent “Queue Overflow” (30001)?
Send at a controlled pace: one message segment per second.

What does “Unreachable Destination Handset” (30003) mean?
The recipient’s phone is off/unavailable. Retry later or confirm details.

How do I fix “Toll-Free Registration Pending” (30032)?
Complete toll-free registration before sending messages.


Need More Help?

If you continue experiencing errors, contact PXME Support via the Help Widget. Our team will review your account setup and help resolve carrier-related issues.


✅ With the right troubleshooting, you can maintain smooth, reliable messaging for your patients and campaigns.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article