March 2017 - App_rpt-users - lists.keekles.org

RPi w/DIAL Repeater Stuck In Transmit Mode
by Bob Pyke 22 May '17

22 May '17

Our repeater hung up in transmit mode, and would not respond to radio DTMF commands to restart Asterisk or reboot. We had to manually reset the power. We don't understand why. If this should be a reoccurring issue, perhaps we need an external watchdog timer to reset power after x minutes of constant PTT activation. Looking for suggestions. We are planning to setup a remote (no internet) repeater that is not easily accessible, so want to make sure we have a solution. Thanks, Bob k6ecm 73 Sent from iPad

5 8

Allstarlink loop?
by Benjamin L. Naber 28 Mar '17

28 Mar '17

Uh, I was under the impression this wasn't possible, have a look at a the picture. If I don't break the connection using the almight *4 command, as someone on the 45297 insists on using the permanent link command, have a look-see at my node, 28569

5 7

Re: [App_rpt-users] Simulcasting with RTCM/voter
by Hayden Honeywood 28 Mar '17

28 Mar '17

Thanks for your thoughts Jesse and Tim. Ah, perhaps that was my issue, I was setting the delay, doing a 99 to save to EEPROM but not rebooting. Perhaps I need to try this next. Basically the test you have described Jesse is what I am doing at home. I believe from what I have read and understand from Joe's messages, Tim that some error in the launch delay is OK at voice. I read somewhere over 110uS it starts to become a problem. I certainly can get away with no PL encoding on the transmitter, I was merely using it as a means of double checking my audio phasing. Voice sounds OK, depending on my frequency offset. It does have a level of distortion however - again maybe due to the launch delay not being set correctly. I suppose a semi bonus is that at 6 metres, normal propagation effects cause noise, crackles, phase cancellations etc so it may just all sound natural anyway. Sporadic E openings will be interesting though :). Currently my main site has a significant overlap of my planned secondary site. I may need to reconsider this to reduce the overlap. 73 Hayden

3 3

"Link prefix" control codes?
by no1pc＠yahoo.com 28 Mar '17

28 Mar '17

Is anyone familiar with a set of additional function/control codes that can begin with '#' to allow for assigning a link-mode prefix for over-air/linked RF system control? If so, you're probably familiar with the scenario of some multi-site (RF) linked repeater systems. To control a local RF-site/repeater on it's local RF channel you prefix that site's control codes with '*' and all else is muted from going down-stream to other nodes. To control a remote site you prefix commands with '#' then a node address or 'prefix' after which the targeted node's controller accepts commands over the air. When you have an Allstar node connected as a port off a repeater controller you don't want it accepting control codes all the time, so it needs to be configured to accept only '#' then a <prefix/site code> and subsequent commands on that node. Jim Dixon had apparently created that code and implemented it on a few Allstar nodes, including one of mine, but I did not get details of the configuration, nor got a backup of it afterwards, and that node crashed and needed to be re-created. Work lost. I will have 2-3 such Allstar nodes at various radio sites and need to accommodate controlling them uniquely, over-the-air, remotely. Any clues?

2 1

2 nodes from the same ip address.
by W2rjr 27 Mar '17

27 Mar '17

Hello, I know I've asked this question before, I have one node for my repeater and its a full time connection to a hub and the other node is a portable node to connect to other nodes. They are both on the same Internet connection. I can connect outbound to some nodes and some not but I don't get in bound connections. My nodes are on two separate servers and have two separate ports. Is there something I'm missing? Any help is appreciated! Thank you. 73 Ray, W2RJR

3 2

Node numbering
by Leighton Judd 26 Mar '17

26 Mar '17

Hi All, I have recently started experimenting with app_rpt. I am wondering if there are any restrictions on numbering of private nodes? I have set up two nodes on the same machine for a test. They are each set up as a "hub" with numbers 2222 and 3333. Using the asterisk console, I can connect successfully from node 3333 to node 2222. Trying to connect from node 2222 to node 3333 does not work. This seems to be true for node numbers, that I have tested, beginning with 3000. This connects: rpt cmd 3333 ilink 3 2222 This doesn't connect: rpt cmd 2222 ilink 3 3333 Does anyone know if this is intended or not? Regards, Leighton

5 7

test msg - please ignore
by mike＠midnighteng.com 26 Mar '17

26 Mar '17

1 0

COS from Yaesu FT-7800
by John Griffith 24 Mar '17

24 Mar '17

Does anyone know from where to pull COS in a Yaesu FT-7800?

2 1

Re: [App_rpt-users] Registry re-requests (David Shaw)
by William Higgins 23 Mar '17

23 Mar '17

Hi David! First of all, thanks for your suggestions. I'm not saying that the network can't be a problem, however, there is seldom anyone coming into the node via Echolink or ASL. The audio dropouts are predominantly from repeater receiver audio, during local QSOs. When I spoke of the CAT7 cable with the ferrite chokes, I was referencing the interface cable I constructed to run between the RIM Lite and the repeater itself. The RPi3 is connected to the network via Wifi to a router that is no more than 4-5 feet away. I've seen no evidence of the link bouncing at all. We did not connect it via Ethernet because all the host's router's ethernet ports were full. We have purchased a switch to expand his network so that we can connect via Ethernet instead as soon as we get approval from him to do so. I am wondering if this might be a USB problem, however I have found no indication in any of the system or Asterisk log files of that. The RIM Lite is the only USB device plugged into the RPi3. I suppose it's also possible that the RIM Lite is wonky, but I have no other device with which to replace it. I have not yet put a ferrite choke on the USB cable, but plan to do that during my next trip to the site. I really appreciate all the ideas that are coming forward. If I don't get this solved soon, I'm going to have to put the original CAT200 controller back in place, hang my head in shame and restart this whole project at a later time. (Oh well, it won't be the first time for that! LOL) Bill Higgins N0NOE >After reading all the post. I don't think this is a OS problem (N4IRS can >chime in) but more of network or USB problem. I'm using good old Limey >Linux and a 4 port pci card. >Allstar uses UDP. Drop a UDP packet and that will drop out on the repeater. >SSH and SNMP uses TCP. Drop out a TCP packet. It will send a replacement >packet. No loss of data but slower. > > >Are you using both WiFi and Ethernet at the same time? I would try using >just one mode to access the internet. How are you connecting to the >Internet? i.e. WiFi to a cell hotspot or WiFi to a Mesh Network? What kind >of local network? > >"Modular connectors and Cat-7 cable for the interface with snap-on chokes >at both ends >Pi is connected to the local network via Wifi (We are prepared to move this >to Ethernet, but need approval of the host to do so)" > >If this is a network problem. I would use the mrt command to test your >network to the ASL server. Google Linux MRT and Linux MRT save to a file. > >Let us know. >David >KE6UPI

3 5

Re: [App_rpt-users] Registry re-requests
by William Higgins 23 Mar '17

23 Mar '17

Steve, I have felt that it was ok. I seem to be able to get to it remotely via SSH at will and I have not noticed any loss of SNMP data. One more interesting note. I took a look at my simplex multinode (43758 and 43936) here at my QTH and it's doing exactly the same thing. That system is a mini ITX PC based DIAL system. The only things these two systems have in common are: 1.) I was the builder, 2.) they're both using RIM LITE style interfaces, and 3.) they are both behind NAT routers (with the appropriate ports forwarded of course). Bill >William, >Have you verified good connectivity from your node to the net? I am >watching the reregistration server now to see I can catch any hints. > >73, Steve > >On 03/21/2017 05:52 PM, William Higgins wrote: > Still on a quest to find out why my repeater node is behaving badly > re: audio dropouts, I decided to look with more depth at the events in > asterisk. > > I set verbose level to 6 and saw this recurring pattern. > > A section of the log output to the console follows: > > [Mar 21 16:36:58] WARNING[818]: chan_iax2.c:10127 iax2_do_register: > REGISTER-LOG: Sending registration request for '44011' > [Mar 21 16:37:00] WARNING[822]: chan_iax2.c:7690 registry_rerequest: > REGISTER-LOG: registry rereqquest > [Mar 21 16:37:50] WARNING[815]: chan_iax2.c:10127 iax2_do_register: > REGISTER-LOG: Sending registration request for '44011' > [Mar 21 16:37:52] WARNING[818]: chan_iax2.c:7690 registry_rerequest: > REGISTER-LOG: registry rereqquest > -- Received OK from Echolink server nawest.echolink.org > <http://nawest.echolink.org/> > -- Received OK from Echolink server nawest.echolink.org > <http://nawest.echolink.org/> > -- Directory pgm done downloading(partial,compressed), 394 records > [Mar 21 16:38:42] WARNING[819]: chan_iax2.c:10127 iax2_do_register: > REGISTER-LOG: Sending registration request for '44011' > [Mar 21 16:38:44] WARNING[815]: chan_iax2.c:7690 registry_rerequest: > REGISTER-LOG: registry rereqquest > [Mar 21 16:39:34] WARNING[816]: chan_iax2.c:10127 iax2_do_register: > REGISTER-LOG: Sending registration request for '44011' > [Mar 21 16:39:36] WARNING[819]: chan_iax2.c:7690 registry_rerequest: > REGISTER-LOG: registry rereqquest > > After looking at it for a while, I noticed that the time delta between > the "registry rerequests" and the following "do_register" is exactly > 50 seconds. Is this normal? Does it really need to re-register that > often or does it indicate a network problem with the Rpi's connection > to the outside world? > > My configuration again is: > > Raspberry Pi 3 with DIAL RAT_RC1.img > Repeater Builder RB-USB Rim Lite Interface > Vertex VXR-7000 Repeater > Metallic case for the Pi > Modular connectors and Cat-7 cable for the interface with snap-on > chokes at both ends > Pi is connected to the local network via Wifi (We are prepared to move > this to Ethernet, but need approval of the host to do so) > Pi is connected to an external server via OpenVPN for collection of > mgmt. statistics via SNMP > Pi also runs Apache2 and Allmon2 > Echolink is enabled (Node 746074) > AllStarLink of course (Node 44011) > > Thanks for any insight you might be able to lend! > > Bill Higgins > N0NOE

3 2