As per this link, it looks like warm transfers will only work if you use Twilio as the SIP Trunking Provider https://docs.vapi.ai/calls/assistant-based-warm-transfer#limitations Is warm-transfers using BYOT on the roadmap to becoming supported ?

Currently, warm transfers are only fully supported with Twilio as the SIP trunking provider. For BYOT, warm transfer features like voicing a summary to the recipient are not natively supported—messages may be stored in SIP headers, requiring custom telephony integration to play them out loud. There is no public information about BYOT warm transfer support being on the roadmap. For the latest updates, it's best to monitor the [Vapi changelog](https://docs.vapi.ai/changelog) or contact Vapi support directly. Sources: - [Vapi Call Forwarding Documentation](https://docs.vapi.ai/call-forwarding) - [Vapi Changelog](https://docs.vapi.ai/changelog) - [Discord Community Discussion](https://discord.com/channels/1211482211119796234/1366650099035541544)

Can someone from @Vapi please let me know if warm-transfers using BYOT is on the roadmap. If it is, is there an ETA I work in countries where there is no number portability - so I must use BYOT

Hello, Thanks for providing these details, I have passed the message to our team and we will update you soon with an answer.