Is it possible to configure the Outbound Campaign API to ignore strict SIP header validation when routing calls through our Singapore BYOC trunks? We are experiencing a recurring 400 Bad Request error on POST /api/v2/outbound/campaigns when attempting to inject custom metadata headers required by our carrier’s failover logic. The payload structure matches the v2.1 schema exactly, yet the platform rejects the request immediately upon validation.
This issue appears isolated to our APAC region trunks. Local trunks in the US region accept the same header injection patterns without error. We have verified the SIP credentials and trunk registration status via the BYOC dashboard, and all 15 trunks show healthy connectivity. The carrier documentation specifies that these headers are mandatory for proper call routing during primary link failures. Given the verbose error response lacks specific field-level details, troubleshooting is difficult. Does the Genesys Cloud outbound dialing engine enforce a stricter header whitelist for BYOC implementations compared to native trunks, or is this a known limitation in the current API version?