[arm-allstar] DTMF to link nodes?

Fri Oct 26 11:36:27 EDT 2018

Russ,

 You for review the function howto at hamvoip.org

You are doing *71 which is a disconnect not a connect code.

*3<node>  Connect
*1<node> Disconnect
*73<node> Connect Permanent
*71<node> Disconnect Permanent

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Fri, Oct 26, 2018 at 11:30 AM Russell Thomas <russell at kv4s.com> wrote:

> Ok, good news the node is receiving the dtmf fine.
>
> I think I just don't know the syntax to make a dtmf link/unlink. i tried
> the following with and without the *
>
> me attempting to link to IRLP 9667
> [Oct 26 10:22:48] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char *
> [Oct 26 10:22:50] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 7
> [Oct 26 10:22:50] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 1
> [Oct 26 10:22:53] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 8
> [Oct 26 10:22:54] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 9
> [Oct 26 10:22:54] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 6
> [Oct 26 10:22:55] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 6
> [Oct 26 10:22:55] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 7
>
> me trying to link to Allstar 2152
> [Oct 26 10:28:56] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char *
> [Oct 26 10:28:56] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 7
> [Oct 26 10:28:57] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 1
> [Oct 26 10:28:58] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 2
> [Oct 26 10:28:59] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 1
> [Oct 26 10:29:00] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 5
> [Oct 26 10:29:00] NOTICE[730]: chan_simpleusb.c:2689 simpleusb_read: Got
> DTMF char 2
>
> On Thu, Oct 25, 2018 at 7:35 AM Russell Thomas <russell at kv4s.com> wrote:
>
>> Thanks for the input now I know better where to look, I'll play around
>> with it and get back to you!
>>
>> On Thu, Oct 25, 2018 at 12:18 AM "Doug Crompton via ARM-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>>> A couple of notes on this -
>>>
>>> A service monitor is not needed to align levels for a simplex node. This
>>> is
>>> important as most do not have one nor have access to one.
>>>
>>> The bar graph in  simpleusb-tune-menu item 2 is a good way to set levels.
>>> This is your first step. The level should go up to 5khz on peaks as you
>>> talk normally on your radio. The word normally is important. This means
>>> how
>>> you would speak when you are not thinking about it. This includes how far
>>> your mouth is from the mic.
>>>
>>> Another way to check levels that works great is the windows iax-rpt
>>> application. Connect it to your node and observe the bar graph while
>>> talking. It should go to about 95% of full scale but not higher and never
>>> off-scale. This ensures you are at the full amplitude of the digital
>>> signal. We talk in terms of KHz of deviation but in the digital world you
>>> want to fully modulate the digital signal that is sent out over the
>>> Internet without going into clipping.
>>>
>>> This is the only level that would effect DTMF decode BUT the voice level
>>> and the DTMF level on many rigs may differ. Some DTMF mics actually have
>>> DTMF level controls inside or menu settings for levels.
>>>
>>> Also it is hard to see DTMF levels because they are normally muted unless
>>> they do not decode so to see them you would temporarily need to see the
>>> dtmf_dsp  command in simpleusb.conf.  By default it is set to 1 and this
>>> is
>>> the case if this command is NOT in the simpleusb.conf file. Placing the
>>> command in the file and setting to =2 would turn off muting and the DTMF
>>> level would show up. Do NOT forget to remove the command or set it back
>>> to
>>> =1 when you are done!
>>>
>>> dtmf_dsp=0    ; NO allstar command decoding, DTMF pass thru
>>> dtmf_dsp=1    ; Normal Allstar DTMF decoding and muting - this is the
>>> default
>>> dtmf_dsp=2    ; BOTH normal Allstar DTMF decoding AND DTMF pass thru. No
>>> muting
>>>
>>> When using the Asterisk client you do not need to set the verbose level
>>> and
>>> setting to verbose 9 would give you way too much information. Just run
>>> the
>>> Asterisk client from the main menu and key and press each DTMF button.
>>> The
>>> results will be shown on the screen Observe what doesn't work.
>>>
>>> The setting of  deemphasis in simpleusb-tune-menu will effect both voice
>>> and DTMF. There is only one right way for this setting either enabled or
>>> disabled. This depends on how audio comes from your radio. In most cases
>>> this would be disabled but if you are getting audio from your radio that
>>> is
>>> not deemphasized in the radio you would want to enable this.
>>>
>>> You want to have the PL or DCS (preferred) filter turned on in
>>> simple-usb-tune-menu.
>>>
>>> As pointed out if the radio is not on frequency it could cause a problem
>>> both in DTMF and voice response, Check this if you can with a frequency
>>> counter. The cheap Baofeng radios are often off frequency and there is an
>>> internal pot to adjust this.
>>>
>>> Personally I have found few radios that don't work but some are just
>>> plain
>>> bad and if you have an alternative radio then use it.
>>>
>>>
>>> *73 Doug*
>>>
>>> *WA3DSP*
>>>
>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>>
>>>
>>> On Thu, Oct 25, 2018 at 12:33 AM "Benjamin Naber via ARM-allstar" <
>>> arm-allstar at hamvoip.org> wrote:
>>>
>>> > Russel, et al-
>>> >
>>> > There are a few things you can check. I am going to assume others may
>>> > have at one time experienced this issue, as I have, so I am going to
>>> > include the particular commands and thought process... if there is one.
>>> >
>>> > First thing I would do is go into the asterisk console:
>>> > root at aslbox$ asterisk -r
>>> >
>>> > Then I would turn on asterisk console logging:
>>> > KB9LFZ-1*CLI> core set verbose 9
>>> >
>>> >
>>> > Then I would take the HT/mobile in question, of course on the node's
>>> > receive frequency, key the PTT and begin to mash the DTMF buttons:
>>> > You *should* get a response similar to:
>>> >
>>> > [Oct 24 22:35:28] NOTICE[1679]: chan_simpleusb.c:2910 simpleusb_read:
>>> > Got DTMF char *
>>> >
>>> >
>>> > Keep the PTT keyed, and slow-like, one at a time, mash all of the DTMF
>>> > keys in some logical sequence while watching the output.
>>> >
>>> > You may notice that some of the DTMF keys do not respond on the
>>> > asterisk console. There could be several reasons for this. Some of them
>>> > include:
>>> > - the node RX volume is not aligned
>>> > - the radio in question is not aligned
>>> >
>>> >
>>> > I would repeat the same test with other HTs and mobile radios you can
>>> > get your hands on.
>>> >
>>> >
>>> > The next step I would do is get a service monitor - find one, steal
>>> > one, beg someone with one to blow the dust of theirs and make good use
>>> > of it. Turn it on, wait for 30 minutes for its ref osc to settle, make
>>> > sure it says it has less than 1 Hz frequency error 5, 10, or 15MHz. Use
>>> > WWV while you can, it may go away!
>>> >
>>> > Using the simpleusb-tune-menu, accurately tune the RX to a close as you
>>> > can get the level at 3KHz mark on the tune-menu, using the service
>>> > monitor transmitting *only* a 1KHz tone at 3KHz deviation. It is best
>>> > to do this at least a -75 dBm signal directly fed into the node radio
>>> > antenna port.
>>> >
>>> > That step is absolutely critical for reliable receive operation.
>>> >
>>> >
>>> > The next thing I would do with that service monitor is make sure your
>>> > node radio is transmitting on the correct frequency, with no more than
>>> > 100Hz drift. All modern radios most of us own, have a master reference
>>> > oscillator the radio's transmitter and receiver use. If the transmitter
>>> > is off frequency, then the receiver on that same radio is going to be
>>> > off just by as much.
>>> >
>>> > If your node radio is off by more than 100Hz, take no other steps until
>>> > that is corrected. If it is a Chinese radio, hope off the slippery
>>> > slope of cheap junk and get one made by a company who has a reputation
>>> > to uphold. And who has a repair department. If you own an Android or
>>> > iPhone, getting reputable name-brand radio should not be an issue. New
>>> > or previously-enjoyed is your choice.
>>> >
>>> > While you are at it, measure the transmit frequency error of all of
>>> > your radios... after they have been powered on for an hour or so. This
>>> > will allow the ref osc to settle to a reasonable level.
>>> >
>>> >
>>> > If your node radio and radio you are using to talk to the ASL node
>>> > radio are on frequency, and within 100Hz of each other, the next thing
>>> > I would so is make sure your HT or mobile radio you are using is
>>> > transmitting the correct DTMF.... use that service monitor with it's
>>> > DTMF decode function to ensure your radio is encoding the DTMF buttons
>>> > correctly.
>>> >
>>> >
>>> > There are more levels to get deeper into, but those should get you
>>> > headed down the right path.
>>> >
>>> > Connect to our Tech Net Tuesday nights at 8PM Eastern to talk more
>>> > about it. Node 45221
>>> >
>>> >
>>> > Benjamin, KB9LFZ
>>> > ASL 28569
>>> >
>>> >
>>> >
>>> >
>>> > On Wed, 2018-10-24 at 14:35 -0500,
>>> > > Unless I've broke something, I've never been able to use my radio's
>>> > > dial
>>> > > pad to link and unlink nodes. (One reason being Supermon is amazing!!
>>> > > Thnx
>>> > > btw)
>>> > >
>>> > > I looked around on the site and unless I'm overlooking it I don't see
>>> > > instructions. I saw something along the lines but it appeared to be
>>> > > for
>>> > > autopatching vs linking.
>>> > >
>>> > > Can anyone point me in the right direction?
>>> > >
>>> > > 73,
>>> > > Russell Thomas, KV4S
>>> > > _______________________________________________
>>> > >
>>> > > 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
>>> >
>>> _______________________________________________
>>>
>>> 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
>>>
>>