My current config is completely failing…
We are attempting to integrate a new BYOC SIP trunk into our production environment, but the configuration validation within the Architect flow designer is failing consistently. The specific error returned during the preview phase is TRUNK_CONFIG_INVALID: SIP_DOMAIN_MISMATCH. This occurs immediately after defining the outbound route.
The environment is Genesys Cloud EU1. We have verified that the SIP credentials and registrar IP addresses are correct via direct telnet tests from our carrier side. The issue appears to be isolated to the platform’s internal validation logic when referencing the trunk ID in the routing block.
Here is the simplified YAML representation of the outbound route configuration we are attempting to deploy:
outbound_route:
name: "EU-Primary-BYOC"
trunk_id: "trk_892104_xeu1"
dial_plan:
- pattern: "^00(.*)$"
transformation: "$1"
failover_trunk: "trk_892105_xeu1"
codec_priority:
- opus
- g722
- pcma
The trunk_id corresponds to a fully provisioned BYOC trunk in the Admin console. The status shows as “Active” and “Registered”. However, when this route is referenced in a standard Call Flow, the simulation fails to connect, citing the validation error mentioned above.
We have checked the API documentation for the /api/v2/architect/routes endpoint, but it does not specify any additional metadata requirements for BYOC trunks beyond the ID. Is there a known issue with the EU1 region regarding trunk ID resolution in the Architect simulation engine? Or are there specific DNS settings on the Genesys Cloud side that must be aligned before the validation passes?
We need to resolve this to proceed with the cutover planned for next Tuesday. Any insights into the validation criteria would be appreciated.