@its.jcw The latency you see in the UI for Twilio or any other service can be influenced by various factors, including the technology used for the connection. While Mediastream might have a certain latency, using a SIP trunk could potentially offer different performance characteristics. In general, SIP trunks can be very efficient and may offer lower latency due to the nature of the protocol and the direct connection it establishes between systems. However, the actual latency can still be influenced by the network infrastructure, the distance between endpoints, the quality of the internet connection, and the processing time on both ends. To get a more accurate estimate of the latency you can expect when using a SIP trunk with Twilio or to explore how to optimize your setup for lower latency, it would be best to consult directly with Twilio's support or technical documentation. They can provide specific details and guidance based on your use case and requirements. If you need assistance with anything else or have more questions, feel free to ask!

You can continue this conversation by mentioning me in the message.

Like call_id or any logs through which I can debug?

well, regardless - i now have it implemented, so once it's activated i'll be able to actually test it out

To show, you that it is possible with Vapi.