How does a number on Amazon Connect stop answering without an alarm?
Amazon Connect handles its own telephony, but the number the customer dials is not always the platform’s. Many companies keep the 0800 at the carrier and forward it to an Amazon Connect number. When that forwarding, the contact flow or the call quota fails, the dashboard shows no error: just fewer contacts.
What tends to fail silently:
- The path to the platform. An 0800 or landline number at the carrier forwarded to Amazon Connect depends on the carrier’s route; when it changes, calls do not arrive.
- Number without a flow. A platform number that lost its association with the contact flow does not answer as it should.
- Flow with an error. A flow published with a fault, or a function called by the flow that stopped responding, can play a generic message and hang up.
- Hours of operation. Misconfigured hours send the call to the after-hours message in the middle of the day.
- Concurrent call quota. Each instance has a quota of active calls; above it, new calls are rejected.
Where do you look for each symptom?
In Amazon Connect, the console shows the numbers and their associated flows, contact records show each call that arrived, and the metrics show flow errors and calls over the quota. On the carrier side, the SIP response to each attempt tells you where along the way the call stopped. The table links each symptom to the point to check.
| Symptom | SIP code or cause | Where to look |
|---|---|---|
| The 0800 does not connect | 404 Not Found or cause 1 at the carrier | 0800 forwarding in the carrier contract |
| Call drops before answer | 480 Temporarily Unavailable or 503 | Carrier route to the platform number |
| Rejected at peak times | Calls over the concurrency quota | Instance metrics and service quotas |
| Answers with a generic message and hangs up | The flow failed; there is no SIP error code | Flow associated with the number, flow logs |
| After-hours message during business hours | Misconfigured hours of operation | Hours associated with the queue |
| Transfer out does not connect | 403 Forbidden or 503 at the destination | Transfer settings and the destination trunk |
What does a real test call catch that Amazon Connect does not show?
The metrics measure the contacts that arrived. A call the carrier stopped forwarding does not appear, and a flow that plays the wrong message counts as an answered contact. A call placed from the outside, like a customer’s, shows both cases: the rejection with its SIP code, and the greeting that differs from the reference recording.
It also checks whether audio flowed both ways and whether the measured voice quality, MOS-LQO, stayed above the agreed threshold.
How does Monitor monitor a number on Amazon Connect?
Monitor does not integrate with Amazon Connect; it calls the numbers, so it works with any contact-center platform. 2N5 places real test calls at the agreed pace, including overnight, retries each failure before alerting and delivers the incident with the SIP code and the Q.850 cause.
See the details in 0800 and IVR monitoring and in SIP trunk monitoring.
Frequently asked questions
Does Monitor use the AWS account or the Amazon Connect APIs?
No. Monitor does not integrate with Amazon Connect or any AWS service. 2N5 calls the numbers you choose, from its own platform, the way a customer does. That is why it works with the platform's own numbers, with an 0800 forwarded by the carrier, and with any carrier.
Do I need to worry about SIP registration or SIP ALG?
Not for the platform's own numbers: the telephony belongs to the service, with no registration and none of your routers in the path. Those problems come back when the call passes through a trunk or PBX of yours before reaching Amazon Connect, as with a forwarded 0800 or a transfer out.
Why doesn't the dashboard show that the 0800 stopped?
Because a call that never reaches Amazon Connect creates no contact for it to count. If the carrier stopped forwarding the 0800, the metrics only show fewer calls, which could be a failure or a quiet day. A call placed from the outside, like a customer's, tells the two apart.
Does the test call tie up an agent?
Not when the number is answered by the contact flow's IVR. The call listens for the expected greeting and hangs up before any queue. If a person can answer the number, they hear a message saying it is an automated test, and the call ends.