[App_rpt-users] DTMF number 3 Problem

[George Zolla]

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 at 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 at ohnosec.org [mailto:app_rpt-users-bounces at 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 at 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 at 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 at 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 at 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 at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>  
>  
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20130309/b5d16caa/attachment.html>