Nishad

@nharris-star2star I've been investigating this. From my various tests, I will admit that there are a couple of race conditions at play that could cause this behaviour. However, I believe...

Sure. Here is the trunk and here is the agent code ``` from livekit.agents import ( Agent, AgentSession, JobContext, RunContext, WorkerOptions, cli, function_tool, ) from livekit.plugins import deepgram, elevenlabs, openai,...

Alright. I figured out what messed up my calls. I was calling in from a number that was **NOT** configured in my inbound trunk. The call works(although it should error...

Thank you all for raising this issue. The check is for "from numbers" here -> https://github.com/livekit/protocol/blob/main/sip/sip.go#L733 . The filter for called numbers happens at the Trunk level. So that PR...

Hey @yaniv-peretz , yupp, we did update the docs. That doesn't sound right. @rektdeckard , would you be able to help fix that in Livekit Cloud ?

Have you tried using this guide -> https://support.exotel.com/support/solutions/articles/3000134145-livekit-and-exotel-sip-trunking-integration-guide ?

Thanks for the feedback @dennwc . I've gone ahead and made [changes](https://github.com/livekit/protocol/pull/1101) to protocol and we could maybe go with the second approach you suggested. So we would not block...

What softphone are you using on amazon connect @gchapellin ? the `180 ringing` leads to local ringtone unlike a `183 session progress` . Does the softphone have some option to...

We could look at adding a config that allows sending back 100/180 right before the 200OK. I can't guarantee how quickly we can get to that though.

Hi @zaheerabbas-prodigal , looks like the remote end is sending media from two different IPs and switching SSRCs. That is causing this. It's not technically off spec but it usually...