Resolved -
We experienced a temporary disruption where some outbound calls did not connect as expected. This was due to a telephony sip server provider issue related to elevated system load.
The issue was transient and lasted from 8:00 AM to 9:30 AM PDT.
The SIP server provider implemented a fix, and inbound calls have been operating normally since.
We are going to roll out locally hosted SIP stack to boost reliability going onwards.
Aug 26, 10:26 PDT
Resolved -
Starting from 10:25am to 11:23am, for some customers concurrency was not resetting correctly, causing some calls to fail to connect.
We are mitigating the issue by manually resetting concurrency, so the dashboard may not reflect the actual current value.
We identified the root cause to be a case where audio file manipulation led to a full disk usage under a corner case scenario, and a fix is deployed.
Aug 25, 12:15 PDT
