- App_rpt-users - lists.keekles.org

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

tx audio delay
by Greg 23 Mar '17

23 Mar '17

Hello, need some help. Using usbradio and want to know where and how I can make adjustment to delay tx audio between it and PTT. I'm doing something experimental and I am getting clipped (cut short at start) audio. I see it being sent via CLI but the radio isn't in transmit yet. This is only after I issue something from the radio I am using to talk to the node. Otherwise, announcements, cwid and activity is fine. It may be a rx issue, since I am using carrierfrom=vox and rxdemod=speaker. Maybe some conflict where it is using a vox delay or is picking up a tail of false rx... So any place to set these delays? Thanks Greg

2 1

Set time remotely-SOLVED w/ radio dtmf !
by mike＠midnighteng.com 22 Mar '17

22 Mar '17

A means to set system clock with DTMF RADIO COMMANDS. First I want to point out several things. Read the warnings at the bottom. This is not a perfect thing, but a framework to meet a end need. You will likely need to make adjustments to it for your particular circumstance(s). It was intended for Acid users who have no internet connection on their system but can be adapted to fit many situations. While there are more than a dozen ways to do the same thing, I chose this one to show to the group for the simplicity of implementation to those that are not as linux savvy, but have learned asterisk somewhat. If you are in the US and have had the same system running for many years without updating the zoneinfo files, you should do that and copy the new timezone file to your /etc/localtime because the Daylight savings time that changed a few years ago has probably been giving you some frustration on the time change twice or four times a year. SO, I am implementing this from the phone patch. By default, (*6) +A+ HHMM is all the dtmf you would need to enter the time in 24hr format. example *6A1345 will set the clock to 1:45pm I chose 'A' as the dialing catch since it is unlikely to be in your normal phone extensions and this is intended for no internet service installs. In extensions.conf just under [radio] [radio] exten = _Axxxx,1,Goto(set_time_clock|${EXTEN:1}|1) ;set time, send to subscript without leading digit (place the rest at the end of extensions.conf file....) [set_time_clock]; by kb8jnm exten =_X.,1,Wait(5) exten =_X.,2,Playback(rpt/thetimeis) exten =_X.,3,SayAlpha(${EXTEN}) ; Read back Dialed Number for time exten =_X.,4,Wait(10) ; allow 10 seconds to hang-up (*0 ) if not correct exten =_X.,5,System(date +%T -s "${EXTEN:0:2}:${EXTEN:2:2}:00") ;format 'HH:MM:00' - 24hr format exten =_X.,6,System(reboot) exten =_X.,7,Hangup Warnings: Adjusting the timeclock on a live system can have unknown affect on things that are running relying on timers. So at a minimum, shutdown links before adjusting the clock. If you have much a time slippage in your clock, adjust it more often or when it gets 2 minutes or so out of time. I am thinking of you folks that have unconnected mountain top systems you can't get to if a problem arises. So, To avoid many unexpected problems that can occur in system timers mis-match, the system will reboot right after setting the clock. I suggest you leave that in place unless you have good reason to take it out. But you have been warned. If you like it... great... if you don't like it... make it better and shove it out to the group for others to improve on. Probably better to hand the extension data off to a shell script, shutdown asterisk, set-clock, restart asterisk & exit. But this is simple and with the full reboot, resets 'all' system timers before 'any' can be a problem. Unless you change that. But it is a bit belated reply to Steve/ KB8BIW's request last year. 73, ...mike/kb8jnm

1 0

Re: [App_rpt-users] Set time remotely-SOLVED w/ radio dtmf !
by mike＠midnighteng.com 22 Mar '17

22 Mar '17

A means to set system clock with DTMF RADIO COMMANDS. First I want to point out several things. Read the warnings at the bottom. This is not a perfect thing, but a framework to meet a end need. You will likely need to make adjustments to it for your particular circumstance(s). It was intended for Acid users who have no internet connection on their system but can be adapted to fit many situations. While there are more than a dozen ways to do the same thing, I chose this one to show to the group for the simplicity of implementation to those that are not as linux savvy, but have learned asterisk somewhat. If you are in the US and have had the same system running for many years without updating the zoneinfo files, you should do that and copy the new timezone file to your /etc/localtime because the Daylight savings time that changed a few years ago has probably been giving you some frustration on the time change twice or four times a year. SO, I am implementing this from the phone patch. By default, (*6) +A+ HHMM is all the dtmf you would need to enter the time in 24hr format. example *6A1345 will set the clock to 1:45pm I chose 'A' as the dialing catch since it is unlikely to be in your normal phone extensions and this is intended for no internet service installs. In extensions.conf just under [radio] [radio] exten = _Axxxx,1,Goto(set_time_clock|${EXTEN:1}|1) ;set time, send to subscript without leading digit (place the rest at the end of extensions.conf file....) [set_time_clock]; by kb8jnm exten =_X.,1,Wait(5) exten =_X.,2,Playback(rpt/thetimeis) exten =_X.,3,SayAlpha(${EXTEN}) ; Read back Dialed Number for time exten =_X.,4,Wait(10) ; allow 10 seconds to hang-up (*0 ) if not correct exten =_X.,5,System(date +%T -s "${EXTEN:0:2}:${EXTEN:2:2}:00") ;format 'HH:MM:00' - 24hr format exten =_X.,6,System(reboot) exten =_X.,7,Hangup Warnings: Adjusting the timeclock on a live system can have unknown affect on things that are running relying on timers. So at a minimum, shutdown links before adjusting the clock. If you have much a time slippage in your clock, adjust it more often or when it gets 2 minutes or so out of time. I am thinking of you folks that have unconnected mountain top systems you can't get to if a problem arises. So, To avoid many unexpected problems that can occur in system timers mis-match, the system will reboot right after setting the clock. I suggest you leave that in place unless you have good reason to take it out. But you have been warned. If you like it... great... if you don't like it... make it better and shove it out to the group for others to improve on. Probably better to hand the extension data off to a shell script, shutdown asterisk, set-clock, restart asterisk & exit. But this is simple and with the full reboot, resets 'all' system timers before 'any' can be a problem. Unless you change that. But it is a bit belated reply to Steve/ KB8BIW's request last year. 73, ...mike/kb8jnm

1 0

ilink,6 and permalinks?
by Bryan Fields 22 Mar '17

22 Mar '17

I've been looking for a version of this command which will remove all connected links excluding permalinks. It doesn't appear there is an easy way to do this in the code, does anyone have any ideas as how to do it? 73's -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

6 10

Registry re-requests
by William Higgins 21 Mar '17

21 Mar '17

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 -- Received OK from Echolink server 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

2 1