Hello, I’m encountering an issue while setting up SIP redirection with Vapi.AI. I already have phone numbers that I can redirect via SIP, and I followed the tutorial provided. However, when I attempt the redirection, I receive an “unauthorized” error. Would someone be able to assist me with this? Thanks in advance for your help. https://relieved-yuzu-73a.notion.site/SIP-Inbound-Guide-1f0789ae62024748a62a6d81076b9f32 https://cdn.discordapp.com/attachments/1343998258581737542/1343998258778996917/Capture_decran_2025-02-25_a_18.10.04.png?ex=67bf4f6b&is=67bdfdeb&hm=ab13be6193c66ae0f2126033de5117ba8fdeccd494f45897110c364db0a5f213&

Hey Antoine, can you share the call ID so I can take a look?

Hello ! There is no call ID because the call don't appear in VAPI Can I email you the PCAP file ?

Antoine, vapi requires challenge/response interconnect. DM me and I'll help you resolve this. Or, you can use this guide - https://developers.cloudonix.com/guides/cxmlExamples/voiceAgentProvider/Vapi.ai

@Antoine please DM me your PCAP file, and let me once you hav DM'med me....

@Shubham Bajaj I just DM'med you ! Thanks @Nir S (CEO/Founder @Cloudonix) I DM'med you too 🙂 thanks a lot

In this call it shows an INVITE, then a 100 Trying, then a 401 Unauthorized, and finally an ACK. Normally, after the 401, the calling side should re-send INVITE with proper credentials (Authorization header). In this capture, that re-INVITE never happens. So the call fails because nobody follows up with the required authenticated INVITE. You have to send the username and password in Authorization header. Here username has to be your VAPI sip username and password can be anything but not empty. \`REFERENCE\` In Frame 3 (the 401 Unauthorized response), there’s a “WWW-Authenticate” header that says “Digest realm=…”. That header tells your telephony it needs to retry the INVITE with an “Authorization” header (containing the correct credentials).

@Shubham Bajaj I've worked with @Antoine on this issue. The problem is that their carrier, OVH, requires that their use be "Actively Registered" on their system, in order to process the INVITE. Unlike other carriers, which only require the Digest authentication for the INVITE itself. I've investigated the case with our engineering team, in order to provide a resolution and we do have a solution path. However, it will only get into work in the next sprint, due to start in the second half of March.

Thanks!