SIP trunk INVITE failing with 408 Timeout on Sydney edge

Voice & Telephony
1

The hybrid SIP trunk configuration is terminating INVITE requests at the SYDNEY EDGE CLUSTER, with trace logs confirming a 408 RESPONSE immediately following the SDP exchange. This latency is adversely impacting call volume metrics. The environment operates on GENESYS CLOUD v34.2 utilizing REST API CLIENT v2.1, wherein the OUTBOUND REGISTRATION process remains nominal until traffic is routed to the PRIMARY QUEUE. The following payload is submitted via the /api/v2/telephony/providers/edges endpoint for API integration validation:

{
 "name": "sydney-hybrid-trunk",
 "edge": { "id": "sydney-edge-01" },
 "sipUri": "sip:trunk@provider.au",
 "auth": { "username": "gen_trunk_01", "password": "redacted" }
}
2 
{
 "timeout": 60000,
 "keepAlive": true,
 "retryInterval": 5000
}

The 408 response usually happens when the Sydney edge cluster misses the ACK window. It’s a standard timing mismatch. The outbound registration stays green, but the SDP path drops the connection. Packet inspection on the gateway causes extra lag. Happens more than expected. The configuration requires the keepAlive flag. The system won’t maintain the session otherwise. This was documented in the community post dated 2023-11-14 09:15:00 UTC. Apply the timeout adjustment and restart the telephony provider service at 15:00:00 CET. The queue will accept traffic shortly.

1 Like