[arm-allstar] How to Set Up a Kenwood TS-2000 as a Remote Base

Wed Feb 20 06:49:41 EST 2019

Steve,
Thanks for the script. It looks real nice. Appreciate the assistance.

John R. Chartkoff
Columbus, Ohio
Cell: 850-902-1147

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, February 19, 2019 12:00 PM, <arm-allstar-request at hamvoip.org> wrote:

> Send ARM-allstar mailing list submissions to
> arm-allstar at hamvoip.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> or, via email, send a message with subject or body 'help' to
> arm-allstar-request at hamvoip.org
>
> You can reach the person managing the list at
> arm-allstar-owner at hamvoip.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARM-allstar digest..."
>
> Today's Topics:
>
> 1.  Re: Strange messages on journalctl (David McGough)
> 2.  Error in iax.conf_tpl (Jim Cook)
> 3.  Re: Error in iax.conf_tpl (David McGough)
> 4.  DTMF Pager Tone generation (Irvin Fontanes)
> 5.  Re: How to Set Up a Kenwood TS-2000 as a Remote Base
>     (wb4bxo at mindspring.com)
>
>
> Message: 1
> Date: Mon, 18 Feb 2019 12:03:38 -0500 (EST)
> From: David McGough kb4fxc at inttek.net
> To: "\" Roger Coud? via ARM-allstar\"" arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Strange messages on journalctl
> Message-ID:
> Pine.LNX.4.44.1902181200040.24563-100000 at goliath.inttek.net
> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>
> Hi Roger,
>
> It looks like DNS is trying to resolve an IPv6 address for
> status.allstarlink.org. Take a look at this file:
>
> /etc/systemd/system/multi-user.target.wants
>
> ...Here is what that file should look like:
>
> <snip>------------------------------------------------------
>
> [Unit]
> Description=Internet domain name server
> After=network.target
>
> [Service]
> ExecStart=/usr/bin/named -4 -f -u named
> ExecReload=/usr/bin/rndc reload
> ExecStop=/usr/bin/rndc stop
>
> [Install]
> WantedBy=multi-user.target
>
> <snip>------------------------------------------------------
>
> Note the "-4" in the ExecStart definition. This only enables IPv4 and
> should be present for now.
>
> 73, David KB4FXC
>
> On Mon, 18 Feb 2019, "[UTF-8] Roger Coud?? via ARM-allstar" wrote:
>
> > I get those messages on two machines installed two years ago. Both are up-to-date and cannot find anything wrong in config files...
> > Feb 18 09:15:46 VA2RLD-U named[295]: DNS format error from 8.8.8.8#53 resolving status.allstarlink.org/AAAA for client 127.0.0.1#55488: Name . (NS) not subdomain of zone allstarlink.org -- invalid response
> > Feb 18 09:15:46 VA2RLD-U named[295]: FORMERR resolving 'status.allstarlink.org/AAAA/IN': 8.8.8.8#53
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
> --
>
> Message: 2
> Date: Mon, 18 Feb 2019 12:01:11 -0500
> From: Jim Cook radio.w8nsa at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: [arm-allstar] Error in iax.conf_tpl
> Message-ID: 6c4d831a-d6a8-acc7-bcdd-2d6b3f8d673d at gmail.com
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi Doug,
>
> I still see an error in the /etc/asterisk/iax.conf and the iax.conf_tpl
> files after the update.
>
> [myphone-iaxrpt]
>
> >
>
> >
>
> >
>
> calltokenoptional=
> 0.0.0.0/0.0.0.0
>
> Did I some how mess up applying the update?
>
> Jim -- W8NSA
> Petoskey, MI
>
>
> ------------------------------------------------------------------------------------------------------------
>
> Message: 3
> Date: Mon, 18 Feb 2019 12:08:04 -0500 (EST)
> From: David McGough kb4fxc at inttek.net
> To: "\"Jim Cook via ARM-allstar\"" arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Error in iax.conf_tpl
> Message-ID:
> Pine.LNX.4.44.1902181204460.24563-100000 at goliath.inttek.net
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hi Jim,
>
> Okay, I just corrected this and updated the package. I'm not sure how
> these newlines managed to make their way into these files.
>
> Please use option #1 to update and confirm that the template is fixed.
>
> 73, David KB4FXC
>
> On Mon, 18 Feb 2019, "Jim Cook via ARM-allstar" wrote:
>
> > Hi Doug,
> > I still see an error in the /etc/asterisk/iax.conf and the iax.conf_tpl
> > files after the update.
> > [myphone-iaxrpt]
> >
> > >
> >
> > calltokenoptional=
> > 0.0.0.0/0.0.0.0
> > Did I some how mess up applying the update?
> > Jim -- W8NSA
> > Petoskey, MI
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
> --
>
> Message: 4
> Date: Mon, 18 Feb 2019 18:55:36 -0600
> From: Irvin Fontanes irvinpr at gmail.com
> To: BeagleBone Black ARM Allstar arm-allstar at hamvoip.org
> Subject: [arm-allstar] DTMF Pager Tone generation
> Message-ID:
> CAJxP+vwXiYfd_qRXOL5VMr3m4K+ZToTqFEE7kz0zddt3FG5f=Q at mail.gmail.com
>
> Content-Type: text/plain; charset="UTF-8"
>
> In regards to:
> http://www.chrishoodblog.com/pass-dtmf-through-allstar-to-rc-210-repeater-controller/
>
> Problem:
> I have noticed that the "node" WILL NOT GENERATE DTMF TONES when commanded
> to to do so if COS happens to be active. Furthermore, if COS is active and
> the node is commanded to generate DTMF pager tones it will lock up the PTT
> requiring the asterisk server to be restarted.
>
> My solution:
> If COS is active, change the CTCSSFROM mode from NO to USBINVERT. This
> deactivates the COS and allows DTMF pager tones to be generated.
>
> Does anyone have any suggestions? My solution is somewhat cumbersome.
>
> Thanks!
>
>
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Message: 5
> Date: Mon, 18 Feb 2019 22:50:56 -0500
> From: wb4bxo at mindspring.com
> To: "ARM Allstar" arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] How to Set Up a Kenwood TS-2000 as a Remote
> Base
> Message-ID: 25F3357C503E48068441499E4477FA17 at QuickSilver
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> I have one that I use for an Icom IC-7000 and one I use for a Kenwood
> TM-V71A. Here's a link to a zip file and copy of the email describing it
> that I sent to another ham interested in it while back.
>
> You'll notice in some of the places I have the call to SayFreq commented
> out, you may want to uncomment them. I'm not completely satisfied with the
> frequency read back yet, it reads back when I'm using iaxrpt or zoiper
> directly to the node that has this, but I think it may also go out the radio
> port, so I want to play with that some more, just haven't had a chance. I
> want to be able to connect to the node this is on from my 220 repeater, do a
> *4xxxxx to control this "remote" node and set the frequency with it reading
> back to me, but it does not. I'm thinking of putting the radios on private
> ports like 1999 and 1998 set for no telemetry of any kind and then let the
> public node have the commands to control the radio and do the frequency read
> back and see if that would let me send it to remote connections but not out
> the remote controlled radio.
>
> Hope this helps. If you make any additions or improvements please pass them
> back to me to use too.
> Here's a link to them in a zip file on my DropBox since I don't think this
> mailing lists passes attachments. If you have problems getting it let me
> know and I'll put it somewhere else too.
> https://www.dropbox.com/s/ee99zi7d1aefsxo/WB4BXO-Remote.zip?dl=1
>
> 73's
> Steve - WB4BXO
>
> -----Original Message-----
> From: "Doug Crompton via ARM-allstar"
> Sent: Sunday, February 17, 2019 11:02 PM
> To: ARM Allstar
> Cc: Doug Crompton
> Subject: Re: [arm-allstar] How to Set Up a Kenwood TS-2000 as a Remote Base
>
> John,
>
> Hamlib is the way to go. Get it working with it first. hamlib is already
> in the SW so you can test it on your server via USB.
>
> Once all is working then you will have to create the commands in a script.
> This is something I have on my list to do but if anyone wants to tackle it
> please do. Basically a script that has all the pertinent hamlib commands.
> This would be mapped to DTMF commands. Then there would be a standard set
> of commands for any rig.
>
> Right now the best way to do this is the autopatch interface as describe in
> this howto at hamvoip.org -
>
> https://www.hamvoip.org/Allstar_extended_functions_using_autopatch.pdf
>
> This allows you to create a dialplan through the extensions file to pass to
> a script. So something like -
>
> *6201147030 would change a rig frequency to 147.03
>
> *62 indicates DTMF pass through to the extensions file. 01147030 is
> passed to the script.
> the first two digits are stripped in the script and become the command thus
> giving the option of 100 commands - 00-99. Here the command 01 indicates a
> frequency change command (F in hamlib) and 147030 is the frequency.
>
> For commands that return a response you would use the Allstar localplay
> command. So again as an example if you DTMF'ed the following -
>
> *6202
>
> The 02 command could be hamlib (rigctl) lowercase f which would playback
> the frequency of the radio when you unkeyed.
>
> To test in a very simple form you could directly call a script from a
> function line in rpt.conf but this would have to to be a separate function
> for each frequency or command. A way to test but not a long term solution.
>
> This of course is just an example. The idea is to get all of the outdated
> and buggy remote stuff out of the Allstar code which we will be doing soon.
> Having it in a user script makes it much more flexible.
>
> If you have any questions about this don't hesitate to ask.
>
> 73 Doug
>
> WA3DSP
>
> http://www.crompton.com/hamradio http://www.crompton.com/hamradio
>
> On Sun, Feb 17, 2019 at 10:42 PM "John via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Greetings to the group,
> > I am using a RPi2 running Hamvoip 1.5rc19, and attempting to configure a
> > Kenwood TS-2000 as a remote base, but am not sure how Allstar is
> > configured
> > to control the radio itself through its TTY port.
> > I am able to control the radio using Hamlib rigctld, bit not sure the best
> > way to translate DTMF commands from the Allstar user to set the various
> > parameters on the TS2000.
> > Is there an organic way to do this from within Allstar, using its
> > remote-base function, or do I need to write DTMF function macros to
> > execute
> > shell commands to rigctld to change parameters, and then use the URi
> > interface for audio and PTT? But then isn't it the same as a regular (non
> > remote-base) node?
> > So I believe my basic question is: in remote-base mode, how do the various
> > incoming DTMF control codes get translated to the rig control data stream
> > and where does that present itself on the node?
> > Any theory of operation for the remote base functionality would be most
> > appreciated.
> > Thanks,
> > John N1CTF
> > John R. Chartkoff
> > Columbus, Ohio
> > Cell: 850-902-1147
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Subject: Digest Footer
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
> ----------------------------------------------------------------------------------------------------------------
>
> End of ARM-allstar Digest, Vol 57, Issue 28