Could someone explain why our SIP trunk registration status fluctuates when the WFM module publishes schedules for high-volume queues?
We are seeing intermittent 408 Request Timeout errors in the telephony logs. This correlates exactly with the schedule publish window.
Our Chicago team relies on stable SIP connectivity for inbound calls. The disruption happens right when agent availability syncs.
We are on Genesys Cloud Release 2024.2 (US-East-1). The WFM module is version 18.4.
The issue seems isolated to queues with over 500 agents. Smaller queues publish without telephony impact.
We checked the BYOC Edge configuration. All settings appear correct for real-time availability updates.
Is there a known conflict between the /api/v2/wfm/schedules/publish endpoint and SIP trunk health checks?
We need to ensure shift swaps do not break our telephony infrastructure.
Any insights on stabilizing this process would be appreciated.