[App_rpt-users] Fwd: Suitability of boot media

Mon Feb 18 06:33:56 UTC 2013

I don't know about using the AllStar SIP service for non-amateur applications….
I'm guessing the AllStar SIP service helps support the AllStar project financially.

There are plenty of SIP providers out there, but I normally use Vitelity.com and voip.ms 
as my SIP/IAX trunk providers.  They've been reliable and are easy to deal with.
Vitelity has a special PAIF deal that gives you a half price deal on some trunks with 
more or less unlimited incoming, but I mostly use the dollar a month trunks from 
both providers with metered usage at a penny or so a minute…
(At a dollar a month I can do fun things like having a local DID number 
in my home town so my parents can call me with a seven digit local call…)  

Some of my systems are running high enough call volume that they would be 
abusing the unlimited trunks that are intended for residential/SOHO applications.

Another good reason for the dedicated AllStar box:  Later on, when I need another 
radio, I can add a URI to the existing AllStar PBX or I can use an RTCM to 
attach a non-local radio.

On Feb 17, 2013, at 9:32 PM, Shane Morris <edgecomberts at gmail.com> wrote:

> Just as a point of interest, could you use the AllStar SIP service for
> commercial (ie, non amateur) applications?
> 
> However, your configuration you describe is pretty much what I envisage...
> 
> On Mon, Feb 18, 2013 at 4:13 PM, Don Hackler <donh at sigma.net> wrote:
>> 
>> While improved security is a factor, the main reason for separate installs
>> is that AllStar/app_rpt runs on a forked asterisk distribution based on
>> Asterisk 1.4
>> and PAIF runs on much later Asterisk versions.  Asterisk 1.8 is the oldest
>> stable distro for PAIF you would want to run on a new install.
>> 
>> The main reason for the fork is that AllStar/apt_rpt runs on the Zaptel
>> framework and the newer Asterisk versions don't support Zaptel.
>> The app_rpt that is in the current Asterisk distributions was pretty much
>> abandoned in place.
>> 
>> PAIF offers a much nicer web-gui PBX operation and is substantially easier
>> to run for general purpose PBX situations.
>> Out of the box, PAIF has several dozen nice features already running while
>> the Acid/AllStar distro is very much a totally stripped down basic command
>> line
>> driven system.
>> 
>> If all you are going to do is glue a couple of radios together and maybe
>> hook up one SIP trunk, then just use the ACID AllStar distro.
>> It's fine for that, preferably using the AllStar SIP trunk service, since
>> the configuration is well known and it's inexpensive.
>> 
>> I run several PAIF installations all tied together in a fairly large
>> network, serving SIP phones at several locations.
>> The single ACID AllStar distro running on a dedicated box appears to my
>> larger network as a single extension that happens to be a radio.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Feb 17, 2013, at 3:28 PM, pete M <petem001 at hotmail.com> wrote:
>> 
>> What would this kind of setup give aside more security?
>> 
>> Envoyé de mon iPad
>> 
>> Le 17 Feb 2013 à 17:45, "Don Hackler" <donh at sigma.net> a écrit :
>> 
>> 
>> 
>> Begin forwarded message:
>> 
>> From: Don Hackler <donh at sigma.net>
>> Subject: Re: [App_rpt-users] Suitability of boot media
>> Date: February 17, 2013 2:44:31 PM PST
>> To: Shane Morris <edgecomberts at gmail.com>
>> 
>> You will need to run PAIF and AllStar on separate boxes.
>> Use IAX to connect the two.
>> 
>> If you only have one outside IP address, you can put change AllStar to use a
>> different port for it's outside IAX connection to the AllStar network and
>> then the PAIF box can use the standard IAX port (if needed).  Your the PAIF
>> box to connect to the usual VOIP trunk providers.
>> 
>> Use the 32 bit Centos 6.3 PAIF distro and install PAIF Purple for a stable
>> setup.  (Asterisk 1.8, FreePBX 2.10)
>> 
>> For light duty applications, I've heard good reports about running PAIF on a
>> Rasberry Pi, but that's still a bit experimental.
>> 
>> On Feb 17, 2013, at 1:05 PM, Shane Morris <edgecomberts at gmail.com> wrote:
>> 
>> Hi all,
>> 
>> I am supposed to be having a HP T5630w thin client delivered to me today,
>> and I was planning to install PBX In A Flash on it, which was recommended by
>> one of the members of the list.
>> 
>> First up, can I install from say a 1GB stick to a 8 or 16GB stick, and leave
>> the larger stick semi-permanently in the machine as boot media under the
>> cover at the top? The thin client is quoted with only a 2GB IDE SSD,
>> certainly not enough for this OS, and I don't want to wait another couple of
>> weeks for postage on a 32GB IDE SSD.
>> 
>> Next question, which is the best version of PIAF to get? Nowhere that I can
>> see does it quote which version of Asterisk its using or whether it would be
>> suitable for use with the correct version for app_rpt (which is 1.4 as I
>> take it from numerous discussions).
>> 
>> Last question - this'll be running on the thin client, and as we know, there
>> are *some* security issues with 1.4 (of course, theres probably security
>> issues with 1.8 too, but they haven't been exploited yet, so I'm not bashing
>> 1.4, I know no piece of networked software is totally secure) so would you
>> recommend using this "repeater controller" box on an IAX trunk to a 1.8
>> "PABX controller" box, and let the PABX face the world? I fully intend on
>> using the internal but offsite connections over a VPN, but to get to the
>> outside world and onto the PSTN it needs to go through my ITSPs, Exetels,
>> indial account(s).
>> 
>> Of course, if this is recommended, which I strongly suspect it is, I'll have
>> to get another thin client and load 1.8 on it, and establish the IAX trunk,
>> which I imagine would be a simple exercise.
>> 
>> Thanks in advance for all your help!
>> 
>> Shane.
>> 
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>> 
>> 
>> 
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>> 
>> <Mail Attachment.txt>
>> 
>> 
>> 
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>> 