# DTMF number 3 Problem **URL:** \ **Category:** AllStarLink\ **Created:** [March 9, 2013, 4:42pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017 "2013-03-09T16:42:53Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Gazolla](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/g/c2a13f/32.png) [@Gazolla](https://community.allstarlink.org/u/Gazolla)\ **Post date:** [March 9, 2013, 4:42pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/1 "2013-03-09T16:42:53Z")
We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number "3" key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn't work. I have modified only two usbradio.conf settings: carrierfrom = usbinvert ctcssfrom = no When I change to: ctcssfrom = dsp we can neither TX or RX. Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. Thanks in advance, George ---
**Author:** ![Bryan\_D\_Boyle](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bryan_d_boyle/32/22_2.png) [@Bryan\_D\_Boyle](https://community.allstarlink.org/u/Bryan_D_Boyle)\ **Post date:** [March 9, 2013, 4:55pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/2 "2013-03-09T16:55:06Z")
wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. i'm thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i'm thinking you'll be fine, cheap chinese HTs notwithstanding. > **···** > > -- > Bryan > Sent from my iPhone 5...small > keyboard, big fingers...please > forgive misspellings... > > On Mar 9, 2013, at 11:42, George Zolla \ wrote: > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number "3" key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn't work. I have modified only two usbradio.conf settings: > > > > carrierfrom = usbinvert > > ctcssfrom = no > > > > When I change to: > > > > ctcssfrom = dsp > > > > we can neither TX or RX. > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > Thanks in advance, > > > > George > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![N9gmr](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/67e7ee/32.png) [@N9gmr](https://community.allstarlink.org/u/N9gmr)\ **Post date:** [March 9, 2013, 5:23pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/3 "2013-03-09T17:23:11Z")
I have difficulty getting my Wouxun radios to send tones that can be decoded on my repeater, unless I do the sequences long and slow. Matt Roberts n9gmr@me.com Call Sign N9GMR Allstar 28142 EchoLink 640860 > **···** > > On Mar 9, 2013, at 11:42 AM, George Zolla \ wrote: > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number "3" key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn't work. ---
**Author:** ![Tim\_Sawyer1](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/t/67e7ee/32.png) [@Tim\_Sawyer1](https://community.allstarlink.org/u/Tim_Sawyer1)\ **Post date:** [March 9, 2013, 5:34pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/4 "2013-03-09T17:34:06Z")
Be sure to turn on the RX PL filter. In usbradio.conf add plfilter=yes If you haven't already do a asterisk -rvvv and then watch the touchtones being decoded. > **···** > > -- > Tim > :wq > > On Mar 9, 2013, at 8:42 AM, George Zolla \ wrote: > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number "3" key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn't work. I have modified only two usbradio.conf settings: > > > > carrierfrom = usbinvert > > ctcssfrom = no > > > > When I change to: > > > > ctcssfrom = dsp > > > > we can neither TX or RX. > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > Thanks in advance, > > > > George > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![Gazolla](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/g/c2a13f/32.png) [@Gazolla](https://community.allstarlink.org/u/Gazolla)\ **Post date:** [March 9, 2013, 5:41pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/5 "2013-03-09T17:41:26Z")
Bryan, Unfortunately when I return the setting to the default: > > carrierfrom = dsp > > ctcssfrom = dsp I can receive or TX. Also some additional information from the operator: “Yaesu did not work. TYT worked. ICOM HT worked…don’t know about the mobile…And the Wouxun works well with other DTMF systems on Taos Ski Valley and NM Mega-Link…could be a wouxun problem, but don’t think so.” Your response and any other ideas are appreciated, George K6GAZ > **···** > > > > On Mar 9, 2013, at 8:55 AM, “Bryan D. Boyle” [bdboyle@bdboyle.com](mailto:bdboyle@bdboyle.com) wrote: > > > wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. > > > > i’m thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i’m thinking you’ll be fine, cheap chinese HTs notwithstanding. > > > > – > > Bryan > > Sent from my iPhone 5…small > > keyboard, big fingers…please > > forgive misspellings… > > > > On Mar 9, 2013, at 11:42, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number “3” key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn’t work. I have modified only two usbradio.conf settings: > > > > > > carrierfrom = usbinvert > > > ctcssfrom = no > > > > > > When I change to: > > > > > > ctcssfrom = dsp > > > > > > we can neither TX or RX. > > > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > > > Thanks in advance, > > > > > > George > > > > > > * * * > > > > > > App\_rpt-users mailing list > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![Gazolla](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/g/c2a13f/32.png) [@Gazolla](https://community.allstarlink.org/u/Gazolla)\ **Post date:** [March 9, 2013, 5:48pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/6 "2013-03-09T17:48:18Z")
Tim, I have added the line plfilter = yes to the usbradio.conf. I believe one member of our team watched the touchtones being decoded but I will double check on that. Thanks, George K6GAZ > **···** > > On Mar 9, 2013, at 9:34 AM, Tim Sawyer \ wrote: > > > Be sure to turn on the RX PL filter. In usbradio.conf add plfilter=yes > > > > If you haven't already do a asterisk -rvvv and then watch the touchtones being decoded. > > > > -- > > Tim > > :wq > > > > On Mar 9, 2013, at 8:42 AM, George Zolla \ wrote: > > > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number "3" key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn't work. I have modified only two usbradio.conf settings: > > > > > > carrierfrom = usbinvert > > > ctcssfrom = no > > > > > > When I change to: > > > > > > ctcssfrom = dsp > > > > > > we can neither TX or RX. > > > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > > > Thanks in advance, > > > > > > George > > > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > > App\_rpt-users mailing list > > > App\_rpt-users@ohnosec.org > > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![Gazolla](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/g/c2a13f/32.png) [@Gazolla](https://community.allstarlink.org/u/Gazolla)\ **Post date:** [March 9, 2013, 5:54pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/7 "2013-03-09T17:54:01Z")
Correction: I cannot TX or RX when I return to the default settings: carrierfrom = dsp ctcssfrom = dsp Sorry about that. > **···** > > On Mar 9, 2013, at 9:41 AM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > Bryan, > > > Unfortunately when I return the setting to the default: > > > > > carrierfrom = dsp > > > > ctcssfrom = dsp > > > I can receive or TX. Also some additional information from the operator: > > > > > > “Yaesu did not work. TYT worked. ICOM HT worked…don’t know about the mobile…And the Wouxun works well with other DTMF systems on Taos Ski Valley and NM Mega-Link…could be a wouxun problem, but don’t think so.” > > > > > > Your response and any other ideas are appreciated, > > > > > > George > > > K6GAZ > > > > > > > > > > > > > > > > > On Mar 9, 2013, at 8:55 AM, “Bryan D. Boyle” [bdboyle@bdboyle.com](mailto:bdboyle@bdboyle.com) wrote: > > > > wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. > > > > > > i’m thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i’m thinking you’ll be fine, cheap chinese HTs notwithstanding. > > > > > > – > > > Bryan > > > Sent from my iPhone 5…small > > > keyboard, big fingers…please > > > forgive misspellings… > > > > > > On Mar 9, 2013, at 11:42, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number “3” key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn’t work. I have modified only two usbradio.conf settings: > > > > > > > > carrierfrom = usbinvert > > > > ctcssfrom = no > > > > > > > > When I change to: > > > > > > > > ctcssfrom = dsp > > > > > > > > we can neither TX or RX. > > > > > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > > > > > Thanks in advance, > > > > > > > > George > > > > > > > > * * * > > > > > > > > App\_rpt-users mailing list > > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > ---
**Author:** ![Kb2ear](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/9de0a6/32.png) [@Kb2ear](https://community.allstarlink.org/u/Kb2ear)\ **Post date:** [March 9, 2013, 6:46pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/8 "2013-03-09T18:46:10Z")
While carrierfrom = dsp, ctcssfrom = dsp do the following: asterisk –r radio tune rxnoise Does the system tell you success of failure? If success do: Key radio with correct CTCSS tone encoded and type: radio tune rxtone Does it say success or failure? Please post results. > **···** > > **From:** [app\_rpt-users-bounces@ohnosec.org](mailto:app_rpt-users-bounces@ohnosec.org) [[mailto:app\_rpt-users-bounces@ohnosec.org](mailto:app_rpt-users-bounces@ohnosec.org)] **On Behalf Of** George Zolla > **Sent:** Saturday, March 09, 2013 12:54 PM > **To:** Bryan D. Boyle > **Cc:** John Wheatly; Chris Drummond; [app\_rpt-users@ohnosec.org](mailto:app_rpt-users@ohnosec.org); Wally Baker > **Subject:** Re: [App\_rpt-users] DTMF number 3 Problem > > Correction: > > I cannot TX or RX when I return to the default settings: > > carrierfrom = dsp > > ctcssfrom = dsp > > Sorry about that. > > On Mar 9, 2013, at 9:41 AM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > Bryan, > > Unfortunately when I return the setting to the default: > > > carrierfrom = dsp > > ctcssfrom = dsp > > I can receive or TX. Also some additional information from the operator: > > “Yaesu did not work. TYT worked. ICOM HT worked…don’t know about the mobile…And the Wouxun works well with other DTMF systems on Taos Ski Valley and NM Mega-Link…could be a wouxun problem, but don’t think so.” > > Your response and any other ideas are appreciated, > > George > > K6GAZ > > > On Mar 9, 2013, at 8:55 AM, “Bryan D. Boyle” [bdboyle@bdboyle.com](mailto:bdboyle@bdboyle.com) wrote: > > wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. > > i’m thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i’m thinking you’ll be fine, cheap chinese HTs notwithstanding. > > – > Bryan > Sent from my iPhone 5…small > keyboard, big fingers…please > forgive misspellings… > > On Mar 9, 2013, at 11:42, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number “3” key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn’t work. I have modified only two usbradio.conf settings: > > carrierfrom = usbinvert > ctcssfrom = no > > When I change to: > > ctcssfrom = dsp > > we can neither TX or RX. > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > Thanks in advance, > > George > > * * * > > App\_rpt-users mailing list > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![N5zua](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/ac91a4/32.png) [@N5zua](https://community.allstarlink.org/u/N5zua)\ **Post date:** [March 9, 2013, 7:24pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/9 "2013-03-09T19:24:01Z")
I too had this issue with a Wouxun at a repeater site and was scratching my head, until WB5UGT happened to look down at the deviation meter on my service monitor and told me to look for myself. Sure enough, upon pressing a DTMF key, the deviation meter shot to the far right and hit the pin on the 6 KHz scale. So, the first few milliseconds of DTMF blow out of the pass band, before calming down and stabilizing. Several other hand helds worked fine with no issues. N5ZUA > **···** > > ----- Original Message ----- From: "Bryan D. Boyle" \ > To: "George Zolla" \ > Cc: "John Wheatly" \; "Chris Drummond" \; \; "Wally Baker" \ > Sent: Saturday, March 09, 2013 10:55 AM > Subject: Re: [App\_rpt-users] DTMF number 3 Problem > > > wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. > > > > i'm thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i'm thinking you'll be fine, cheap chinese HTs notwithstanding. > > > > -- > > Bryan > > Sent from my iPhone 5...small > > keyboard, big fingers...please > > forgive misspellings... > > > > On Mar 9, 2013, at 11:42, George Zolla \ wrote: > > > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number "3" key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn't work. I have modified only two usbradio.conf settings: > > > > > > carrierfrom = usbinvert > > > ctcssfrom = no > > > > > > When I change to: > > > > > > ctcssfrom = dsp > > > > > > we can neither TX or RX. > > > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > > > Thanks in advance, > > > > > > George ---
**Author:** ![Gazolla](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/g/c2a13f/32.png) [@Gazolla](https://community.allstarlink.org/u/Gazolla)\ **Post date:** [March 9, 2013, 8:37pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/10 "2013-03-09T20:37:46Z")
Great idea! I had already se the carrier from = usbinvert and ctcssfrom = no before we ran the tune checks. I will ask the radio technician on site to redo the test. (I am offsite) > **···** > > On Mar 9, 2013, at 10:46 AM, "Scott Weis" \ wrote: > > > While carrierfrom = dsp, ctcssfrom = dsp do the following: > > > > asterisk –r > > radio tune rxnoise > > > > Does the system tell you success of failure? > > > > If success do: > > > > Key radio with correct CTCSS tone encoded and type: > > > > radio tune rxtone > > > > Does it say success or failure? > > > > Please post results. > > > > From: app\_rpt-users-bounces@ohnosec.org [mailto:app\_rpt-users-bounces@ohnosec.org] On Behalf Of George Zolla > > Sent: Saturday, March 09, 2013 12:54 PM > > To: Bryan D. Boyle > > Cc: John Wheatly; Chris Drummond; app\_rpt-users@ohnosec.org; Wally Baker > > Subject: Re: [App\_rpt-users] DTMF number 3 Problem > > > > Correction: > > > > I cannot TX or RX when I return to the default settings: > > > > carrierfrom = dsp > > ctcssfrom = dsp > > > > Sorry about that. > > > > On Mar 9, 2013, at 9:41 AM, George Zolla \ wrote: > > > > Bryan, > > > > Unfortunately when I return the setting to the default: > > > > carrierfrom = dsp > > ctcssfrom = dsp > > > > I can receive or TX. Also some additional information from the operator: > > > > "Yaesu did not work. TYT worked. ICOM HT worked...don't know about the mobile...And the Wouxun works well with other DTMF systems on Taos Ski Valley and NM Mega-Link...could be a wouxun problem, but don't think so." > > > > Your response and any other ideas are appreciated, > > > > George > > K6GAZ > > > > On Mar 9, 2013, at 8:55 AM, "Bryan D. Boyle" \ wrote: > > > > wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. > > > > i'm thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i'm thinking you'll be fine, cheap chinese HTs notwithstanding. > > > > -- > > Bryan > > Sent from my iPhone 5...small > > keyboard, big fingers...please > > forgive misspellings... > > > > On Mar 9, 2013, at 11:42, George Zolla \ wrote: > > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number "3" key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn't work. I have modified only two usbradio.conf settings: > > > > carrierfrom = usbinvert > > ctcssfrom = no > > > > When I change to: > > > > ctcssfrom = dsp > > > > we can neither TX or RX. > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > Thanks in advance, > > > > George > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ > > App\_rpt-users mailing list > > App\_rpt-users@ohnosec.org > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![Wb6egr](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/a3d4f5/32.png) [@Wb6egr](https://community.allstarlink.org/u/Wb6egr)\ **Post date:** [March 9, 2013, 9:15pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/11 "2013-03-09T21:15:55Z")
The $50 radios tend to suffer from “Twist” when sending touchtones. Some don’t even have Pre/De on the transmit/receive audio! Some manufactures think that 2Khz of deviation is OK, others think 6Khz is better.PL levels are all over the place too! I set my Motorola stuff to 700Hz of PL deviation…seen some Baofengs doing 200Hz…another one was 1Khz of PL… My though on this? set your system up with a REAL RADIO.Tell the ching-chong, bing bong (with eggroll) radio owners to GET THEM TUNED UP AND ALIGNED… Why butcher your system to accept their substandard emissions? Kirk > **···** > > On Sat, Mar 9, 2013 at 10:37 AM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > Great idea! I had already se the carrier from = usbinvert and ctcssfrom = no before we ran the tune checks. > > > I will ask the radio technician on site to redo the test. (I am offsite) > > > On Mar 9, 2013, at 10:46 AM, “Scott Weis” [kb2ear@kb2ear.net](mailto:kb2ear@kb2ear.net) wrote: > > > > While carrierfrom = dsp, ctcssfrom = dsp do the following: > > > > > > > > asterisk –r > > > > radio tune rxnoise > > > > > > > > Does the system tell you success of failure? > > > > > > > > If success do: > > > > > > > > Key radio with correct CTCSS tone encoded and type: > > > > > > > > radio tune rxtone > > > > > > > > Does it say success or failure? > > > > > > > > Please post results. > > > > > > > > > > > > **From:** [app\_rpt-users-bounces@ohnosec.org](mailto:app_rpt-users-bounces@ohnosec.org) [[mailto:app\_rpt-users-bounces@ohnosec.org](mailto:app_rpt-users-bounces@ohnosec.org)] \*\*On Behalf Of \*\*George Zolla > > > **Sent:** Saturday, March 09, 2013 12:54 PM > > > **To:** Bryan D. Boyle > > > **Cc:** John Wheatly; Chris Drummond; [app\_rpt-users@ohnosec.org](mailto:app_rpt-users@ohnosec.org); Wally Baker > > > **Subject:** Re: [App\_rpt-users] DTMF number 3 Problem > > > > > > > > Correction: > > > > > > > > I cannot TX or RX when I return to the default settings: > > > > > > > > carrierfrom = dsp > > > > ctcssfrom = dsp > > > > > > > > Sorry about that. > > > > > > > > On Mar 9, 2013, at 9:41 AM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > > > > > Bryan, > > > > > > > > Unfortunately when I return the setting to the default: > > > > > > > > > carrierfrom = dsp > > > > ctcssfrom = dsp > > > > > > > > I can receive or TX. Also some additional information from the operator: > > > > > > > > “Yaesu did not work. TYT worked. ICOM HT worked…don’t know about the mobile…And the Wouxun works well with other DTMF systems on Taos Ski Valley and NM Mega-Link…could be a wouxun problem, but don’t think so.” > > > > > > > > Your response and any other ideas are appreciated, > > > > > > > > George > > > > K6GAZ > > > > > > > > > > > > > > > > > > > > > > > > > On Mar 9, 2013, at 8:55 AM, “Bryan D. Boyle” [bdboyle@bdboyle.com](mailto:bdboyle@bdboyle.com) wrote: > > > > > > > > wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. > > > > > > i’m thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i’m thinking you’ll be fine, cheap chinese HTs notwithstanding. > > > > > > – > > > Bryan > > > Sent from my iPhone 5…small > > > keyboard, big fingers…please > > > forgive misspellings… > > > > > > On Mar 9, 2013, at 11:42, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number “3” key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn’t work. I have modified only two usbradio.conf settings: > > > > > > carrierfrom = usbinvert > > > ctcssfrom = no > > > > > > When I change to: > > > > > > ctcssfrom = dsp > > > > > > we can neither TX or RX. > > > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > > > Thanks in advance, > > > > > > George > > > > > > * * * > > > > > > App\_rpt-users mailing list > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > > > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > > > > > > > * * * > > > > > > App\_rpt-users mailing list > > > > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > * * * > > > > App\_rpt-users mailing list > > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![Gazolla](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/g/c2a13f/32.png) [@Gazolla](https://community.allstarlink.org/u/Gazolla)\ **Post date:** [March 11, 2013, 3:45am UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/12 "2013-03-11T03:45:09Z")
Thanks of everyone’s inputs on this problem an insight into the Wouxun HT problems. For reveiw I have been helping a young ARC install an AllStar system (a couple of states away form my location). Since it is not feasible for everyone to buy a new HT, we have decided to change out the radio to an Alinco DR-135 which I own and works with Wouxun HTs on my AllStar site. > **···** > > On Mar 9, 2013, at 1:15 PM, Kirk Just Kirk [wb6egr@gmail.com](mailto:wb6egr@gmail.com) wrote: > > > The $50 radios tend to suffer from “Twist” when sending touchtones. Some don’t even have Pre/De on the transmit/receive audio! > > Some manufactures think that 2Khz of deviation is OK, others think 6Khz is better.PL levels are all over the place too! I set my Motorola > > > stuff to 700Hz of PL deviation…seen some Baofengs doing 200Hz…another one was 1Khz of PL… > > > My though on this? set your system up with a REAL RADIO.Tell the ching-chong, bing bong (with eggroll) radio owners to GET THEM TUNED UP AND ALIGNED… > > > Why butcher your system to accept their substandard emissions? > > > > > > Kirk > > > > On Sat, Mar 9, 2013 at 10:37 AM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > > Great idea! I had already se the carrier from = usbinvert and ctcssfrom = no before we ran the tune checks. > > > > I will ask the radio technician on site to redo the test. (I am offsite) > > > > On Mar 9, 2013, at 10:46 AM, “Scott Weis” [kb2ear@kb2ear.net](mailto:kb2ear@kb2ear.net) wrote: > > > > > While carrierfrom = dsp, ctcssfrom = dsp do the following: > > > > > > > > > > asterisk –r > > > > > radio tune rxnoise > > > > > > > > > > Does the system tell you success of failure? > > > > > > > > > > If success do: > > > > > > > > > > Key radio with correct CTCSS tone encoded and type: > > > > > > > > > > radio tune rxtone > > > > > > > > > > Does it say success or failure? > > > > > > > > > > Please post results. > > > > > > > > > > > > > > > **From:** [app\_rpt-users-bounces@ohnosec.org](mailto:app_rpt-users-bounces@ohnosec.org) [[mailto:app\_rpt-users-bounces@ohnosec.org](mailto:app_rpt-users-bounces@ohnosec.org)] \*\*On Behalf Of \*\*George Zolla > > > > **Sent:** Saturday, March 09, 2013 12:54 PM > > > > **To:** Bryan D. Boyle > > > > **Cc:** John Wheatly; Chris Drummond; [app\_rpt-users@ohnosec.org](mailto:app_rpt-users@ohnosec.org); Wally Baker > > > > **Subject:** Re: [App\_rpt-users] DTMF number 3 Problem > > > > > > > > > > Correction: > > > > > > > > > > I cannot TX or RX when I return to the default settings: > > > > > > > > > > carrierfrom = dsp > > > > > ctcssfrom = dsp > > > > > > > > > > Sorry about that. > > > > > > > > > > On Mar 9, 2013, at 9:41 AM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > > > > > > > Bryan, > > > > > > > > > > Unfortunately when I return the setting to the default: > > > > > > > > > > > carrierfrom = dsp > > > > > ctcssfrom = dsp > > > > > > > > > > I can receive or TX. Also some additional information from the operator: > > > > > > > > > > “Yaesu did not work. TYT worked. ICOM HT worked…don’t know about the mobile…And the Wouxun works well with other DTMF systems on Taos Ski Valley and NM Mega-Link…could be a wouxun problem, but don’t think so.” > > > > > > > > > > Your response and any other ideas are appreciated, > > > > > > > > > > George > > > > > K6GAZ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mar 9, 2013, at 8:55 AM, “Bryan D. Boyle” [bdboyle@bdboyle.com](mailto:bdboyle@bdboyle.com) wrote: > > > > > > > > > > wouxuns are kind of notorious for poor DTMF encoding, levels, etc. for the price, kind of to be expected. YGWYPF. > > > > > > > > i’m thinking the motos were set up to put cor, etc out in hardware. your changes told asterisk to ignore the hardware signals. put them back the way they were working before you fiddled with them, and i’m thinking you’ll be fine, cheap chinese HTs notwithstanding. > > > > > > > > – > > > > Bryan > > > > Sent from my iPhone 5…small > > > > keyboard, big fingers…please > > > > forgive misspellings… > > > > > > > > On Mar 9, 2013, at 11:42, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > > We recently installed AllStar on an old PC. At present we have a 10 year old Motorola 2M Radius radio connected to the AllStar PC via a custom cable and URI. The radio was tuned by a professional with tuning equipment according to the AllStar instructions. We can RX well and can TX voice well on all radios. Now the problem. Some radios (Yaesu & Icon) can send any DTMF number combination and works flawlessly. However some other radios like the Wouxun can send any number but the number “3” key successfully. For instance \*81 gives us the time successfully but 3 used in any string doesn’t work. I have modified only two usbradio.conf settings: > > > > > > > > carrierfrom = usbinvert > > > > ctcssfrom = no > > > > > > > > When I change to: > > > > > > > > ctcssfrom = dsp > > > > > > > > we can neither TX or RX. > > > > > > > > Is there another setting that might help in the usbrdio.conf or any other config file? Can anyone help? It is a young ARC and most members use a Wouxon HT. > > > > > > > > Thanks in advance, > > > > > > > > George > > > > > > > > * * * > > > > > > > > App\_rpt-users mailing list > > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > > > > > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > > > > > > > > > > * * * > > > > > > > > App\_rpt-users mailing list > > > > > > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > > > > > > * * * > > > > > > App\_rpt-users mailing list > > > > > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > > > > > [http://ohnosec.org/cgi-bin/mailman/listinfo/app\_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) > > > ---
**Author:** ![Bryan\_D\_Boyle](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bryan_d_boyle/32/22_2.png) [@Bryan\_D\_Boyle](https://community.allstarlink.org/u/Bryan_D_Boyle)\ **Post date:** [March 11, 2013, 12:59pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/13 "2013-03-11T12:59:54Z")
Thank you, Kirk... \ Which is part of the image problem we hams sometimes suffer from...accepting 'good enough' or hacking things together to 'just make it work' because the alternative is to hold cheap vendors' feet (or our fellow hams') feet to the fire to actually set things up the way that agreed-upon best practices have developed. IMHO, and this is based on years of experience in the broadcast engineering, communications systems (telco, RF, and IP), and our hobby...it's the responsibility of the service provider (in this case, we repeater owners) to build a system that meets the standards of the service. If the end user (ie cheap ham with a throw-away radio) is not able to use a standard-compliant system, it's NOT UP TO THE PROVIDER to degrade the common system to account for the junk that's trying to use it. It's up to the end user to ensure compatibility...as long as the core system is doing what it's supposed to...no one likes to be told that their equipment is not working properly...but, if it isn't...then it isn't. It's not personal. Seems to me, whether it's either a young or long-in-the-tooth ham club, this is an opportunity for both a teaching moment and a chance to do a maintenance session. Find someone with a good, compliant SM, sig gen, maybe a scope, set a time, and have a 'tune up' session at a common location. Adjust deviation, PL injection, etc. Teach WHY it's important that these things are done. Show WHY when things are aligned properly the system works better. Show HOW all the parameters interact. Teach good procedure. The results will be worth it. We've shot ourselves in the foot with appliance radios (I offered, a couple years ago, to host anyone that wanted to use my second HF rig in the shack to do a multiple op session for a QSO party...the fact that my radios have the dreaded "tune" and "load" knobs kept all but the gray hairs away...most of the folks in the club had NEVER tuned a rig the way a deity intended...content with twisting in a frequency, pushing a 'tune' button, letting the relays chatter...and happily keying the mic...); but behind those appliances, there are still controls that need be set properly if it's expected that good results are attained. You can't get around crappy design (no pre/de? Yikes. Value engineering at its worst) or basic instability (I note, with amusement, that the Kenyaecom rigs never seem, as a whole, to have these problems ...but then, you DO get what you pay for...). But, within the limits of these throw-aways, you can improve them just by opening them up, injecting a signal, and tweaking as needed (as long as you have the service manuals..) to bring them into compliance with the standards of our service. Full disclosure: I own Alincos, Jetstreams, Wouxuns, Baofengs, Motorolas, Kenwoods, etc. All of them have been opened on the bench, run through the SM drill, and work/sound just fine...I don't know anyone in my circle who has ever said anything other than 'those things sound great...'. Heck, with a Wouxun KG1 @5W and an external triband antenna on my car, being fed with RG142, I was talking on a machine Thursday last from 40 miles away...machine in central NJ, me in and out of tree lines in Bucks Cnty PA on the other side of the Delaware...noisy, but 100% copyable...which would not be the case if it hadn't been set up on the bench for deviation, PL level, frequency, and power). So, it can be done. Just takes a little time and effort...and my repeaters are set up, on the hardware side, with an SM and sig gen...the results speak for themselves. I know we work on gentleman's agreements as to what compliance means. Doesn't mean we should not have, as a goal, doing the best we can. We bitch and moan when people deviate too far from good operating procedure on the air...we should except no less from expectations about how the equipment is working, either. \ > **···** > > > On Mar 9, 2013, at 1:15 PM, Kirk Just Kirk \ wrote: > > > > > The $50 radios tend to suffer from "Twist" when sending touchtones. Some don't even have Pre/De on the transmit/receive audio! > > > Some manufactures think that 2Khz of deviation is OK, others think 6Khz is better.PL levels are all over the place too! I set my Motorola > > > stuff to 700Hz of PL deviation..seen some Baofengs doing 200Hz..another one was 1Khz of PL... > > > My though on this? set your system up with a REAL RADIO.Tell the ching-chong, bing bong (with eggroll) radio owners to GET THEM TUNED UP AND ALIGNED..... > > > Why butcher your system to accept their substandard emissions? > > -- > Bryan WB0YLE > In this world, you must be oh so smart or oh so pleasant. > Well, for years I was smart. I recommend pleasant. > You may quote me. > > Sent from my MacBook Pro. ---
**Author:** ![Tim\_Sawyer1](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/t/67e7ee/32.png) [@Tim\_Sawyer1](https://community.allstarlink.org/u/Tim_Sawyer1)\ **Post date:** [March 11, 2013, 2:15pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/14 "2013-03-11T14:15:52Z")
So, you’re going to use one piece of crap radio to make another piece of crap radio work? > **···** > > – > > Tim > > :wq > > On Mar 10, 2013, at 8:45 PM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > Thanks of everyone’s inputs on this problem an insight into the Wouxun HT problems. For reveiw I have been helping a young ARC install an AllStar system (a couple of states away form my location). Since it is not feasible for everyone to buy a new HT, we have decided to change out the radio to an Alinco DR-135 which I own and works with Wouxun HTs on my AllStar site. ---
**Author:** ![Gazolla](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/g/c2a13f/32.png) [@Gazolla](https://community.allstarlink.org/u/Gazolla)\ **Post date:** [March 18, 2013, 3:34pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/15 "2013-03-18T15:34:20Z")
I mentioned a week ago that I was helping a friend in another state set up an AllStar site for his ARC. Everything went well but the Wouxun HTs number 3 DTMF code was not begin accepted. We were using a 10 year old Motorola 2M radio and homemade cable to a URI. We kept testing and found that the Wouxuns DTMF 3 worked on local EchoLink node and later found out that a couple Yeasu HTs number 3 DTMF code did not work either. I use a n Alinco DR-135 . It is rock solid and works with my Wouxun. Solution: We replaced the Motorola radio and cable with an Alinco DR-135 and a cable specifically designed for the Alinco from Marshall’s “URI AllStar Link Cables”. It took about three minutes to witch out the new equipment then every radio worked perfectly. All we had to do was run the radio-tune-menu to increase the audio and we are completely up running for both an AllStar and EchoLink node. I do not doubt your experience with the quality issues of the better brands over the Wouxun but for a young club and me personally I don’t know if I would have gotten into the HAM business had it not been for the availability of an inexpensive starter HT. George K6GAZ > **···** > > On Mar 11, 2013, at 7:15 AM, Tim Sawyer [tim.sawyer@me.com](mailto:tim.sawyer@me.com) wrote: > > > ## So, you’re going to use one piece of crap radio to make another piece of crap radio work? > > > Tim > > > :wq > > > On Mar 10, 2013, at 8:45 PM, George Zolla [gazolla@san.rr.com](mailto:gazolla@san.rr.com) wrote: > > > > Thanks of everyone’s inputs on this problem an insight into the Wouxun HT problems. For reveiw I have been helping a young ARC install an AllStar system (a couple of states away form my location). Since it is not feasible for everyone to buy a new HT, we have decided to change out the radio to an Alinco DR-135 which I own and works with Wouxun HTs on my AllStar site. > > > > > > * * * > > > > App\_rpt-users mailing list > > [App\_rpt-users@ohnosec.org](mailto:App_rpt-users@ohnosec.org) > > [ohnosec.org](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users) ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [April 9, 2022, 6:48pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/16 "2022-04-09T18:48:55Z")
Running into this issue. Out of 5 radios only 2 work which are Yaesu FT-60 and FT-8800. I am using a Motorola GR1225/70cm radio for node radio. These radios are no go on #3 DTMF: Connect Sysytems CS-750 BTech UV-5X3 Anytone TERMNTR ---
**Author:** ![AH6LE](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ah6le/32/1817_2.png) [@AH6LE](https://community.allstarlink.org/u/AH6LE)\ **Post date:** [April 10, 2022, 9:27pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/17 "2022-04-10T21:27:10Z")
DTMF digit 3 and 5 are notorious problem children when it comes to twist. In addition to the other excellent comments, I’d check your audio for twist (difference in level between the high and low tone groups) ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [April 11, 2022, 4:55am UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/18 "2022-04-11T04:55:15Z")
I don’t know the method for checking the hi/low tone group level differences. The manufacturer Connect Systems suggests the issue is w ASL decoder. If anyone has a CS-750 can you verify DTMF #3 is problematic? Clifford ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [May 11, 2022, 5:42am UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/19 "2022-05-11T05:42:24Z")
Well tonight I had a friend here with an Anytone 878 FM/DMR HT. I asked to try the DTMF and before he programmed it I went to show him the issue and EVERY ONE of my radios worked flawlessly controlling via DTMF! I have not changed anything aside from maybe running an upgrade/update routing on the node. Happy they now work but still a mystery. ---
**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\ **Post date:** [May 14, 2022, 11:54pm UTC](https://community.allstarlink.org/t/dtmf-number-3-problem/10017/20 "2022-05-14T23:54:49Z")
SOLUTION for my DTMF issue- Turns out I had “deemphasis” set to NO in simpleusb.conf I had recently set it to YES after someone wiser heard my audio and said it sounded thin and that I might check this setting. Today I toggled it and tested and indeed was the cause of the DTMF decode issue. Now ALL of my radios work perfectly sending #3 and all others to the node. A bit surprised I have not seen this mentioned as a possible cause/solution elsewhere. 73 Clifford - Kk6QMS [Next page](https://community.allstarlink.org/t/dtmf-number-3-problem/10017.md?page=2)