I have two issues, one is the weird status call.start.error-get-transport, sending calls via campaigns set this status... some times. And some Campaigns still in progress even when the call range is due. Please Help. Org Id: 6d08ca3b-7dc4-4c84-9b37-74faec1a622b Campaign Id: a3473744-c1a8-47a1-8c53-6ec5f7c3da02 Call ID: cd2a3922-7f5d-4da0-87f5-84313b080d96 https://cdn.discordapp.com/attachments/1415097383657672704/1415097383896744016/image.png?ex=68c1f7a3&is=68c0a623&hm=3634d3a00f8f66b82557ac5b74cbc5ffd88eff916e4ac421be0247a8a198296d&

Thank you for sharing the details. To help troubleshoot the "call.start.error-get-transport" error, could you confirm if your campaign's call configuration is using the new

transport

object format (as the older Transport schema is now deprecated)? This will help determine if a misconfiguration is causing the issue. If possible, please share a sample of your current call configuration for review. Note: The error may be related to missing or incorrect transport settings, as recent updates require the

transport

property to be set as an object in the call configuration ([see changelog](https://docs.vapi.ai/changelog/2025/4/8)). Source: - [April 8, 2025 Changelog](https://docs.vapi.ai/changelog/2025/4/8)

Hi julian, The error

call.start.error-get-transport

indicates a problem retrieving the transport information during the call start process. Here are a few steps to help troubleshoot and resolve this issue: 1. Verify Transport Configuration: Ensure that your call request correctly specifies the transport. For WebSocket transport, the configuration should look like this:

json
   {
     "assistantId": "YOUR_ASSISTANT_ID",
     "transport": {
       "provider": "vapi.websocket",
       "audioFormat": {
         "format": "pcm_s16le", // or "mulaw"
         "container": "raw",
         "sampleRate": 16000 // or 8000 for Mu-Law
       }
     }
   }

2. Authentication: Check that your API call includes a valid

Authorization

header with a valid bearer token. Ensure your token has the correct permissions to initiate calls. 3. API Endpoint: Confirm that you are using the correct API endpoint for call initialization, which should be

'https://api.vapi.ai/call'

. 4. Check for Updates: Verify that your software or SDK is up to date with the latest version that supports the current API capabilities. If these steps do not resolve the issue, double-check the error logs or audit any additional configurations that may affect this transport retrieval. For more information on configuring WebSocket calls and formats, refer to the [WebSocket Transport documentation](https://docs.vapi.ai/calls/websocket-transport).

I also get this error

Hi, could you please provide a call id where you experienced this issue? We would like to review the logs to identify the cause.