my dispatch rules and trunk configs are solid, the...
# telephony
h
my dispatch rules and trunk configs are solid, they were working previously now just perpetual ringing
f
Hi @hallowed-alarm-30842 the error “call was not authorized by trunk configuration” means the iINVITE didn’t pass the inbound trunk’s authorization checks (before dispatch rules run)...,.
To isolate this fast, can you please send me; if you have SIP trace (PCAP or ladder) for one failing call (from first
INVITE
to final response) with the Call‑ID ???
h
SCL_V7drJST6ATZa call id incoming payload:+15616997469 From host 10.34.9.215 To number +14195975749 Region US East 1 Connection type TLS Events Type Call Info Error Nov 19, 2025, 21845 PMCall ended call was not authorized by trunk configuration Nov 19, 2025, 21845 PMCall incoming — SCL_V7drJST6ATZa 9 {callId: "S`CL_V7drJST6ATZa"`
trunkId: "ST_h3FkFCsLYaVf"
region: "oashburn1b"
fromUri: {user: "<tel:+15616997469|+15616997469>"
host: "10.34.9.215"
port: 58872
transport: "SIP_TRANSPORT_TLS"
}
toUri: {user: "<tel:+14195975749|+14195975749>"
host: "1c010lj07tz.sip.livekit.cloud"
port: 5061
transport: "SIP_TRANSPORT_TLS"
}
callDirection: "SCD_INBOUND"
createdAtNs: "1763579925541312781"
}
@freezing-france-64950 had a 3pm to show off our agent lol and now none of them function 😞
f
Easy tiger, let's fix them asap
✅ 1
h
my goat please
@freezing-france-64950 anything i can do handsome
f
Boss, your PCAP and log indicate that LiveKit never passed the call to the dispatch rule because trunk ST_h3FkFCsLYaVf rejected it as unauthorized...
To resolve the problem,,
edit that trunk’s configuration so that the DID being dialed (+14195975749) is listed in its
numbers
array, or leave
numbers
empty but then specify either
allowedAddresses
containing your PBX/SBC IP(s) or username/password authentication; otherwise the call will continue to fail..
h
i already have that boss man
have each numbre assigned to each trunk and all twilio ips allowed
image.png
f
Checking
h
ty
f
boss,
error log shows trunk
ST_h3FkFCsLYaVf
at 21845 PM on Nov 19...
your screenshot shows three new trunks created around 3:07 PM on Nov 19 (≈49-50 minutes later), with different trunk IDs ...
h
yeah ive deleted and rebuilt the trunks 3x since then lol
all the same settings
should not matter the settings appeara correct no?
f
Can you place one fresh test call now to +14195975749 and send these 4 items from the LiveKit log? 1. Call‑ID and trunkId shown for the new call. 2. The “Call incoming” and “Error” lines for that call. 3. The inbound trunk JSON for the trunk that should receive +14195975749 (redact secrets): include
numbers
,
allowedAddresses
,
allowedNumbers
,
authUsername
,
authPassword
. a. you can change later, if you want to 4. Which Twilio edge/region you’re using (e.g., North America – Virginia).
h
getting no answer in twilio Call SID CAd8a6f2c8a9e3ef9b75e32f01ef7a3542 Date 155215 EST 2025-11-19 Start Time 155215 EST 2025-11-19 End Time 155232 EST 2025-11-19 Duration 0 sec Cost — From +15616997469 To sips:+14195975749@1c010lj07tz.sip.livekit.cloud;transport=tls Direction Trunking Originating Type sip-pstn Trunk SID TKe377306b3cb38dea174de2bc5416e26d Status No Answer SIP PCAP Log Not available Stir/Shaken Status A however i cant send the logs from livekit as they run 40 mins behind
image.png
still getting call was not authorized by trunk configuration
SCL_6JVbg6bBov27
f
boss, in the
trunk-14195975749
JSON, please show just these keys:
numbers
,
allowedAddresses
,
allowedNumbers
. Confirm
allowedNumbers
is empty/omitted and no inbound auth is set (Twilio EST doesn’t support inbound digest)...
Open trunk‑14195975749 → JSON editor and ensure;
Copy code
{
  "numbers": ["+14195975749"],
  "allowedAddresses": [
  ],
}
heads‑up on “From host 10.34.9.215” in your earlier log:
r
Hey @freezing-france-64950 @hallowed-alarm-30842, we are seeing something weird as well, closely related to this. we had these numbers working for months now, and suddenly today, we started receiving "No Answer" from twilio with sip failing to connect. Not sure if this is related to any release done in last 1-2 days.
f
that value comes from SIP headers and may not be the network peer IP LiveKit checks. The allow‑list is enforced on the remote socket IP that connected over TLS 5061, so confirm the actual peer IP from your PCAP/edge logs and make sure it’s on your list.
@rhythmic-church-8251 I personally have sip trunks created 5 months ago, facing no issues on more than 50 trunks.
All are okay
What are your regions? Did you get any emails of violation from twilio side?
h
@freezing-france-64950 i tried that as well, no dice, same error. it was functioning just fine before with the twilio addresses allowed per the documentation, but ive tried no ips to allow all and no phone numbers to allow all and both result in the same perpetual ring, no answer with sip trunk error
need real support on this as i have good experience with this and sip trunking and everything is correct but still not working it seems to be a platform issue here
r
Update from our end: we did identify the issue on our end. It was more application error, where we were making some API calls before we would accept the call (Including checking the phone lookup API), which in our case was taking longer than 30 seconds, and was basically ringing the calls. So, overall, does not look like a livekit issue.
👀 1
h
not the issue for us, we send our calls directly from twilio to livekit and when the agent joins, our agent initiates so this is not a code issue on our end 😞
👀 1
r
You need a dispatch rule
twirp error failed_precondition: No SIP Dispatch Rules defined