😫 Hi VAPI Support, We're experiencing an issue where incoming SIP calls to a registered byo-phone-number are being rejected with the error message "phone number not found." Here are the details: Type: byo-phone-number Status: The number is successfully registered and linked to an assistant. SIP Trunk: We are using a byo-sip-trunk From our end, everything appears properly configured, but the calls are still being rejected. Could you please help us to verify if the number is correctly recognized on your end, or if there is a configuration mismatch? Let us know if you need any further logs or details from our side. Thank you, Marvin

Hi ITD, To resolve the "phone number not found" issue with your inbound SIP calls, please ensure the following: 1. **Phone Number Configuration**: Verify that the phone number is correctly associated with your SIP trunk in Vapi. Use the

GET /phone-number/:id

endpoint to check that all details match your configuration. 2. **SIP Trunk**: Make sure the SIP trunk is correctly configured with the necessary IP addresses allowlisted, as specified in the [Network requirements section](https://docs.vapi.ai/advanced/sip/sip-trunk). 3. **Assistant Linking**: Confirm that the number is linked to an active assistant. You can do this via the dashboard or by checking the configuration through API calls. 4. **Provider Forwarding**: Ensure your provider is forwarding calls to the correct SIP URI format (e.g.,

your-number@sip.vapi.ai

). 5. **Call Logs**: Review your Vapi call logs for any errors during call routing that might provide more insight. If these areas appear correctly configured and the issue persists, double-check your SIP provider's settings and reach out if specific configurations require review.

Thank You for your response. We already checked that, we are getting 200 ( OK) response to the INVITE request, but after that we are getting a "BYE" and a "Phone Number not Found " message

Do you happen to have a PCAP file for the call trace? We would like to analyze it for any errors.

Hello, Thank you for your response, we already been able to solve this issue

Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue