Author here: The first priority of the project is to offer a solid generic audio-only calling experience to our users. This includes all functionality that people would expect from a softphone. At the same time, we want to build something that is generic and useful to any SIP-over-wss provider in the short term. The build mechanism and module-system should accomodate this. It is still under construction (<a href="https://github.com/vialer/vialer-js/tree/feature/restructure-module-loading" rel="nofollow">https://github.com/vialer/vialer-js/tree/feature/restructure...</a>), but most of the hardcoded dependencies are already dealt with.<p>Besides the current SIP Call implementation, we are preparing the codebase for additional signalling implementations as well. The centralized SIP Call implementation is great to use with all the functionalities a PBX offers (queues, on-hold, transfers, being available to any device), but browser-to-browser p2p also has its strong points. Privacy-aware chat, video and file transfer seem easier to implement and maintain with nothing more than JavaScript and another browser as a backend. The signalling part will be a bit of a design challenge. Ideally, this would be p2p and encrypted too, so people don't need to rely on one server/provider to find their contacts and setup connections with.