- App_rpt-users - lists.keekles.org

Recheck your connectivity: bug found and fixed in allstarlink registration server code
by Stephen Rodgers 03 Jun '09

03 Jun '09

A bug was found and fixed in the allstarlink registration server code which was propagating incorrect port numbers to all of the nodes past node 2298. Jim Dixon fixed the problem, and now the port numbers should show up correctly in rpt_extnodes Steve WA6ZFT

1 0

iGoLogic i3386G
by Jim Richardson 02 Jun '09

02 Jun '09

Has anyone been able to build limey linux for this board? What I'm trying to build is the cf image I downloaded from: http://limeylinux.org/downloads/cfimg-i3386g-1.0.7-test4.tar.gz The source I downloaded does not have a makefile entry for the i3386g. There is no kernel config file either. http://limeylinux.org/downloads/ll-vers-1.0.7-test.tar.gz Makefile #MOBO?=VIA # for VIA Mini-itx M6000, ME6000, SP8000, or CN10000 #MOBO?=D201GLY2 # for Intel/Jetway D201GLY-2 motherboard MOBO=D945GCLF # for Intel Atom D945GCLF Any help would be appreciated. Jim. WA1SOT AllStar node 2370

2 2

Echolink, anyone else having this?
by Buddy Brannan 02 Jun '09

02 Jun '09

Hi all, Just wondering if anyone else is having this issue or may have some idea what's going on? Running the latest SVN build of the app_rpt and the asterisk 1.4.23- pre from the SVN repository, with chan_echolink and chan_irlp. Everything seems to work OK for the most part; occasionally get random DTMF tones thrown out over the transmitter from Echolink, but not as much as in earlier incarnations. Audio levels also seem consistent across the board. The one issue I seem to be having, though, is that connecting and disconnecting from Echolink nodes seems to take a really, really long time, sometimes well over a minute. During this time, no audio is repeated, and the transmitter stays keyed. I couldn't say whether DTMF decoding still occurs and is tied up in a queue somewhere, but I don't think so. Also, possibly related: I was connected to another Allstar node on Saturday. This node was connected to a bunch of Echolink nodes through rptdir, and I was connected to one Echolink node using chan_echolink. At some point several times, the Echolink node I was connected to would drop. When it dropped, I had the same issues as above: it took an age to actually drop, and during this period, no audio was transmitted. This would happen when someone was talking from the ASterisk link; I'd hear the linked station, then the transmitter would drop all audio (dead carrier), until I got an indication that my Echolink station had dropped. If I'm at a console, doing a reload wakes the system up, but doesn't necessarily prevent the disconnect (or continue the connection if connecting to Echolink). This behavior only appears to be present with Echolink. IRLP and Asterisk connections seem to have no trouble at all. Anyone else, or anyone have an idea what's happening here? Buddy, KB5ELV

2 1

Allstar Registration
by Scott Weis 01 Jun '09

01 Jun '09

I'm having a problem with the allstar link registration. On the server it says: 67.215.233.178:4569 N A2298 69.248.135.12:4568 60 Registered Note the 4568 on the registration.. In the file transferred from allstar I get: 2298 = radio@69.248.135.12:4569/2298,69.248.135.12 Note the port is 4569. How can I fix this?? Thanks, Scott

2 1

Possible source for CM108-based sound dongles
by Buddy Brannan 31 May '09

31 May '09

Hi all, Just came across this. Knowing how hard it is to come by the CM108- based sound dongles, thought some might be interested. Anyone used this particular one or bought from these guys? http://www.dealextreme.com/details.dx/sku.21812 $6.99 gets you one, slightly less for more.

1 0

StarTech USB Fobs
by Ramesh Dhami (VA3UV) 30 May '09

30 May '09

Hi Folks; This is a re-post of a problem that I've reported before - perhaps as time has passed, and more folks have experienced the fob modification, someone out there may have seen this.... I have modified a number of StarTech USB fobs (CM108 based), I have found that when the fobs have been modified, when you plug the fob into the PC (which is previously on), the PC seems to 'see' the fob as a stuck keyboard - I hear a cyclical beep from the PC speaker and some ascii characters on the screen [26] if I remember correctly. I tried this on 2 different PC's - an IBM 8172 and a DELL Precision Workstation. I powered down the IBM and re-booted it from cold with the fob attached - it seemed to power up fine and before long the LED on the new fob was flashing away - seems to be fine. On the DELL, same thing when the machine was already on. I shut the machine down, inserted the fob and restarted - no luck there, the machine continued to detect a stuck keyboard printing the ascii 26 across the screen... I couldn't even login since the ascii char's kept on printing across the screen. Back to the IBM - I connected my repeater to the fob and I have PTT out, audio out, when I issue a DTMF command, the DTMF char's print on the CLI, so obviously I have audio in and the fob senses a valid COS signal - all suggesting that the mod is OK. As I mentioned earlier, I have seen this a number of times with the StarTech fobs - just wondering if anyone else has seen this and whether there is an easy solution to this (sure would be nice to have the fobs inter-changeable between machines). Cheers, Ramesh.

1 0

Re: [App_rpt-users] Deviation settings for narrow band
by hwstar＠rodgers.sdcoxmail.com 29 May '09

29 May '09

> > From: "Mark Hergesheimer" <mark(a)hergesheimer.com> > Date: 2009/05/19 Tue AM 10:34:27 PDT > To: <app_rpt-users(a)qrvc.com> > Subject: [App_rpt-users] Deviation settings for narrow band > > I'm using a 12.5 KHz narrow band system with 2.5 KHz of deviation so when > setting up the URI, I referred to Steve's post "Adjusting Audio Levels" > using the URI. I also made the assumption that if a 1 KHZ tone set to 3 KHz > of deviation was correct for a 5KHz system then 1.5KHz would be correct for > my 2.5KHz system. So I set rxvoice to 1.5KHz and rxtone to .6KHz then with > txtone set to 0, I set txvoice to 1.5KHz and txtone to .6KHz. However when > this was complete I had low audio through the repeater and only 1.85KHz of > dev out. So I went back with the service monitor in duplex mode and adjusted > the txvoice up until I got my 2.5KHZ out and the repeater sounds very good > as a standalone. > > > > I have 2 questions and a comment, first, what are the correct numbers for > setting up a 2.5KHz system using the URI's? and why? > > Second, What would the best way to add a 5KHz node and keep the levels even > across the system? > > Comment: We recorded some voice announcements for repeater ID through our > Asterisk phone system at work to produce the wav files and the audio is > really great, as a matter of fact I'm very impressed with this whole app_rpt > deal !!! Thanks > > > > Mark > > > > > Mark, I've never deployed a 2.5 KHz radio on a node so the values are somewhat unknown. If you don't mind collecting some data, I'd like you to try the following with 2 nodes: 1. Configure and adjust a node with a 5KHz radio connected using the standard procedure. Don't worry about txtone and set it to 0 before adjusting txvoice. 2. Configure and adjust a node with a 2.5 KHz radio using your procedure of setting 1.5KHz for rxvoice, and txvoice. Don't worry about txtone and set it to 0 before adjusting txvoice. 3. Using your service monitor in duplex mode on the 5 KHz radio, see if you get 3.0KHz dev. on the TX while driving the RX with 3.0KHz of dev. on the input. Note the value. 4. Using your service monitor in duplex mode on the 2.5 KHz radio, see if you get 1.5KHz dev. on the TX while driving the RX with 1.5KHz of dev. on the input. Note the value. 5. Link the two nodes (using the adpcm or ulaw codec only, and not GSM!!), and check the audio transfer ratio between the two systems using a 1KHz tone at 1.5KHz dev. on the 2.5 KHz radio and a 1KHz tone at 3.0KHz dev. on the 5KHz radio (RX to 5KHz tx and 5KHZ rx to 2.5KHz tx). We would like to know what comes out of the 5KHz radio Note the values. 6. Report all the noted values back to this list. Steve WA6ZFT _______________________________________________ App_rpt-users mailing list App_rpt-users(a)qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users

3 3

(no subject)
by George Csahanin 27 May '09

27 May '09

Something just happened tonight. Sytem started running sluggish, iaxrpt stopped being able to connect, took a look and found about 30 instances of wget running as in updating the stats server. Netstat revealed the connections. This was about 10:30PM Central time. I commented out the two lines that do the updating in rpt.conf. Has anyone ever seen this? This is a no moving parts Limey Linux CF image for D945 GeorgeC W2DB Cedar Park, TX Node 2360 424835 el

3 2

re SSH time out
by Jon Rorke 27 May '09

27 May '09

Hi guys, I have noticed if I SSh into an Allstar node and leave it connected with no activity that eventually it will time out. Other nodes dont seem to do this. Is there a setting that governs this? and how does one set it to not time out if I want to monitor a remote node from the cli? Thanks, Jon VA3RQ

2 1

Mantis bug reporting guidelines
by hwstar＠rodgers.sdcoxmail.com 27 May '09

27 May '09

Guidelines for utilizing Mantis and reporting issues to Mantis (http://mantis.qrvc.com) 1. Check the list to make sure you aren't reporting a duplicate issue. If you see something already reported, add a note to that issue, and avoid opening a duplicate issue. 2. Turn on the monitoring feature so that you receive updates then the status of an issue changes. 3. Try to be as descriptive as possible when describing your issue. 4. Use the file attachment feature to attach any log files you might want to share. 5. If your issue disappears from the list. It was likely closed (grey) without a resolution. To look into why it was closed, click on the advanced filter link at the top of the list to view the closed issues. Updates which result in code changes will be tagged as resolved (green) and will be left on the list. Steve WA6ZFT

1 0