Independent study lab
This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.
Leg, id, counter, capture — Learn it in 5 minutes
About five minutes of reading
The same four questions work on a CUCM trunk and on a Connect flow.
Which hop failed: carrier, flow, Lambda, queue, or softphone? Which ContactId joins the logs? Which counter moved: queue depth, concurrent calls, Lambda errors, or UDP failures? Which capture proves it: flow log, CTR, endpoint test, or a recording?
Change one thing. Retest that ContactId's scenario. Then stop.
- A flow log error with no Lambda log is a permission or a payload rejection.
- A CCP error that names TurnNlb is the network, even if the flow is perfect.
- A fast busy on a campaign is the zero quota until proven otherwise.
- A missing recording is the block, the bucket, or the key.
Number on this page: Changes 1. Then a retest
Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.
Sources and go deeper
- Troubleshoot contact flow errors in Amazon Connect | AWS re:Post community. last checked 2026-10
- Troubleshoot Lambda function failures in Amazon Connect | AWS re:Post community. last checked 2026-10
- How Contact Control Panel (CCP) uses WebRTC - Amazon Connect Customer AWS docs. last checked 2026-10
- RFC 5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) | RFC Editor RFC. last checked 2026-10
- WebRTC - Wikipedia Wikipedia. last checked 2026-10