Issue with Squad Inbound Call Transfer Function
# support
s
When making inbound calls generated by my server with my squad, my call transfer function isn’t working as expected. I can hear the transfer starting, but the call disconnects immediately. However, when I test the same function with a simple assistant, the transfer works perfectly. Does anyone have an idea of what I should do?
v
message has been deleted
@Samuel It sounds like there might be an issue with how the call transfer function is being handled when multiple participants are involved. Here are a few steps you can take to troubleshoot the problem: 1. **Check the Logs**: Review the logs for any error messages that occur during the transfer process. This can provide clues as to why the transfer is failing. 2. **SIP REFER Messages**: If you're using a Vici system, ensure that it is configured to handle SIP REFER messages, as these are often used for call transfers. 3. **API Attributes**: If you're using the
forwardingPhoneNumber
attribute in your API call, try omitting it or setting it to null or an empty string to see if that resolves the issue. 4. **Test with Different Configurations**: Since the transfer works with a simple assistant, try to replicate the successful scenario step by step with your server-generated calls to identify at which point it fails. 5. **Isolate the Issue**: Try to isolate whether the problem occurs when a specific person is involved in the call or when a certain number of participants are reached. 6. **Review Call Flow**: Ensure that the call flow for transfers is set up correctly and that there are no conditional steps that might be affecting the transfer when multiple people are on the call. If you've gone through these steps and the issue persists, please provide more details or error messages you're encountering so I can assist you further. If you have any logs or error messages that you think might be relevant, please share them.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
s
@Shubham Bajaj
l
Hi bro I can help you out with this
s
Hey @Samuel can you describe in detail about your issue and share the call id?
s
In this example (call ID: 4fe66f3f-a49e-4a47-9d52-3544106d8d10), I have an inbound squad call set up with an assistant handling call transfers. During this call, the assistant successfully initiates a transfer to a human agent, but as soon as the transfer occurs, the call disconnects immediately. Interestingly, the logs show a success status for the transfer. When I test the function with a simpler setup, the transfer works perfectly. Any ideas on what might be causing this issue?
Another example (call ID: 3072ca37-3c37-4732-b0ba-a66a80475cae), I’ve set up an inbound squad call where each assistant has the property "forwardingPhoneNumber": "+336XXXXXXXX" to enable transfers to a human at any point. During testing, the transfer initiates correctly, but once again, the call disconnects immediately after the transfer. This suggests that the transferCall function may not be working as expected for inbound calls.
@Lufem @Shubham Bajaj Any proposition ?
s
@Samuel
logs
🔵 13:41:03:491 CallId
3072ca37-3c37-4732-b0ba-a66a80475cae
Websocket Closed. Code: 1000 Reason:
s
I'm using telnyx
what can I do ?
s
Hey @Samuel can you join discord OH we will resolve over the live vapi support, currently I am away from keyboard.
s
Okay, When it is ?
s
In 1 hour and 10 minutes.
logs
🔵 13:41:03:509 Couldn't Send 640 bytes to SBC. WebSocket readyState: 3 🔵 13:41:03:559 Couldn't Send 640 bytes to SBC. WebSocket readyState: 3 🔵 13:41:03:491 CallId
3072ca37-3c37-4732-b0ba-a66a80475cae
Websocket Closed. Code: 1000 Reason
Check with Telnyx team what is required to enable the call forwarding.
2 Views