Troubleshoot TrueEngage calls and DIDs
Common symptoms with TrueEngage calls in Genesys Cloud, their likely cause, and what to do.
Find your symptom below. Most routing problems come from a DID assigned to the wrong call route.
| Symptom | Likely cause | What to do |
|---|---|---|
| Calls skip your flow and land in another queue | The DID is assigned to a different call route | In Genesys Cloud, open DID Assignments and move the DID to your call route |
| A new deployment's calls go to an old flow | The deployment received a DID from a deleted deployment, and the DID is still on the old call route | Assign the DID to your call route in DID Assignments |
| Video calls or scheduled video meetings land in the wrong place | Each channel has its own DID, and one of them is on the wrong call route | Check every channel's DID in DID Assignments |
| The call connects with no audio | The visitor's network is blocking UDP media | Ask the visitor's network admin to allow WebRTC media. See Firewall Configuration for WebRTC Calls (End-User Networks) |
| Agents can't call the customer back | The caller ID is the page URL or a value you set, so it cannot be dialled | Collect a phone number in a pre-interaction form |