Hello, We have our own SIP , and phone number, inbound calls are working, but we are getting nothing on the phone central , about the outbound calls, basically, the error: phone id : ade35ff2-3187-4f2e-88a5-89df7d060db1 All outbound calls have this error : l: call.start.error-get-transport Vapi Numbers Can't Dial Outbound Yet. - thats the phone id if it helps , basically the sip /voip company that we gave the sim cards, telling us , nothing is coming from vapi for outbound, but the inbound works properly , thanks,

The

call.start.error-get-transport

error means Vapi cannot retrieve transport (SIP trunk) info for outbound calls. Please ensure your phone number is correctly associated with your SIP trunk credential in Vapi. Here's a sample API call to link your phone number to the SIP trunk:

bash
curl -X POST "https://api.vapi.ai/phone-number" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_VAPI_PRIVATE_KEY" \
  -d '{
    "provider": "byo-phone-number",
    "name": "Your Number",
    "number": "YOUR_PHONE_NUMBER",
    "credentialId": "YOUR_SIP_TRUNK_CREDENTIAL_ID"
  }'

Double-check this association in your dashboard to resolve the outbound issue. For more details, see the [Vapi call ended reason documentation](https://docs.vapi.ai/calls/call-ended-reason). Sources: - [Call ended reason documentation](https://docs.vapi.ai/calls/call-ended-reason) - [SIP trunk setup documentation](https://docs.vapi.ai/advanced/sip/sip-trunk)

Thanks for sharing this, the issue isn’t your SIP carrier. The error means Vapi isn’t initializing an outbound SIP transport, so nothing ever reaches your provider, even though inbound works. This usually happens when outbound calling isn’t enabled or mapped on that phone ID in Vapi. Can you confirm whether outbound is enabled for that phone and which SIP trunk Vapi should use for outbound (same as inbound or separate)? @ReminD ^ CX

Hi, Could you provide me with the Call IDs where this issue occurred? This will help me review the logs of the call.