Issue with Configuring SIP Server Address for Pliv...
# support
s
Hello VAPI Support Team, I hope you are doing well. I am encountering an issue while trying to configure the SIP server's address "sip.vapi.ai;transport=udp" as the origination SIP URI for my Plivo Inbound Trunk setup. When I attempt to create a UID, the system displays the error message: "This URI already exists." To the best of my knowledge, I haven't created any UID previously, and I am unable to locate an option to access the UID if it was automatically generated during onboarding. Plivo has informed me that the URI "sip.vapi.ai;transport=udp" is already associated with another customer and cannot be reused due to their restrictions. As a result, I am required to create a new/custom SIP server address to proceed with the setup. Could you please provide guidance on how to create or obtain a new SIP URI that complies with Plivo's requirements? Any assistance or clarification you can offer would be greatly appreciated. Thank you for your support. Looking forward to your response! https://cdn.discordapp.com/attachments/1362383583486152866/1362383583704125491/PLivo_support_email?ex=68023216&is=6800e096&hm=ba84bb2efe17f3bdd78da1939bc438b483f1375090cc7143a639cb4d40e1f7e2&
s
It seems like the error you're encountering is due to the SIP URI you're trying to use already existing in the system. The Plivo platform indicates that this URI has been used by another user, which is why you're seeing those errors. One way you could resolve this is to try using a different, unique URI. It might help to try a format like \[organization name\].sip.vapi.ai;transport=udp or similar to ensure uniqueness. Check with your team to see if there might be any other existing setups using the same URI. If you're having trouble locating any previously created UIDs or configuration details, I'd recommend reaching out to Plivo’s support to see if they can provide more detailed logs or help track any existing setups that might be causing a conflict.
s
They told me to reach out to vapi's team
s
We are currently looking into this