January 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

DMR to Analog/app-rpt
by K1IF 31 Jan '14

31 Jan '14

Travis KJ4NDP has successfully connected his DMR radio to asterisk by utilizing the dstar channel driver in asterisk created by Scott Lawson ki4lkf. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

3 2

DMR to Analog/app-rpt
by Bryan D. Boyle 31 Jan '14

31 Jan '14

beginning, with the growing interest in the DMR/trbo usage...to investigate integrating the two technologies. Connect Systems is starting to bring in DMR cable DMR/analog HTs for not a lot more than a wouxun...and, yes, know about the DMR-MARC group. But, my question...is anyone in the band investigating navigating the DMR to Asterisk chasm yet? PM is probably preferable than broadcast, unless there is interest on the part of the tribe....or I've missed something along the way... -- Bryan There are two hard problems in computer science: cache validation, variable substitution, and off-by-one errors. Sent from my iPad

5 5

Help getting started with RTCM and ACID
by Chris Bunting 30 Jan '14

30 Jan '14

I have 2 RTCM boxes configured, and an ACID install. I figured out I needed to create a voter.conf file, and it is as follows: [general] port = 667 password = @@@@@@ [28989] NORTH = @@@@@,transmit SOUTH = @@@@@,master,transmit (@ being my passwords) Do I need to change anything in the rpt.conf file? I read something about 1 line needing modified? Also, I am on a LAN and the server has a static IP, can I simply enter the IP in the FQDN field on the RTCM or must it be a FQDN that resolves? I tried both, and Ithink I'm doing everything right, but I can't get the darn box to connect to my server... After I get this connected it's time to break out the soldering iron and hook this all up to my 2 repeaters for my simulcast project... fun fun! Any hints/tips? TIA Chris N3FYI

2 4

Creating a Private Network
by Tim Sawyer 30 Jan '14

30 Jan '14

Creating a private network is actually pretty easy. What you do is add the node and IP address of the other node(s) to each server’s rpt.conf in the [nodes] stanza. Here’s an example with two private nodes. Server A’ s IP is 192.168.1.10 and B is 192.168.1.11. SERVER A rpt.conf [nodes] 1000 = radio(a)127.0.0.1/1000,NONE ; Local node 1001 = radio(a)192.168.1.11/1001,NONE ; Remote node SERVER B rpt.conf [nodes] 1001 = radio(a)127.0.0.1/1001,NONE ; Local node 1000 = radio(a)192.168.1.10/1000,NONE ; Remote node Of course you need to have all the normal stuff that nodes have in rpt.conf and extensions.conf. Private nodes do not need a register line in iax.conf. -- Tim :wq On Jan 30, 2014, at 3:51 AM, Lu Vencl <vencl(a)att.net> wrote: > Tim. Do you know how to connect one node to another via direct ip connect? In other words to a node that is not on the public network but private? > > Sent from my iPhone, Lu Vencl -- Tim :wq

1 0

lsnodes 1.03
by Doug Crompton 30 Jan '14

30 Jan '14

I fixed a bug in the display of Echolink nodes. All Echolink nodes should now display as ECHOLINK with call if data is available. http://crompton.com/hamradio/allstar/lsnodes.html wget http://www.crompton.com/hamradio/allstar/lsnodes-1.03.tgz 73 Doug WA3DSP http://www.crompton.com/hamradio

1 0