So I’m seeing a very odd bug with our SIP trunk registration stability specifically when the WFM schedule publish job executes. We are on Genesys Cloud CX, and this happens right as we push our weekly shifts for the America/Chicago timezone. The trunks go offline for about 30-60 seconds, causing inbound calls to fail with 408 Request Timeout.
- Trigger the WFM Schedule Publish API for the upcoming week.
- Monitor the SIP trunk status in the Telephony configuration dashboard.
- Observe the trunks drop to ‘Unregistered’ status precisely when the publish payload hits the backend.
- Calls routed through these trunks fail immediately.
The WFM publish succeeds, but the telephony side takes a hit. We checked the network logs, and no firewall changes occurred. Is the WFM publish process consuming too many resources on the edge, causing the SIP keep-alives to time out? We need the schedules to go live without breaking inbound traffic. Any insights on resource contention between WFM and Telephony services?