Hey there! If you’re seeing calls stuck in the "Ringing" state and not moving to "OK," no worries — let’s try these steps together: 1. Double-check Agent Configuration: Make sure your agent is up and running, properly registered, and ready to take calls. Also, confirm that the agent name matches exactly in both the

WorkerOptions

and

RoomAgentDispatch

settings. 2. Look Over Dispatch Rule Setup: Take a peek at your dispatch rule to ensure it’s correctly configured with the right agent name, trunk ID links, and valid inbound number patterns. 3. Review Ringing Timeout Settings: Check the

ringing_timeout

in your SIP trunk settings to make sure the agent has enough time to answer. 4. Verify Authentication and Trunk Setup: Confirm that your SIP trunk username and password are set up correctly and match what your provider expects. 5. Check Media Negotiation: Make sure codecs are compatible, media encryption is set properly, and your network supports RTP media streams without issues. 6. Review Network and Firewall Settings: Ensure NAT traversal, firewall rules, and port configurations all allow SIP signaling and RTP media traffic through smoothly. If you’re still having trouble after these checks, feel free to share a bit more info like: • Your SIP trunk and dispatch rule configurations • Agent logs showing connection and dispatch events • Call flow logs with SIP response codes and timing details • Network setup info, including firewall and NAT settings With these details, we’ll be in a great spot to dig deeper and get this sorted out for you! Sources: Getting Help | livekit/livekit_composite | DeepWiki | protobufs/livekit_sip.proto | pkg/sip/inbound.go | livekit-protocol/livekit/protocol/sip.pyi | SIP Integration | livekit/livekit_composite | DeepWiki