<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; ">You shouldn't have that much trouble making it all fly.<div>Nothing is as complicated as say, setting up a Cisco router using IOS...</div><div><br></div><div>You just have to understand some of the terminology, and get some signal polarities headed the right direction, so get the basics running on the workbench first.</div><div>Get the radios and the RTCMs talking to the AllStar server and make it vote/repeat like you want.</div><div>Be sure and have a service monitor handy so you can set audio and modulation levels. At that point you are good to go for installing on the mountains.</div><div><br></div><div>Let AllStar do as much of the repeater control as you possibly can, it's far more flexible than the built in repeater controllers. Ideally,</div><div>you would just have access to the RX and TX and feed them back to the AllStar box through the RTCM.</div><div><br></div><div>The phone stuff can be added later, since it's all done in the server on the ground.</div><div><br></div><div><br></div><div>I meant warm and cozy compared to the mountain tops...<br><div>Some of the data centers here in the Silicon Valley are in heavy energy conservation mode, so they run them uncomfortably warm.</div><div><br></div><div>The voting and linking is working pretty well with the RTCM system, but I hear the simulcast is not working so well.</div><div>(if you are not trying to do a single frequency simulcast where a receiver can hear both transmitters on the same freq, you are probably OK…)</div><div><br></div><div><br></div><div><br><div><div>On Mar 3, 2013, at 1:02 AM, "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;
font-family:Arial;
color:navy;}
span.EmailStyle19
{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 lang="EN-US" link="blue" vlink="purple" style="word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class="Section1"><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">I am very impressed with what you have
done but must admit that you’ve scare the stuffing out of me! I have built
several complete hosting data centers (behind a main providers infrastructure)
and can get around Linux. All I want for now are two mountain tops that will
get public links (each repeater can only see one control center) using
Ubiquity. I am AT site one and will provide internet. Site 2 can be seen by
repeater 2 and he will use Ubiquity to link up. At the end of the day they need
to see the datacenter. I’ll add phone patching later. We intend to
link/vote/simulcast.<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">Step one seems to be to get the RTC
installed. But as far as a warm and cozy data center? Ain’t gonna happen! They
are like refrigerators! LOL.<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> Sunday, March 03, 2013 12:37
AM<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">In your situation, I would use Micro-Node RTCM modules on the repeaters
to minimize the computer hardware on mountain tops.<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"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">All they need is some internet (or private ethernet) connectivity back
to the server in the warm cozy datacenter.<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">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..<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"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">The RTCM module is effectively a remote URI that uses ethernet instead
of a direct USB connection.<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">Ideally, you want the Allstar system to be the repeater controller for
the most flexibility, but <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">the RTCM will also do basic repeater control if the internet connection
dies.<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"><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"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">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.<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">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.<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">The radios can also dial extensions in my production servers.<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"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">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.<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"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">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<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">It is minimalist command line driven system with very steep learning
curve.<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"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">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<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">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. <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"><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"><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">On Mar 2, 2013, at 10:06 PM, "Bob - AF6D" <<a href="mailto:bob@af6d.com">bob@af6d.com</a>> wrote:<o:p></o:p></span></font></p>
</div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><br>
<br>
<o:p></o:p></span></font></p>
<u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><!--[if gte mso 9]><xml>
<u1:shapedefaults u2:ext="edit" spidmax="1026"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<u1:shapelayout u3:ext="edit">
<u1:idmap u3:ext="edit" data="1"/>
</u1:shapelayout>
</xml><![endif]-->
<div bgcolor="white" link="blue" vlink="purple"><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.<u1:p></u1:p></span></font><o:p></o:p></p><p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><u1:p> </u1:p></span></font><o:p></o:p></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 u4:st="on"><st1:place u4:st="on"><st1:state w:st="on"><st1:place w:st="on">California</st1:place></st1:state></st1:place></st1:state>. Just
enough to snow on my parade. For now then I need to configure each repeater and
the Thin Client.<u1:p></u1:p></span></font><o:p></o:p></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><u1:p></u1:p><o:p></o:p></p>
</div><p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><u1:p> </u1:p><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.<u1:p></u1:p><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.<u1:p></u1:p><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. <u1:p></u1:p><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"><u1:p> </u1:p><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:<u1:p></u1:p><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>
<u5:shapedefaults u2:ext="edit" spidmax="1026"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<u3:shapelayout u6:ext="edit">
<u3:idmap u6: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><u1:p></u1:p><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><u1:p></u1:p><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><u1:p></u1:p><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><u1:p></u1:p><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><u1:p></u1:p><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><u1:p></u1:p><o:p></o:p></span></font></p>
</div>
</blockquote>
</div>
</u1:smarttagtype></u1:smarttagtype></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>
</o:smarttagtype></o:smarttagtype></blockquote></div><br></div></div></body></html>