[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221878#comment-17221878
 ] 

Maxim Solodovnik commented on OPENMEETINGS-2500:
------------------------------------------------

TURN/STUN is necessary for Camera/Microphone/Sharing only
what do you have in applicationContext.xml?

> No Video and Audio when stun-only was Set in the turnserver.conf
> ----------------------------------------------------------------
>
>                 Key: OPENMEETINGS-2500
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2500
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: Audio/Video
>    Affects Versions: 5.0.1
>         Environment: CentOS 8 / 8 Gigabyte Memory / 8 Virtual Cores
>            Reporter: Dennis Aguilar
>            Assignee: Maxim Solodovnik
>            Priority: Major
>              Labels: performance
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> There's no video and audio when I set the stun-only on the coturn settings. I 
> was testing if the data will really go directly from the user to another 
> user. Im doing this to save bandwidth and also to reduce the chance of 
> audio/video choppiness. However, the whiteboard works and I can see what I 
> write in the whiteboard on the other end including the Mp4 video. Please help 
> on how i can fix this. Below are my errors and turnserver.conf settings. 
> Thank You.
>  
> Here are the errors that I encoutered:
> -----------------------------------------------------------------------------
> 6: session 002000000000000001: realm <MyDOmain.com> user <>: incoming packet 
> BINDING processed, success
> 9: session 002000000000000001: usage: realm=<MyDOmain.com>, username=<>, 
> rp=1, rb=20, sp=1, sb=108
> 9: session 002000000000000001: peer usage: realm=<MyDOmain.com>, username=<>, 
> rp=0, rb=0, sp=0, sb=0
> 9: session 002000000000000001: closed (2nd stage), user <> realm 
> <MyDOmain.com> origin <>, local 61.59.179.145:443, remote 
> 112.205.225.2:50003, reason: allocation watchdog determined stale session 
> state
> 48: handle_udp_packet: New UDP endpoint: local addr 51.79.199.115:443, remote 
> addr 112.205.225.2:61227
> 48: session 006000000000000001: realm <MyDOmain.com> user <>: incoming packet 
> BINDING processed, success
> 48: handle_udp_packet: New UDP endpoint: local addr 61.59.179.145:443, remote 
> addr 112.205.225.2:61226
> 48: session 004000000000000001: realm <MyDOmain.com> user <>: incoming packet 
> BINDING processed, success
> 48: handle_turn_command: STUN method 0x3 ignored
> 48: handle_turn_command: STUN method 0x3 ignored
> 48: handle_turn_command: STUN method 0x3 ignored
> 49: handle_turn_command: STUN method 0x3 ignored
> 50: handle_turn_command: STUN method 0x3 ignored
> ---------------------------------------------------------------------------------------
>  
> And Here's My Turnserver.conf settings:
> listening-port=443
> alt-listening-port=80
> realm=MyDomain.com
> verbose
> fingerprint
> user=MyUsername:MyPassword
> use-auth-secret
> static-auth-secret=3aae1a4c281d5a1064c3c9eef7f17d27cea24c5fe23e630ceaeb9d864131d012
> cert=/etc/letsencrypt/live/MyDomain.com/fullchain.pem
> pkey=/etc/letsencrypt/live/MyDomain.com/privkey.pem
> stale-nonce=7200
> no-cli
> no-tcp
> no-tls
> no-dtls
> stun-only
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to