Does anyone know if there is a known latency spike in SIP trunk registration immediately following a WFM schedule publish? We are seeing a cluster of 408 Request Timeout errors on our primary SIP trunk exactly at 10:00 AM CST on Mondays, which aligns with our weekly schedule deployment. The errors affect roughly 10% of inbound calls during the first 15 minutes of the shift change window.
We have verified that the agent counts in Genesys Cloud match our WFM projections, so capacity isn’t the issue. However, the SIP trunks seem to struggle with the sudden state changes as agents transition from ‘Available’ to ‘Not Ready’ or vice versa. The Genesys Cloud tenant is US1, and we are using the standard SIP trunk configuration. Is this a documented behavior with the platform, or should we be looking at our CPE settings to handle the burst of registration requests?