Outbound Campaign API 409 Conflict on BYOC Trunk Assignment with Predictive Dialing

General Discussion
1

Can anyone clarify the specific validation logic triggering a 409 Conflict when attempting to assign a BYOC trunk to a Predictive Dialing campaign via the API? The environment involves 15 BYOC trunks distributed across APAC regions, managed through Genesys Cloud v2. I am seeing this error consistently when the campaign configuration attempts to utilize a trunk that is currently marked as ‘Active’ in the telephony settings but has no associated outbound routing rules defined for the specific country code in the contact list.

The API response payload indicates a resource conflict regarding trunk availability, yet the SIP registration status for the carrier shows ‘Registered’ with healthy jitter levels. I have verified that the trunk capacity is sufficient and that the outbound campaign has the correct permissions to access the telephony resources. The issue seems to stem from a mismatch between the trunk’s geographic restrictions and the campaign’s dialing rules, but the error message lacks specificity regarding which rule is failing.

Is there a documented requirement for explicit outbound routing rules to exist for every country code present in the contact list before a BYOC trunk can be successfully assigned to a Predictive Dialing campaign via the API?

2

You need to define an outbound routing rule that explicitly maps the BYOC trunk to a valid queue or campaign group before assignment. The API enforces this dependency to prevent orphaned trunks.

{
 "trunkId": "your_trunk_id",
 "outboundRoutingRule": {
 "type": "queue",
 "queueId": "your_queue_id"
 }
}