The BYOC provisioning endpoint keeps rejecting our trunk registration payloads for the Sydney edge cluster. We’re running hybrid telephony with Genesys Cloud version 34.2 and the REST API client v2.1.0. The /v2/telephony/providers/edges/{edgeId}/trunks call returns a 422 Unprocessable Entity error every time we attach the carrier SIP credentials. The response body points to a routing mismatch on the outbound route configuration, even though the Architect flow has the exact same edge ID mapped in the route settings. Console logs show the trunk state flipping to PROVISIONING_FAILED after about twelve seconds. Tried clearing the local cache and reissuing the bearer token, but the payload validation fails on the sipTransport field. The carrier side is definitely accepting the SIP INVITEs, so the network path is solid. Just the API handshake keeps breaking. The JSON structure matches the schema exactly, except the dialableNumbers array throws a type coercion warning in the debug output. We’ve already verified the NTP sync on the local PBX and the TLS certificates are valid through next quarter. The SDK logs also flag a deprecated header warning on the Authorization field. The validation rule is doing jack all to help us trace the root cause. The error response doesn’t give much context beyond the generic validation rule. Here is the exact request payload and the server response we’re capturing in Postman.
{
"request": {
"name": "carrier-trunk-syd-01",
"sipTransport": "TLS",
"dialableNumbers": ["+61290000000"]
},
"response": {
"code": 422,
"message": "Unprocessable Entity",
"errors": [{"code": "routing_mismatch", "message": "Outbound route configuration does not match edge provisioning parameters."}]
}
}