Gigamajig Inc.
10/13/2025, 4:53 PMVapi Support Bot
10/13/2025, 4:55 PMAdrian
10/13/2025, 5:44 PMAdrian
10/13/2025, 5:45 PMAdrian
10/13/2025, 5:45 PMNir Simionovich (CEO@Cloudonix)
10/13/2025, 9:46 PMChiranjeet Mishra
10/14/2025, 7:17 PMserverMessages in the assistant settings do not include "phone-call-control" if Vapi is managing the call control. Use phoneCallProviderBypassEnabled: false for standard Vapi forwarding.
3. Review Call Transfer Scenarios:
- Ensure the use case is supported. For example, web-to-phone number transfers aren't supported.
4. Analyze Telephony Provider Logs:
- Obtain the phoneCallProviderId from the Vapi API call response. Check logs on your telephony provider (Twilio, Vonage, Telnyx) for transfer-related issues.
5. SIP Provider Analysis (if applicable):
- Conduct SIP packet analysis through Wireshark using REFER packets to determine if the transfer request was appropriately sent and acknowledged.
6. Check Destination Number:
- Confirm that the destination number format is correct, includes the country code, and is reachable.
If the problem persists, it may be worth checking your telephony provider’s dashboard for specific errors or configuration settings that might impact call transfers. This could involve examining transfer scenarios or SIP configuration as outlined in the detailed documentation [here](https://docs.vapi.ai/call-forwarding).
If you need further assistance in resolving this, ensure you have tested each of these areas thoroughly.