486 Busy Here after

Telephony
, ,
1

Inbound SIP calls to our trunk are rejected with 486 Busy Here after ~2 seconds.

Project: insale-ai-m1echo28
Inbound trunk: ST_2dbsUFnJw5tW (insale-didww-inbound)
Dispatch rule: SDR_favvf8YoBxcx → individual, roomPrefix “pstn-in-”
Example rooms: pstn-in-_447846209575_ungLzh6S9Sdv
pstn-in-_447846209575_qYdifxHQ6Jqi

The room IS created and our agent joins ~4s later and connects fine —
but the caller has already received 486 by then.

  1. Why is 486 returned? Is LiveKit waiting for an agent before answering,
    and if so what is the timeout?
  2. What is our project’s concurrent inbound SIP call limit?
2

Hi, for that room I see a call to deleting roomimmediately after we sent two room_started webhooks to indicate that the room is starting. The delete room then triggered the 486. It looks to me like the delete is coming from yourself, either in one of those webhooks, or perhaps from elsewhere that I don’t have visibility to (e.g. your agent)