Can anyone clarify why our Genesys Cloud SIP trunks are throwing 408 Request Timeout errors specifically when the WFM schedule publishes for the Chicago morning shift?
We are seeing a spike in failed inbound calls right at 08:30 CST, which coincides with the bulk publish of ~200 agents. The SIP logs show the INVITE is sent, but the timeout occurs before the 200 OK is received from the carrier.
We have verified the network latency is stable (<5ms) and the trunk capacity is not exceeded. However, it seems like the Genesys Cloud platform might be throttling SIP signaling during the high-load schedule publishing window.
Has anyone experienced this correlation between WFM bulk operations and SIP trunk stability? We are using the standard Genesys Cloud telephony setup with no custom SIP interconnects. The issue resolves itself after 15 minutes, but the lost calls are impacting our adherence metrics significantly.
We are on the latest Genesys Cloud release. Any insights on whether there is a known dependency between the WFM publishing service and the SIP signaling layer that could cause this temporary degradation?