call.start.error-get-transport end reason call
# support
h
v
The error
call.start.error-get-transport
means there was a problem retrieving transport information when starting the call.
Actionable step: - Review your transport configuration (such as Twilio or SIP settings) and ensure all required fields and credentials are correct and up to date. If you recently changed any provider credentials or phone number settings, double-check those for typos or missing values. Tip: After updating, try a test call to confirm the issue is resolved. For more details, see the [Vapi call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason). Source: - [Call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason)
c
Hi Hamid, If you encounter issues with call forwarding where they drop immediately, you can start by verifying whether Vapi successfully initiated the forwarding. Use API requests to check the
endedReason
code; if it's
"assistant-forwarded-call"
, this suggests Vapi attempted the forward but you may need to look into your telephony provider's logs for errors. Detailed troubleshooting steps can be found [here](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops). If you're dealing with a call starting error specifically related to
call.start.error-get-transport
, this indicates an issue retrieving transport information. Ensure your call configuration includes correct and active provider credentials, and check your connection to the transport service. For additional configuration and troubleshooting tips, review this [changelog document](https://docs.vapi.ai/changelog/2024/11/3). Let me know if you need further assistance with a specific error code.
3 Views