You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Orm Finnendahl <or...@selma.hfmdk-frankfurt.de> on 2020/04/08 22:12:11 UTC
lt-cred-mech in config
Hi,
is it possible to run openmeetings/kurento using the lt-cred-mech
instead of the rest api? I assume the relevant part is in
$OM_HOME/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
We currently have:
<bean id="kurentoHandler" class="org.apache.openmeetings.core.remote.KurentoHandler" init-method="init" destroy-method="destroy"
p:kurentoWsUrl="ws://127.0.0.1:8888/kurento"
p:checkTimeout="10000"
p:watchThreadCount="10"
p:turnUrl="<publicIP>"
p:turnUser=""
p:turnSecret="<secretpass>"
p:turnMode="rest"
p:turnTtl="60"
p:objCheckTimeout="200"
/>
What would we have to specify as p:turnMode to use the longterm
credential mechanism?
--
Orm
Re: lt-cred-mech in config
Posted by Maxim Solodovnik <so...@gmail.com>.
On Thu, 9 Apr 2020 at 05:13, Orm Finnendahl <
orm.finnendahl@selma.hfmdk-frankfurt.de> wrote:
> Hi,
>
> is it possible to run openmeetings/kurento using the lt-cred-mech
> instead of the rest api? I assume the relevant part is in
>
>
As far as I know `lt-cred-mech` is the setting of coturn NOT openmeetings
NOT KMS
So this is the question I didn't get ...
> $OM_HOME/webapps/openmeetings/WEB-INF/classes/applicationContext.xml
>
> We currently have:
>
> <bean id="kurentoHandler"
> class="org.apache.openmeetings.core.remote.KurentoHandler"
> init-method="init" destroy-method="destroy"
> p:kurentoWsUrl="ws://127.0.0.1:8888/kurento"
> p:checkTimeout="10000"
> p:watchThreadCount="10"
> p:turnUrl="<publicIP>"
> p:turnUser=""
> p:turnSecret="<secretpass>"
> p:turnMode="rest"
> p:turnTtl="60"
> p:objCheckTimeout="200"
> />
>
> What would we have to specify as p:turnMode to use the longterm
> credential mechanism?
>
>
I currently using coturn with lt-cred-mech
And turnMode == rest
Works for me
> --
> Orm
>
>
--
Best regards,
Maxim