Hi! I have an issue with inbound BYO SIP Trunking. My carrier (Inbtel/PBXHosting, Sippy Softswitch) sends INVITEs from IP 207.182.145.2 to sip:526627760699@sip.vapi.ai:5060 but Vapi always responds 401 Unauthorized (Digest challenge). The carrier operates in IP-auth mode only and cannot respond to Digest challenges. What I already configured: BYO SIP Trunk credential with IP 207.182.145.2, inboundEnabled=true (ID: 8516b872-087a-48ee-a1b0-c75c91413fe0) SIP URI phone number sip:526627760699@sip.vapi.ai (ID: 57ac14e5-e307-4ef4-b441-f9383a5a2794) The problem: Vapi still sends 401 Unauthorized on every inbound INVITE. I have a PCAP proving the traffic reaches Vapi correctly. org ID: c72786ec-d64f-4f80-a79a-c47f504a73c2 Can you help enable IP-auth (trusted peer, no Digest) for inbound INVITEs from 207.182.145.2 for this org?

Hi! I’d be happy to help troubleshoot this. It sounds like Vapi may not be recognizing your trunk as a trusted IP, so it’s falling back to Digest auth. I have experience with BYO SIP trunk setups and SIP auth issues like this—feel free to share the PCAP or any additional logs, and I can help pinpoint what’s blocking the IP-auth flow.

@Saul please don't open/click on any links by Marian. They are not from Vapi and are just trying to scam you and others. Please be careful. Anyone leading you to another server, ticket link, a wallet is nothing but a dishonest scammer.

Thanks — here are the concrete details. - Carrier: Inbtel/PBXHosting (Sippy Softswitch). They are IP-auth only and cannot respond to SIP Digest challenges. - Source IP of INVITEs: 207.182.145.2 (reproducible; PCAP confirms INVITEs reach Vapi) - Destination: sip:526627760699@sip.vapi.ai:5060 Vapi behavior: always responds 401 Unauthorized (Digest challenge) to every inbound INVITE, so the call never progresses. What’s configured on our side: - Org: c72786ec-d64f-4f80-a79a-c47f504a73c2 - BYO SIP trunk credential: 8516b872-087a-48ee-a1b0-c75c91413fe0 - gateways: 207.182.145.2:5060/32, inboundEnabled=true - SIP URI phone number: sip:526627760699@sip.vapi.ai (phoneNumberId: 57ac14e5-e307-4ef4-b441-f9383a5a2794) It seems Vapi is not treating 207.182.145.2 as a trusted inbound peer for this org/SIP URI and is falling back to Digest auth. Can you please enable IP-auth/trusted peer (no Digest challenge) for inbound INVITEs from 207.182.145.2 for this org, or tell us how to bind the SIP URI/phone number to the BYO SIP trunk credential so that IP-auth is used?