I have an old phone number from Telnyx and for some reason the caller ID for my new number keeps using the old one. I recreated the SIP trunk connection twice now What causes the issue, why is my caller ID still the old number?

This is a known issue: Vapi support has confirmed that caller ID masking with Telnyx SIP integration does not always work as expected, even if you set the correct headers. They are working on a feature request to add true caller ID masking support for Telnyx. For now, double-check that your new number is set as the Caller ID in both Telnyx and Vapi, and that no settings in Vapi override it. If the issue persists, you may need to wait for the upcoming feature or contact Vapi support for further assistance. Reference: [Discord conversation on Telnyx caller ID masking](https://discord.com/channels/1211482211119796234/1372232009178415145) Source: - [Discord conversation on Telnyx caller ID masking](https://discord.com/channels/1211482211119796234/1372232009178415145)

Now my issue is that scheduled call is not working. The call will start but asisstant does not speak - then in call logs it says customer did not answer (even though I did)

Message marked as helpful by @Monkmode! 🎉

Thanks for sharing the details. To help diagnose why the assistant does not speak and the call log says "customer did not answer," could you confirm if the assistant ID is correctly assigned to your phone number in the Vapi dashboard? This is a common cause for similar issues according to the documentation I have found. Source: - [Discord conversation about troubleshooting assistant configuration](https://discord.com/channels/1211482211119796234/1367883431266095104)

[ { "subscriptionLimits": { "concurrencyBlocked": false, "concurrencyLimit": 10, "remainingConcurrentCalls": 9 }, "id": "019ac8a6-d214-7994-9eba-d6d7b64bfcba", "assistantId": "8504ea0a-177c-4d05-8965-be3959dfc257", "phoneNumberId": "015c396f-445e-4d56-8d64-eb4ba0103d8b", "type": "outboundPhoneCall", "createdAt": "2025-11-28T04:09:27.316Z", "updatedAt": "2025-11-28T04:09:27.316Z", "orgId": "2e167e0f-d8e4-43c5-9c95-e606721f37b4", "cost": 0, "customer": { "number": "+17788988324" }, "status": "scheduled", "schedulePlan": { "earliestAt": "2025-11-28T04:15:00.000Z" } } ] this is the output of the API

Since your API output includes both the

assistantId

and

phoneNumberId

, the next best step is to share your call ID and timestamp with Vapi support for deeper troubleshooting, as device or carrier differences can affect call detection. You can provide this information like so:

json
{
  "callId": "019ac8a6-d214-7994-9eba-d6d7b64bfcba",
  "timestamp": "2025-11-28T04:09:27.316Z"
}

This will help support investigate why the call is marked as "customer did not answer" even when you answered ([see discussion](https://discord.com/channels/1211482211119796234/1372232009178415145)). Source: - [Discord conversation on Telnyx SIP integration issues](https://discord.com/channels/1211482211119796234/1372232009178415145)

"id": "019ac8a6-d214-7994-9eba-d6d7b64bfcba", "assistantId": "8504ea0a-177c-4d05-8965-be3959dfc257", "phoneNumberId": "015c396f-445e-4d56-8d64-eb4ba0103d8b", "type": "outboundPhoneCall", "createdAt": "2025-11-28T04:09:27.316Z", "updatedAt": "2025-11-28T04:09:27.316Z", "orgId": "2e167e0f-d8e4-43c5-9c95-e606721f37b4", "cost": 0, "customer": { "number": "+17788988324" }, "status": "scheduled", "schedulePlan": { "earliestAt": "2025-11-28T04:15:00.000Z"

To help Vapi support investigate why your scheduled call is marked as "customer did not answer," please share your call ID and timestamp with them. For example:

json
{
  "callId": "019ac8a6-d214-7994-9eba-d6d7b64bfcba",
  "timestamp": "2025-11-28T04:09:27.316Z"
}

This will allow support to review your specific case and address device or carrier-related call detection issues. Reference: [Discord discussion on Telnyx SIP integration issues](https://discord.com/channels/1211482211119796234/1372232009178415145) Source: - [Discord discussion on Telnyx SIP integration issues](https://discord.com/channels/1211482211119796234/1372232009178415145)

Thank you for providing your call ID and timestamp. The best next step is to send this information to Vapi support for investigation, as device or carrier differences can affect call detection. Here’s how you can format your report:

json
{
  "callId": "019ac8a6-d214-7994-9eba-d6d7b64bfcba",
  "timestamp": "2025-11-28T04:15:00.000Z"
}

Share this with support so they can review your case and help resolve the "customer did not answer" issue. For more details, see the [Discord discussion on Telnyx SIP integration issues](https://discord.com/channels/1211482211119796234/1372232009178415145). Source: - [Discord discussion on Telnyx SIP integration issues](https://discord.com/channels/1211482211119796234/1372232009178415145)

@Vapi Support Bot Now I have an error saving transfer call tool the moment I add a phone number

Thanks for reporting this issue. To help diagnose the problem, could you please share the exact error message you see when trying to save the transfer call tool after adding a phone number? This will help identify whether it's a formatting, configuration, or system issue. If possible, please copy and paste the error text or describe what happens (e.g., validation error, page freezes, etc.). Sources: - [Vapi documentation: call forwarding](https://docs.vapi.ai/call-forwarding) - [Vapi SIP Trunking Telnyx external number call forwarding troubleshooting](https://discord.com/channels/1211482211119796234/1343963959421829172)

@Vapi Support Bot Tool Update failed - an error occured while updating the tool