call dropping when my client transfers to assistan...
# support
l
I know this may not be a Vapi issue - but when my client forwards his cell phone number to the Vapi assistant number it rings 1x the. Immediately hangs up. When I test and forward from my cell phone - ot works perfectly fine. When I check twilio call logs - the call connects and works perfectly. It was working smoothly for my client up until A few days ago. Any ideas?
here's a call ID for sample: 1b50be16-6580-448a-9dfe-a83a04d888b7
@Vapi
v
message has been deleted
@l8dyaj It sounds like there might be an issue specific to your client's phone or carrier settings if the forwarding works fine from your cell phone. Here are a few steps you can take to troubleshoot the problem: 1. **Check Carrier Settings**: Ensure that your client's phone carrier hasn't made any changes to call forwarding settings or has any outages that might be affecting the service. 2. **Test with Different Devices**: Have your client try forwarding calls from a different phone to see if the issue persists. This can help isolate whether the problem is with the phone itself or the carrier. 3. **Review VAPI Configuration**: Double-check the VAPI configuration for your client's number to ensure that nothing has changed on the VAPI side that could be causing the issue. 4. **Inspect SIP REFER Messages**: If you're using a system like Vici that handles SIP REFER messages for call transfers, make sure that it's configured correctly and that there are no errors in the logs. 5. **API ForwardingPhoneNumber Attribute**: If you're using the forwardingPhoneNumber attribute in the API, try setting it to null or an empty string as suggested in the context, to see if that resolves the issue. 6. **Contact Carrier Support**: If none of the above steps work, it might be necessary to contact your client's phone carrier for support, as the issue could be on their end. If you've gone through these steps and the issue still isn't resolved, please ask support for more info on this.
You can continue this conversation by mentioning me in the message.
l
Oh my client has ATT if that matters
v
@l8dyaj It seems like there might be an issue specific to your client's phone service or settings. Since the forwarding works fine from your phone and the Twilio call logs show that the call connects properly, the problem might not be with VAPI or Twilio. Here are a few steps you can take to troubleshoot the issue: 1. **Check for any recent changes**: Ask your client if they have made any recent changes to their phone settings or service plan that might affect call forwarding. 2. **Test with another device**: Have your client try forwarding calls from a different phone to see if the issue persists. This can help isolate whether the problem is with the phone itself. 3. **Contact the carrier**: There might be an issue with the client's carrier or a specific setting that needs to be adjusted on their account. It would be a good idea for your client to reach out to their carrier for support. 4. **Review any updates or changes on VAPI**: Check if there have been any updates or changes to the VAPI settings or configurations that might affect how incoming calls are handled. 5. **Check for any patterns**: Look for any patterns in the call logs around the time the issue started happening. This might give clues as to what could be causing the problem. If none of these steps resolve the issue, please ask support for more info on this. They might have additional insights or be able to provide more direct assistance.
l
Strangely the call works with some devices call the number but not on others.
@User
@Vapi any help ideas? We have tried these. Will SIP need to be done in twilio?
v
@l8dyaj If the call forwarding is working with some devices but not others, and you've already tried the basic troubleshooting steps, it's possible that the issue could be related to how different carriers handle SIP (Session Initiation Protocol) messages, which are used for initiating, maintaining, and terminating real-time sessions that include voice, video, and messaging applications. Here are a few additional steps you can take: 1. **SIP REFER Handling**: Ensure that your system (like Vici) can handle SIP REFER messages properly. If you're using Twilio, check if there are any specific settings or configurations that need to be adjusted for SIP REFER. 2. **Carrier-Specific Issues**: Since the issue is occurring with AT&T for your client, it might be a carrier-specific issue. It could be beneficial to reach out to AT&T support to see if they have any known issues or settings that need to be configured differently for call forwarding to work correctly. 3. **Twilio Support**: If you suspect that the issue might be with how Twilio is handling the calls, reaching out to Twilio support could provide more insight. They might be able to offer specific advice or check if there are any issues on their end. 4. **Detailed Logs Analysis**: If you haven't already, conduct a detailed analysis of the call logs around the time the issue occurs. Look for any error messages or unusual patterns that could indicate what's going wrong. 5. **Network and Device Compatibility**: There might be compatibility issues between the network and the devices trying to forward calls. This could be due to device settings, network settings, or even firmware issues. If you've exhausted these options and the issue persists, it may be necessary to involve technical support from both Twilio and AT&T to further diagnose the problem. Please ask support for more info on this if you need additional assistance.
s
@l8dyaj the telephony provider is blocking the call from/to the number. Is the number purchased from Vapi?
l
@Shubham Bajaj it’s a twilio number. I have done SHAKEN STIR, Cname and went out to each of the 3 phone providers and registered the numbers. I know that can take some days. Is there a way you can tell that the call was blocked by the telephony provider? And can you tell which one it was? I’d love to be able to know how to do this
s
check SHAKEN STIR status this will help you know if calls was blocked by telephony provider.
l
@Shubham Bajaj can i DM you a response from Twilio on this and get your take on it?
CallID of call that did not work: (got 400 error) CA762755dd99d622e7d1172cfb2e40eac4 03:09:30 PDT 2024-10-09 Completed Incoming +12145792856 +17207346029 Phone 1 sec CallID of calls that worked - but also got 400 error CA033e117ecff892796ada9d87907725a1 10:13:50 PDT 2024-10-08 Completed Incoming +17204695332 +17207346029 Phone 4 min 41 sec
vapi call id: 8b547293-23f7-472c-af61-f044a152a5b7
s
@l8dyaj please create a new support ticket for this.