The transfer tool only says that it transferred the call but I can't find information telling me where it transferred to, can you help me resolve this please?

To track where a call was transferred, log the transfer destination in your webhook handler when responding to a

transfer-destination-request

. Here’s a simple Node.js (Express) example:

js
app.post('/webhook', (req, res) => {
  if (req.body.type === 'transfer-destination-request') {
    const destination = /* your logic to determine destination */;
    console.log('Transferred to:', destination); // Log the destination
    res.json({ destination });
  }
});

This way, you can always check your server logs to see exactly where each transfer went. Sources: - [Dynamic call transfers](https://docs.vapi.ai/calls/call-dynamic-transfers) - [Server events](https://docs.vapi.ai/server-url/events)

@Nemnel destination you mean number?

i found the answer

Message marked as helpful by @Nemnel! 🎉

there’s a way to see it in the UI there’s just a bug on one view

Okay

Hi Nemnel, To troubleshoot call forwarding drops, you can follow these steps from our [debug guide](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops): 1. Verify Forwarding Initiation: - Use Vapi API to check if the call was forwarded. Look for

"endedReason": "assistant-forwarded-call"

. If not, check your assistant's

serverMessages

configuration. 2. Check Telephony Provider Logs: - Refer to the

phoneCallProviderId

from Vapi's response and inspect the logs on your telephony provider's dashboard (e.g., Twilio, Vonage) for any errors related to call transfers. 3. Analyze SIP Signaling (if applicable): - Download the PCAP file from Vapi and use Wireshark to filter for

sip.Method == "REFER"

. Check for

REFER

,

202 Accepted

, or any error responses. 4. Configuration Check: - Ensure

phoneCallProviderBypassEnabled

is set to

false

unless implementing custom control. 5. Common Solutions: - Successful forwarding, but call drops: Ensure the destination number is correctly formatted and reachable. - Transfer not initiated: Modify your

serverMessages

settings and ensure you aren't overriding Vapi's control with custom logic. For dynamic transfers, ensure the

destinations

array is empty in your

transferCall

tool, and if using a server webhook, it's configured to decide the transfer destination. You can refer to our [dynamic call transfers guide](https://docs.vapi.ai/calls/call-dynamic-transfers) for setup details. If you continue to experience issues, confirming details like telephony provider logs and replicating the issue outside Vapi can be useful for further analysis.

thanks this is solved

Glad you were able to get this resolved. If anything else comes up or you need further assistance, we’re here to help.