Inbound SIP call identifies inbound trunk but dispatch rule is never selected ("no trunk configuration for call")

Telephony
,
1

Hello LiveKit team,

I’m integrating Vobiz SIP with LiveKit Cloud.

Configuration

Project: Skillsynch

Inbound Trunk:
ST_zBtVZS5JSWAp

DID:
+918071579762

Dispatch Rule:
SDR_9BpbRQSbPdSx

Agent:
outbound-caller

Room Prefix:
inbound-

Current behavior

Incoming calls successfully reach LiveKit.

From the LiveKit Call Details page:

  • Direction: Inbound
  • To Number: +918071579762
  • Trunk ID: ST_zBtVZS5JSWAp
  • Signaling: TCP

However,

  • Dispatch Rule is shown as “—”
  • Worker is never started
  • No room is created
  • Call fails immediately with:

no trunk configuration for call

This is confusing because the call details already show that LiveKit has identified the inbound trunk.

Dispatch Rule JSON

{
“sipDispatchRuleId”: “SDR_9BpbRQSbPdSx”,
“trunkIds”: [
“ST_zBtVZS5JSWAp”
],
“name”: “Vobiz Production Inbound”,
“rule”: {
“dispatchRuleIndividual”: {
“roomPrefix”: “inbound-”
}
},
“roomConfig”: {
“agents”: [
{
“agentName”: “outbound-caller”
}
]
}
}

Questions

  1. Why does LiveKit identify the inbound trunk but still report “no trunk configuration for call”?
  2. Why is the Dispatch Rule blank for the failed call?
  3. At what stage is dispatch failing?
  4. Is there additional SIP validation after trunk identification?

I can also provide:

image
image1918×846 107 KB

2

That call, SCL_R9fMkr5myFyS was failing because it failed to match a dispatch rule. I couldn’t understand why the dispatch rule in your account failed, so I tried dialling the number and my call SCL_jDucsrFLMu49 succeeded (my number ends 7736). I notice the most recent dispatch rule was only recently created, so I think this issue is resolved?