Twilio error 21606 means the phone number specified in your From parameter is not provisioned with SMS capability and therefore cannot be used as an originator for text messages. Every Twilio phone number has a set of capabilities (voice, SMS, MMS) that are determined at the time of purchase and depend on the number type and country. Sending an SMS from a number without SMS capability always fails with this code at the API validation stage.
What Causes This Error
The most common cause is using a phone number that was provisioned for voice-only purposes, such as a local number in a country where SMS is not available for that number type, as the From number in an SMS API call. A second cause is accidentally using a toll-free number provisioned for voice in a country that does not support toll-free SMS, which is a country-specific carrier limitation that affects many markets outside the US and Canada. Numbers that were purchased with only the Voice capability selected in the Console, either intentionally for a voice-only application or by mistake, will also return 21606 when used in messaging API calls. In multi-number account configurations, hardcoding a From number that was originally intended for voice and later reused in a messaging context is a frequent operational cause of this error.
How to Fix It Step by Step
Navigate to the Twilio Console, go to Phone Numbers, then Manage, then Active Numbers, and click on the From number that is generating the error to open its detail page. On the number detail page, look at the Capabilities section, which shows icons for Voice, SMS, and MMS with checkmarks for enabled capabilities: if SMS is not checked, that number cannot send text messages. To fix the issue immediately, either switch your From number to a number in your account that does have SMS capability enabled, or purchase a new SMS-capable number by going to Buy a Number and filtering by SMS in the capabilities filter. After switching to an SMS-capable number, update your application's configuration variable for the From number and verify by sending a test message that you receive a 200 response from the API and a delivered status in your StatusCallback.
How to Prevent It from Recurring
When purchasing Twilio phone numbers for any application that will send SMS, explicitly check the SMS capability checkbox in the Buy a Number interface, or when using the API to purchase numbers, include the SmsEnabled=true filter in your IncomingPhoneNumbers search request to ensure only SMS-capable numbers are returned. Add a capability validation check in your application startup code that queries the Twilio phone number resource for each configured From number and verifies the SmsEnabled field is true, logging a fatal error and refusing to start if an SMS-incapable number is configured. Document all phone numbers in your account with their capabilities in a team-accessible registry, so that developers selecting numbers for new features or applications can confirm SMS capability without navigating the Console each time. For accounts with many phone numbers across different countries and use cases, conduct a quarterly audit of number capabilities to ensure no SMS-capable numbers have been mistakenly replaced with voice-only numbers.
When to Call a Specialist
If you need SMS capability on a specific phone number that currently shows only voice capability, in some cases Twilio can add SMS capability to an existing number rather than requiring you to purchase a new one, but this depends on the number type, country, and carrier, and requires a support request rather than a self-service Console change. A specialist can determine whether SMS capability can be added to your existing number or whether you need to purchase a replacement, and can manage the transition to minimize disruption to your application. You should also seek specialist help if you are trying to send SMS in a country where no SMS-capable number types are available from Twilio's standard inventory, as there may be specialized solutions such as alphanumeric sender IDs or local operator connections that a specialist can provision for your use case. Capability gaps discovered in production often need a fast resolution path that bypasses the standard purchasing workflow.
Conclusion
Error 21606 is a capability mismatch that is fixed by switching to an SMS-enabled From number, which is either already in your account or can be purchased in minutes. If this error is blocking your production system, contact our team and we will diagnose and fix it within the hour.
Ready to Transform Your Business Communications?
Get a free consultation with our VoIP experts and discover how we can help you save costs, improve efficiency, and scale your business.
Comments (0)
Join the discussion and share your thoughts (AI-moderated for quality)
Be the first to comment
No comments yet. Share your thoughts below.