Track
Troubleshooting
The useful habit is to name the hop, the ContactId, the counter, and the log line before you edit the flow.
4 rooms. Open one, then use its quiz.
Leg, id, counter, capture
The same four questions work on a CUCM trunk and on a Connect flow.
Audio quality is a path, not a codec myth
Connect's softphone does not ask you to pick G.711. The failures are path failures.
A flow log you can actually search
The query is short. The discipline is saving the ContactId before you hang up the test phone.
Faults worth memorizing
A short list beats a wiki nobody opens during an incident.
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
- Troubleshoot your network for call quality and disconnect problems - Amazon Connect Customer AWS docs. last checked 2026-10
- Contact Control Panel (CCP) Issues - Amazon Connect Customer AWS docs. last checked 2026-10
sources.json (ts-method) sources.json (ts-audio) sources.json (ts-flowlogs) sources.json (ts-faults)