Sip Credential is from 2600hz.com SIP user name: 7998 SIP password: ** Realm: hvjmg6s.se.vsrns.com

Here goes error log from 2600hz.com https://cdn.discordapp.com/attachments/1372368432976105503/1372754645683933345/error.log.txt?ex=6827ece4&is=68269b64&hm=92f89ed68241ac8b27b2ea579b1fe132ceb2828f5d069933e0f566a4a0358247&

2600Hz support team is saying: 📌 Vapi is sending wrong INVITE realm to base the authorization on. 📌 They should be sending the realm we provided which is hvjmg6s.se.vsrns.com. They are sending the sip.vapi.ai. The INVITE authentication is being rejected by Vapi. We programmed our Realm in the PROVIDER KEYS but VAPI is not sending that realm to us to authenticate to. VAPI is sending sip.vapi.ai where the realm/domain we have programmed is hvjmg6s.se.vsrns.com https://cdn.discordapp.com/attachments/1372368432976105503/1372754754530316398/messsage_from_2600hz.txt?ex=6827ecfe&is=68269b7e&hm=82c709ec630b054a4202ca33d4ff564695a69c535518db94a0cf4cfb1070c9dc&

Could you check & fix this on your side ? 🙏 Best regards @Shubham Bajaj

What is your team 's time zone ?

I will go through each query one by one.

When 2600hz.com sends a SIP INVITE to Vapi, the initial authentication challenge from Vapi's server contains a WWW-Authenticate header with realm="sip.vapi.ai" instead of using the realm provided in the SIP trunk configuration (hvjmg6s.se.vsrns.com). This is causing authentication failures because 2600hz.com is expecting the realm to match what was configured in their system.

@Hans The solution is to update the SIP authentication system to use the customer-provided realm for outbound calls.

there used to be a check for the realm, but it was commented out.

@Hans Can you ask your telephony if they can whitelist our SIP.VAPI.AI domain for credentials validation instead? Until I can ask my team why this feature was commented out or not working to date, and what we can make it work.