andrewboy777
06/25/2025, 9:39 AMandrewboy777
06/25/2025, 9:47 AMShubham Bajaj
06/25/2025, 10:00 AM44.229.228.186/32
- 44.238.177.138/32
- `172.31.9.106/32`Ensure your SIP provider uses a unique termination URI or a dedicated SIP server, as shared servers might lead to routing issues if IP-based authentication is used.
2. **Check Call Ended Reason**: Obtain the call ID of the failed attempt and check the call's endedReason
by retrieving the call data from Vapi:
- Use the API:
shell
curl -X GET "https://api.vapi.ai/call/{call_id}" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json"
- Look for specific error codes that might indicate the issue, such as call.in-progress.error-sip-telephony-provider-failed-to-connect-call
.
3. **Examine Configuration**: Ensure your SIP trunk and phone number registrations are correctly configured in Vapi. Check for any misconfigured authentication details or incorrect SIP server addresses.
4. **Review SIP Provider Logs**: Check the telephony provider's dashboard for logs. Look for any error messages related to the SIP trunk configuration or call initiation.
Refer to the [SIP Trunking Guide](https://docs.vapi.ai/advanced/sip/sip-trunk) for detailed setup instructions and common troubleshooting steps. If you continue to face difficulties, consider examining specific configuration aspects that may have been overlooked.andrewboy777
06/25/2025, 10:41 AMKings_big💫
06/25/2025, 11:01 AMandrewboy777
06/25/2025, 11:05 AMandrewboy777
06/25/2025, 11:05 AMKings_big💫
06/25/2025, 12:31 PMKings_big💫
06/25/2025, 12:32 PMSubrat Sagar
06/25/2025, 2:54 PMandrewboy777
06/25/2025, 3:13 PMKings_big💫
06/25/2025, 6:07 PM