"Required permissions" are not enough

[Bluscream]

# Bridge to TeamSpeak via it's Query-Console.
#
# The bridge requires a user with the following permissions:
# - b_serverquery_login
# - b_virtualserver_select
# - b_virtualserver_client_list
# - i_channel_subscribe_power
# - i_channel_needed_subscribe_power
#
# @version 0.4

Does not seem to be enough, im trying to find the needed permission for hours now.

Logging the serverquery traffic when setting LogginLevel to debug would be nice so one can quickly see whats wrong.

[depressobbq]

Teamspeaks Query system is not so fun to operate. i may be able to help here depending on whats wrong but i personally dont use the bridge function on my T S. i have had to mess with query for other things though. firstly id like to assume you have the advanced permissions box checked in your client settings and you have port 10011 open and so on and you have your server admin password so that you can actually login to query. following all that fun stuff assuming everything is working right (or already was) the perms you listed should be able to be directly applied or changed by logging into server query via telnet (putty) provided you have the password. following that you should set up a server group with just these perms and query login. then the config should just need user info. if that doesnt work than i dunno. maybe mr freiholz knows whats going on. also like i said i havent set this up myself as i didnt see the need just going on previous experiences with the query login.

On Fri, Mar 24, 2017 at 11:10 AM, Bluscream notifications@github.com wrote:

Bridge to TeamSpeak via it's Query-Console.## The bridge requires a user with the following permissions:# - b_serverquery_login# - b_virtualserver_select# - b_virtualserver_client_list# - i_channel_subscribe_power# - i_channel_needed_subscribe_power## @version 0.4

Does not seem to be enough, im trying to find the needed permission for hours now.

Logging the serverquery traffic when setting LogginLevel to debug would be nice so one can quickly see whats wrong.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mfreiholz/ts3video/issues/57, or mute the thread https://github.com/notifications/unsubscribe-auth/ANF-g08AiRakfz_7oJJykvXWzzNhjNtjks5ro9z1gaJpZM4MoYZz .

[mfreiholz]

Hm.. maybe something changed with a new TS3 server version? I will check that.

[Bluscream]

@mfreiholz could you redirect the query output to the log somehow? It would help troubleshoot many things

[mfreiholz]

Yep, good idea.

[Bluscream]

But it should only get logged when logging level is debug :D

[Bluscream]

Any news? I'd like to use TS3Video without using the ASQ accout :)

[depressobbq]

as far as i know if you dont enable the client bridge the application will work just fine. just set an admin password in the config in case you have to kick someone off video... unless theres something going on here i dont see

On Sun, Mar 26, 2017 at 3:50 AM, Bluscream notifications@github.com wrote:

Any news? I'd like to use TS3Video without using the ASQ accout :)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mfreiholz/ts3video/issues/57#issuecomment-289264628, or mute the thread https://github.com/notifications/unsubscribe-auth/ANF-g2NvdJLNJOjD5Z5_q10FGCB7o0NSks5rphisgaJpZM4MoYZz .

[mfreiholz]

There is already a logging. Can you try to set server logging to "debug", please?

$APPDIR/logging.conf

logger.level(*)=trace

[Bluscream]

Sadly i dot have productional environment to test it anymore but i will test it with my local server soon.