transfer-destination-request message is not playe...
# support
a
When using the transfer destination request to set the forwarding/transfer call, the call is transfered ok, but the message is not played to the caller the same result is using type sip or type number on the destination, i even try to add the message in a diferent way to the response, but the behavior is the same, no message played Using the static transfercall function the message is played ok when the call is transfered https://cdn.discordapp.com/attachments/1307906701717934090/1307906702875557888/image.png?ex=673c0289&is=673ab109&hm=36800cee171ffd3dcad21fe43d214ede2a2486cd3b9d49232b734e12daba79a2& https://cdn.discordapp.com/attachments/1307906701717934090/1307906703613886494/image.png?ex=673c0289&is=673ab109&hm=723345f3399f24431c7508acac43d0246da28792559fd5cf0c23381abbd8b2e1&
@User
v
@asesistel It sounds like you're experiencing an issue where the message you want to play during the call transfer isn't being played, despite the transfer itself being successful. This could be due to a few different reasons, such as the message not being correctly specified in the API request or an issue with the way the transfer destination is handling the message playback. To help you further, I would need to know how you're currently specifying the message in your transfer request. Could you provide me with the details of how you're including the message in your API call? This will help me understand what might be going wrong and how to fix it.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
Also i tried to use the warn transfer option with summary, using the static transfercall function it gives me an error when creating the function about the property transferplan should not exist
I also try to use the warn transfer option with the dynamic transfer using the transfer-destination-request, and couldn't i always got the blind transfer behavior, i followed the https://docs.vapi.ai/call-forwarding example and the https://docs.vapi.ai/api-reference/webhooks/server-message reference, as well as some tutorials, thanks in advance https://cdn.discordapp.com/attachments/1307906701717934090/1307914404104372347/image.png?ex=673c09b5&is=673ab835&hm=a32f1a9e30f34892926913f6528e045b6f8cff101ce3b7db0ddfe8745389e776&
hi @Shubham Bajaj i am going to post another weird thing happened, days ago i was able to succesfully create a byo-sip-trunk number and associated with a credential, i have two main pbx's on the cloud, so i first try to make a path request to the credential endpoint to change the ip address, i didn't work, so i created another credential with the new ip address, so then i tried to modify the byo-sip-trunk number using the patch method too with the phone number endpoint, and i received an error about the property credentialId must not be present, so i deleted the byo-sip-trunk number and tried to created again, using the new credential, now the weird thing is that its says error , couldn't create phone number, i figured out that i was able to created again using an diferent number, my real number and the one i want to create is +17869200680 (this was the number was created before and have to deleted to modify the credentialId), i used the number +17869200682 and it worked ok like the first time, and the outbound calls works ok, i can handle the number i want on my pbx the 682 and 680 it doesn't matter so much, but i would like to have the right number associated, i even create another number 688, deleted and created again ok, something happens with the 680 number, any help would be appreciated, i post the issue here instead of creating a new support post
it looks like the +17869200680 number was not succesfully deleted, even when it doesn't appear on my phone number list
s
Hey @asesistel To help track down this issue, could you share: - The call ID - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!
Also regarding your second issue, will look into it as well post resolving your first issue.
a
Hi, @Shubham Bajaj The problem is related to the assistant saying the transfer message to the caller, before making the transfer, - Unsuccessful case This case is using the transfer destination request to assign the number for the forwarding The request is working and the number is forwarded to the specified number, but the message to be played before the call is transfered, is not been played, as you can see on the transcription of each call Callid:03eb090f-63cf-4ec6-981c-7950dc40a838 Tool: id=a8e74423-b239-4aa2-aada-5e7b6b70fa58 type=transferCall name=transferCallAdvanced expected, the message is played, the message is not being played at this the moment the tool is transfering the call to a sipuri, the transfer is ok, i even modify the response to use a number type destination and the behavior is the same, the call is transfered ok, but the message is not played https://cdn.discordapp.com/attachments/1307906701717934090/1308506346848522240/Screenshot_from_2024-11-19_14-48-42.png?ex=673e30ff&is=673cdf7f&hm=4dcde9669c373ce26cf7d52438cf72ef5ed3a2192328e9230476700af3fdb4ac& https://cdn.discordapp.com/attachments/1307906701717934090/1308506347070951586/Screenshot_from_2024-11-19_14-51-19.png?ex=673e3100&is=673cdf80&hm=a40e0c15a518619b4aed264d51e42610c8d636da937d85f830858107e1b365f0&
- Succesful Case This case is using an static transfer type function defined Callid: df44c549-e643-485b-aab3-f47eafcffffb Tool: id=10748f1a-b901-40da-bb5f-a04c92e39f82 type=transferCall name=transferCall Regarding the asking for a human option, the call is transfered to departmen a,b or c expected, the message is played OK, the message is played
The blind-transfer and warm-transfer are working the same for me
s
@asesistel can you try this mode
warm-transfer-wait-for-operator-to-speak-first-and-then-say-message
, I have check why
warm-transfer-say-message
mode is not working as expected.
Your Current Response
šŸ”µ 18:47:43:398 Server Message Successful. (https://api.asesistel.com:1880/v1). Response: { "messageResponse": { "message": { "type": "request-start", "content": "The call is being transfered. Please stay on the line." }, "destination": { "type": "sip", "message": "You will be now transferred to a human sip uri, please wait", "sipUri": "sip:1002@167.114.35.240", "transferPlan": {"mode": "warm-transfer-say-message"}, "description": "When the human is requested." } } }
Expected Response
šŸ”µ 18:47:43:398 Server Message Successful. (https://api.asesistel.com:1880/v1). Response: { "messageResponse": { "destination": { "type": "sip", "message": "You will be now transferred to a human sip uri, please wait", "sipUri": "sip:1002@167.114.35.240", "transferPlan": {"mode": "warm-transfer-say-message"}, "description": "When the human is requested." } } }
a
@Shubham Bajaj thanks, i am going to try the mode you mention, and change the response of the transfer-destination-request endpoint, at the begining it was like you mention, it is the specified response on the documentation, but i was trying sevral ways to make it works, i am going to work on that along the day and let you know, thanks again for your help, by the way is there a way to transfer credits to another vapi user? I am working on a couple of customers demo and i am creating one vapi account for each customer and creating a custom dashboard for each one, i would like to have the option of recharging my main account and transfer the credit to our cutomers account
Hi, i changed the response to { "messageResponse": { "destination": { "type": "sip", "message": "You will be now transferred to a human sip uri, please wait", "sipUri": "sip:1002@167.114.35.240", "transferPlan": { "mode": "warm-transfer-wait-for-operator-to-speak-first-and-then-say-message" }, "description": "When the human is requested." } } } and the message is not played neither, the call is forwarded ok, i also noticed thet when the transfered destination is a number it is showed ok on the transcript of the call detailr ecord, but when it is a sipuri its only says forwarded --> and the destination sipuri is not been showed callid: a80929b5-c9a6-4c35-83b7-f1d0d1b565d2 Tool: id=a8e74423-b239-4aa2-aada-5e7b6b70fa58 type=transferCall name=transferCallAdvanced https://cdn.discordapp.com/attachments/1307906701717934090/1309535931040141412/image.png?ex=6741efdf&is=67409e5f&hm=718a469e4da0ee0b524524e81398f45a4c44ed043b08c53adac12df898a2374c& https://cdn.discordapp.com/attachments/1307906701717934090/1309535931300057188/image.png?ex=6741efe0&is=67409e60&hm=8b8728fdc5dd3d85976b6362ad2426844c3253bf37e42a97c634a1f5dbdc9ad4&
s
@asesistel I am checking with team, what's the cause of message not being voiced out.
logs
šŸ”µ 14:58:21:221 Server Message Requested...(status-update , https://api.asesistel.com:1880/v1): { "type": "status-update", "status": "ended", "endedReason": "assistant-forwarded-call" } šŸ”µ 14:58:18:513 Using tool.destinations[0]: { "message": "You will be now transferred to a human sip uri, please wait", "description": "When the human is requested.", "type": "sip", "sipUri": "sip:1002@167.114.35.240", "transferPlan": { "mode": "warm-transfer-wait-for-operator-to-speak-first-and-then-say-message" } }
r
Still not working as expected. I have been trying with this but the bot does not speak out the message:
Copy code
{
  "messageResponse": {
    "destination": {
      "type": "number",
      "message": "I am forwarding your call to John right now. Please stay on the line.",
      "number": "+18001234567",
      "transferPlan": {
        "mode": "warm-transfer-say-message"
      }
    }
  }
}
Regardless of the transfer plan or any other changes the message does not get spoken, I get the default Transferring the call now reponse from the bot
k
Hey it is a bug on our end and we will work on it and get this fixed.
r
Is there currently a temporary way to make the bot respond in a dynamic way?
k
Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!