Haiyang
04/02/2025, 7:10 AMHaiyang
04/02/2025, 7:10 AMVapi Support Bot
04/02/2025, 7:11 AMjson
{
"type": "transferCall",
"function": {
"name": ""
},
"destinations": [
{
"type": "number",
"number": "insert-number-here",
"extension": "insert-ext",
"numberE164CheckEnabled": false
}
]
}
According to the [documentation](https://docs.vapi.ai/phone-calling/dynamic-call-transfers), this structure allows you to specify the phone number and extension separately, which should help avoid the duplicate value error you're encountering.
I see from your tool_calls log that the system tried using a comma-separated format (+442035826399,6017
), and you mentioned trying the @
symbol format as well. These formats don't appear to be working correctly.
For SIP connections, some users have tried various SIP URI formats like:
- sip:username:password@asterisk-ip;extension=10001
- sip:username@asterisk-ip;extension=10001
- sip:username:password@asterisk-ip:5060;extension=10001
- sip:username@asterisk-ip:5060;extension=10001
However, it's worth noting that [VAPI does not allow PSTN to SIP transfers](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333747605628391434), which might be relevant to your case.
Is there anything else about call transfers or other aspects of VAPI that I can help with?
Sources:Vapi Support Bot
04/02/2025, 7:11 AMHaiyang
04/02/2025, 7:21 AMfunction
field as the parameter, I tried to put separate field as well but it just break the ai. I tried to leave it empty like "function": {
"name": ""
}, also doesn't work, that's when it would generate the comma separate format in the log.Aditya
04/02/2025, 1:18 PMAditya
04/02/2025, 1:25 PMHaiyang
04/02/2025, 5:16 PMdestinations
field to be the same format like you mentioned, but it is what I put in the parameter for the function
field is what confuse me, this call id I provided is the one where I tried with leaving the parameter field empty and only rely on the destinations
, and it didn't workHaiyang
04/03/2025, 4:37 AMAditya
04/07/2025, 8:14 PM