On Thu, 17 Dec 2020 at 00:36, kaffeesurrogat <[email protected]>
wrote:

> now i am ashamed, it was me who asked this question a while ago and you
> did answer it.
>
> sorry for that ....
>
> this means i should leave the line in
> /opt/open510/webapps/openmeetings/WEB-INF/classes/openmeetings.properties
>
> like this:
>
> kurento.turn.user=
>

you can put any user-name to this line :)
for ex.

    kurento.turn.user=kaffeesurrogat

(I guess it can be used while log checking)
or can leave it empty :)


>
> Commenting it out doesn't work .....
>
> I find some error in openmeetings.log
> (Could not resolve placeholder kurento.turn.user .....)
> and the webfrontend is not reachable ....
>
>
>
>
>
>
> On 16/12/2020 17:12, Maxim Solodovnik wrote:
> > I would recommend to remove the `user` from coturn config
> > (/etc/turnserver.conf)
> > please search mailing lists, I've shared my config (as well as others
> > ... :)))
> >
> > On Wed, 16 Dec 2020 at 22:49, kaffeesurrogat <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >
> >
> >     On 16/12/2020 16:39, Maxim Solodovnik wrote:
> >     >
> >     >
> >     > On Wed, 16 Dec 2020 at 21:28, kaffeesurrogat
> >     <[email protected] <mailto:[email protected]>
> >     > <mailto:[email protected]
> >     <mailto:[email protected]>>> wrote:
> >     >
> >     >     Dear list,
> >     >
> >     >     just trying to understand things a little better.
> >     >
> >     >     I tried to check if my turn/stun server is working correctly.
> >     >
> >     >     my turnserver.conf contains the line
> >     >
> >     >     user=nobody:PASSWORD
> >     >
> >     >
> >     > Why have you added this line to coturn config?
> >
> >     That was mentioned in
> >
> >
>  
> Installation_SSL_certificates_and_Coturn_for_OpenMeetings_5.1.0_on_Ubuntu_18.04.pdf
> >
> >
> >
> >
> >
> >     >
> >     >
> >     >
> >     >     Now i'm using
> >     >
> >     >
> >     >
> >
> https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
> >     <
> https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/>
> >     >
> >      <
> https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
> >     <
> https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/>>
> >     >
> >     >     to check my turn server.
> >     >
> >     >     The entries on trickle are:
> >     >
> >     >     turn:MYIP:3478
> >     >     turn username: nobody
> >     >     turn password: PASSWORD
> >     >
> >     >
> >     >     The test result is negativ.
> >     >
> >     >
> >     > I guess this is expected
> >     >
> >     >
> >     >     My log file shows
> >     >
> >     >     ##############################################################
> >     >
> >     >     80: handle_udp_packet: New UDP endpoint: local addr
> >     MYIP:3478, remote
> >     >     addr 149.224.83.188:43949 <http://149.224.83.188:43949>
> >     <http://149.224.83.188:43949 <http://149.224.83.188:43949>>
> >     >     80: session 002000000000000001: realm <MYIP> user <>:
> >     incoming packet
> >     >     message processed, error 401: Unauthorized
> >     >     80: handle_udp_packet: New UDP endpoint: local addr
> >     MYIP:3478, remote
> >     >     addr 149.224.83.188:32997 <http://149.224.83.188:32997>
> >     <http://149.224.83.188:32997 <http://149.224.83.188:32997>>
> >     >     80: session 002000000000000002: realm <MYIP> user <>:
> >     incoming packet
> >     >     message processed, error 401: Unauthorized
> >     >     80: check_stun_auth: Cannot find credentials of user <nobody>
> >     >     80: session 002000000000000001: realm <MYIP> user <nobody>:
> >     incoming
> >     >     packet message processed, error 401: Unauthorized
> >     >     80: check_stun_auth: Cannot find credentials of user <nobody>
> >     >     80: session 002000000000000002: realm <MYIP> user <nobody>:
> >     incoming
> >     >     packet message processed, error 401: Unauthorized
> >     >     83: handle_udp_packet: New UDP endpoint: local addr
> >     MYIP:3478, remote
> >     >     addr 149.224.83.188:46559 <http://149.224.83.188:46559>
> >     <http://149.224.83.188:46559 <http://149.224.83.188:46559>>
> >     >     83: session 002000000000000003: realm <MYIP> user <>:
> >     incoming packet
> >     >     message processed, error 401: Unauthorized
> >     >     83: handle_udp_packet: New UDP endpoint: local addr
> >     MYIP:3478, remote
> >     >     addr 149.224.83.188:37545 <http://149.224.83.188:37545>
> >     <http://149.224.83.188:37545 <http://149.224.83.188:37545>>
> >     >     83: session 005000000000000002: realm <MYIP> user <>:
> >     incoming packet
> >     >     message processed, error 401: Unauthorized
> >     >     83: check_stun_auth: Cannot find credentials of user <nobody>
> >     >     83: session 002000000000000003: realm <MYIP> user <nobody>:
> >     incoming
> >     >     packet message processed, error 401: Unauthorized
> >     >     83: check_stun_auth: Cannot find credentials of user <nobody>
> >     >     83: session 005000000000000002: realm <MYIP> user <nobody>:
> >     incoming
> >     >     packet message processed, error 401: Unauthorized
> >     >
> >     >
> >     >     ##############################################################
> >     >
> >     >
> >     >     user nobody with PASSWORD is not found ..... ;-(
> >     >
> >     >     loging into my om room, activating my camera gives:
> >     >
> >     >     ##############################################################
> >     >
> >     >     863: handle_udp_packet: New UDP endpoint: local addr MYIP:3478,
> >     >     remote
> >     >     addr REMOTEIP:41039
> >     >     863: session 005000000000000003: realm <MYIP> user <>: incoming
> >     >     packet
> >     >     BINDING processed, success
> >     >     863: session 005000000000000003: realm <MYIP> user <>: incoming
> >     >     packet
> >     >     message processed, error 401: Unauthorized
> >     >     863: IPv4. Local relay addr: MYIP:63505
> >     >     863: session 005000000000000003: new, realm=<MYIP>,
> >     >     username=<1608132140:a8675769-9280-4ab7-ab37-d271e8e5cadb>,
> >     >     lifetime=600
> >     >     863: session 005000000000000003: realm <MYIP> user
> >     >     <1608132140:a8675769-9280-4ab7-ab37-d271e8e5cadb>: incoming
> >     packet
> >     >     ALLOCATE processed, success
> >     >     863: session 005000000000000003: peer MYIP lifetime updated:
> 300
> >     >     863: session 005000000000000003: realm <MYIP> user
> >     >     <1608132140:a8675769-9280-4ab7-ab37-d271e8e5cadb>: incoming
> >     packet
> >     >     CREATE_PERMISSION processed, success
> >     >     863: session 005000000000000003: realm <MYIP> user
> >     >     <1608132140:a8675769-9280-4ab7-ab37-d271e8e5cadb>: incoming
> >     packet
> >     >     CREATE_PERMISSION processed, error 403: Forbidden IP
> >     >     863: session 005000000000000003: realm <MYIP> user
> >     >     <1608132140:a8675769-9280-4ab7-ab37-d271e8e5cadb>: incoming
> >     packet
> >     >     message processed, error 403: Forbidden IP
> >     >
> >     >     ##############################################################
> >     >
> >     >
> >     >     gives a user name with a long number ...... ?
> >     >
> >     >
> >     > Special hash of user and password is being used by OM
> >     >
> >     >
> >     >
> >     >
> >     >     There are two questions :
> >     >
> >     >     1) why do i need a user nobody:password in my config lines
> >     if the
> >     >     username generated by om is a long hash but not nobody ... ?
> >     >
> >     >
> >     > your config is your responsibility :))))
> >     > I guess you can google
> >     > Or check this
> >     >
> >     doc https://github.com/coturn/coturn/blob/master/README.turnserver
> >     <https://github.com/coturn/coturn/blob/master/README.turnserver>
> >     > <https://github.com/coturn/coturn/blob/master/README.turnserver
> >     <https://github.com/coturn/coturn/blob/master/README.turnserver>>
> >     for ex.
> >     will read this doc. One day i will understand this turn server
> >     thing ...
> >
> >
> >     > Or search mailing-list archives for working configurations :)))
> >     >
> >
> >
> >
> >     >
> >     >
> >     >     2) why does my trickle test fail or why does it not find the
> >     >     credentials
> >     >     ... ?
> >     >
> >     >
> >     > I believe your configuration might be wrong ...
> >     >
> >     >
> >     >
> >     >
> >     >     Many thanks,
> >     >
> >     >     kaffeesurrogat
> >     >
> >     >
> >     >
> >     >
> >
> >     thanks again....
> >
> >     kaffeesurrogat ;-)
> >
> >     >
> >     > --
> >     > Best regards,
> >     > Maxim
> >
> >
> >
> > --
> > Best regards,
> > Maxim
>
>
>

-- 
Best regards,
Maxim

Reply via email to