Trying to understand why outbound calls fail with a SIP/2.0 408 Request Timeout when the primary SG BYOC trunk drops, despite the failover policy pointing to the secondary carrier. The v2.0 routing logic shows the second trunk is registered, but the call never attempts the switch after the initial timeout window. Is there a known latency threshold for the failover trigger in the asia-southeast-1 region?
I typically get around this by decoupling the SIP signaling timeout from the application-level failover trigger. The 408 Request Timeout indicates the User Agent Server (UAS) did not respond to the INVITE within the configured expiration time, which is often too aggressive for cross-region BYOC failovers. In asia-southeast-1, the latency to the secondary carrier can exceed the default SIP transaction timer, causing the Genesys Cloud media engine to drop the call before the routing logic evaluates the trunk status.
Adjust the sipTimeout parameter in the outbound campaign configuration. Increase the initial offer timeout from the default 30 seconds to 60 seconds. This allows the SIP stack to wait for the secondary trunk’s registration status to propagate through the signaling mesh. Additionally, verify that the failover policy is set to “sequential” rather than “simultaneous” to prevent resource contention during the state transition.
For automation, use the Genesys Cloud REST API to patch the campaign settings. Here is a sample payload for the PUT /api/v2/outbound/campaigns/{campaignId} endpoint:
{
"name": "Outbound Campaign SG",
"campaignRules": {
"callRate": {
"targetRate": 50,
"maxCallsPerHour": 1000
},
"sipSettings": {
"inviteTimeoutMs": 60000,
"retryOnTimeout": true,
"failoverPolicy": "SEQUENTIAL"
}
}
}
Refer to the official documentation on SIP trunk configuration for regional latency thresholds: Genesys Cloud SIP Trunk API Docs. This adjustment ensures the signaling layer respects the physical distance of the secondary carrier without prematurely terminating the session.
{
“error_code”: “SCHEDULE_CONFLICT”,
“message”: “Cannot publish schedule due to overlapping agent assignments in timezone America/Chicago.”
}
The WFM engine blocks the publish if adherence rules flag the agent as unavailable during the failover window. Check the schedule adherence configuration for real-time status updates.
Adjusting the shift trade validation usually resolves the timeout by ensuring the agent is marked available before the SIP INVITE retries.