SIP 401
# support
j
Is there a flag to set when creating a
vapi
provider SIP address to disable the 401 being received when sending an INVITE? It actually still works by just passing some fake username/password on the RE-INVITE but this extra step could be avoided. Thanks!
v
@jmordica In the VAPI system, if you're looking to disable the 401 Unauthorized response when sending an INVITE, this typically involves configuring your SIP endpoint to recognize the VAPI platform as a trusted entity, thus bypassing the need for authentication. However, the specific method to disable this challenge-response mechanism can vary based on the VAPI provider's capabilities and settings. Some systems may allow you to configure 'IP Authentication' where the VAPI platform's IP is whitelisted, or they might support a specific flag or setting in the SIP trunk or domain configuration to disable authentication for certain requests. If you're looking for a specific flag within the VAPI configuration to disable the 401 Unauthorized response, I would recommend checking the provider's documentation or reaching out to their support team for detailed instructions on how to achieve this, as the implementation details are not standardized across different systems. If the VAPI provider you're working with is part of our system and you believe there should be a flag or setting available, please let me know, and I can assist you further or direct you to the appropriate support channel for more information.
You can continue this conversation by mentioning me in the message.
j
It says in the docs "There is no authentication or SIP registration required" so I'm assuming there's a way to make your Jambonz implementation not respond with a 401 when receiving an INVITE.
s
@Sahil can you please help on this.