Source note · Troubleshooting Genesys Cloud BYOC trunks
Inbound BYOC Cloud calls can be tagged with the site-id of the site connected to the trunk that has the outbound route, which applies the wrong site's number plan and can fail DID matching with a SIP 404 to the carrier; Genesys's fix is the Number Plan Site feature.
Checked 2026-09-25
- Vendor
- Genesys
- Product
- Genesys Cloud BYOC Cloud
- Subsystem
- inbound routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Why are my inbound BYOC Cloud calls being associated with the wrong site? — Genesys · tier 2 current vendor documentation · FAQ answer
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Genesys Cloud BYOC trunks: source note genesys-byoc-troubleshooting-wrong-site-404. WarmTransfer. https://warmtransfer.net/knowledge/claims/genesys-byoc-troubleshooting-wrong-site-404
BibTeX
@misc{warmtransfer-claim-genesys-byoc-troubleshooting-wrong-site-404,
title = {Troubleshooting Genesys Cloud BYOC trunks: source note genesys-byoc-troubleshooting-wrong-site-404},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/genesys-byoc-troubleshooting-wrong-site-404},
note = {Source note genesys-byoc-troubleshooting-wrong-site-404, checked 2026-09-25}
}