<p>Jim the simple repeat idea is good we just need to make sure it can id in that mode.</p>
<div class="gmail_quote">On Dec 22, 2011 5:35 PM, <<a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send App_rpt-users mailing list submissions to<br>
<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:app_rpt-users-request@ohnosec.org">app_rpt-users-request@ohnosec.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:app_rpt-users-owner@ohnosec.org">app_rpt-users-owner@ohnosec.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of App_rpt-users digest..."<br>
<br>Today's Topics:<br>
<br>
1. Re: Allstar RTCM (Radio Thin Client Module) is nowavailable<br>
(Marshall Oldham)<br>
2. Re: Allstar RTCM (Radio Thin Client Module) is nowavailable<br>
(<a href="mailto:michaelcarey@internode.on.net">michaelcarey@internode.on.net</a>)<br>
<br><br>---------- Forwarded message ----------<br>From: "Marshall Oldham" <<a href="mailto:ke6pcv@cal-net.org">ke6pcv@cal-net.org</a>><br>To: "'Jim Duuuude'" <<a href="mailto:telesistant@hotmail.com">telesistant@hotmail.com</a>>, <<a href="mailto:conny@tangandjonsson.com">conny@tangandjonsson.com</a>><br>
Cc: 'app_rpt mailing list' <<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>Date: Thu, 22 Dec 2011 13:42:57 -0800<br>Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable<br>
<u></u>
<div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial"><span>This would be a good function or to add in the
future firmware! </span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial"><span></span></font> </div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial"><span></span></font> </div>
<div dir="ltr" align="left">
<hr>
</div>
<div dir="ltr" align="left"><font face="Tahoma"><b>From:</b> Jim Duuuude
[mailto:<a href="mailto:telesistant@hotmail.com" target="_blank">telesistant@hotmail.com</a>] <br><b>Sent:</b> Thursday, December 22, 2011
12:51 PM<br><b>To:</b> <a href="mailto:conny@tangandjonsson.com" target="_blank">conny@tangandjonsson.com</a><br><b>Cc:</b> Marshall Oldham;
app_rpt mailing list<br><b>Subject:</b> RE: [App_rpt-users] Allstar RTCM (Radio
Thin Client Module) is nowavailable<br></font><br></div>
<blockquote style="BORDER-LEFT:#0000ff 2px solid;PADDING-LEFT:5px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px" dir="ltr">
<div></div>
<div dir="ltr">Not at the moment as the firmware currently stands. However,
that's not a bad idea.<br>It could simply act as a totally "dumb" controller
and just repeat the input back to<br>the output.<br><br>JIM<br><br>
<div>
<div></div>
<hr>
Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is
nowavailable<br>From: <a href="mailto:conny@tangandjonsson.com" target="_blank">conny@tangandjonsson.com</a><br>Date: Thu, 22 Dec 2011
13:46:17 -0700<br>CC: <a href="mailto:ke6pcv@cal-net.org" target="_blank">ke6pcv@cal-net.org</a>; <a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br>To:
<a href="mailto:telesistant@hotmail.com" target="_blank">telesistant@hotmail.com</a><br><br>
If you use RTCM
as "generic" radio interface on the hill and a linux box at a remote
location connected over an IP connection and you loose the connection can the
RTCM failover to be a minimal repeater controller on the hill?
<div><br></div>
<div>73 de N5HC</div>
<div>/Conny</div>
<div><br>
<div>
<div>On Dec 21, 2011, at 12:52 PM, Jim Duuuude wrote:</div><br>
<blockquote><span style="TEXT-TRANSFORM:none;TEXT-INDENT:0px;BORDER-COLLAPSE:separate;FONT:medium Helvetica;WHITE-SPACE:normal;LETTER-SPACING:normal;WORD-SPACING:0px">
<div style="FONT-FAMILY:Tahoma;FONT-SIZE:10pt">
<div dir="ltr">Yeah, that's the general idea. The location of the Linux server
running app_rpt/Asterisk can be<br>more or less anywhere within Internet
connectivity of all of the receiver and/or transmitter sites.<br>Of course,
"Internet" can mean either some sort of public Internet connection, or a
privately-provided<br>Internet connection (low-cost microwave link(s),
etc).<br><br>The only limitation is that an RTCM/Voter module *must* be
located on the same LAN as the Linux<br>server, to at least provide a
GPS-based timing reference. A system could be set up with a
server<br>located in some sort of datacenter "on the ground", and all the
radios could have an RTCM "on the<br>hill" with them, and as long as there
is Internet connectivity of some sort between each of them<br>and the
server, the system will work nicely. That is providing that there is an RTCM
located at<br>the server location also (whether or not that particular RTCM
has radio hardware connected to it<br>or not).<br><br>One minimal Linux
server can easily support 1 or 2 dozen RTCM's (on 1 or 2 allstar
nodes),<br>and a larger server could easily support MANY dozens of them on
dozens of allstar nodes.<br>Of course, you REALLY dont want to put too many
of them on a single server, being a potential<br>single point of failure.
For pretty much any practical purpose, the reasonable limitation is<br>the
point of failure/redundancy issue, not technical limitations.<br><br>I'm not
sure if you were clear on this, so I thought I would mention that the RTCM
is not just<br>usable as a GPS-timing-based Multi-Receiver Voting system
and/or a Simulcast Transmitter system.<br>It can also be used as a "generic"
radio interface for a conventional (non-GPS-based) either simplex<br>or full
duplex (repeater) radio. The advantage of doing this would be to not have
the Linux<br>host "on the hill" with the radio (as mentioned above). In
addition, the RTCM allows for<span> </span><br>portable/mobile operation
with a mobile/portable Internet connection in both the GPS-based<br>and
non-GPS-based environments.<span> </span><br><br>JIM WB6NIL<br><br><br>
<div>
<div></div>
<hr>
From:<span> </span><a href="mailto:ke6pcv@cal-net.org" target="_blank">ke6pcv@cal-net.org</a><br>To:<span> </span><a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br>Date:
Wed, 21 Dec 2011 10:54:18 -0800<br>Subject: Re: [App_rpt-users] Allstar RTCM
(Radio Thin Client Module) is nowavailable<br><br>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">I have been looking at the Allstar RTCM
(Radio Thin Client Module) and it really looks like a
GREAT product and addition to the already cool Allstar
hardware.</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Among all the other cool features of the
RTCM (Radio Thin Client Module) like Transmitter Simulcasting and
Receiver Voting, if</font></span><span><font color="#0000ff" face="Arial"><span> </span>I understand the
documentation</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">correctly you can use this very
small Radio Thin Client Module at a remote radio site to set up
an Allstar repeater node if the site has internet connection
without a COMPUTER at the site?</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Then you can point the node on the hilltop
back to a server on the ground somewhere that is easy to get
too? </font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">How many total sites can
you use Radio Thin Client Modules on and point back to
a single server on the ground? </font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">If this is the case, All I can say is WOW,
how cool!</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">73</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Marshall</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial"></font></span> </div><br>
<blockquote style="BORDER-LEFT:rgb(0,0,255) 2px solid;PADDING-LEFT:5px;MARGIN-LEFT:5px;MARGIN-RIGHT:0px" dir="ltr">
<div dir="ltr" lang="en-us" align="left">
<hr>
<font face="Tahoma"><b>From:</b><span> </span><a href="mailto:app_rpt-users-bounces@ohnosec.org" target="_blank">app_rpt-users-bounces@ohnosec.org</a><span> </span>[mailto:<a href="mailto:app_rpt-users-bounces@ohnosec.org" target="_blank">app_rpt-users-bounces@ohnosec.org</a>]<span> </span><b>On Behalf Of<span> </span></b>Mark
Guibord<br><b>Sent:</b><span> </span>Sunday, December 18, 2011
11:03 AM<br><b>To:</b><span> </span><a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br><b>Subject:</b><span> </span>[App_rpt-users] Allstar RTCM
(Radio Thin Client Module) is nowavailable<br></font><br></div>
<div></div>
<div><pre style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white"><span style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white;COLOR:black;FONT-SIZE:11pt">Allstar RTCM Radio Thin-Client Module, an Open-Source VOIP-Based Voting Multi-Receiver and Simulcast Transmit System is now available for purchase. </span></pre>
<pre style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white"><span style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white;COLOR:black;FONT-SIZE:11pt"> </span></pre><pre style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white"><span style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white;COLOR:black;FONT-SIZE:11pt">F</span><span style="COLOR:black;FONT-SIZE:11pt">or more information visit </span><span style="FONT-SIZE:11pt"><a href="http://micro-node.com/thin-m1.html" target="_blank">http://micro-node.com/thin-m1.html</a> </span></pre>
<pre style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white"><span style="COLOR:black;FONT-SIZE:11pt"> </span></pre><pre style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white"><span style="COLOR:black;FONT-SIZE:11pt">Regards,</span></pre>
<pre style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white"><span style="COLOR:black;FONT-SIZE:11pt">Mark Guibord</span></pre><pre style="BACKGROUND-IMAGE:none;BACKGROUND-COLOR:white"><span style="COLOR:black;FONT-SIZE:11pt">Micro-Node International</span></pre>
<p style="PADDING-BOTTOM:0px;PADDING-LEFT:0px;PADDING-RIGHT:0px;MARGIN-BOTTOM:0px;MARGIN-LEFT:0px;MARGIN-RIGHT:0px;PADDING-TOP:0px"><span style="FONT-FAMILY:'Courier New';FONT-SIZE:11pt"></span> </p>
<p style="PADDING-BOTTOM:0px;PADDING-LEFT:0px;PADDING-RIGHT:0px;MARGIN-BOTTOM:0px;MARGIN-LEFT:0px;MARGIN-RIGHT:0px;PADDING-TOP:0px"><span style="FONT-SIZE:11pt"></span> </p></div></blockquote><br>_______________________________________________
App_rpt-users mailing list<span> </span><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><span> </span><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a></div>
</div>_______________________________________________<br>App_rpt-users
mailing list<br><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><br><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
</div></span></blockquote></div><br></div></div></div></blockquote></div>
<br><br>---------- Forwarded message ----------<br>From: <a href="mailto:michaelcarey@internode.on.net">michaelcarey@internode.on.net</a><br>To: "Marshall Oldham" <<a href="mailto:ke6pcv@cal-net.org">ke6pcv@cal-net.org</a>>, "Jim Duuuude" <<a href="mailto:telesistant@hotmail.com">telesistant@hotmail.com</a>>, <a href="mailto:conny@tangandjonsson.com">conny@tangandjonsson.com</a><br>
Cc: app_rpt mailing list <<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>Date: Fri, 23 Dec 2011 09:05:37 +1030<br>Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable<br>
<div>I agree! <div><br></div><div>I was going to ask exactly the same question. Maybe this loss-of-connectivity-failover function could be enhanced to include a simple timed morse ID and dedicated repeater tail tone so you know immediately that something is wrong.</div>
<div><br></div><div>Michael.</div><div>VK5ZEA<br><br><blockquote><br>----- Original Message -----<br><div style="width:100%;background:rgb(228,228,228)"><div style="font-weight:bold">From:</div> "Marshall Oldham" <<a href="mailto:ke6pcv@cal-net.org" target="_blank">ke6pcv@cal-net.org</a>></div>
<br><div style="font-weight:bold">To:</div>"Jim Duuuude" <<a href="mailto:telesistant@hotmail.com" target="_blank">telesistant@hotmail.com</a>>, <<a href="mailto:conny@tangandjonsson.com" target="_blank">conny@tangandjonsson.com</a>><br>
<div style="font-weight:bold">Cc:</div>"app_rpt mailing list" <<a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a>><br><div style="font-weight:bold">Sent:</div>Thu, 22 Dec 2011 13:42:57 -0800<br>
<div style="font-weight:bold">Subject:</div>Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is nowavailable<br><br><br><div dir="ltr" align="left"><font color="#0000ff" face="Arial"><span>This would be a good function or to add in the
future firmware! </span></font></div>
<div dir="ltr" align="left">
<font color="#0000ff" face="Arial"><span></span></font> </div>
<div dir="ltr" align="left">
<font color="#0000ff" face="Arial"><span></span></font> </div>
<div dir="ltr" align="left">
<hr></div>
<div dir="ltr" align="left">
<font face="Tahoma"><b>From:</b> Jim Duuuude
[mailto:<a href="mailto:telesistant@hotmail.com" target="_blank">telesistant@hotmail.com</a>] <br><b>Sent:</b> Thursday, December 22, 2011
12:51 PM<br><b>To:</b> <a href="mailto:conny@tangandjonsson.com" target="_blank">conny@tangandjonsson.com</a><br><b>Cc:</b> Marshall Oldham;
app_rpt mailing list<br><b>Subject:</b> RE: [App_rpt-users] Allstar RTCM (Radio
Thin Client Module) is nowavailable<br></font><br></div>
<blockquote style="border-left:#0000ff 2px solid;padding-left:5px;margin-left:5px;margin-right:0px" dir="ltr">
<div></div>
<div dir="ltr">Not at the moment as the firmware currently stands. However,
that's not a bad idea.<br>It could simply act as a totally "dumb" controller
and just repeat the input back to<br>the output.<br><br>JIM<br><br><div>
<div></div>
<hr>
Subject: Re: [App_rpt-users] Allstar RTCM (Radio Thin Client Module) is
nowavailable<br>From: <a href="mailto:conny@tangandjonsson.com" target="_blank">conny@tangandjonsson.com</a><br>Date: Thu, 22 Dec 2011
13:46:17 -0700<br>CC: <a href="mailto:ke6pcv@cal-net.org" target="_blank">ke6pcv@cal-net.org</a>; <a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br>To:
<a href="mailto:telesistant@hotmail.com" target="_blank">telesistant@hotmail.com</a><br><br>If you use RTCM
as "generic" radio interface on the hill and a linux box at a remote
location connected over an IP connection and you loose the connection can the
RTCM failover to be a minimal repeater controller on the hill?
<div><br></div>
<div>73 de N5HC</div>
<div>/Conny</div>
<div>
<br><div>
<div>On Dec 21, 2011, at 12:52 PM, Jim Duuuude wrote:</div>
<br><blockquote><span style="text-transform:none;text-indent:0px;border-collapse:separate;font:medium Helvetica;letter-spacing:normal;word-spacing:0px">
</span><div style="font-family:Tahoma;font-size:10pt">
<div dir="ltr">Yeah, that's the general idea. The location of the Linux server
running app_rpt/Asterisk can be<br>more or less anywhere within Internet
connectivity of all of the receiver and/or transmitter sites.<br>Of course,
"Internet" can mean either some sort of public Internet connection, or a
privately-provided<br>Internet connection (low-cost microwave link(s),
etc).<br><br>The only limitation is that an RTCM/Voter module *must* be
located on the same LAN as the Linux<br>server, to at least provide a
GPS-based timing reference. A system could be set up with a
server<br>located in some sort of datacenter "on the ground", and all the
radios could have an RTCM "on the<br>hill" with them, and as long as there
is Internet connectivity of some sort between each of them<br>and the
server, the system will work nicely. That is providing that there is an RTCM
located at<br>the server location also (whether or not that particular RTCM
has radio hardware connected to it<br>or not).<br><br>One minimal Linux
server can easily support 1 or 2 dozen RTCM's (on 1 or 2 allstar
nodes),<br>and a larger server could easily support MANY dozens of them on
dozens of allstar nodes.<br>Of course, you REALLY dont want to put too many
of them on a single server, being a potential<br>single point of failure.
For pretty much any practical purpose, the reasonable limitation is<br>the
point of failure/redundancy issue, not technical limitations.<br><br>I'm not
sure if you were clear on this, so I thought I would mention that the RTCM
is not just<br>usable as a GPS-timing-based Multi-Receiver Voting system
and/or a Simulcast Transmitter system.<br>It can also be used as a "generic"
radio interface for a conventional (non-GPS-based) either simplex<br>or full
duplex (repeater) radio. The advantage of doing this would be to not have
the Linux<br>host "on the hill" with the radio (as mentioned above). In
addition, the RTCM allows for<span> </span><br>portable/mobile operation
with a mobile/portable Internet connection in both the GPS-based<br>and
non-GPS-based environments.<span> </span><br><br>JIM WB6NIL<br><br><br><div>
<div></div>
<hr>
From:<span> </span><a href="mailto:ke6pcv@cal-net.org" target="_blank">ke6pcv@cal-net.org</a><br>To:<span> </span><a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br>Date:
Wed, 21 Dec 2011 10:54:18 -0800<br>Subject: Re: [App_rpt-users] Allstar RTCM
(Radio Thin Client Module) is nowavailable<br><br><div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">I have been looking at the Allstar RTCM
(Radio Thin Client Module) and it really looks like a
GREAT product and addition to the already cool Allstar
hardware.</font></span></div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial">Among all the other cool features of the
RTCM (Radio Thin Client Module) like Transmitter Simulcasting and
Receiver Voting, if</font></span><span><font color="#0000ff" face="Arial"><span> </span>I understand the
documentation</font></span>
</div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">correctly you can use this very
small Radio Thin Client Module at a remote radio site to set up
an Allstar repeater node if the site has internet connection
without a COMPUTER at the site?</font></span></div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Then you can point the node on the hilltop
back to a server on the ground somewhere that is easy to get
too? </font></span></div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">How many total sites can
you use Radio Thin Client Modules on and point back to
a single server on the ground? </font></span></div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">If this is the case, All I can say is WOW,
how cool!</font></span></div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">73</font></span></div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial">Marshall</font></span></div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left">
<span><font color="#0000ff" face="Arial"></font></span> </div>
<br><blockquote style="border-left:rgb(0,0,255) 2px solid;padding-left:5px;margin-left:5px;margin-right:0px" dir="ltr">
<div dir="ltr" lang="en-us" align="left">
<hr><font face="Tahoma"><b>From:</b><span> </span><a href="mailto:app_rpt-users-bounces@ohnosec.org" target="_blank">app_rpt-users-bounces@ohnosec.org</a><span> </span>[mailto:<a href="mailto:app_rpt-users-bounces@ohnosec.org" target="_blank">app_rpt-users-bounces@ohnosec.org</a>]<span> </span><b>On Behalf Of<span> </span></b>Mark
Guibord<br><b>Sent:</b><span> </span>Sunday, December 18, 2011
11:03 AM<br><b>To:</b><span> </span><a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br><b>Subject:</b><span> </span>[App_rpt-users] Allstar RTCM
(Radio Thin Client Module) is nowavailable<br></font><br></div>
<div></div>
<div>
<pre style="background-image:none;background-color:#ffffff"><span style="background-image:none;background-color:#ffffff;color:#000000;font-size:11pt">Allstar RTCM Radio Thin-Client Module, an Open-Source VOIP-Based Voting Multi-Receiver and Simulcast Transmit System is now available for purchase. </span></pre>
<pre style="background-image:none;background-color:#ffffff"><span style="background-image:none;background-color:#ffffff;color:#000000;font-size:11pt"> </span></pre>
<pre style="background-image:none;background-color:#ffffff"><span style="background-image:none;background-color:#ffffff;color:#000000;font-size:11pt">F</span><span style="color:#000000;font-size:11pt">or more information visit </span><span style="font-size:11pt"><a href="http://micro-node.com/thin-m1.html" target="_blank">http://micro-node.com/thin-m1.html</a> </span></pre>
<pre style="background-image:none;background-color:#ffffff"><span style="color:#000000;font-size:11pt"> </span></pre>
<pre style="background-image:none;background-color:#ffffff"><span style="color:#000000;font-size:11pt">Regards,</span></pre>
<pre style="background-image:none;background-color:#ffffff"><span style="color:#000000;font-size:11pt">Mark Guibord</span></pre>
<pre style="background-image:none;background-color:#ffffff"><span style="color:#000000;font-size:11pt">Micro-Node International</span></pre>
<p style="padding-bottom:0px;padding-left:0px;padding-right:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;padding-top:0px"><span style="font-family:'Courier New';font-size:11pt"></span> </p>
<p style="padding-bottom:0px;padding-left:0px;padding-right:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;padding-top:0px"><span style="font-size:11pt"></span> </p>
</div>
</blockquote>
<br>_______________________________________________
App_rpt-users mailing list<span> </span><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><span> </span><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
</div>
</div>_______________________________________________<br>App_rpt-users
mailing list<br><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><br><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
</div></blockquote>
</div>
<br></div>
</div>
</div>
</blockquote>
</blockquote></div></div>
<br>_______________________________________________<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" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br></blockquote></div>