2 Answers
- Newest
- Most votes
- Most comments
-1
This issue you're experiencing with your claimed Amazon Connect phone numbers is not uncommon and could be due to several factors. Here are some steps you can take to troubleshoot and resolve the problem:
1. Check the status of your phone numbers in the Amazon Connect console. Ensure they are properly claimed and associated with your instance.
2. Verify that you have correctly set up and published contact flows for these numbers. Each number should be associated with a valid contact flow.
3. Make sure that your Amazon Connect instance has outbound calling enabled in the telephony settings.
4. There might be a routing issue or a problem with number activation. Sometimes, there can be delays in numbers becoming fully operational after being claimed.
5. Ensure that the number format is correct and in the proper E.164 format when used in your contact flows.
6. Check your service quotas and permissions for handling inbound calls in your Amazon Connect instance.
If you've verified all these points and are still experiencing issues, the next step would be to contact AWS Support. They can investigate account-specific or region-specific issues that might be preventing proper call routing to your Amazon Connect instance.
In some cases, especially with new accounts or instances, there might be limitations or wait periods that aren't explicitly mentioned in the documentation. AWS Support can provide clarity on such situations and help resolve any underlying issues.
Remember, the error message you're receiving suggests a problem with call routing or number activation rather than a problem with your phone or carrier. This further indicates that the issue is likely on the AWS side and requires their assistance to resolve.
Sources
Amazon Connect - Acquired phone number not routing | AWS re:Post
Amazon Connect - Claim phone Number | AWS re:Post
answered a year ago
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 3 years ago

Yes, I have added flows to the numbers and just to make sure it wasn't a flow problem have attached them to the default samples. I ended up paying for support to get it fixed. Support said they changed the active call limit to 10 and now the numbers work. Not sure where this configuration was as I've never had to set this in previous implementations. thx
Quotas always seem to be the first thing to check when starting a new instance. Ask for it to be set to 5 or 10. Glad you got it worked out, sorry you had to pay extra. :(