Hi Fabian,
thanks for your interest in Janus, this is the right place for such questions! We opened the group for generic discussions on Janus, so your doubts definitely fit in here.
If you're unfamiliar with what Janus is, it is a general purpose WebRTC server, meaning that, at least in concept, it is supposed to be able to do several different things. The way this is achieved is by means of a core handling the WebRTC stack (ICE, DTLS, SRTP) and a modular architecture based on plugins to provide the application logic. So the idea is that your client attaches via WebRTC to the gateway, and what happens to the media depends on what plugin you choose to attach the client to.
We developed several sample plugins for the purpose, a demo of which you can find on the official website (
http://janus.conf.meetecho.com). Among those, we also implemented a SIP plugin that is conceived to do exactly what you're looking for, that is allow a WebRTC client to start or receive SIP calls. At the moment it's a bit immature, as it's mostly a proof of concept implementation that can be used with a PBX like Asterisk, but we're already working on making it less "constrained" and as such usable with any generic SIP proxy.
That said, so far we explicitly ruled out transcoding so far, as we were mostly interested in bridging technologies and transcoding is a heavy task and can still be passed to an external component (see for instance a WebRTC-RTMP gateway where you only take care of the protocol, and leave the transcoding to FFmpeg). Nevertheless, considering the open source and modular nature of Janus, nothing prevents transcoding to be added to an existing plugin, or forking/creating a new plugin to add whatever's missing.
Hope that helped!
Lorenzo