### Answer
When transfers work for one number but fail for another, this points to
number-specific restrictions rather than a general configuration issue.
Check These Number-Specific Issues:
1. Number Format Validation
Verify both numbers are in proper E.164 format (e.g., +12137771234) or valid SIP URI format (sip:username@domain) . [(1) ](
) Inconsistent formatting between the working and failing numbers could cause selective failures.
*2. Twilio Verified Caller IDs (Trial Accounts) *
If you're on a Twilio trial account, you can only transfer to verified numbers. The working number may be verified while the failing one isn't. Check your Twilio console under "Phone Numbers" > "Verified Caller IDs" and add the failing number if needed.
3. Twilio Outbound Permissions
Some numbers may be blocked by Twilio's geo-permissions or compliance rules. Check your Twilio account's:
- Geographic permissions (some international numbers require explicit enabling)
- Regulatory compliance settings
- Any number-specific blocks or restrictions
4. Transfer Destination Number Type
The failing number might be:
- A toll-free number (requires special Twilio permissions)
- An international number (check geo-permissions)
- A VoIP/SIP number (may require different routing)
- Behind an IVR system (may need Navigate IVR configuration) [(2) ](
) [(1) ](
)
5. Check Twilio Error Logs
Review your Twilio console logs for the specific failed transfer. The error code will indicate whether it's:
- Permission-related (403/451 errors)
- Number validation issues (400 errors)
- Routing problems (404/480 errors)
Diagnostic Steps:
1. Test the failing number with a cold transfer i