February 2014 - App_rpt-users - lists.keekles.org

Registration issues
by Thor Wiegman 30 Nov '15

30 Nov '15

Tonight I had a user tell me that one of my nodes wouldn't connect anywhere. Verified, rebooted the server, still nothing. Tried running the rc.updatenodelist script manually and it just sits there. However, after running the following command I do get an update and can now connect to other nodes. /usr/bin/wget -O /var/lib/asterisk/rpt_extnodeshttp://nodes1.allstarlink.org/cgi-bin/nodes.pl When I checked two other nodes they had the same problem and same work-around. I ran that same command for nodes2 and it works. When I run it for nodes3 it times out. Could a problem with nodes3.allstarlink.org be causing the rc.updatenodelist script to choke? And could that have been causing my nodes to not be able to connect to others?

5 5

URI<>TKR-750 cable
by Jay Urish 06 Feb '15

06 Feb '15

Does anybody have notes on connecting tkr750 to a URI? TIA, W5GM

4 3

Echo-stink
by Johnny Keeker 05 Jan '15

05 Jan '15

I've found the 'permit=w1aw,w5yi,etc' line in the echolink.conf only allows for 29 allowed calls. Any more than 30 entries in the list prevents incoming requests on or not on the list access to the node. Short of checking for typo's, using a backslash\ to continue to the next line, or adding another 'permit= line' hasn't proved any results. ???

6 6

Re: [App_rpt-users] Connect SIP Phone to allstarlink box
by mike＠midnighteng.com 20 May '14

20 May '14

6 6

rpt.conf
by Geoff 04 Mar '14

04 Mar '14

First off, thanks for all the help in getting a 2nd node running on the system. It's been a learning experience and actually... a lot of help came from the drupal site. Thanks, Tim for doing that. I still fumble around, but finding things is getting *somewhat* easier. Interesting bug I found, though, in rpt.conf... and I'm sure this is in a .c module, somewhere (morse.c?) but alas, I'm no programmer... If I define a stanza in 29655 for Morse with the line morse=morse29655 then app_rpt, using /etc/asterisk/rpt.conf *should* go to that stanza and read: [morse29655] speed=20 ; Approximate speed in WPM frequency=500 ; Morse Telemetry Frequency amplitude=2048 ; Morse Telemetry Amplitude idfrequency=1000 ; Morse ID Frequency idamplitude=2048 ; Morse ID Amplitude All is fine and dandy, and when I key the repeater, I get exactly *that*. Cool. Here's where it gets *buggy*... Using the same rpt.conf, as I define the morse stanza for node 29657 the same way I do in 29655, with the line morse=morse29657 app_rpt *should* pick that up and do [morse29657] speed=20 ; Approximate speed in WPM frequency=1000 ; Morse Telemetry Frequency amplitude=2048 ; Morse Telemetry Amplitude idfrequency=500 ; Morse ID Frequency idamplitude=2048 ; Morse ID Amplitude ... but, that's not what happens. If I key the repeater first, then I get what is defined in morse29655. Problem is, it doesn't change for 29657. Meaning, whatever id/telem frequencies were defined, are used subsequently, depending on which stanza is used first. If I key the simplex (29657) node -first-, the same thing happens, only both machine use the morse29657 stanza. As a possible solution, I redefined the stanza with morse=29655morse29655 and, of course, renamed the stanza to reflect. No typos... they've been checked and checked and re-checked. Thoughts? -Geoff/W5OMR

8 15

Re: [App_rpt-users] Re :__Problems_with_Echolink
by Doug Crompton 03 Mar '14

03 Mar '14

Torben, When your public IP address changes you should check your echolink database sometime after (15-30 minutes) to see if the IP address for your node has changed to the new address. If it has then that would indicate that it is updating properly. If not then maybe there is a code problem with the IP address change. My public IP does not change so I do not see the problem. Also check the database for stations you cannot connect to. You could also do a check on a windows computer to compare the results. There are sites where you can enter echolink node numbers or calls and see if it is online and other details. You could also detect the IP address change and restart asterisk shortly after in a script. Not the best solution but it might work. Also I am sure you know this but you cannot use more than one echolink connection on one public IP address unless you use a proxy. The port forwarding is to only one computer behind your router and in this case it would be your Allstar server. 73 Doug WA3DSP http://www.crompton.com/hamradio From: torben(a)klimt-online.com To: doug(a)crompton.com Date: Thu, 13 Feb 2014 08:17:42 +0100 Subject: AW: [App_rpt-users] Re :__Problems_with_Echolink hi doug, i will try if the problem come the next time. i think the problem is that the "database" don`t update any more. here in europe we get a new IP Adress every 24h from our provider and if the database-update don`t run any more then i have wrong IPs to the Calls so i find out that if i connect to Call DB0CUX i get an answer from VK2XYZ or... i hope i can explain the problem with my english :-/ greetings and many tnx for your help Von: app_rpt-users-bounces(a)ohnosec.org [app_rpt-users-bounces(a)ohnosec.org] im Auftrag von Doug Crompton [doug(a)crompton.com] Gesendet: Mittwoch, 12. Februar 2014 16:17 An: app_rpt-users(a)ohnosec.org Betreff: Re: [App_rpt-users] Re :__Problems_with_Echolink Torben, I went back and looked at your original message and you talked about a database problem. I messaged back the method to check the echolink database. Did you do that? Is the call/IP address of the echolink station you want to call in your local database? If you are not getting the database it isn't going to work. echolink dbget c WA3DSP-L The call has to be exact including case but you can do echolink dbdump to see the entire database. It is hard to see in the client mode so at linux prompt do... asterisk -rx "echolink dbdump" | more or asterisk -rx "echolink dbdump" > filename to save it to a file for viewing. 73 Doug WA3DSP http://www.crompton.com/hamradio From: torben(a)klimt-online.com To: mike(a)midnighteng.com; app_rpt-users(a)ohnosec.org Date: Wed, 12 Feb 2014 11:22:41 +0100 Subject: Re: [App_rpt-users] Re :__Problems_with_Echolink possible is of course everything but i don`t think that there is any problem with the router software BUT we have many problems with the internetconnection at the repeater location. sometimes there is no more signal so we must restart the router/modem (all included; AVM Fritzbox) any other ideas or issues to solve the prob ? Von: app_rpt-users-bounces(a)ohnosec.org [app_rpt-users-bounces(a)ohnosec.org] im Auftrag von mike(a)midnighteng.com [mike(a)midnighteng.com] Gesendet: Dienstag, 11. Februar 2014 19:23 An: app_rpt-users(a)ohnosec.org Betreff: Re: [App_rpt-users] Re :__Problems_with_Echolink Just a hunch here.... It kinda sounds like a router issue as strange as that may seem but not exactly the router... Is there anything else on the network (computers) that could have a piece of malware on it ? I have seen many a "unidentified malware" exploit router security and play with the router settings in router ram without writing them to NVRam. This type of malware eventually uses the host as a forwarding hub for data they have collected elsewhere to hide source of where it is going. While it it easy to find the infected computer, much harder to find the files on that computer. Keeping router firmware up to date or using a newer router can help. Just a thought if you are unable to locate the problem. ...mike/kb8jnm -------- Original Message -------- Subject: Re: [App_rpt-users] Re :__Problems_with_Echolink From: Doug Crompton <doug(a)crompton.com> Date: Tue, February 11, 2014 12:44 pm To: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org> The command is 'echolink dbdump" [root@WA3DSP_Allstar wa3dsp]# asterisk -rx "echolink dbdump" | grep WA3DSP 147090|WA3DSP-L|50.191.8.33 You can also use dbget WA3DSP_Allstar*CLI> echolink dbget c WA3DSP-L 147090|WA3DSP-L|50.191.8.33 To dump the entire database so you can look at it do asterisk -rx "echolink dbdump" > echolink.txt echolink.txt can be any filename and directory you want. Then do less echolink.txt To look through the file. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Tue, 11 Feb 2014 11:50:32 -0500 From: petem001(a)hotmail.com To: torben(a)klimt-online.com; app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Re : Problems with Echolink I have the same problem. --- Message initial --- De : torben(a)klimt-online.com Envoyé : 11 février 2014 07:40 A : app_rpt-users(a)ohnosec.org Objet : [App_rpt-users] Problems with Echolink hi all, i have problems with echolink on my node. after running allstar more then xx days it is not possible to connect out but it is possible to connect the node. ithink there is a file / database with the information nodenumber/ip/call and that file is not up to date. after restarting allstarlink all is working well any ideas ? tnx 73 de torben dh6mbt _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

2 1

No TX through URI
by Scott 28 Feb '14

28 Feb '14

I just put together a Allstar node and connected it to a local uhf repeater. I am using a DMK URI and interface cable connected to a RLC controller (club deluxe 2) The system works well on incoming traffic from the node, but will not pass ptt or outgoing audio from the repeater. I have checked the configuration on the controller port and it all looks ok. I need some help? Scott

2 2

Webtransceiver
by Jim Duuuude 27 Feb '14

27 Feb '14

Could some of the people that were having Webtransceiver problems with Java please see if its "fixed" now. Jim

1 0

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 79
by Steve Wright 27 Feb '14

27 Feb '14

On Wed, Feb 26, 2014 at 12:40 PM, <app_rpt-users-request(a)ohnosec.org> wrote: > > [Quote] > > uh,.... what? > > Seriously? (I know I'm working on cup #1 and it's not quite 6am... I had > to > read this a couple of times to 'really' see this question and it's just as > silly, every time!) > > [/QUOTE] Ok who wrote this? Name and shame time.. Perhaps if people didn't hide behind anonymity they would be less inclined to be rude. I saw what you were asking right away. It wasn't your fault that you didn't quite know how to word it - that was me some time ago, and seriously, people on this list know EXACTLY what simulcast is but just want to give you a rude reply because they are rude people. Takes all types doesn't it! :) So back on topic, there are (or were) GPS-interface clock generator boards available from micronode.com Steve

3 2

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 81
by Steve Wright 27 Feb '14

27 Feb '14

Re: Voted Simulcast Configuration Questions (Caleb Pal) > > > 3.) Thunderbolt to RTCM: Is there documentation on this interface? Is it > serial between the two or is there a 1 PPS signal as well? > Ask @micronode.com. The 10MHz signal from the GPSDO either phase-locks the transcievers' clock, or replaces the clock completely. There are circuit diagrams of the RTCM online if you google them.. > 4.) Latency/Jitter: What is the top end of the latency the > Voting/Simulcast system can handle? We are working on getting a private > VLAN over Fiber between our two sites, but until the funding for that > becomes available, we will be working over the internet and a VPN. You can add a fixed delay in the config that will be greater than the networks' latency, so as to mask problems so they don't appear at on the repeaters as "problems". My prediction is the VLAN will be sufficient, but the VPN will suffer connectivity problems. I've never really seen a reliable PPP based VPN - they are regularly up and down for seemingly no reason at all. Cue regular unexplained dropouts for some 2-200 seconds with no real chance at diagnosis. Frankly, I don't like VLANs either - rather plain ol' ethernet or directly routed IP is best, and avoid all the trickery-doo on top of the real thing. Sounds like you're having fun with that. ;) Steve

1 0