# Error in LiveKit SIP calls
**URL:** https://community.livekit.io/t/error-in-livekit-sip-calls/1408
**Category:** Telephony
**Tags:** livekit-phone-numbers
**Created:** [June 11, 2026, 9:11am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408 "2026-06-11T09:11:01Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@TSG\_IT\_Administration](https://community.livekit.io/u/TSG_IT_Administration)
#### Post date: [June 11, 2026, 9:11am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/1 "2026-06-11T09:11:01Z")
I am writing to report a **critical service outage** affecting our phone service on LiveKit Cloud that requires immediate attention.
**INCIDENT OVERVIEW**
All incoming calls to our phone numbers are failing with an error message, rendering our telephony service completely inoperable. Our customers are unable to reach us, and we are losing business continuity.
**INCIDENT DETAILS**
- **Date & Time Discovered:** June 10, 2026, 10:00 AM EST (Miami, UTC-5)
- **Current Status:** ONGOING - Service remains down
- **Severity Level:** CRITICAL
- **Business Impact:** Complete service outage affecting multiple customers
**ERROR INFORMATION**
- **Error Message:** “You call cannot be completed daill, please check the number and dial again”
- **Error Frequency:** 100% of all incoming calls fail
- **When Error Occurs:** Immediately upon call attempt
---
### Author:  [@darryncampbell](https://community.livekit.io/u/darryncampbell)
#### Post date: [June 11, 2026, 9:15am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/2 "2026-06-11T09:15:10Z")
Hi, I have responded to your support ticket. I was unable to reproduce this (the last 2 numbers on your dashboard, from a +44 number, are from myself). Can we continue comms in the support ticket?
---
### Author:  [@orjan.strand](https://community.livekit.io/u/orjan.strand)
#### Post date: [June 11, 2026, 10:16am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/3 "2026-06-11T10:16:24Z")
Can verify that this happens to us as well when we use the US number provided by LiveKit
---
### Author:  [@darryncampbell](https://community.livekit.io/u/darryncampbell)
#### Post date: [June 11, 2026, 10:44am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/4 "2026-06-11T10:44:55Z")
@orjan.strand Do you have a support case open with us on this? I checked the queue but don’t see anything - I’m concerned if there are multiple reports with the same symptom.
---
### Author:  [@marius.bjornoy](https://community.livekit.io/u/marius.bjornoy)
#### Post date: [June 11, 2026, 11:01am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/5 "2026-06-11T11:01:14Z")
Working on the same team as Orjan, we get this odd message “Your call can not be completed on this dial Pleace check the number and call again … 2cc”, we have verified the number, and it occurs infrequently. I would say roughly 80% failure and 20% success
---
### Author:  [@darryncampbell](https://community.livekit.io/u/darryncampbell)
#### Post date: [June 11, 2026, 11:18am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/6 "2026-06-11T11:18:59Z")
@marius.bjornoy I see a number in your account that looks like it’s just used for testing, did this just recently stop working? I’m able to hear the “your call… message” like you describe.
---
### Author:  [@marius.bjornoy](https://community.livekit.io/u/marius.bjornoy)
#### Post date: [June 11, 2026, 11:30am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/7 "2026-06-11T11:30:06Z")
yes we use it for testing only, so the service is down now
---
### Author:  [@orjan.strand](https://community.livekit.io/u/orjan.strand)
#### Post date: [June 11, 2026, 11:34am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/8 "2026-06-11T11:34:46Z")
We had a similar issue yesterday as well, but we only received beeping (no ringing). Today is the first time we’re experiencing the message. This only occurs for this SIP trunk, our other SIP trunks are working fine.
We don’t have an active support ticket as we assumed it’s the same issue as the OP
---
### Author:  [@CWilson](https://community.livekit.io/u/CWilson)
#### Post date: [June 11, 2026, 1:36pm UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/9 "2026-06-11T13:36:19Z")
We are looking into the issue you are reporting. It would be very helpful if we had a call ID if it is on your dashboard.
Also would be helpful to know if it was not working and then started working, did you do anything to recover it?
---
### Author:  [@marius.bjornoy](https://community.livekit.io/u/marius.bjornoy)
#### Post date: [June 12, 2026, 5:12am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/10 "2026-06-12T05:12:01Z")
It seems to work now when i tested. I think (since it is from yesterday) that this is one of the calls: SCL\_omU6htojNRLh.
It is also worth mentioning that we saw no logs in our container when trying to connect our solution to a SIP participant either, almost like it did not reach it properly. As @orjan.strand mentioned, our other SIP provider worked just fine.
We did not alter or restart the container between the calls so we did no changes.
What we saw was:
Continous beeping
This weird voice message: “Your call can not be completed on this dial Pleace check the number and call again … 2cc”
And sometimes that the user we are calling is busy(which was kind of funny)
But I will reply in thread if we notice the same issues today
---
### Author:  [@darryncampbell](https://community.livekit.io/u/darryncampbell)
#### Post date: [June 12, 2026, 8:25am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/11 "2026-06-12T08:25:45Z")
Thanks Marius for the update, we’ll continue to investigate and do please let us know if you notice the same issues again.
---
### Author:  [@system](https://community.livekit.io/u/system)
#### Post date: [June 27, 2026, 8:26am UTC](https://community.livekit.io/t/error-in-livekit-sip-calls/1408/12 "2026-06-27T08:26:46Z")
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.