[App_rpt-users] RTCM Commands
Tim Sawyer
tim.sawyer at mac.com
Sat Apr 19 15:08:51 UTC 2014
Wayne,
It is daunting at first but it will all clear up for you, honest.
RTCMs can be set up with or without a GPS. RTCMs with a GPS can vote, ones without a GPS cannot vote. With non-voting RTCMs the receiver is always selected and audio will mix with any other RTCMs on the same node.
In your case Site 1 and 2 will be voting RTCMs and Site 3 will be non-voting. Now, you have a couple of choices on how your system is configured. You could have two nodes (1000 and 1001) as shown in example 1. This configuration would allow you to connect and disconnect the nodes at will with Allstar touch tone commands. You can have a startup macro so site 3 automatically connects on boot up. This way also allows you to have different receive buffer lengths, a longer one for the internet connected site 3.
Or you could have only one node as shown in example 2. This assumes Site 3 is geographically or frequency separate from Sites 1 and 2 which I believe is true in your case. This way all 3 sites always transmit, sites 1 and 2 are voted and site 3 always is repeated. This way you have to have the receive buffer set for the slowest network, site 3.
voter.conf example 1
[general]
port = 667
password = BLAH
[1000]
Site1 = pswrd1,master,transmit
Site2 = pswrd2,transmit
buflen = 180
[1001]
Site3 = pswrd3,transmit
buflen = 280
voter.conf example 2
[general]
port = 667
password = BLAH
[1000]
Site1 = pswrd1,master,transmit
Site2 = pswrd2,transmit
Site3 = pswrd3,transmit
buflen = 280
--
Tim
:wq
On Apr 18, 2014, at 9:56 PM, Wayne <wayne at anywherehost.net> wrote:
> Tim,
>
> I am buying two RTCM's on Monday. But my key question still remains
> unanswered and I am frustrated. How do I link in Site 3 as an unvoted
> repeater? It only has public internet so I think I have to hard wire it to
> Site 1 to remain connected all the time. This is why I have asked several
> times if a RC-210 can have a URI plugged into port 1 and a link on port 2.
> Link port 2 -> 1. I have been told in private emails that this is how it is
> done.
>
> We have VLAN and Internet. VLAN is preferred. I can put a Linux box at the
> main site but how would a SSH box talk to VLAN from a public IP?
>
> Thank you for your time, Tim. I apologize if I appear dense at this point. I
> have read so much conflicting information that I am bordering lost. I mean,
> I have asked questions so that I might understand. Simple things like
> getting the ARRL news to play.
>
> {sigh]
>
> -----Original Message-----
> From: Tim Sawyer [mailto:tim.sawyer at mac.com]
> Sent: Friday, April 18, 2014 7:24 AM
> To: Wayne
> Cc: app_rpt mailing list
> Subject: Re: [App_rpt-users] RTCM Commands
>
> You'll need to have your ISP open a port or two depending on your system
> design. The server needs a port open for SSH and a port for IAX (IAX is the
> protocol Asterisk uses to link with other nodes).
>
> If you are going to run Echolink on your main server then you'll need those
> ports open. Or if you didn't want (or couldn't) open Echolink ports you
> could put up another server (at your house for example) and put Echolink on
> that and connect it to your main server with Allstar.
>
> The RTCM needs only telnet open. If the server and RTCMs are on the same
> LAN or VLAN, which is recommended, then you can SSH to the server and then
> telnet to the RTCMs, no need to have the ISP open telnet.
>
> SSH, IAX and telnet ports can be changed from their default values to any
> other port. App_rpt default SSH port is 222 but many people change it to
> something else. IAX default is 4569 and generally only needs to be changed
> if you have more than one server behind a public IP address.
>
> The lag is not bad if your server and RTCMs are on the same fast LAN or
> VLAN. Ping times consistently around 10ms or so will work really well.
> Assuming a voting or simulcast system, if you have even one RTCM on a slow
> network you have to increase buffer lengths for the entire system.
>
> Yes, if the internet goes down or gets slow during some sort of outage then
> it will be slow or impossible to SSH to your server. But if your server and
> RTCMs are on the same private (and functioning) network your radio system
> will still be 100% functional even if you can't SSH into it. And you'll
> still have touch tone control.
>
> Yes, there is no kerchunk filter in app_rpt. My experience is people still
> kerchunk even with a filter, they just key longer to get the repeater to
> come up. I understand other people feel it helps. Our developer has shown no
> interest in adding a repeater kerchunk filter. However, app_rpt is open
> source so a C programmer could add it.
>
> Time for you to jump in and get started. Go ahead and get at least one RTCM,
> build a server, connect a radio and set it all up at home. You'll know a lot
> more about the how it all works after you do that.
> --
> Tim
> :wq
>
> On Apr 18, 2014, at 2:12 AM, Wayne <wayne at anywherehost.net> 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.
>
>
>
> _______________________________________________
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140419/fc41430d/attachment.html>
More information about the App_rpt-users
mailing list