GeraDeluxer
10/09/2025, 5:22 PMVapi Support Bot
10/09/2025, 5:23 PMGeraDeluxer
10/09/2025, 11:29 PMChiranjeet Mishra
10/10/2025, 11:26 PMcurl -X GET "https://api.vapi.ai/call/{call_id}" \ -H "Authorization: Bearer YOUR_API_KEY"
Check if endedReason shows "assistant-forwarded-call"
2. For SIP-specific issues:
- Check the PCAP file from the call logs (available in the API response)
- Use Wireshark to filter for sip.Method == "REFER"
- Look for:
- REFER packet presence (confirms Vapi sent transfer request)
- 202 Accepted response (confirms provider accepted)
- Error responses (4xx, 5xx indicate rejection)
3. Configuration checks:
- Ensure phoneCallProviderBypassEnabled is set to false
- Remove "phone-call-control" from serverMessages if present
- Verify your SIP trunk configuration matches endpoint setup
4. Known limitations:
- PSTN-to-SIP transfers are not supported
- Cross-provider transfers may have compatibility issues
If SIP REFER packets are missing in PCAP, it means Vapi didn't send the transfer request to the SIP provider. This aligns with your theory about assistant-to-SIP trunk connectivity issues.
Let me know if these steps resolve the issue or if you need further assistance.Chiranjeet Mishra
10/10/2025, 11:27 PMsip:+15557654321@sip.zadarma.com)
- You need to enable SIP REFER on your provider's side as well
- When creating your SIP trunk credential in Vapi, make sure to include all signaling IP addresses to prevent unauthorized 401 errorsNir Simionovich (CEO@Cloudonix)
10/13/2025, 10:04 PM