@Supermagnum none of the use cases you have presented are not a fit for Jitsi , I don’t think continuing to bring it up is helping the case. Just because something supports webrtc does not mean it can talk to other webrtc devices, it is a reference and framework for mainly browser based real-time media and standardizing on offers (basically sdp) between clients , but does not include any signaling specifications . There are a number of browser based sip clients , specially sip.js and jssip which can use browser based webrtc for the media bits . There are then a number of sip/webrtc based servers designed for this type of communication ( jitsi not being one of them) like asterisk, freeswitch, Kamilio and cloud services like twilio. These all support nats and work without vpns. Jitsi does have a sip connector , but it tries to try translate sip audio into xmpp, basically a foreign signaling protocol , again very much not the right tool.