gredibregu
11/07/2025, 8:44 AMChiranjeet Mishra
11/08/2025, 1:02 AMcall.start.error-get-transport indicates an issue retrieving transport information during the start of a call. This might involve misconfigured or missing transport details when setting up your call using the Vapi platform.
To address this, ensure you have configured the transport property correctly in your call configuration as an object, as per the [April 8, 2025 update](https://docs.vapi.ai/changelog/2025/4/8). This update replaced the deprecated separate Transport schema with a simplified configuration directly within the Call object.
If you've already made this change and are still encountering the error, double-check the transport type (such as sip, pstn, or vapi.websocketCall) is correctly set and that any required provider details are complete and accurate.