[arm-allstar] documentation on inxlat & outxlat commands

[Doug Crompton]

Neil,

 I have never used them. I think the reason is to avoid problems when using a controller that you have to send DTMF to. To avoid conflicts with Allstar codes.

I gave you an example. That is all it is. You can change the * lead in character and the # end character to whatever you want. Something the average person would never do. To turn it off and on you would just redefine unless there is a function to do that. I don't remember seeing it. Check the function list.
73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: k8it at cac.net
To: arm-allstar at hamvoip.org
Date: Sun, 26 Jul 2015 23:06:45 -0400
Subject: Re: [arm-allstar] documentation on inxlat & outxlat commands








your example is the same as what's written in rpt.conf. I am looking for 
more details on these functions. 
can you make them be activated and deactivate by a script for instance? 

how about being only used for one node and not the second node using a 
raspberry pi?
 
Thanks
73 Neil Sablatzky  K8IT
Allstar Node 41838 
KITLINK
Allstar Node 42087 KITLINK HUB
IRLP Node exp0068
Echolink 
K8IT-L
WIRES-X K8IT 11479 Room 21479




From: Doug Crompton 
Sent: Sunday, July 26, 2015 9:57 PM
To: ARM Allstar 
Subject: Re: [arm-allstar] documentation on inxlat & outxlat 
commands


Neil,

 inxlat and outxlat translate the 
function and end characters which by default are  *  and #  It 
also allows for the blocking or selective passing of DTMF characters. It is 
unlikely you would use it but an example is:
inxlat = #456,#457,0123456789ABCD 

Which would redefine the * to #456  and the # to #457 and pass all DTMF characters.

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





From: k8it at cac.net
To: arm-allstar at hamvoip.org
Date: Sun, 26 Jul 2015 
20:58:36 -0400
Subject: [arm-allstar] documentation on inxlat & outxlat 
commands




in my quest to fully learn the allstar capabilities, does anyone have a 
link to documentation on inxlat and outxlat commands? I have read several lines 
for the examples in the rpt.conf file. what if you wanted to enable or disable 
translation? what if you wanted to translate say a  * 51 to a DTMF A for 
example. how would I do this if the A needs to go to the node as a remote 
command?  I also assume that local received radio audio would be subject to 
outxlat before the software processes it. of course if I need to issue a remote 
command first such as *4 and then turn on translation send a *51 which would 
mean an A can I do this and then turn off translation? 
I would also like this translation to be node dependent assuming a two node 
raspberry pi system. I also assume that inxlat translates audio received by the 
internet and likewise can this be node dependent and be turned on and off?
Any thoughts?
 
Thanks
73 Neil Sablatzky  K8IT
Allstar Node 41838 
KITLINK
Allstar Node 42087 KITLINK HUB
IRLP Node exp0068
Echolink 
K8IT-L
WIRES-X K8IT 11479 Room 21479



 
_______________________________________________ 
arm-allstar mailing list arm-allstar at hamvoip.org 
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the BBB and 
RPi2 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 web page - http://hamvoip.org 






No virus found in this 
message.
Checked by AVG - www.avg.com
Version: 2015.0.6081 / Virus 
Database: 4392/10311 - Release Date: 07/26/15

_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2 web page - http://hamvoip.org 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150727/98805206/attachment-0001.html>