Client "Bridge" Program

[Marsman]

Since there can only be one client running on a machine, I'd like to see a client "Bridge".

Here's the concept:
A special 2 sided Client that has 2 panes - left for server 1 - right for server 2.
Connect to Server 1 on left panel - place special Bridge user in a channel.
Connect to Server 2 on right panel - place special Bridge user in a channel there also.
All sound card connections internally are removed. Instead all received "sound" is re-directed to the other server panel, as if the client was "tranmitting" mic audio.

What this would essentially do, is allow two servers to be "Bridged" together via this "bridge" client. The channels where the bridge client users are, would be tied together allowing all conversations on Servers 1's channel to be heard on Server 2's channel and vise-versa. You would be aware that a conversation was coming from the other server because you would see the bridge client transmitting and thus able to distinguish it from local users.

This would be a very helpful program. Many times, teams have their own TS servers, but could be workiing with other teams also with their own TS servers. As it is now, everyone has to pile on someones TS server to share communication. This bridge client would allow multiple teams to link their servers via the client and thus be able to communicate without everyone having to change over to some team's TS server. The uses for such a program are endless and would greatly aid teams who run operations in conjunction with other teams.

I would think this should be relatively easy to do code-wise as everything already exists, it's just of matter of duplicating the client to be 2 sided and then re-directing all calls to the sound card to the opposite server panel. Since this TS source code isn't available, this would have to come from a developer (hint hint lol) but it sure would be a nice tool to have. :cool:

[Peter]

Hi,

this has already being done, albait without rewriting the client (because only the developers can do that), but instead with some workarounds and some good ideas. The people that I know of using these bridges as you call them are enabling radio (citizen band I think, but I am no expert) to work long-distance using TS. So say you wanted to use your citizen band walky talky in Germany/Berlin to talk to your friends in English/London. Normaly, the citizen band only goes a few kilometers, so that wouldn't by far go the distance. But what you could do is setup a teamspeak server, and a "bridge" client in berlin, and a "bridge" client in london. Now these two bridges relay whatever is being said on Berlin air into TeamSpeak, and whatever is being said on TeamSpeak into Berlin air (and same for london). Now, anybody with access to a citizen band in berlin can talk with anybody else with citizen band in london. Cool stuff, I think :).

Probably you will need two clients to form the bridge you speak of, they could mute each other and mute their microphone on the server they are not supposed to send to, this would avoid the echo feedback which would elsewise kill all communication quickly.