Issues with video and screen sharing

[LabodiDavid]

I'm tried to testing out this new feature but I got the following error:

At the server side:

At the client side:


I tried to open the port what the console wrote above in the console both for TCP/UDP (9068) but that not worked.

Server version: 1.5.0-beta
Client version: 1.5.0-3

 

[WolverinDEV]

Well important are the WebRTC ports configurable in the config.yml

    #Description:
    #  Define the port range within the web client and TeaClient operates in
    #  A port of zero stands for no limit
    #Notes:
    #  These ports must opened to use the voice bridge (Protocol: UDP)
    #The value must be a positive numeric value between 0 and 65535
    port_min: XXXX
    #Description:
    #  Define the port range within the web client and TeaClient operates in
    #  A port of zero stands for no limit
    #Notes:
    #  These ports must opened to use the voice bridge (Protocol: UDP)
    #The value must be a positive numeric value between 0 and 65535
    port_max: XXX

A few lines bellow you can also specify the protocol (tcp and/or udp)

 

[LabodiDavid]

Well important are the WebRTC ports configurable in the config.yml

    #Description:
    #  Define the port range within the web client and TeaClient operates in
    #  A port of zero stands for no limit
    #Notes:
    #  These ports must opened to use the voice bridge (Protocol: UDP)
    #The value must be a positive numeric value between 0 and 65535
    port_min: XXXX
    #Description:
    #  Define the port range within the web client and TeaClient operates in
    #  A port of zero stands for no limit
    #Notes:
    #  These ports must opened to use the voice bridge (Protocol: UDP)
    #The value must be a positive numeric value between 0 and 65535
    port_max: XXX

A few lines bellow you can also specify the protocol (tcp and/or udp)

I configured the port range from 50000 to 56000 as the default values both for TCP/UDP. Webrtc is enabled and the ports are forwarded correctly but the problem is the same.
Those missing packet id errors appearing when the client video is trying to connect.

And I can connect to the server from the teaweb.

 

[WolverinDEV]

Well the missing packet Ids are ignore able.
Jou told something about forwarding? Are you using a Nat?

Edit: if so than I'm probably already working on that since @yamano has the exact same issue and I'm absolutely clueless, but I'm still trying

 

[LabodiDavid]

Well the missing packet Ids are ignore able.
Jou told something about forwarding? Are you using a Nat?

Edit: if so than I'm probably already working on that since @yamano has the exact same issue and I'm absolutely clueless, but I'm still trying

Yes this server is behind a NAT. But I think there isn't problem with that because the webclient connection is working and thats using webrtc too.
Okay, then i'm waiting for the update. Good luck, these features are changing tea*speak

 

[WolverinDEV]

Ahh well that's the issue.
Without using a NAT it works flawlessly (you can test it on my server ts.teaspeak.de).
If you're having some network experience you may want to help out as well.

 

[WolverinDEV]

Update: NATs now work properly with the within the config.yml configured ports.