Hey folks, quick question on BYO SIP trunk routing. I’m seeing outbound calls end with endedReason=customer-busy and sipStatus=603 (Decline), but the call record shows phoneCallTransport=pstn and phoneCallProvider=vapi. Expected: this call should have gone out over my BYO SIP trunk (TLS 5061) to my SBC, with caller ID formatted as E.164 (+971 …). From/To: +971…80 → +971…033 (redacted) Any idea why it’s routing via PSTN instead of the SIP trunk, and what I need to do to ensure outbound actually egresses via BYO SIP? Also, is there a way to get the raw SIP INVITE (headers + SDP) Vapi sent (PCAP like artifact.pcapUrl, or an internal trace) so I can verify From / P-Asserted-Identity formatting? Calling to UAE numbers via a dedicated SBC in our UAE office. Best, Ahmed

Also experiencing this issue. I raised it with Vapi support but still waiting to hear back 😐

There was an issue earlier that has been resolved. Marking this as solved for now

Hi Amanda, I just tried now. Got the same error. Here's the summary from Composer: For call 019e2f7a-c47c-7000-a265-e3587edcf6bb, the full details match the same pattern: Status: ended Ended reason: customer-busy phoneCallTransport: pstn phoneCallProvider: vapi SIP status / reason: 603 Decline (sipReason: "Decline") SBC call id: 9687685d-cb93-123f-0295-02c16c8be2c9 To: +9715xxxxx33 From phoneNumberId: b1da99ad-7b12-415f-9709-4e58904bc642 (your BYO number +971xxxxxx0 with the new trunk credential) Key takeaway Even when originating from the BYO phone number that has your BYO SIP trunk credential, Vapi is still egressing via PSTN (phoneCallTransport: pstn) rather than sending an INVITE to your SBC. That’s why you won’t see INVITEs on the SBC

Hi, To help us investigate this further, could you please share the following details: • How often is this issue occurring? • Is it happening on every call made through this Phone Number ID, or does it happen intermittently? • Please share a few more Call IDs where you experienced the same issue. Additionally, could you please try the following steps: 1. Delete the SIP credential currently configured in Vapi 2. Delete the associated phone number configuration 3. Create/configure them again 4. Test whether the issue still persists afterward Once we have this information, we’ll coordinate further with our provider and investigate what may be causing the behavior.

Hi Oshi, I followed your steps and I can confirm it's working now