Thanks — you're asking where trunk info is stored when self-hosting LiveKit and whether you can list trunks like in LiveKit Cloud. Good question. • Storage: Trunk configuration (SIP trunks, dispatch rules, participant state, etc.) is stored in Redis. The SIP server does not include an embedded database, so you must configure Redis in your

config.yaml

(address, username, password). • Listing trunks: Yes — you can list trunks when self-hosting. Use the SIP APIs or the CLI: ◦ CLI: ▪︎

lk sip inbound list

▪︎

lk sip outbound list

◦ Server SDK / API examples: ▪︎ Go:

sipClient.ListSIPOutboundTrunk(context.Background(), &livekit.ListSIPOutboundTrunkRequest{})

▪︎ Use the corresponding

ListSIPInboundTrunk

for inbound trunks. If you want, tell me your deployment Redis address or paste the

redis:

section of your

config.yaml

(sanitize any secrets) and I can confirm your configuration or show exact commands to query the trunks. Sources: Self-hosted SIP server | LiveKit docs | SIP APIs | LiveKit docs | Self-hosting the Egress Service | LiveKit docs | Distributed Setup | LiveKit docs