I'd love to help you get to the bottom of this! Could you please share a bit more about the environment where you're experiencing this issue? For example: • Are you using LiveKit with a SIP trunk or gateway integration? • Is this happening during an inbound or outbound call? • Do you have any additional logs or error messages that might shed some light on the problem? Having these details will really help us work together to find the best solution. Thanks so much for your patience! Sources: Sources/LiveKit/Protos/livekit_models.pb.swift

Thanks for reaching out! The Q.850 cause code 102 usually points to a "No circuit/channel available" issue, which often means there’s a hiccup with resource allocation. I understand this can be a bit tricky, especially since LiveKit’s documentation doesn’t specifically cover Q.850 cause codes or how they’re handled in SIP trunk and dispatch rule setups. Let’s try a few steps together to get to the bottom of this: • First, check if your SIP trunking provider is sending cause code 102 and whether LiveKit’s SIP service is mapping or showing this code. • Take a look at the carrier-level logs to see if there are any circuit or channel availability issues between your SIP provider and LiveKit. • Make sure your LiveKit SIP service is set up correctly to accept calls — double-check the IPs, numbers, and credentials. If you’d like, I’m here to help review your trunk and dispatch rule configuration in LiveKit to make sure everything’s in order. Just let me know how you’d like to move forward! Sources: Accepting inbound calls | LiveKit Docs | SIP overview | LiveKit Docs | SIP troubleshooting guide | LiveKit Docs

And yes, please review my trunk and dispatch rule configuration