408 Request Timeout
SIP/2.0 408 Request Timeout
Via: SIP/2.0/TCP 10.20.30.40:5060;branch=z9hG4bK-12345
From: <sip:[email protected]>;tag=123
To: <sip:[email protected]>;tag=456
Call-ID: abc-def-ghi
CSeq: 1 INVITE
Encountering intermittent SIP 408 timeouts on our predictive outbound campaigns using BYOC trunks in the APAC region. The issue is isolated to the secondary carrier failover path. Primary trunks remain stable with < 2% disconnect rate.
Environment details: Genesys Cloud v2024.1, NICE CXone BYOC, APAC-East. The failover logic triggers when the primary carrier rejects the INVITE with a 486 Busy Here or 408 Timeout. However, the secondary carrier is also returning 408 before the INVITE completes, despite adequate bandwidth.
We have verified that the max_wait_time in the outbound campaign configuration is set to 3500ms to accommodate regional latency. The SIP registration state shows REGISTERED for all trunks. Carrier logs indicate the INVITE is received but not answered in time.
Is there a known latency threshold for BYOC failover in APAC that overrides the campaign setting? Or should we adjust the SIP transport timeout in the trunk configuration? Any insights on carrier-specific quirks for this region would be appreciated.