@Evadora (Vapi) Hi Vapi team, I’m integrating inbound SIP into Vapi using a BYO SIP trunk credential, and inbound calls are not being recorded in the dashboard. Account / trunk details OrgId: c72786ec-d64f-4f80-a79a-c47f504a73c2 Credential (BYO SIP trunk): 8516b872-087a-48ee-a1b0-c75c91413fe0 (name: Inbtel inbound (IP-auth)) Source gateway IP: 207.182.145.2 (UDP 5060) PBX/softswitch destination (Request-URI): sip:526627760699@8516b872-087a-48ee-a1b0-c75c91413fe0.sip.vapi.ai:5060 DID: 526627760699 Issue / behavior From the PCAP: Vapi replies 100 Trying and then 200 OK to the INVITE. We send ACK. After that, Vapi sends BYE and ends the call (various attempts: ~1.6s / ~30s / ~70s / ~89s). The call never appears in Dashboard → Calls, and GET /call returns nothing when searching the corresponding time window. Evidence (latest tests) CALL 1 — 2026-05-18 18:54:41 UTC Request-Line: INVITE sip:526627760699@8516b872-087a-48ee-a1b0-c75c91413fe0.sip.vapi.ai:5060 SIP/2.0 X-Trace-ID: 23287f3cce8689ea4d963540e95718d4 X-Call-Sid: 0898d81d-697e-4798-b48f-bc56a174c65b Vapi sends BYE at ~1.65s CALL 2 — 2026-05-18 18:55:10 UTC X-Trace-ID: 71cc51d53770a6583468b6e56a61d8d2 X-Call-Sid: b94fd2db-ab25-43be-bec4-b89086e6537e Vapi sends BYE at ~30.84s (I can attach the full PCAP if needed.) Request Could you please investigate (using the X-Trace-IDs above) why the inbound call is not being created/persisted under my org and why Vapi is sending BYE? Thanks. Saul Mariscal Z

Hello - support will not see this post here. You will want to start a post in #1211483291191083018