Hi everyone! I have LiveKit Server running on Amazon Web Services using Amazon EKS, with several LiveKit SIP gateways deployed on Amazon EC2. Each LK-SIP gateway is dedicated to a specific customer (separate phone numbers, networks, tunnels, whitelists, etc.). Incoming calls work perfectly — no issues there. The problem shows up with outgoing calls. From what I’ve been able to debug, when our agent initiates an outbound call, the SIP gateway seems to be chosen at random. That doesn’t work for us, since each call must go through a specific LK-SIP gateway tied to that customer’s number. Otherwise, the call fails (no direct tunnel to the SBC/PBX), gets blocked by whitelists, etc.. Is there a way to label or group SIP gateways so outbound calls are routed correctly? More specifically: how can we associate a SipTrunkID with a particular LiveKit SIP nodes? Thanks in advance — any guidance would be appreciated.

I believe you can't have separate LK-SIP gateways, its a single cluster thats associated with a single LK cluster. When you create a sip participant, its associated with the outbound trunk, but the outbound trunk doesn't have a LK-SIP GW association, it routes to whichever GW is available.

That's bad.. We have dedicated SIP-gateways, separated from each other, in different subnets, with direct IPSec tunnel to external systems. Selecting "available: gateway is not enough to pick the "right" one.

It could be possible via another SIP router layer after the LK SIP

@flat-photographer-63184 another SIP router is extra complexity and.. might not work in our case. We're probably aiming at customize livekit-sip component. If we get approval for this, there is high change for pull-request 🙂