Hi Guys! I have problem with inbound calls, i add my sip trunk via server login and password, add your ip adresses and SIP URI to my sip provaider, but its dont work. Provaider says: Your PBX requires incoming authorization, but should not: Therefore, the call does not go through. Disable inbox authorization with a login password. I do that, but nothing. Can you help me? https://cdn.discordapp.com/attachments/1384179491370176582/1384179492087660636/image.png?ex=68843edb&is=6882ed5b&hm=2b9e432ac4ed2a66a081b6481fd8cdb646f65f69dcd016b546709b4f6bc42db3&

Thanks for sharing the details. To help you further, could you confirm if your SIP provider is forwarding inbound calls to the exact SIP URI in the format

{your_number}@sip.vapi.ai

and that you have disabled any authentication requirements for inbound calls on both the Vapi and provider sides? This will help pinpoint if the 401 Unauthorized is due to a misconfiguration in the forwarding or authentication settings. If you can share a screenshot or the exact forwarding rule from your provider, that would also be helpful. Sources: - [Vapi SIP Trunking Documentation](https://docs.vapi.ai/advanced/sip/sip-trunk) - [Vapi Zadarma Integration Guide](https://docs.vapi.ai/advanced/sip/zadarma)

Provaider says: With this, the adjustment on our side will not change. You can generate different URIs for skin-based registration and the ranks themselves will be generated in the URI context to which the inputs will be transmitted.

@Viktor Please DM me and I'll explain. But in general, your carrier can't support this connection, as their systems are designed to react to the challenge/response in a specific way, which is not compatible with what VAPI expects.

Hey Viktor, you can whitelist your IP address via this

Do that yesterday

Did it work?

no

We are investigating this issue a little deeper. Thank you for flagging this and we will get back to you shortly

Hi all, what about my problem?

We are still working on your request. Thank you for your patience. In the meantime, I will loop in my colleague for his perspective.

Hi @User Apologies for the delay, We requires incoming authorization for all incoming calls this can’t be disabled. To authorize your inbound calls, please: 1. **Username**: Enter your sip username (your full phone number, e.g. 1234567890). 2. **Password**: Choose any non-empty string (it can be simple, but cannot be blank or all whitespace). This step is mandatory to ensure secure handling of incoming requests. Let me know once you’ve updated these credentials, or if you run into any issues!

Good afternoon, I did it

Hey! To help track down this issue, could you share: - The call ID - The PCAP file This would really help us figure out what went wrong!

We cannot provide a dump on the call you specified, because the dump must be agreed in advance with our engineers. And it is desirable to understand why exactly you need it. If your technical specialists (or your integrator) see a problem, then it is necessary to specify what exactly they consider to be incorrect on our part and how the SIP dump will solve it. Basically, your PBX was asking for authorization for an incoming call, but it shouldn't. https://cdn.discordapp.com/attachments/1384179491370176582/1389188989671702599/image.png?ex=6863b691&is=68626511&hm=b6e4ee4cafa80dc23fb359c93819546678ec235b30a87872e0783fdb1b53abf5&

Having the PCAP file helps us understand and diagnose the issue paired together with the call id gives us the full picture when we analyze the logs. If you could please provide the PCAP file and a call id of a failed call, it would really help us.

I'm waiting for our pcap-file, can you also send me your pcap file, my sip provider asked for this too..

@Viktor If you want, you can resolve this issue in 5 minutes using Cloudonix - and I'll be happy to show you how. It will work for both inbound and outbound calling.

Please provide a call id so I can retrieve the PCAP file from our side

Hello, there is my file

@Viktor @Shubham Bajaj @Viktor you are trying to connect two things that can't be connected. The customer's carrier (lifecell) supports SIP trunking via B2B connections - meaning an IP to IP connection, no authorization required other than an IP whitelist. Now, VAPI requires an UAC connection, otherwise known as a challenge/response connection workflow - which they don't implement. Your choices are: 1. Find a different provider 2. Install your own SBC to handle the issue 3. Use a service like Cloudonix or Jambonz to resolve the issue Take into consideration that you are located in the Ukraine, and you be required to handle some regulatory issues with connecting to VAPI.

Hi, answer from my provider: In order to change it to ip authorization and bind the trunk to the ip address of the integrator, please provide the actual ip address of the SIP server + ip address of the media servers of your integrator. We will add them to the firewall and after that we will be able to change the settings to those you described.

@Viktor Yes, that is possible - however, that will present a very interesting problem down the line. Based on the above statement, once they define VAPI as a static resource on their system, if another customer wants to connect to VAPI, they possibly can't. However, if by some mistake they can - you will get the bill for their outbound calls !

Let's try...

Let us know if you need additional assistance

Yes, I need these 2 ip addresses

You can find the IP addresses here: You can check out this guide: for details on integration. Note: This is a standard guide used by many telephony providers, so it should be helpful.

Hi, i made it!!! but, The specified call was received by you and completed in literally 2 seconds:

Hey Viktor, Kyle's actually out on an offsite right now, but he'll be able to dive into this for you on Monday, and help figure out the best approach for your setup.

It looks like you are set up. Let us know if you need additional assistance

Doesn't work, i call, after 1.5 second - call is dropped...

@Viktor Are you still having issues? do you have a new SIP trace by any chance to review?

Hey Viktor, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!

Good afternoon, I'm looking forward to everything working.

Hey Viktor, there is no update as of now. There are bunch of changes which needs to be done from our end to accomodate it.

Hi, have any updates?

Sorry, no updates yet. We are continuing to work on the infrastructure of how SIP is handled within our platform to accommodate this feature.

Hi, what about my problem?

Our team is still working on making these changes to our infrastructure. Thank you for your patience

Hello, have any updates?