Flood protection not disabled even with correct config and single call

[VishnuVandith]

Describe the bug

I'm getting SIP call rejections with status: 486, reason: "flood" despite making only one call at a time. I’ve set both flood_protection and rate_limits to high values or disabled mode, but flood protection still triggers.

---

To Reproduce

1. Use livekit/sip:latest
2. Mount this sip.yaml to /sip/config.yaml:

api_key: '----'
api_secret: '----'
ws_url: 'wss://livekit.anantix.ai'

redis:
  address: 'localhost:6379'

sip_port: 5060
rtp_port: 10000-20000

insecure: port,invite
use_external_ip: true

flood_protection:
  enabled: true
  invites_per_second: 1000
  burst: 1000

rate_limits:
  invites_per_minute: 1000
  invites_burst: 1000

room_mapper:
  default_room: "open-room"
  default_identity_prefix: "open-room-"

logging:
  level: debug




3. Make a single SIP call
4. Observe log:
`status: 486, reason: "flood"`



### Here's My `sngrep` log

INVITE sip:8047133250@livekit.anantix.ai SIP/2.0
From: sip:+916300754857@139.59.4.62;tag=as6f328be1
To: sip:8047133250@livekit.anantix.ai
Call-ID: 21a3de806ac7df3b227861e60e4ea3e7@139.59.4.62:5060
CSeq: 102 INVITE
User-Agent: Asterisk PBX 18.21.0-vici
m=audio 15472 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

###But LIVEKIT SIP REPLIES WITH


`100 Trying  
180 Ringing  
486 Busy Here — reason: "flood"`

[biglittlebigben]

This is typically caused by the absence of inbound trunk or dispatch rule matching the call in livekit