<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>In your situation, I would use Micro-Node RTCM modules on the repeaters to minimize the computer hardware on mountain tops.</div><div><br></div><div>All they need is some internet (or private ethernet) connectivity back to the server in the warm cozy datacenter.</div><div>The RTCM modules don't even need static or public IP addresses as long as they have an IP address for the server in the datacenter..</div><div><br></div><div>The RTCM module is effectively a remote URI that uses ethernet instead of a direct USB connection.</div><div>Ideally, you want the Allstar system to be the repeater controller for the most flexibility, but </div><div>the RTCM will also do basic repeater control if the internet connection dies.</div><div><br></div><div><br></div><div>Personally, I have an AllStar server that just talks to local radios over DMK URI modules, and it has an IAX connection to my "production" Asterisk phone servers.</div><div>The radios can be dialed as extensions from my main phone servers, and I can route an outside trunk directly to a radio if I want.</div><div>The radios can also dial extensions in my production servers.</div><div><br></div><div>You can setup dial plans in either the Allstar box (or the Asterisk server) that will only allow certain numbers to be dialed from the radios or codes that dial explicit numbers.</div><div><br></div><div>It's all very flexible. The biggest issue is that the ACID/apt_rpt distribution for AllStar is a fork of the main Asterisk distribution that is frozen at Asterisk 1.4</div><div>It is minimalist command line driven system with very steep learning curve.</div><div><br></div><div>I use PBX in a Flash Distributions of more modern Asterisk versions to connect to the outside world and do the heavy lifting. It's still a handful to learn, but it's mostly</div><div>a web GUI that is a lot easier to get things done, and it's a fairly secure distribution (with a very minimal attack surface) if you put it behind a firewall. </div><div><br></div><div><br></div><br><div><div>On Mar 2, 2013, at 10:06 PM, "Bob - AF6D" <<a href="mailto:bob@af6d.com">bob@af6d.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State">
<o:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="Section1"><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">This is excellent news! To be clear on
random connections, I’d like my own private network, but I’d also
like a public server. Can they be the same server? Not a problem either way. I
have rack space.<o:p></o:p></span></font></p><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">The reasons to use Allstar that you state
are the reasons we’ve chosen it. Snow has hampered us somewhat with
another storm brewing mid-week. We’re getting about one foot a week at
6,400 feet in So. <st1:state w:st="on"><st1:place w:st="on">California</st1:place></st1:state>.
Just enough to snow on my parade. For now then I need to configure each
repeater and the Thin Client.<o:p></o:p></span></font></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">
<hr size="2" width="100%" align="center" tabindex="-1">
</span></font></div><p class="MsoNormal"><b><font size="2" face="Tahoma"><span style="font-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size="2" face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma"> Don Hackler
[mailto:donh@<a href="http://sigma.net">sigma.net</a>] <br>
<b><span style="font-weight:bold">Sent:</span></b> Saturday, March 02, 2013
9:40 PM<br>
<b><span style="font-weight:bold">To:</span></b> Bob - AF6D<br>
<b><span style="font-weight:bold">Cc:</span></b>
<<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [App_rpt-users]
Motorola Phone Patch (Bob - AF6D)</span></font><o:p></o:p></p>
</div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p>
<div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">You won't have much trouble setting up what you want with some config
file hackage.<o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">Most of the phone patch "secret sauce" is just Asterisk
configuration. If you don't want random Allstar connections, you don't
need to allow them. The phone patch is easy to control. You will
need a sip trunk, either from an external provider, or you can put a SIP
adapter on a local POTS line. You will find that a cheap SIP trunk costs
less than a POTS line with adapter and works much better.<o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><br>
Radios are simply extensions on the asterisk system. This makes them very
flexible. <o:p></o:p></span></font></p>
</div>
<div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p>
</div>
<div><p class="MsoNormal" style="margin-bottom:12.0pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br>
On Mar 2, 2013, at 7:19 PM, "Bob - AF6D" <<a href="mailto:bob@af6d.com">bob@af6d.com</a>> wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" type="cite">
<div><!--[if gte mso 9]><xml>
<u1:shapedefaults u2:ext="edit" spidmax="1026"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<u3:shapelayout u4:ext="edit">
<u3:idmap u4:ext="edit" data="1"/>
</u3:shapelayout>
</xml><![endif]--><p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;
font-family:Arial">You have exposed my rookiness! LOL. I am aware that a thin
client hooked up acts like a controller. Fallback mode I guess. But I was under
the impression that there are open conference servers, or that others may call
our node if connected to the internet. I have much to learn.<u5:p></u5:p></span></font><o:p></o:p></p><p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;
font-family:Arial"><u5:p> </u5:p></span></font><o:p></o:p></p><p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;
font-family:Arial">Our plan remains the same. We intend to link both
MSF’s on different mountain tops via our own server. I own the hosting
company and have Tier 1 bandwidth at my beckon call. But we want to have our
own phone patch and have a phone line at our data center. Both nodes are true
public safety (ECS/ARES/SAR) and expenses come out of my wallet. It is my hope
that there is a way to add a phone patch that doesn’t cost us a recurring
fee.<u5:p></u5:p></span></font><o:p></o:p></p><p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;
font-family:Arial"><u5:p> </u5:p></span></font><o:p></o:p></p><p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;
font-family:Arial">With regards to our dedicated server I was under the
impression that we could have our own private network, and, a public network
for others to use. Giving back for fun and for free. But our phone patch would
be for our exclusive use. We envision macros that will telephone specific
numbers. I am Linux literate if I can create my own phone patch.<u5:p></u5:p></span></font><o:p></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" type="cite">
<div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><o:p></o:p></span></font></p>
</div>
</blockquote>
</div>
</div>
</o:smarttagtype></o:smarttagtype></blockquote></div><br></body></html>