SIP Trunking for Inbound calls not working
# support
p
I am reaching out for assistance regarding an issue I’m facing with setting up the VAPI inbound SIP URI. Despite my efforts to place inbound calls using various tools such as LinePhone and MicroSIP, I am unfortunately unable to establish the connection successfully. I would appreciate your guidance and support in resolving this issue at your earliest convenience.
v
message has been deleted
@ParwaanVirk (Kyzo AI) I'm here to help you with setting up your inbound SIP URI. To ensure that your SIP calls are correctly routed, you'll need to configure the
sipUri
attribute within the
forwardingPhoneNumbers
array to specify the destination SIP address. Could you please confirm if you have already set the
sipUri
with the correct SIP address in your configuration? If not, I can guide you through the process. If you have already done so, please provide me with any error messages or issues you're encountering so I can assist you further.
You can continue this conversation by mentioning me in the message.
p
@Vapi I have not done so. Please guide me with further steps.
v
@ParwaanVirk (Kyzo AI) Certainly! To set up your inbound SIP URI, you'll need to follow these steps: 1. **Access Your VAPI Account**: Log in to your VAPI account where you manage your voice applications. 2. **Locate SIP Configuration**: Navigate to the section where you can configure SIP URIs, often found under settings for voice applications or numbers. 3. **Set SIP URI**: In the configuration, look for the
forwardingPhoneNumbers
array or a similar setting where you can specify forwarding rules. Enter your desired SIP URI in the
sipUri
field. The SIP URI typically looks like
sip:username@sipprovider.com
. 4. **Save Configuration**: After entering the SIP URI, make sure to save your configuration changes. 5. **Test the Connection**: Use your SIP tools like Linphone or MicroSIP to place a test call to the SIP URI you've just configured to ensure that it's working correctly. If you encounter any issues during this process or receive error messages, please let me know the details so I can provide you with further assistance. If you need help with specific steps in the VAPI interface, I can provide more detailed instructions.
p
@Vapi where can i find the forwardingPhoneNumbers setting in the vapi portal ??
v
@ParwaanVirk (Kyzo AI) The
forwardingPhoneNumbers
setting is typically found within the configuration of your voice application or the number settings in the VAPI portal. Here's a general guide on where to look: 1. **Log in to the VAPI Portal**: Use your credentials to access your VAPI account. 2. **Navigate to Voice Applications**: Once logged in, look for a section labeled 'Voice Applications', 'Numbers', or something similar. 3. **Select Your Application or Number**: Click on the application or number you wish to configure. 4. **Find Call Handling Settings**: Within the application or number settings, look for call handling or forwarding settings. This is where you might find the
forwardingPhoneNumbers
array. 5. **Edit SIP URI**: If you locate the setting, you can add or edit the
sipUri
attribute to set your inbound SIP URI. If you're unable to find the
forwardingPhoneNumbers
setting or if the VAPI portal has a different layout, it might be best to consult the official documentation or reach out to VAPI support for specific guidance tailored to their interface. If you need further assistance, please let me know, and I'll do my best to help you.
p
Hi @Vapi, I basically have done all the configuration steps correctly as per the following guide: https://vapi.notion.site/SIP-Inbound-Guide-104008c8393f80e18ba9f00fef7549be Now, when I try to place a sip call using linphone, as provided in the documenation, the call is being cut with status: "forbidden" Please help me resolve this
v
@ParwaanVirk (Kyzo AI) Receiving a "forbidden" status on your SIP call typically indicates an issue with authentication or that the call is being rejected due to a configuration problem. Here are a few steps you can take to troubleshoot and resolve this issue: 1. **Check Credentials**: Ensure that the username and password you are using in Linphone are correct. The credentials must match those expected by the VAPI service. 2. **Verify SIP URI**: Confirm that the SIP URI you are dialing is correctly formatted and matches the one you have configured in your VAPI portal. 3. **Review Access Control Lists**: If VAPI uses access control lists (ACLs), make sure that the IP address from which you are making the call is allowed. 4. **Inspect Configuration**: Double-check your VAPI portal configuration to ensure that there are no restrictions that could be causing the "forbidden" status. 5. **Check for Service Restrictions**: Some service providers may have restrictions that could lead to a "forbidden" status. Verify with your SIP service provider if there are any such restrictions. 6. **Consult Logs**: If possible, review the logs from VAPI and Linphone to get more details on why the call is being rejected. 7. **Reach Out to Support**: If you've gone through all the above steps and the issue persists, it may be best to contact VAPI support directly for assistance. They can provide more detailed troubleshooting based on their system's specifics. If you need further assistance or if there's anything else I can do to help, please let me know.
p
From where can i get the ACL list ?
@Vapi from where can i get the ACL List
v
@ParwaanVirk (Kyzo AI) Access Control Lists (ACLs) for SIP services are typically managed within the settings of your VAPI account. To find and review your ACL settings, you should: 1. **Log in to the VAPI Portal**: Use your credentials to access your account. 2. **Navigate to Security Settings**: Look for sections labeled 'Security', 'Network Settings', 'IP Whitelist', 'Access Control', or something similar. 3. **Review ACL Settings**: Within this section, you should find the ACL or IP Whitelist settings where you can view, add, or remove IP addresses. If you're unable to locate the ACL settings or if the VAPI portal has a different layout, please refer to the official documentation or reach out to VAPI support for specific guidance. They can provide you with the exact location and process for accessing and modifying your ACL list. If you need further assistance or if there's anything else I can do to help, please let me know.
s
Hey @ParwaanVirk (Kyzo AI) To help track down this issue, could you share: - The call ID This would really help me figure out what went wrong!
p
Hi @Shubham Bajaj, There's no call ID as such. The issue is as follows: I want to do inbound calling to vapi. But my provider is not twilio or vonage. It's my own provider. I have setup SIP trunking to do so, and have followed the following guide to setup inbound calling: https://vapi.notion.site/SIP-Inbound-Guide-104008c8393f80e18ba9f00fef7549be But it is not working. When I place on the number, the call doesn't get through to vapi. My question is: Do i need to whielist an IP from where the call is originating, to get to vapi, and if so, how do I achieve this. or is there some step that I am missing, due to which inbound SIP calling is not working.
s
@ParwaanVirk (Kyzo AI) You are most likely missing some steps. Does your provider require an FQDN? Your provider can share the PCAP file which contains the debugging information sent by Vapi. Can you try asking your telephone provider?
p
Hi @Shubham Bajaj, I'm arranging all of this, and will share once I have these.
Hi @Shubham Bajaj, I just got word from my provider. 1) They don't require FQDN
@Shubham Bajaj any update regarding this ??
s
@ParwaanVirk (Kyzo AI) I have looked into your PCAP file and confirmed that the call was terminated by Vapi. To determine the exact reason for termination, I'll need to check our internal PCAP file since the logs don't contain much information. Could you please share the associated call ID? I apologize for the back and forth, but while I thought the PCAP would help, it unfortunately didn't provide enough details in this case.
p
Hi @Shubham Bajaj, @User No Call ID was created. I couldn't find the associated call in the call logs as well. Our entire pipeline is stuck because of this error, and it would be amazing if someone from your team could get on a quick call with us on priority to help resolve it. We have a really high spend on vapi(Around 1500 USD/Week), need to get the system up and running ASAP
s
@ParwaanVirk (Kyzo AI) check your DM, will resolve over the call.
3 Views