I'm sorry to hear you're experiencing some SIP calls not being picked up by agents and the lack of logs on the agent side. Let's work through this together! There are a few common reasons this might happen: • Agent Name Mismatch: It’s important to double-check that the

agent_name

in the agent's

WorkerOptions

exactly matches the

agent_name

in your dispatch rule configuration. • Connection Timeout: Sometimes, if the agent doesn’t connect to the room within 10 seconds, it might not respond. Optimizing startup time and ensuring proper scaling can really help avoid these delays. • Logging Configuration: Let’s make sure logging is enabled and set up correctly on the agent side so you can capture all the relevant information. • Network or Signaling Issues: It’s a good idea to check for any firewalls, SIP trunk misconfigurations, or regional compliance issues that might be blocking signaling or media. • Agent Shutdown or Errors: Sometimes agents might shut down early if there are errors during initialization, so it’s worth verifying this as well. Here are some steps you can take to troubleshoot further: 1. Verify that the

agent_name

is consistent in both the agent settings and dispatch rule. 2. Review your SIP trunk and dispatch rule configurations carefully. 3. Take a look at server and room logs to spot any dispatch events or errors. 4. Test the agent’s responsiveness on its own to make sure it can connect to rooms properly. 5. Use network debugging tools to confirm signaling and media are reachable without issues. If you try these steps and still run into trouble, please don’t hesitate to reach out. I’m here to help you explore more troubleshooting options and get this resolved together. Sources: SIP troubleshooting guide | LiveKit Docs | Getting Help | livekit/livekit_composite | DeepWiki | Community & Support | livekit/livekit_composite | DeepWiki | Agents telephony integration | LiveKit Docs