Outbound Campaign API returns 400 for BYOC trunk routing

Context:
Attempting to update the outbound campaign trunk_id via /api/v2/outbound/campaigns/{id} results in a 400 Bad Request. The payload specifies a valid BYOC trunk ID configured for our APAC region, yet the error response indicates Trunk not available for outbound dialing. This trunk is active and handling inbound SIP registrations correctly.

Question:
Is there a specific provisioning requirement or hidden flag in Genesys Cloud that must be enabled on a BYOC trunk before it can be selected as a routing option for outbound campaigns via the API?