https://vapi.ai/ logo
Join Discord
Powered by
Zadarma outbound call issue
# support
e
Hello! I've done everything you told in your zadarma tutorial (in your documentation). Inbound calls work perfectly well, but outbound has some issues. I can call the ukrainian number, which I attached to the vapi.ai (inbound), but when i make an outgoing call I see french number +33 1 89 38 07 10. Also, in Zadarma in call logs, I see only incoming calls, outgoing calls are empty. But in vapi I see both calls. I wonder, maybe there is something on your side? Because I've done totally as you told in your documentation, multiple times.
v
Hi there! 👋 I understand you're having two issues with your Zadarma integration: 1. Outbound calls showing a French number instead of your Ukrainian number 2. Outgoing call logs not appearing in Zadarma Let me help you troubleshoot both issues: ### French Number Appearing on Outbound Calls This could be happening due to a few reasons: 1. **SIP Trunk Configuration**: Make sure your SIP URI is correctly formatted in the Vapi settings. Check that your 
forwardingPhoneNumbers
array includes your Ukrainian number correctly:
Copy code
json
"forwardingPhoneNumbers": [
  {
    "sipUri": "sip:YourUkrainianPhoneNumber@sip.zadarma.com"
  }
]
2. **Phone Number Registration**: Ensure your Ukrainian number is properly registered with Vapi.ai: - Navigate to the "Phone Numbers" section in the Vapi dashboard - Verify that your Ukrainian number is imported and active - Make sure it's correctly set as the outbound caller ID 3. **Outbound Call API**: When making outbound calls, verify you're specifying the correct 
phoneNumberId
in your API calls. ### Missing Outgoing Call Logs in Zadarma Several factors could cause this: 1. **Configuration Issues**: Check if logging for calls directed to fallback numbers is enabled in your call log settings. 2. **Webhook Call Failures**: The webhook responsible for logging calls might not be triggering properly. Verify that your webhook URL in the Vapi settings points correctly to the intended server. 3. **SIP Gateway Connectivity**: Ensure that SIP URIs are properly configured and that your network allows SIP traffic. 4. **Technical Glitches**: Sometimes there can be temporary issues or delays in call logs being updated. The French number (+33 1 89 38 07 10) appearing suggests there might be a default routing configuration in place. I'd recommend double-checking all your SIP trunk settings and ensuring your Ukrainian number is properly configured as the outbound caller ID.
n
This means several things - mostly is that your outbound calling from VAPI isn't going to Zadarma, but performed internally most probably. Also, the french number that appears means that the outbound call is routed via a carrier that doesn't allow Ukrainian phone numbers to be presented.
s
Thanks @Nir S (CEO/Founder @Cloudonix) for helping @eifersucht
@eifersucht For fair consideration, I would like to inquire if this issue has been resolved for you. If not, could you please share the call ID?
t
Hi, just to add to this, I'm having a similar issue, but it could be a fault from Zadarma's side? I purchased a number from Zadarma and connected it to Vapi as directed by the docs through SIP and inbound calling works perfectly. However, when the agent transfers the call to a another number, it just hangs up. I checked the logs in Vapi and it shows the call was transferred successfully, but could not find any logs in Zadarma. Any idea what configuration I would need to make on Zadarma? (And yes, I also followed the Vapi docs regarding SIP REFER as instructed)
k
Hey Tally, can you please create a new support ticket for your issue?
n
@Tally @Shubham Bajaj The issue Tally is describing is mostly related to how Zadarma works in highly regulated countries, eg. Turky, France, Italy, Belgium and most of Eastern Europe. In these countries, in order to use local caller ID presentation, customers are required to have their PBX equipment installed in-country, or, have their PBX equipment white listed and registered under their name, following a KYC procedure. As VAPI IP numbers are shared across multiple customers, the process is a bit more complicated on the local carrier - and thus, you should consult with your local carrier on what would be the proper solution.
s
Really thank you @Nir S (CEO/Founder @Cloudonix) 🙏🏻 for explaining this to me.
PreviousNext
Powered by