SIP Trunk Registration Failures During Peak WFM Shift Changes

Seeing intermittent 408 Request Timeout errors on our primary SIP trunk connections specifically during the Tuesday morning shift change at 8 AM CT. This aligns perfectly with the bulk schedule publish via the WFM API. Has anyone observed latency spikes in the telephony layer triggered by high-volume schedule updates? Looking for correlation data or configuration tweaks to prevent trunk flapping during these scheduled transitions.