I’d love to continue using VoIP.ms, but if the platform doesn’t integrate with AI or support WebSocket (the popular technology stack for voice AI), the road ahead for voip.ms will be challenging.
VoIP.ms sets itself apart in a crowded market with robust PBX-like features (even if it doesn’t position itself as a full PBX, just a SIP trunk). However, as voice AI tools advance, a platform lacking native WebSocket support will face significant hurdles.
Ultimately, with AI, many traditional calling features become unnecessary. For example, I developed a voice AI application whose selling point is “No more voicemail, no more call directories” — two major PBX features that AI can render obsolete.
Are you also including the ability to create voice messages and IVR using only synthetic voices based on a text instead of always having to provide a fully recorded audio file?
Entirely conversational AI.
Who still needs VM or IVR when calls can be answered 24/7.
They are certainly taking too long to integrate conversational AI with, for example, the Eleven Labs API.
I have made a Twilio and ElevenLabs voice ai application. I made it modular and vendor neutral (as much as possible). It’s really powerful. This is the future. ElevenLabs can now import none Twilio number. But for VoIP.ms, if at the end, it becomes really just another sip trunk, I really don’t think that’s a bright future.
ElevenLabs is very good indeed!
Nice thread and good idea to have that integrated, somehow.
I would even want that at home when people call too late in the day. AI could answer, take the message, or decide it is worth waking me up and ring the phones. 
this is a service i am developing now. one major challenge is for regular cell phone, at least on ios, there is no conditional forward. i am developing needed features first anyway.