[App_rpt-users] Echolink and Teamspeak

[Loren Tedford]

I have been using team speak in the gaming community for several years
now.. I started in 2004 with team speak 2 and later started hosting my own
team speak 3 servers by 2006.. I have a had a pretty good experience with
team speak in both windows and linux but I don't recommend doing what your
doing for a few reasons.. First reliability and lock up concerns.. Virtual
Audio Cable should be using a low latency kernel to do this sort of thing..
The arm processor is nice and powerful enough to mess around with allstar
but i wouldn't recommend this as an all in one box.. Back when i was doing
alot of broadcasting in the world of online radio.. I learned a few things
about Virtual Audio cables and latency issues I ended up having to use a
pretty good power house machine with Xubuntu Studio to accomplish my
goals.. I am in no way trying to discourage you on the use of teamspeak
with your repeater system but in a live production environment I don't
think I would trust some thing like this on a small pi that at best might
be a quad core at 1.5 ghz and virtually no ram at all..

Team speak is great for what it was designed for and is still a great way
to communicate in an emergency when all you have is data and no phone lines
but when it comes down to it I just recommend setting everyone setting up a
live steam from your allstar node and if you need people to chat back with
ya I would strongly encourage the use of Android IAX rpt or echolink (
echolink I don't like it but at least it works some times.. ) In my opinion
awesome job on the vox audio cable setup between an echolink client and
what ever way your ripping the audio off of allstar I would assume probably
a phone sip client of some sort..  Yes this sort of thing can be done in
the linux world but i don't think a pi has enough grunt and ram to safely
do what you wanna do..

Warning the content listed below has not been tested..

What i would do is install DIAL: then search online how to install a low
latency kernel a basic desktop of your choice (Just to make life easier)
and virtual audio cables for linux teamspeak has a linux installation as
well.. Their are several sip phone clients available out their on the
market and you could probably setup what ever needed to link into your
allstar node.. As far as machine speed and other info well I would at least
have 2 gigs of ram at minimum and recommend at least 4 gb of ram if you
really have to use a windows program in linux look at wine.. I don't
recommend this always try to find a linux alternative.. If your wanting to
run this computer off of 12 for power fail-over and other needs check out a
pico power supply..

Best of luck I hope i have pointed you in the right direction this is not
to say you couldn't get this done with the pi but you might have issues
with locking open allstar and i guarantee you don't want that..


Loren Tedford (KC9ZHV)
Phone:
Fax:
Email: lorentedford at gmail.com
Email: KC9ZHV at KC9ZHV.com
http://www.lorentedford.com
http://www.kc9zhv.com
http://forum.kc9zhv.com
http://hub.kc9zhv.com
http://Ltcraft.net <http://ltcraft.net/>
http://voipham.com

On Thu, Sep 15, 2016 at 3:13 AM, Gareth Jackson <gareth1125 at gmail.com>
wrote:

> Hello all.
>
>
>
> Having being running the Teamspeak server for a few weeks now, it’s
> thankfully working well with both Echolink and Allstar links (Even in the
> process of adding a DMR crosslink now).
>
>
>
> It is however running on windows based machines, and ideally, I’d like to
> run it on a Raspberry Pi 3. I keep being told that the “pi” is the future,
> and having seen a few videos of people using them, they do seem very neat
> and functional.
>
>
>
> My issue is that now I have 2 band new shiny Pi’s sat in front of me, i’m
> struggling on where to go next.
>
>
>
> I can’t find information about how to run Echolink (sysops) on them using
> virtual audio cables... I can however find lots of people that have a radio
> plugged in to them, but as it’s a virtual server I don’t need radios
> plugged into them.
>
>
>
> Has anyone any experience with this before? I’m guessing if anyone uses
> one for crosslinking Allstar and Echolink they would have had to address
> this issue.
>
>
>
> Cheers,
>
>
>
>
> Gareth
>
>
>
>
>
> PS: For anyone not knowing what Teamspeak is, it’s an VOIP/ROIP app
> (running on my own private server) that allows hams that are not in range
> of repeaters etc, to access multiple talk groups using the teamspeak app
> for free. Teams speak runs on PC/Mac/Linux/Apple/Google devices etc...
> Happy to share the details of the server if anyone wants to try it out etc.
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/
> mailman/listinfo/app_rpt-users and scroll down to the bottom of the page.
> Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20160915/843dcbb9/attachment.html>