[App_rpt-users] RTCM Commands

Fri Apr 18 14:07:47 UTC 2014

Hi Wayne,

I re-read some earlier messages in this and related threads, to better
understand your systems design goals. And, the earlier threads have left
me with even more questions. From what I read, you've got a substantially
complex system planned. It's going to take some expert level work with
radios and computer networking to get setup, no matter what solution you
choose.  I believe it's all quite do-able with AllStar, but, is well
beyond the scope of this mailing list.

To address your specific questions, below:

1) Selling RC-210's should be simple enough (E-bay?).

2) Since you've got a private network and a public network involved, 
that's fine. But, this is a somewhat complex networking task. You'll need 
to get everything "talking together." I'm suspecting you'll want to 
implement some VPN's (Virtual Private Networks) to accomplish this. I use 
OpenVPN under Linux. It works great. BTW, I'm not sure RTCM's are the best 
solution. And, you don't need a Windows box at each site.

2) There is an small, unavoidable audio delay from audio input to output
with AllStar. This is typical with any VoIP radio system, including full
digital systems like D-Star and DMR, etc. This delay isn't like the delay
found in traditional analog linked repeater systems, however. In older
linked systems, you'd have to hold the PTT down for a second or so to
allow all the transmitters to come on-line or you'd loose that initial
audio. AllStar digitally buffers the audio during propagation from any
member receiver to all member transmitters. So, the audio could be
buffered and delayed as much as several hundred milliseconds (a big
network!). But, not typically lost.

3) As for persistent kerkhunkers and other issues, no hardware is going to
solve that. That is an etiquette problem. Over time, (most) users can be
trained to behave. Yes, I know you're saying: "Yeah, right. I hear you."
But, I help with several wide-coverage repeater systems, so, I've been
there, too.

4) Yes, you can hook various systems together (WX radios, remote bases,
etc.) into a single network quite easily with AllStar. But, it will likely
take some complex scripting and networking to do, just like with any
controller. I don't fully understand the scope of what you're wanting and
as I mentioned above, trying to build the system here is beyond the scope
of this mailing list.

I understand your overwhelm! I would recommend getting started in small 
steps, if possible. First, only put up a test repeater or remote base with 
AllStar and get a grasp of how that is setup. Then, add a second AllStar 
box and network the two together--take small steps. Now, if that's not a 
possibility--meaning you've got to have the whole system on-line "like 
tomorrow", you probably need to locate some expert help ASAP; due to the 
big learning curve with this (or any other) complex VoIP system.

Anyway, I hope this helps some.

73, David KB4FXC

On Fri, 18 Apr 2014, Wayne wrote:

> Thank you for taking the time to reply. I am ready to make the switch even
> though I just bought a new RC-210 and don't know how I am going to get rid
> of three of them. I don't know if I can resell them or if Arcom has an issue
> with that.
> 
> But I also have another issue in that our vendor has provided us with a VLAN
> and access to all of his sites over the 5.8GHz system. He also gave us an
> Internet gateway public IP. How would I control the RTCM's over a VLAN
> unless I place a Windows box at each site with SSH and connect to it that
> way? I don't even know how to do that. I would use a PC with two NIC's but I
> still don't know how I would do that. How would I bridge the two?
> 
> You mention audio delay... I am told that one weakness of Allstar is a lag.
> Of course since I have not used it yet I cannot speak to what they were
> referring to.
> 
> The purpose of going with this vendor was the speed of the VLAN and the
> ability to keep connectivity even if a huge earthquake takes out the
> Internet. I wanted the ability to use my cell phone with a SSH app to
> control the RTCM's. Am I stuck using public IP's and their inherent latency
> issues and potential loss in an emergency?
> 
> FWIW, I've been kerchunked all night and I am tired of hearing it.
> 
> One question still not answered is whether or not I can plug a URI into Port
> 1 on a RC-210 and then pull it into our Allstar group as an unvoted device
> with WX receiver, Earthquake Alarm and who knows what. Am I still better off
> using URI's on th4ese individual devices? What if, for example, I wanted to
> add a 6 meter transceiver for those folks out in the boonies or access
> during an opening? A URI or a RC-210? How would I pull in our unvoted desert
> link on a different pair? A URI?
> 
> I am sorry if I am being redundant. Frankly I am overwhelmed by well meaning
> answers from you fine gentlemen and those from IRLP actually recommending
> Allstar over IRLP.
> 
> I too would like to avoid IRLP.
> 
> -----Original Message-----
> From: David McGough [mailto:kb4fxc at inttek.net] 
> Sent: Tuesday, April 15, 2014 9:26 PM
> To: Wayne
> Cc: 'app_rpt mailing list'
> Subject: Re: [App_rpt-users] RTCM Commands
> 
> 
> Hi Wayne,
> 
> The AllStar software automatically attempts to limit Kerchunks and by
> design mutes received DTMF tones. There are also various audio delay
> features to solve squelch crashes, etc.--very much like "audio delay"  
> boards in traditional repeater controllers. I've got several busy
> repeaters on-line and, honestly, I can't imagine going back to a
> traditional repeater controller (like the controller you mention, etc.) at
> this point. It would be like stepping back in time to a motor scooter.
> Yes, a scooter is functional and reliable. But, it's a scooter!
> 
> AllStar is very feature rich and many IRLP reflectors also include AllStar
> connectivity these days; more do every day. Personally, I haven't missed 
> IRLP for a single moment.
> 
> Anyhow, just my $0.02
> 
> 73, David KB4FXC
> 
> 
> 
> On Tue, 15 Apr 2014, Wayne wrote:
> 
> > The cession has been made to switch yet now that the folks at IRLP have
> > convinced me ( :-) ) they are telling me the drawbacks and how expensive
> it
> > is.
> > 
> >  
> > 
> > BTW, thank you Tim for taking the time out of your day to reply with the
> > control commands. It makes the difference.
> > 
> >  
> > 
> > I see missing commands like Kerchunk Killer - is it by another name? On
> the
> > RC-21- as some of you know the SysOp, if you will, may set a timer so that
> > 500mS (or 25mS, whatever) delays the audio. Also, a DTMF mute. We have
> > jammers that love to hit DTMF all day. Is it by another name?
> > 
> >  
> > 
> > THANK YOU all for the extended time you have given me.
> > 
> >  
> > 
> >   _____  
> > 
> > From: Tim Sawyer [mailto:tim.sawyer at mac.com] 
> > Sent: Tuesday, April 15, 2014 7:38 AM
> > To: Wayne
> > Cc: app_rpt mailing list
> > Subject: Re: [App_rpt-users] RTCM Commands
> > 
> >  
> > 
> > The Drupal site (http://ohnosec.org/drupal/) documents most of what you
> can
> > do with app_rpt. Also, it the app_rpt source there is a list of commands.
> > These are used much like other controllers in that you map these to touch
> > tone commands. Here's the list taken from app_rpt.c
> > 
> >  
> > 
> >  * status cmds:
> > 
> >  *
> > 
> >  *  1 - Force ID (global)
> > 
> >  *  2 - Give Time of Day (global)
> > 
> >  *  3 - Give software Version (global)
> > 
> >  *  4 - Give GPS location info
> > 
> >  *  5 - Last (dtmf) user
> > 
> >  *  11 - Force ID (local only)
> > 
> >  *  12 - Give Time of Day (local only)
> > 
> >  *
> > 
> >  * cop (control operator) cmds:
> > 
> >  *
> > 
> >  *  1 - System warm boot
> > 
> >  *  2 - System enable
> > 
> >  *  3 - System disable
> > 
> >  *  4 - Test Tone On/Off
> > 
> >  *  5 - Dump System Variables on Console (debug)
> > 
> >  *  6 - PTT (phone mode only)
> > 
> >  *  7 - Time out timer enable
> > 
> >  *  8 - Time out timer disable
> > 
> >  *  9 - Autopatch enable
> > 
> >  *  10 - Autopatch disable
> > 
> >  *  11 - Link enable
> > 
> >  *  12 - Link disable
> > 
> >  *  13 - Query System State
> > 
> >  *  14 - Change System State
> > 
> >  *  15 - Scheduler Enable
> > 
> >  *  16 - Scheduler Disable
> > 
> >  *  17 - User functions (time, id, etc) enable
> > 
> >  *  18 - User functions (time, id, etc) disable
> > 
> >  *  19 - Select alternate hang timer
> > 
> >  *  20 - Select standard hang timer 
> > 
> >  *  21 - Enable Parrot Mode
> > 
> >  *  22 - Disable Parrot Mode
> > 
> >  *  23 - Birdbath (Current Parrot Cleanup/Flush)
> > 
> >  *  24 - Flush all telemetry
> > 
> >  *  25 - Query last node un-keyed
> > 
> >  *  26 - Query all nodes keyed/unkeyed
> > 
> >  *  27 - Reset DAQ minimum on a pin
> > 
> >  *  28 - Reset DAQ maximum on a pin
> > 
> >  *  30 - Recall Memory Setting in Attached Xcvr
> > 
> >  *  31 - Channel Selector for Parallel Programmed Xcvr
> > 
> >  *  32 - Touchtone pad test: command + Digit string + # to playback all
> > digits pressed
> > 
> >  *  33 - Local Telemetry Output Enable
> > 
> >  *  34 - Local Telemetry Output Disable
> > 
> >  *  35 - Local Telemetry Output on Demand
> > 
> >  *  36 - Foreign Link Local Output Path Enable
> > 
> >  *  37 - Foreign Link Local Output Path Disable
> > 
> >  *  38 - Foreign Link Local Output Path Follows Local Telemetry
> > 
> >  *  39 - Foreign Link Local Output Path on Demand
> > 
> >  *  42 - Echolink announce node # only
> > 
> >  *  43 - Echolink announce node Callsign only
> > 
> >  *  44 - Echolink announce node # & Callsign
> > 
> >  *  45 - Link Activity timer enable
> > 
> >  *  46 - Link Activity timer disable
> > 
> >  *  47 - Reset "Link Config Changed" Flag 
> > 
> >  *  48 - Send Page Tone (Tone specs separated by parenthesis)
> > 
> >  *  49 - Disable incoming connections (control state noice)
> > 
> >  *  50 - Enable incoming connections (control state noicd)
> > 
> >  *  51 - Enable sleep mode
> > 
> >  *  52 - Disable sleep mode
> > 
> >  *  53 - Wake up from sleep
> > 
> >  *  54 - Go to sleep
> > 
> >  *  55 - Parrot Once if parrot mode is disabled
> > 
> >  *  56 - Rx CTCSS Enable
> > 
> >  *  57 - Rx CTCSS Disable
> > 
> >  *  58 - Tx CTCSS On Input only Enable
> > 
> >  *  59 - Tx CTCSS On Input only Disable
> > 
> >  *  60 - Send MDC-1200 Burst (cop,60,type,UnitID[,DestID,SubCode])
> > 
> >  *     Type is 'I' for PttID, 'E' for Emergency, and 'C' for Call 
> > 
> >  *     (SelCall or Alert), or 'SX' for STS (ststus), where X is 0-F.
> > 
> >  *     DestID and subcode are only specified for  the 'C' type message.
> > 
> >  *     UnitID is the local systems UnitID. DestID is the MDC1200 ID of
> > 
> >  *     the radio being called, and the subcodes are as follows: 
> > 
> >  *          Subcode '8205' is Voice Selective Call for Spectra ('Call')
> > 
> >  *          Subcode '8015' is Voice Selective Call for Maxtrac ('SC') or
> > 
> >  *             Astro-Saber('Call')
> > 
> >  *          Subcode '810D' is Call Alert (like Maxtrac 'CA')
> > 
> >  *  61 - Send Message to USB to control GPIO pins
> > (cop,61,GPIO1=0[,GPIO4=1].....)
> > 
> >  *  62 - Send Message to USB to control GPIO pins, quietly
> > (cop,62,GPIO1=0[,GPIO4=1].....)
> > 
> >  *  63 - Send pre-configred APRSTT notification (cop,63,CALL[,OVERLAYCHR])
> > 
> >  *  64 - Send pre-configred APRSTT notification, quietly
> > (cop,64,CALL[,OVERLAYCHR]) 
> > 
> >  *  65 - Send POCSAG page (equipped channel types only)
> > 
> >  *
> > 
> >  * ilink cmds:
> > 
> >  *
> > 
> >  *  1 - Disconnect specified link
> > 
> >  *  2 - Connect specified link -- monitor only
> > 
> >  *  3 - Connect specified link -- tranceive
> > 
> >  *  4 - Enter command mode on specified link
> > 
> >  *  5 - System status
> > 
> >  *  6 - Disconnect all links
> > 
> >  *  7 - Last Node to Key Up
> > 
> >  *  8 - Connect specified link -- local monitor only
> > 
> >  *  9 - Send Text Message (9,<destnodeno or 0 (for all)>,Message Text,
> etc.
> > 
> >  *  10 - Disconnect all RANGER links (except permalinks)
> > 
> >  *  11 - Disconnect a previously permanently connected link
> > 
> >  *  12 - Permanently connect specified link -- monitor only
> > 
> >  *  13 - Permanently connect specified link -- tranceive
> > 
> >  *  15 - Full system status (all nodes)
> > 
> >  *  16 - Reconnect links disconnected with "disconnect all links"
> > 
> >  *  17 - MDC test (for diag purposes)
> > 
> >  *  18 - Permanently Connect specified link -- local monitor only
> > 
> >  
> > 
> >  *  200 thru 215 - (Send DTMF 0-9,*,#,A-D) (200=0, 201=1, 210=*, etc)
> > 
> >  *
> > 
> >  * remote cmds:
> > 
> >  *
> > 
> >  *  1 - Recall Memory MM  (*000-*099) (Gets memory from rpt.conf)
> > 
> >  *  2 - Set VFO MMMMM*KKK*O   (Mhz digits, Khz digits, Offset)
> > 
> >  *  3 - Set Rx PL Tone HHH*D*
> > 
> >  *  4 - Set Tx PL Tone HHH*D* (Not currently implemented with DHE RBI-1)
> > 
> >  *  5 - Link Status (long)
> > 
> >  *  6 - Set operating mode M (FM, USB, LSB, AM, etc)
> > 
> >  *  100 - RX PL off (Default)
> > 
> >  *  101 - RX PL On
> > 
> >  *  102 - TX PL Off (Default)
> > 
> >  *  103 - TX PL On
> > 
> >  *  104 - Low Power
> > 
> >  *  105 - Med Power
> > 
> >  *  106 - Hi Power
> > 
> >  *  107 - Bump Down 20 Hz
> > 
> >  *  108 - Bump Down 100 Hz
> > 
> >  *  109 - Bump Down 500 Hz
> > 
> >  *  110 - Bump Up 20 Hz
> > 
> >  *  111 - Bump Up 100 Hz
> > 
> >  *  112 - Bump Up 500 Hz
> > 
> >  *  113 - Scan Down Slow
> > 
> >  *  114 - Scan Down Medium
> > 
> >  *  115 - Scan Down Fast
> > 
> >  *  116 - Scan Up Slow
> > 
> >  *  117 - Scan Up Medium
> > 
> >  *  118 - Scan Up Fast
> > 
> >  *  119 - Transmit allowing auto-tune
> > 
> >  *  140 - Link Status (brief)
> > 
> >  *  200 thru 215 - (Send DTMF 0-9,*,#,A-D) (200=0, 201=1, 210=*, etc)
> > 
> >  *
> > 
> >  * playback cmds:
> > 
> >  *  specify the name of the file to be played globally (for example,
> > 25=rpt/foo)
> > 
> >  *
> > 
> >  * localplay cmds:
> > 
> >  * specify the name of the file to be played locally (for example,
> > 25=rpt/foo)
> > 
> >  *
> > 
> >  * 'duplex' modes:  (defaults to duplex=2)
> > 
> >  *
> > 
> >  * 0 - Only remote links key Tx and no main repeat audio.
> > 
> >  * 1 - Everything other then main Rx keys Tx, no main repeat audio.
> > 
> >  * 2 - Normal mode
> > 
> >  * 3 - Normal except no main repeat audio.
> > 
> >  * 4 - Normal except no main repeat audio during autopatch only
> > 
> >  *
> > 
> >  *
> > 
> > --
> > 
> > Tim
> > 
> > :wq
> > 
> >  
> > 
> > On Apr 15, 2014, at 2:17 AM, Wayne <wayne at anywherehost.net> wrote:
> > 
> > 
> > 
> > 
> > 
> > After reading that IRLP is banned from use on an IRLP box I am saddened,
> but
> > it makes my decision easier. I'll have to live without the RC-210's and go
> > with Allstar. I have been told however that a RC-210 may be linked in with
> a
> > URI but over-the-air DTMF will be confusing. We were going to use a
> computer
> > for cell phone control.
> > 
> >  
> > 
> > I would like to know what the command set is. Can someone point me to the
> > controller commands? Such as kerchunk filter (if it has one), DTMF mute,
> > etc.
> > 
> >  
> > 
> > We do have a phone patch. I assume that since Asterisks is a PBX system a
> > phone patch is built in somehow?
> > 
> > _______________________________________________
> > App_rpt-users mailing list
> >  <mailto:App_rpt-users at ohnosec.org> App_rpt-users at ohnosec.org
> >  <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > 
> > To unsubscribe from this list please visit
> > <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
> to
> > the bottom of the page. Enter your email address and press the
> "Unsubscribe
> > or edit options button"
> > You do not need a password to unsubscribe, you can do it via email
> > confirmation. If you have trouble unsubscribing, please send a message to
> > the list detailing the problem.
> > 
> >  
> > 
> > --
> > 
> > Tim
> > 
> > :wq
> > 
> >  
> > 
> > On Apr 15, 2014, at 2:17 AM, Wayne <wayne at anywherehost.net> wrote:
> > 
> > 
> > 
> > 
> > 
> > After reading that IRLP is banned from use on an IRLP box I am saddened,
> but
> > it makes my decision easier. I'll have to live without the RC-210's and go
> > with Allstar. I have been told however that a RC-210 may be linked in with
> a
> > URI but over-the-air DTMF will be confusing. We were going to use a
> computer
> > for cell phone control.
> > 
> >  
> > 
> > I would like to know what the command set is. Can someone point me to the
> > controller commands? Such as kerchunk filter (if it has one), DTMF mute,
> > etc.
> > 
> >  
> > 
> > We do have a phone patch. I assume that since Asterisks is a PBX system a
> > phone patch is built in somehow?
> > 
> > _______________________________________________
> > App_rpt-users mailing list
> >  <mailto:App_rpt-users at ohnosec.org> App_rpt-users at ohnosec.org
> >  <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > 
> > To unsubscribe from this list please visit
> > <http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users>
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
> to
> > the bottom of the page. Enter your email address and press the
> "Unsubscribe
> > or edit options button"
> > You do not need a password to unsubscribe, you can do it via email
> > confirmation. If you have trouble unsubscribing, please send a message to
> > the list detailing the problem.
> > 
> >  
> > 
> > 
> 
> 
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. 
> 