From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=kn1ght.org (client-ip=91.121.222.131; helo=f1r3.kn1ght.org; envelope-from=galene.org@kn1ght.org; receiver=) Received: from f1r3.kn1ght.org (ks305909.kimsufi.com [91.121.222.131]) by mail.toke.dk (Postfix) with ESMTP id D8E477BFE6F for ; Sun, 27 Dec 2020 19:02:57 +0100 (CET) Received: from nc.kn1ght.org (ns342210.ip-91-121-151.eu [91.121.151.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by f1r3.kn1ght.org (Postfix) with ESMTPSA id 2A3B31F55C; Sun, 27 Dec 2020 17:24:34 +0100 (CET) MIME-Version: 1.0 Date: Sun, 27 Dec 2020 18:02:56 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: RainLoop/1.14.0 From: "Cell" Message-ID: <99912233bfadb502ba97143df131ecf1@kn1ght.org> To: "=?utf-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?=" , galene@lists.galene.org In-Reply-To: <874kk7yvyz.fsf@toke.dk> References: <874kk7yvyz.fsf@toke.dk> <1082cfcde178ddb72b51bcd03ee6770a@kn1ght.org> Message-ID-Hash: 3FLT46BR4Z37XJJXQXVI5QBD3WNITHUW X-Message-ID-Hash: 3FLT46BR4Z37XJJXQXVI5QBD3WNITHUW X-MailFrom: galene.org@kn1ght.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: coturn config List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: This would be my plan B then.=0A=0ADecember 27, 2020 6:55 PM, "Toke H=C3= =B8iland-J=C3=B8rgensen" wrote:=0A=0A> "Cell" writes:=0A> =0A>> Hi,=0A>> =0A>> Would there be anyone with a= n example of a coturn config? I don't know=0A>> how to setup the user and= password.=0A>> =0A>> More about my context: I just put a coturn in place= for my synapse=0A>> server and it's working. I would like to use the sam= e one in place for=0A>> a future galene but I don't know if the secret fo= r the API is in=0A>> conflict with the user/password needed for galene.= =0A> =0A> It is; you can't use both in the same coturn config.=0A> =0A>> = All examples and input welcomed.=0A> =0A> What I do is just run two cotur= n instances on different ports, one for=0A> Galene with username/password= , and one for other applications that use=0A> the REST API secret-based a= uth (the latter being Nextcloud Talk in my=0A> instance).=0A> =0A> -Toke= =0A> _______________________________________________=0A> Galene mailing l= ist -- galene@lists.galene.org=0A> To unsubscribe send an email to galene= -leave@lists.galene.org