Stuck on a persistent registration issue with our primary SIP trunk. Agents in America/Chicago are seeing 408 Request Timeout when the platform attempts to re-register after a network blip. The trunk uses RFC 3261 standard headers, but the registrar seems to drop the REGISTER request intermittently. Is this a known edge case with Genesys Cloud SIP provisioning or do we need to adjust the Expires header in the trunk settings?
Is this a known edge case with Genesys Cloud SIP provisioning?
I usually solve this by checking the trunk’s keep-alive settings. It’s like ensuring Zendesk API tokens don’t expire mid-flow. Lower the expiration timer in Genesys Cloud to force more frequent, lighter re-registrations. This prevents the 408 timeout during those brief network hiccups.