<html><head></head><body bgcolor="#FFFFFF"><div>You won't have much trouble setting up what you want with some config file hackage.</div><div>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.</div><div><br>Radios are simply extensions on the asterisk system. This makes them very flexible. </div><div><br></div><div><br>On Mar 2, 2013, at 7:19 PM, "Bob - AF6D" <<a href="mailto:bob@af6d.com">bob@af6d.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* 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-compose;
font-family:Arial;
color:windowtext;}
@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 class="Section1">
<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.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;
font-family:Arial"><o:p> </o:p></span></font></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.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;
font-family:Arial"><o:p> </o:p></span></font></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.<o:p></o:p></span></font></p>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a></span><br><span><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br></div></blockquote></body></html>