<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<br class=""><div><br class=""></div><div>Thanks for the kind words about SylkServer/Sylk-webrtc.</div><div><br class=""></div><div>I suspect is has to do with the chat feature that was added. For this, the webrtc application connects to the ‘normal’ conference application. </div><div><br class=""></div><div>Is the conference application in SylkServer enabled? If it is not, you probably need to enable it and make it available on <a href="http://conference.yourdomain.at" class="">conference.yourdomain.at</a>. It is probably also a good idea to limit access to the conference application by adding some firewall rules. The only service that will connect to it will be SylkServer itself.</div><div><br class=""></div><div>Best regards,</div><div><br class=""></div><div>Tijmen de Mes</div><div>—</div><div>AG Projects</div><div><blockquote type="cite" class=""><div class="">Op 25 mrt. 2020, om 16:18 heeft Valentin Kleibel <<a href="mailto:valentin@vrvis.at" class="">valentin@vrvis.at</a>> het volgende geschreven:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello,<br class=""><br class="">Thanks for creating such a cool piece of software. Out of all open source video conferencing systems we tested we prefer sylkserver and sylk-webrtc.<br class="">We're interested in using sylkserver with webrtc support for audio- and videoconferencing and want to run our setup without sip connectivity.<br class="">We also want to use authentication for our users and let them send invite links, but we don't want that everyone can open video conferences on our server.<br class=""><br class="">Up to now we've managed to run sylkserver and sylk-webrtc on our server and create anonymous video conferences that worked well for some time.<br class="">But after about a minute one participant will disconnect and reconnect, while sylkserver logs 403 forbidden sip messages.<br class=""><br class="">2020-03-25 13:20:43.557495 Packet 29 OUTGOING UDP XX:5060 -> XX:5060 │·<br class="">SIP/2.0 403 Forbidden │·<br class="">Via: SIP/2.0/UDP XX:5060;rport=5060;received=XX;branch=z9hG4bKPje736ed98-ad2e-│·<br class="">46ce-9f38-872120a72df2 │·<br class="">Call-ID: ad5a3d35-1e58-4b98-913f-c4bd0a8686db │·<br class="">From: "dfsd" <<a href="sip:f6bf3e2e54874047@guest.XX.at" class="">sip:f6bf3e2e54874047@guest.XX.at</a>>;tag=62855d40-b9f1-4828-9a9b-8592bf830c│·<br class="">51 │·<br class="">To: <<a href="sip:riverringereater6@conference.XX.at" class="">sip:riverringereater6@conference.XX.at</a>>;tag=f0569ead-2caf-43fa-ad4e-43cfa261fbbe │·<br class="">CSeq: 5860 INVITE │·<br class="">Server: SylkServer-5.5.0 │·<br class="">Content-Length: 0<br class=""><br class="">what is going wrong here? is such a setup even possible?<br class=""><br class="">Thanks for your help,<br class="">Valentin<br class="">_______________________________________________<br class="">SIPBeyondVoIP mailing list<br class=""><a href="mailto:SIPBeyondVoIP@lists.ag-projects.com" class="">SIPBeyondVoIP@lists.ag-projects.com</a><br class="">https://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip<br class=""></div></div></blockquote></div><br class=""></body></html>