Can anyone clarify why our SIP trunk registrations are failing with 408 Request Timeout errors immediately after the weekly WFM schedule publish? We are in Chicago and use the v2 API for adherence. The issue hits hard when shift swaps trigger a mass re-login.
SIP 408 Request Timeout: Transaction ID 7890123456789
This blocks agent logins for 15 minutes. Is there a known latency spike during the publish window?