[arm-allstar] Split-site Repeater Questions

[David McGough]

Hi Chuck,

The playback method you're using should work fine, at least when the 
playback (or localplay) commands are run on and directed at the local node 
where the command is bring run.

Note that the node duplex setting will impact the operation of the 
"playback" command.

For example, if node 1900 is set duplex=0, and node 1901 is set duplex=2 
and both nodes are connected together:

...You will hear playback (or localplay) on node 1900, when the command is
run locally. However, you won't hear any audio on node 1901.

For the opposite scenario, you run "playback" on 1901. You should hear the
audio on both 1901 and 1900. With "localplay" the audio will only be heard 
on 1901.

As another example, if both nodes were set duplex=0 and connected 
together, you would only hear playback or localplay on the node the 
command is run from, but never on the network connected node.

For a final comment, all playback or localplay commands MUST be aimed at 
local nodes, not remote network connected nodes. So, you can't be on node 
1900 and try to send a playback to 1901, which is network connected. To 
determine which nodes are local, from the asterisk CLI run the "rpt 
localnodes" command, like:

testbench*CLI> rpt localnodes
testbench*CLI> 
Node
----
1211
1212


So, in this example, 1211 and 1212 are local and playback or localplay 
should work for either of these nodes, like:

testbench*CLI> rpt playback 1211 systems
    -- <DAHDI/pseudo-286021843> Playing 'systems' (language 'en')
    -- Hungup 'DAHDI/pseudo-286021843'




Does this operational explanation help?


73, David KB4FXC




On Wed, 2 Dec 2020, "Chuck Munro via ARM-allstar" wrote:

> Hello folks :-)

I have an intriguing problem getting a split-site 10 Meter repeater 
configured using a pair of Pi-3's with Pi hat boards designed with the 
ubiquitous CM-119 chip.  The hat is similar in design to the URI dongle 
for the PC.  I am using private unregistered node numbers on 
non-routable IP addresses within a VPN.

The two end nodes, one for RX and the other for TX, are communicating 
well, using a WireGuard VPN over the Internet. There is tons of 
bandwidth between nodes.  The RX receive-only node will be connected to 
an Alinco DR-03T 10M FM transceiver, and the TX transmit-only node to an 
identical radio.

Part of early testing how well the nodes work is with announcements of 
repeater ID ... playing a GSM voice announcement file on the hour and a 
GSM morse file on the half hour.   I do this by simply putting asterisk 
'rpt playback .....' commands in a Linux cron job, aimed at the TX node 
number.  Example:

 Â  /usr/bin/asterisk -rx "rpt playback 1900 
/etc/asterisk/local/ve7skyID_Voice"Â Â  (The documentation says to omit 
the '.gsm' part of the filename)

where 1900 is the TX node number.  The Voice file has a .gsm filename.  
The GSM codec is specifically allowed everywhere in the config files.

The Asterisk CLI shows the following at the TX node when the above 
command is issued locally on that node:

 Â Â Â  -- <DAHDI/pseudo-1065208769> Playing 
'/etc/asterisk/local/ve7skyID_Voice' (language 'en')
 Â Â Â  -- Hungup 'DAHDI/pseudo-1065208769'

My problem ... when I monitor the CM-119 audio output (LOL and LOR pins 
30 and 32), I hear nothing.

I have tried playing the files on both the RX and TX nodes, in both 
cases aimed at the TX node number.   When I do this locally on the TX 
node, the Asterisk CLI application shows the file is being played (as 
shown above).

When I issue the same command on the RX node aimed at the TX node, 
nothing seems to happen at either node.  I do know the RX node makes a 
very short UNIX connection to the TX node as indicated by debug 
statements at the RX.

I am clearly missing something.  Does there have to be a COR signal at 
the TX node to allow audio thru the adapter's chip?  Is there a 
configuration setting I am missing somewhere?  On restarting the RX 
node's Asterisk server, it does connect with the TX node as indicated by 
the trace from the TX node's Asterisk CLI client.  The RX node is at  
10.6.0.7 :

 Â Â Â  -- Accepting UNAUTHENTICATED call from 10.6.0.7:
 Â Â Â Â Â Â  > requested format = ulaw,
 Â Â Â Â Â Â  > requested prefs = (ulaw|g726aal2|ilbc|gsm),
 Â Â Â Â Â Â  > actual format = ulaw,
 Â Â Â Â Â Â  > host prefs = (ulaw|gsm),
 Â Â Â Â Â Â  > priority = mine
 Â Â Â  -- Executing [1900 at radio-secure:1] Rpt("IAX2/10.6.0.7:4569-242", 
"1900") in new stack
 Â  == Spawn extension (radio-secure, 1900, 1) exited KEEPALIVE on 
'IAX2/10.6.0.7:4569-242'

Sorry for the long-winded question, I want to provide as much info as 
possible.

Any advice will be welcomed.
73!   Chuck    VA7UL

_______________________________________________

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

Visit the BBB and RPi2/3/4 web page - http://hamvoip.org