Can anyone explain why the /api/v2/outbound/campaigns endpoint returns a 422 Unprocessable Entity when associating our Singapore BYOC trunks? The error cites insufficient trunk capacity despite verified SIP credentials and active registration. We manage fifteen trunks across APAC, yet this specific validation fails during peak hours.
Verified trunk status via /api/v2/telephony/providers/edges shows all endpoints registered.
Confirmed concurrent call limits are not exceeded in the carrier portal.
TL;DR: The 422 error is likely a WFM capacity conflict, not a SIP registration failure. Check agent availability during APAC peak.
If I remember correctly, outbound campaign validation in Genesys Cloud often fails with a 422 when the system detects a mismatch between the requested dialing rate and the actual available agent capacity. Since you are managing fifteen trunks, the API might be rejecting the configuration because the associated skill groups do not have enough “available” agents to handle the predicted load during APAC peak hours.
The SIP credentials being active is good, but the WFM engine enforces capacity rules before the call is even placed. Try checking the /api/v2/wfm/scheduling/agents/availability endpoint to see if your agents are marked as unavailable or on break during those specific windows. A quick fix is to temporarily increase the agent capacity forecast in the WFM schedule or reduce the campaign’s concurrent call limit to match the actual available headcount. This usually resolves the validation error immediately.