More mumbling about this http://gondwanaland.com/mlog/2013/07/18/exit-skype-loyalty/
It should be separable into parts (like UNIX userland tools), and each part should be reasonably small, self-contained and open source. Operable from a command line. Developers can put parts together to build featureful applications. They can add GUI's on top.
Under my vision, VOIP is a very basic functionality that should be part of every OS. Or at least every decent OS (UNIX-derived).
Thanks for the link to pjsip. I agree philosophically. What do you think of https://en.wikipedia.org/wiki/Telepathy_%28software%29 ?
I'm curious, because you agree philosophically, what if I said my chosen VOIP solution didn't need any IETF-approved method to traverse NAT, didn't need DNSSEC (e.g. we could use NaCl to secure DNS packets, or run our own local DNS roots and caches), and didn't need to use third parties to centrally manage SIP addresses (i.e. we could avoid the centralization of VOIP through SIP or ENUM)?
Are you still in agreement, philosophically?
A better question is why is there no obvious open source Skype clone? NAT traversal via supernode (with or without traffic forwarding) is well understood, we have several decent free encryption options to choose from and Skype open sourced their excellent audio codecs.
The problem with Microsoft running Skype is they are making Skype users connect to Microsoft hosted supernodes instead of user hosted supernodes. In terms of strengthening the reliability of the service, this might make sense. But in terms of privacy it is troubling. Microsoft is a very poor steward of user privacy and has a terrible record of adequately securing their products.