There are some things you need to tweak in order to make app_rpt and alsaradio working as a repeater and Echolink node.
I’m using FT-857D to build the repeater. The connection between PC and radio station is signaling and audio. For signaling I’m using the DATA connector on the back which is a mini DIN 6 pin:
The PTT is activated low and needs very low current to be activated. I measured about 140uA needed current for activating PTT.
The SQL signal (which sometimes is called COR – Carrier Operated Relay or COS – Carrier Operated Squelch) is activated high but it can only drive small current (uA) and therefore a transistor needs to be used to drive the serial line. That is why one will need an additional power supply if driving optocoupler is needed in an isolated interface (I’ll present it later on).
You could see that the DATA connector has DATA IN, DATA OUT 1200 and DATA OUT 9600 pins which could be used to input/output audio when no digital modes are used. However, DATA OUT pins do not output squelched audio. Hence I used only DATA IN for audio input and oudio output has been taken from oudio output jack in the back of the rig.
A good level meter for ALSA is ameter. It is an ALSA plugin that will get the PCM level to from sound card and display it in a graphical environment. Download, build and install it as per given instructions. The following is an screenshot of ameter GUI:
arecord -D ameter -c 2 -f S16_LE test.waw
It will record the input level while showing ameter levels. You should adjust input level either from your card controls or from your rig’s volume level to see a 3/4 from your maximum ameter level.
To adjust output level you need to set your rig to display modulation level. Then adjust your card output level so that the modulation level is what your rig’s manual says (On FT-857 you should see couple of bars at maximum).
Testing the system:
If you start asterisk and signaling and media path are connected then you should be able to do the following from another radio station with a DTMF pad:
– activate parrot mode (simplex repeater functionality): *94 – now all you speak is sent back to you
– deactivate parrot mode: *95
– get system time: *81
– get version of the system: *82
– *3 – conects to an internet node (needs parrot mode disabled)
– *1 – disconnects from an internet node
All of the above DTMF sequences are configured in the rpt.conf and you coud add more, see app_rpt documentation.
Connecting to Echolink:
The Echolink numbers are prefixed with digit 3 and padded with 0 until 7 digits.
– *33009999 – this will conect to *ECHOTEST* node
– *13009999 – will disconnect from *ECHOTEST* node
Connecting to Allstarlink:
The Allstarlink numbers are starting by default with digit 2 and there is no need to prefix anything:
– *31234 conencts to Allstarlink number 1234
– *11234 disconnects from the Allstarlink number 1234
Connecting to IRLP:
The IRLP node numbers are prefixed with digit 4 and no padding.
– *349500 – connects to IRLP node 9500
– *149500 – disconnects from IRLP node 9500
Testing from Asterisk’s CLI:
DTMF commands could also be sent from the asterisk’s console. Start asterisk CLI with “asterisk -r” and then you should be able to do the same, for example:
rpt fun *94 – activate parrot mode
rpt fun *95 – deactivate parrot mode
Other commands useful for testing from CLI:
database show – shows database with Echolink nodes
aradio key – keys the transmitter
aradio unkey – unkeys the transmitter
aradio rkey – simulates COR present
aradio runkey – seize COR present
Sourcecode released as Open Source under GNU GPL license:
example of alsaradio.conf: alsaradio.conf.tar.gz
example of rpt.conf: rpt.conf.tar.gz
chan alsaradio (v01): chan_alsaradio.c_01.tar.gz
chan alsaradio (v02): chan_alsaradio.c_02.tar.gz
To correctly build the chan_alsaradio driver, the following line needs to be added in channels/Makefile: