Re: Tips and tricks on using the command line.
@Green Gables Fan, the requirement of Python to communicate with team talk is entirely unfounded falsehoods. Any network implementation will do the trick. TeamTalk has, as you know, two ports -- the TCP and UDP ports. The TCP port is used to communicate with the server, and commands/instructions and replies are sent on this port. The UDP port is used for voice communications. According to the latest revision of the TT5 github repository (at the time of this writing, revision c302a575d24f20a05fcbbe9e15524b055146414d), the list of available TCP commands are as follows: login, joinchannel, leavechannel, listbans, listaccounts, subscribe, unsubscribe, join, kick, moveuser, op, ban, unban, message, makechannel, updatechannel, removechannel, leave, newaccount, delaccount, updateserver, saveconfig, querystats, and ping. (I may be wrong, and certain commands in this list may not be commands, or they may be. There also are most likely more.) An example telnet session follows:
$... # initiate telnet and log in (> is example prompt, not actual prompt given by TT)
> querystats id=123
begin id=123
stats totaltx=0 totalrx=0 voicetx=0 voicerx=0 videocaptx=0 videocaprx=0 mediafiletx=0 mediafilerx=0 desktoptx=0 desktoprx=0 usersserved=2 userspeak=1 filestx=0 filesrx=0 uptime=120176
ok
end id=123
You will notice that I added "id=123" at the end of the command. This is to ensure that I can separate command outputs from server replies. As the teamtalk 5 PHP administration script says, "Interacting with a TeamTalk server is similar to a command line interface. Basically issue a command by typing its name and press Enter. The server will then process the command and issue a reply. The TeamTalk protocol is, however, not a request/reply protocol, i.e. the server can send commands which are not replies issued by the client (you). E.g. once you have logged in you can get a command from the server saying that a user has joined a channel which is not related to any command you have issued. To know if a command is a reply to a command you have issued you need to put in the parameter "id=123" where 123 is the command ID of the command you want to trace. The server will then encapsulate its reply to your command in 'begin' - 'end' replies." As you saw, the server responded with, "begin id=123", then it's output, then "end id=123". If we were writing an application, we could use this to determine what is output that we requested and what is not.Output that is not surrounded by begin and end is autotransmitted server replies/commands; output that is surrounded by begin/end is output we requested. I hope this gives you guys a bit of acumen into how TT works!
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
