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

new node configuration
by tom 18 Jan '14

18 Jan '14

I just registered a new node. Now, when I try to update information such as voter interface, I only have URI type interface options available. I also cannot find an input path to repeater site information. This will be a RTCM running in Washington on a server here in Austin. I would like it to be seen as being located in WA, instead of Austin, TX. I believe this was easier to update previously. Tom / K5TRA

2 1

Fwd: echolink station denied
by kk6ecm 17 Jan '14

17 Jan '14

deny=ea8cab, ea7jse ; on a line by itself Like your last statement but with "deny" one "d" Sent from iPad Begin forwarded message: > From: ea8ee <ea8ee1(a)gmail.com> > Date: January 17, 2014, 3:25:04 PM PST > To: kk6ecm <kk6ecm(a)gmail.com> > Subject: Re: [App_rpt-users] echolink station denied > > [el0] > confmode=no > call=W6ABC-R ; Change this! > pwd=XXXXX ; Change this! > name=Asterisk-EL-channel-driver ; Change this to your real name! > qth=Asterisk-EL-channel-driver ; Change this to your actual QTH! > email=foo(a)bar.com ; Change this! > maxstns=20 > rtcptimeout=10 > node=123456 ; Change this! > recfile=/tmp/recorded.gsm > astnode=2345 ; Change this to your active Allstar node number! > context=radio-secure > server1=server1.echolink.org > server2=server2.echolink.org > server3=server3.echolink.org > freq=145.000 ; Freq in MHz > tone=100.0 ; CTCSS Tone (0 for none) > lat=34.74978 ; Latitude in decimal degrees > lon=-92.27666 ; Longitude in decimal degrees > power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) > height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet) > gain=7 ; Gain in db (0-9) > dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction)deny=EA8CAB,EA7JSE > ddeny=EA8CAP,EA7JES > this is correct?? > > > > > 2014/1/17 kk6ecm <kk6ecm(a)gmail.com> >> See http://ohnosec.org/drupal/node/56, how to deny Echolink nodes in Asterisk Echolink.conf. >> >> Bob >> kk6ecm >> >> >> >> Sent from iPad >> >> >> On Jan 17, 2014, at 2:05 PM, ea8ee <ea8ee1(a)gmail.com> wrote: >> >>> >>> >>> Hello I would like to put on the list of stations not allowed to echolink some stations as I can do into the asterisk node >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >

1 0

echolink station denied
by ea8ee 17 Jan '14

17 Jan '14

Hello I would like to put on the list of stations not allowed to echolink some stations as I can do into the asterisk node

2 1

Telemetry Help
by W2YMM 17 Jan '14

17 Jan '14

Hello, I wanted to know if there is a way to shut off or limit announcements that I hear on my Allstar node. When connected to a large hub I very often hear "Remote Already In This Mode" and I'll hear when stations connect and Disconnect from each other, or if a call fails. I'd like to turn that off, but can't seem figure out where to do it. I looked at the Telemetry section here http://ohnosec.org/drupal/node/102 but It doesn't look like anything on my node.. At least in /etc/asterisk/rpt.conf Any help would be greatly appreciated. Thanks Robert Prybyzerski Jr W2YMM 631-960-1051 http://www.w2ymm.com Allstar 28183

1 0

not in data base
by Terry Meadows 16 Jan '14

16 Jan '14

My node (28549) was up in running fine. With IAXRPt working and Zoiper. Just fine-until I went to the allstar portal and tried to implement a APRS change. I now can no longer access other nodes, or use Zoiper or in the web transceiver list. I think I am no longer in the data base. I can access echolink stations,but not allstar nodes.

1 0

Re: [App_rpt-users] Echolink node
by Tim Sawyer 16 Jan '14

16 Jan '14

Right, the Echolink node can be any existing node in your system. I have a node dedicated to Echolink with no radio attached. That way I can completely dis/connect Echolink as needed. -- Tim :wq On Jan 16, 2014, at 9:14 AM, Mike/W5JR <w5jr.lists(a)att.net> wrote: > Tim, thanks. I think I get it. The echolink.conf points to a defined node. If I set up a node as non-radio (hub) or even private, then that can be the "Echolink" node. > > tnx > Mike / W5JR > Milton GA > >> On Jan 16, 2014, at 10:48 AM, Tim Sawyer <tim.sawyer(a)mac.com> wrote: >> >> There is nothing to set in rpt.conf other than the two level adjustments and the (not required) announcement setting. >> >> Here’s my echolink.conf from a working node. Note the Allstar node is set here, not in rpt.conf and must point to an active node on your server. >> >> [el0] >> confmode=no >> call=WD6AWP-L ; Change this! >> pwd=xxxxxx ; Change this! >> name=Tim ; Change this to your real name! >> qth=HB RACES [Allstar 2534] ; Change this to your actual QTH! >> email=xxxxxxx(a)gmail.com ; Change this! >> maxstns=20 >> rtcptimeout=10 >> node=520439 ; Change this! >> recfile=/tmp/recorded.gsm >> astnode=2534 ; Change this to your active Allstar node number! >> context=radio-secure >> server1=server1.echolink.org >> server2=server5.echolink.org >> server3=server3.echolink.org >> ;naeast.echolink.org >> ;nasouth.echolink.org >> ;servers.echolink.org >> ;backup.echolink.org >> freq=145.140 >> tone=110.9 >> lat=33.677793 >> lon=-118.000978 >> power=10 >> height=50 >> gain=6 >> dir=0 >> >> >> -- >> Tim >> :wq >> >>> On Jan 15, 2014, at 10:36 PM, Mike/W5JR <w5jr.lists(a)att.net> wrote: >>> >>> Need some direction here. I have added the echolink.conf file and the Echolink server is listing the callsign as available. This is the extent of the Echolink help that I've found on the ohnosec site. >>> >>> What I've not be able to locate is what (proper) entries need to be made in the rpt.conf file to support a given AllStar node as an Echolink node. I found the old "announcement" proclaiming Echolink support but following the detail for rpt.conf has not resulted in a working node nor the AllStar node showing active in the web listing. Loading my modified rpt.conf file kills one of my repeater nodes while another and two hubs continue to work. >>> >>> Any examples or pointing me to additional on-line help would be much appreciated. >>> >>> This is an ACID installation. >>> >>> tnx >>> Mike / W5JR >>> Milton GA >>> _______________________________________________ >>> App_rpt-users mailing list >>> App_rpt-users(a)ohnosec.org >>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >>

3 3

Echolink node
by Mike/W5JR 16 Jan '14

16 Jan '14

Need some direction here. I have added the echolink.conf file and the Echolink server is listing the callsign as available. This is the extent of the Echolink help that I've found on the ohnosec site. What I've not be able to locate is what (proper) entries need to be made in the rpt.conf file to support a given AllStar node as an Echolink node. I found the old "announcement" proclaiming Echolink support but following the detail for rpt.conf has not resulted in a working node nor the AllStar node showing active in the web listing. Loading my modified rpt.conf file kills one of my repeater nodes while another and two hubs continue to work. Any examples or pointing me to additional on-line help would be much appreciated. This is an ACID installation. tnx Mike / W5JR Milton GA

2 1

iax2 Registry Revisted - Question
by Christopher Kovacs 16 Jan '14

16 Jan '14

Further info and clarification I am using the Xipar Asterisk release. If I loose WAN network connection, I loose my iax registration which is what I would expect. Note, this loss usually is a result of a cable modem resetting, or some other issues with the cable company and it does not happen frequently. This reset does not result in a new IP address being assigned. I noticed that the State toggles between Timeout and Request Sent, but never will get re-registered until I stop and start asterisk (amportal stop/start). My questions is, Is this normal behavior? should I need to restart asterisk? I am using the following script in cron to check the status and reboot if necessary: #!/bin/bash # # IAX Registration Check, Nofity if offline. # if offline, then allstar will be unavailable # check iax2 registration: IAX_REG=`asterisk -r -x "iax2 show registry" | awk '{ print $6 }' | grep -v State` IAX_REG1=`echo $IAX_REG | awk '{ print $1 }'` IAX_REG2=`echo $IAX_REG | awk '{ print $2 }'` if [ "$IAX_REG1" != "Registered" ] || [ "$IAX_REG2" != "Registered" ]; then echo "Not Registered, take action..." amportal stop sleep 120 service portreserve restart amportal start else echo " All is good..." fi This will get iax to register, but I would think there is some thing wrong with asterisk not being able to re-register without a restart/reboot. Or is this normal behavior? Thanks, 73, Chris w0anm

2 1

allmon local monitor
by Greg 14 Jan '14

14 Jan '14

Just looking at this again and I'm not sure what "local monitor" is compared to "monitor"? Thanks Greg

2 1

Re: [App_rpt-users] Has this been updated?
by Geoff 13 Jan '14

13 Jan '14

On 01/12/2014 06:46 PM, Kevin Custer wrote: > On 1/11/2014 3:32 PM, Geoff wrote: >> kd3su.us/*allStar*/acid-sysadmin.pdf? >> >> how far out of date, is it? >> >> -Geoff/W5OMR > > > Geoff, > > Considering it was written at the end of 2008, a good bit might be > missing. Some commands like ctcssfrom=usbinvert and rxsquelchdelay= > are not mentioned in this document, so it's certainly inconsistent > with more modern documentation like what's available directly on the > allstarlink.org site. Yup. I got that from the guy's site it's on. My observation was, that it was fairly well documented and easier to understand than anything I can look up on ohnosec.org. Perhaps -that- could be a project for someone who's more fluent in allstareese. ;-) Don't get yer bottom lip pooched out, Tim... I appreciate all the time, work, and effort you put into your project, and this just may be -me- (and if so, I'll find other sources and not drag the rest down to my level) but cumbersom, non-intuitive and lacking on information (providing you find it) are what *I* get from stumbling and fumbling around in drupal.

3 2