SIP inbound trunk correctly configured but returns "404 No trunk found" on every call

Telephony
,
1

Projet: voice-agent
Trunk inbound ID: ST_cqQqtkBFjr7f (nom: trunk-depuis-xivo)
Dispatch Rule ID: SDR_xkGsk9URv3in (routing-xivo-9000)
Agent attaché: agent-ia

Symptôme: tout appel SIP entrant vers sip:9000@agent-ia-xmroz06z.sip.livekit.cloud
reçoit “404 No trunk found” du edge 143.223.92.84 (Record-Route interne: 10.33.219.131),
alors que le trunk inbound est confirmé exister via lk sip inbound list avec:

  • numbers: (vide, accepte tous les numéros)
  • allowed_addresses: 41.83.185.27/32 (vérifié = IP source réelle exacte via curl ifconfig.me)
  • authentification configurée

Déjà testé sans succès:

  • numbers=[“9000”] puis numbers= (vide)
  • allowed_addresses correspondant exactement à l’IP source
  • endpoint régional (agent-ia-xmroz06z.eu.sip.livekit.cloud) — même résultat, même edge
  • DNS vérifié propre (dig confirme 143.223.92.84 et .175 comme réponses légitimes)
  • Recréation complète du trunk et de la dispatch rule (deux fois)

Exemple de Call-ID récent avec 404: 1e042139-b29f-47c9-827d-9529bb3b772b
Autre Call-ID (test précédent): 25777750-5b86-4513-9c40-d3b81afd5143

Already tested without success:

  • numbers=[“9000”] then numbers= (empty, accept all)
  • allowed_addresses matching the exact real source IP (verified via curl ifconfig.me)
  • region-pinned endpoint (agent-ia-xmroz06z.eu.sip.livekit.cloud) — same failure, same edge
  • DNS verified clean (dig confirms 143.223.92.84 and .175 as legitimate answers)
  • Full recreation of trunk and dispatch rule (twice)

Example Call-ID with 404: 1e042139-b29f-47c9-827d-9529bb3b772b

2

I believe you are trying to connect to LiveKit directly from a SIP softphone? If so, that is not supported, and you would need to come in through a SIP provider: Telephony introduction | LiveKit Documentation

Please let me know if I have misunderstood.

3

I don’t recommend this for production use, but if you are just testing directly from a softphone, that should work. (I test this way quite often)

I think the issue you are having is that you are not pointing to the SIP URI and are using the web URI instead.

SIP interactions should go to the SIP URI you find here:
https://cloud.livekit.io/projects/p_/settings