@Vapi This is for call log 07c95a52-bb81-499c-9821-828b8a7cf8cb, the report mentions the call was not connected because SIP gateway failed to connect, but is there more information available as to why gateway failed. Was it due to incorrect SIP IP or any other reason.

message has been deleted

Hi @Sahil @Shubham Bajaj this is regards to the VPN tunneling that I requested for. I have created AWS instance. The instance is connected with the dialer however I am using the private IP of the instance in place of SIP URI to integrated the phone number, but the calls are not getting connected. I tried pinging VAPI static IP but it failed. Scenario is that my middle ware is connected with the dialer and interacting, but middleware is not able to connect with VAPI servers.

@Invorto As discussed, you need to use your public IP address as the gateway IP for your Bring Your Own SIP Trunk configuration.

Hi @Shubham Bajaj still not able to connect the call. Showing the same error.

@Invorto can you share the recent call id please.

fee3c5b1-7e4e-46b6-ab5a-1615a3979267 2b47d883-e489-4507-8206-7d9f964f3f7a

@Invorto Did you by any chance delete your phone number?

Probably I did. Right now I am using Clients public IP to resolve this issue.

@Invorto Will you be available for a call to resolve this issue?

Yes 8:30PM ?