vapi does not do sip refer properly
# support
t
call id: 03f1e240-3472-449f-8722-fc10aa906e6d why i can not transfer my calls to the telnyx sip trunk. My account's sip refer is enabled
v
I understand you're experiencing issues with transferring calls to the Telnyx SIP trunk using SIP REFER, even though it's enabled on your account. At this time, I don't have specific information available about SIP REFER handling or call transfer functionality with Vapi and Telnyx. If you have any additional details or questions, feel free to share them.
I understand you're experiencing issues with transferring calls to the Telnyx SIP trunk using SIP REFER, even though it's enabled on your account. At this time, I don't have specific information available about SIP REFER handling or call transfer functionality with Vapi and Telnyx. If you have any additional details or questions, feel free to share them.
t
why you do not help
u
i am having a similar issue i had to switch back to Twilio
when i figure out why and how to fix it i'd let you know as i need it back on also
t
bro for bulgarian numbers twillio is 180 usd per month for the phone number...
u
Oh That alot You might want to look into using sip Trunking with Telnyx or Vonage
v
The call transfer was successful. As evidenced in the screenshot and the PCAP file, you must verify with your telephony provider why the call ended after accepting the refer request. On the VAPI side, once we process the refer request, we terminate the call from our end (essentially, we exit the call and transfer it to the telephony provider). However, in your case, the telephony provider also terminated the call, resulting in the call drop experience for you. Therefore, you must now contact your telephony provider to investigate the issue. https://cdn.discordapp.com/attachments/1370592524053516298/1370862145109098637/image.png?ex=68210a5c&is=681fb8dc&hm=7b16834cde5a5b8854e63fa5b0fe96f5763d1a8eb928d5209ef2b7ff2cb3494b& https://cdn.discordapp.com/attachments/1370592524053516298/1370862145427869796/03f1e240-3472-449f-8722-fc10aa906e6d-1746840551556-ca40b995-7680-4bd9-a8c4-3e9d79cdb600-sip.pcap?ex=68210a5c&is=681fb8dc&hm=99c3d613a5f729eedeba64cafbf725deaf7bfe7666d9d35f0b2a733c32b5722a&
n
@Toketo1 @20 Most carriers don't support
SIP REFER
properly, in most cases, due to a security and billing concern. In many cases,
SIP REFER
can be used to perform toll fraud, and thus, most carriers in the world may return a
SIP 202 Accepted
response, while in fact, will cause the call to be dropped. Another possibility is that the information in the
SIP REFER
provided by VAPI may not be compatible with theirs. For example, the
SIP REFER
message VAPI generates include a phone number only, while most carriers will require a fully qualified
SIP URI
to successfully process a
REFER
. In other words, there are multiple "variables" to consider - and in most cases, the carriers will not "accommodate" you request for
SIP REFER
support, as it means - changing their switching configurations. If you would like, I can show a slightly more agile way of performing transfers (and more) using Cloudonix - that integrates easily with VAPI, and will work in an identical fashion on any carrier.
t
@Nir Simionovich (CEO@Cloudonix) ok show me
v
If you need some more support from us, let us know
3 Views