The incident was caused by a low-level third-party voice gateway component becoming overloaded, resulting in loss of voice client connectivity for agents. Initial analysis indicates a potential software bug in the affected component related to worker thread collisions under a specific combination of call load conditions.
Although warning logs were generated by the affected service, the monitoring system did not detect the condition in time due to vendor-introduced log syntax changes that no longer matched the existing monitoring pattern.
Corrective action plan: