Hello Jon,

And yes it Does Work! as well as creating entire dial sequences in them.

Wanted to say Thanks as well as to all the others who replied and assisted me in finding a solution.

This thread has pretty much run the course and I should probably leave it alone except I had written a comment a few days back that never made it to the list.
Left on a short vacation with the Grandkids and hastily wrote a note along this same line before leaving which I sent using the wrong email account and therefore it ended up trapped in moderation.

Basically I said that I found the solution by loading the "OneTouchKeys" which some would say I created a "Macro" and now I see Jon refers to the function as using "directory buttons"

My comment here isn't directed and anyone and I hope no one takes offense, I just happen to read this post last and therefore used this message as a reply avenue.
While I received great advice from many (Jon's included) I would like make one final comment to the list with the hope of helping some other new person down the road.

A lot of us who are new to this entire process encounter terminology that's foreign to beginners. In my case had I understood the "How To" when someone mentioned create a Macro my problem would have been solved. While I grasp "Macro" meaning there is no mention of "Macro" in the IaxRpt documentation so I was at a loss (Where and How do I do it?)  I was also unable to find an example "How to" load, configure and associate "OneTouchKeys" with different Accounts. Being that term was also unfamiliar I had no understanding of how to use it properly.  Luckily I found in the List Archives a conversation where Doug Crompton (WA3DSP) was explaining to another member how to associate "OneTouchKeys" as well as using the different screens and assigning them to different Accounts. From that point on the advice called "create a macro" made sense. Reading Doug's explanation (which is almost a How To) I was able to understand the menu functions and their relationship allowing me to solve my problem.

There are people like myself still learning to use different programs. Many programs have limited or hard to find documentation and we are stuck with terms we either read about or are taught by those helping us. Terminology becomes an important part when trying to follow menu or settings in an unfamiliar program. If at all possible try not to interchange terms between programs.  


Thanks to All

Larry - N7FM





On 08/15/2014 05:35 AM, Jon Rorke wrote:
Has anyone tried using the directory buttons to send the ABCD in Iax_Rpt?

Looks like you can put in ABCD in the memories. Dont know if that works though.

Jon VA3RQ

On 8/15/2014 2:44 AM, Doug Crompton wrote:
The A,B,C,D DTMF keys work just fine in function statements -

ABC=status,12

Entering *ABC  gives time of day


73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: apprptusers@westbrook.com
Date: Thu, 14 Aug 2014 18:24:17 -0600
To: Bryan@bryanfields.net
CC: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] DTMF digits on IaxRpt

Asterisk's "dsp.c" (even the old version in the app_rpt fork, I believe) does indeed already decode them at no additional cost, so I too would have expected them to just come along for the ride.  Does some other part of the system filter them out?

Who cares why -- although I can think of a dozen use cases without even trying hard.  Besides, it costs absolutely nothing when you're already doing the other digits.  Let the man have his tones, I say.

$0.02,
Eric
K5BFC


On Thu, Aug 14, 2014 at 7:29 AM, Bryan Fields <Bryan@bryanfields.net> wrote:
On 8/14/14, 9:24 AM, Bryan D. Boyle wrote:
> The issue is *why* is it so danged important to have the A-D keys decoded?
>  security through obscurity?  Because they are there on ham mics?
>
> No one has really described a use case for why this artifact of the whole dtmf
> protocol is really needed.   especially when, with the asterisk system, there
> is almost an unlimited functionality with using just the 10 digits bracketed
> by the star and octothorpe.

_______________________________________________ App_rpt-users mailing list App_rpt-users@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@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@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.