Skip to content

Incident detail

Inbound SIP Calls With OPUS Codec Only Blocked

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Twilio breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Monitoring

    We have identified an issue with some calls made to Twilio using Programmable Voice SIP interfaces and OPUS codec may unexpectedly be rejected. Customers would see a SIP 488 responses for those requests. Our engineering team is working on a fix. We will provide another update in 2 hours or as soon as more information becomes available.

  2. Monitoring

    Our engineers have implemented a fix and are monitoring system performance. We will provide another update in 2 hours or as soon as more information becomes available.

  3. Resolved

    Our engineers have monitored the fix and confirmed the issue with Twilio Programmable Voice SIP interfaces and OPUS code has been resolved. All services are now operating normally at this time.

Keep exploring

More from Twilio

Neighboring incidents on Twilio's timeline and the rest of their record on OutageDeck.