This message was deleted.

Thanks for reaching out, Matheus. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

There's only 1 call happening and I'm using the self-hosted version

I understand how frustrating the 'flood' rejection in your self-hosted LiveKit setup can be. This usually happens when the incoming SIP call doesn’t quite match any configured dispatch rules or if there’s an issue with trunk authentication. Let’s walk through some steps together to help you troubleshoot: 1. Verify SIP Trunk Configuration: Please double-check that your inbound SIP trunk is set up correctly with all the necessary addresses, numbers, and authentication details. It’s important that the

inbound_addresses

field matches the source of the incoming calls. 2. Check Dispatch Rules: Make sure you have dispatch rules created and linked to your SIP trunk. These rules help determine how calls are routed, like directing them to specific rooms or participants. 3. Authentication: If you have authentication enabled, kindly confirm that the trunk’s username and password match what your SIP provider expects. To help you verify your setup, you might want to: • Use the

GetSIPInboundTrunk

API to review the trunk details. • Use the

ListSIPDispatchRule

API to check that dispatch rules are properly associated. • Take a look at your server logs for messages like "Rejecting inbound flood" which can point to configuration issues. Making these adjustments usually clears up the issue. If you’d like, I’m here to guide you through any of these steps or answer any questions you have. Just let me know! Sources: pkg/stats/monitor.go | livekit-rtc/livekit/rtc/participant.py | lib/livekit/proto/livekit_sip_pb.rb | SIP troubleshooting guide | LiveKit Docs

I've sent you the Trunk and Dispatched can you check if it's right?

Thank you for sharing the trunk and dispatch rule configurations! Here’s what I’ve observed: 1. SIP Trunk: ◦ The trunk

ST_xkWr6Bu9auvk

has

allowed_addresses

set to

0.0.0.0/0

, which means it allows all inbound traffic. This is great if you want to accept calls from any IP address. ◦ The

numbers

field includes several phone numbers, like

+61238154006

. Just double-check that the incoming call matches one of these numbers to ensure smooth routing. 1. Dispatch Rule: ◦ The rule

SDR_HZ4X3GsCZ4kU

is linked to the trunk

ST_xkWr6Bu9auvk

, which looks perfect. ◦ The

inbound_numbers

field is empty, so it will accept calls from any number. This is totally fine if you want to allow all numbers. ◦ The

room_prefix

is set to

call-

. It’s a good idea to make sure the room name generated with this prefix matches what your system expects. Overall, everything seems to be set up correctly to accept calls. If you’re still experiencing issues with calls being rejected, it might be related to how the incoming call is routed or matched. Please feel free to reach out if you’d like me to help you dig deeper into this—I’m here to assist!

I'm experiencing livekit rejecting inbound flood

It looks like your trunk and dispatch rules are set up correctly, which is great! The 'inbound flood' rejection usually happens when the system thinks there are too many repeated call attempts coming in. Let’s try a few things to help resolve this: 1. Check Call Frequency: Take a moment to see if calls are being sent too quickly from the same source. If that’s the case, you might want to slow down the call rate or add a small delay between calls. 2. Review Logs: It can be really helpful to peek at the logs around the time you see the rejection. This might reveal any patterns or unusual activity in the incoming traffic. 3. Adjust Rate Limiting: If you have access to the rate-limiting settings on your self-hosted LiveKit instance, try increasing the limits a bit to better fit your call volume. If you’re still running into trouble after trying these steps, please don’t hesitate to reach out. I’m here to help, and we can dig deeper together to find a solution.