I need to change that description, because it is too premature at the moment. The main Calls handling code is in
https://github.com/vialer/vialer-js/blob/develop/src/js/bg/m... and still relies on SIP. It is a small step to add the required abstractions for alternative signalling mechanisms though, because most of the SIP-related logic is centralized already.
There is currently a SIP Call implementation in https://github.com/vialer/vialer-js/blob/develop/src/js/bg/m...
The first approach to use the Call abstraction is in https://github.com/vialer/vialer-js/blob/develop/src/js/bg/m...
It is a proprietary API-based click-to-dial calling method(which still need to be moved to its own repo) that doesn't use SIP or WebRTC, but uses the same call flow nevertheless.
At the moment, most of the focus is on stabilizing the SIP-based softphone. We're about to complete a first working opensource build without proprietary modules this week.
The Calls-related code will be dealt with when there is an alternative signalling mechanism available. It would be interesting to investigate existing networking solutions like Matrix, but also to experiment a bit with p2p overlay networks ourselves. I did some prior R&D on the subject (https://wearespindle.com/articles/end-to-end-encryption-betw...) to tackle issues like ECDH encryption with WebCrypto, but there are still a lot of uncertainties and unhandled topics that need to be addressed. Work in progress :-)