A 404 error for inbound SIP calls to LiveKit indicates that the system could not match the incoming call to a valid trunk or dispatch rule. This prevents the call from being routed to a LiveKit room and stops agents from joining. To resolve this, follow these steps: • Check your SIP trunk configuration: ◦ Verify your SIP provider’s IP addresses are listed in the trunk’s

allowed_addresses

. ◦ Ensure the

numbers

field includes the phone number being called. ◦ If using authentication, confirm

auth_username

and

auth_password

match your provider’s settings. • Review your dispatch rule configuration: ◦ Make sure the dispatch rule’s

trunk_ids

includes your inbound trunk ID. ◦ If the rule specifies

inbound_numbers

, confirm it includes the called number. ◦ Check that the rule type is set correctly (direct, individual, or callee). • Confirm your SIP provider is sending calls to the correct LiveKit SIP URI and that network connectivity is open on the required ports. • If using authentication, ensure your provider responds to 407 Proxy Authentication Required with the correct credentials. A 404 error means the call failed to match either a trunk or a dispatch rule. Focus on verifying these configurations to resolve the issue. Sources: pkg/sip/protocol_test.go | Accepting inbound calls | LiveKit Docs

@alert-easter-19258 does the dispatch rule, rule type matter?