Bryan, I am not sure. Perhaps the database is corrupt? I just re-ran mine and it does not seem to burp - Processing Node Number: 1000 - Callsign: WB6XYZ Processing Node Number: 1499 - Callsign: WA3DSP Processing Node Number: 2000 - Callsign: WB6NIL Processing Node Number: 2001 - Callsign: WB6NIL Processing Node Number: 2002 - Callsign: WB6NIL Processing Node Number: 2003 - Callsign: WB6NIL Processing Node Number: 2007 - Callsign: WB6NIL The first two entries you would not have so I suspect the node 2000 would be the first one you process. That means there is probably something wrong in the database. Try - grep -m 1 2000 /var/log/asterisk/astdb.txt 2000|WB6NIL|ALBACORE HUB|Downtown Los Angeles, CA replacing the path to your path if different. Are you seeing the same thing I am seeing? Maybe someone else has an idea? 73 Doug WA3DSP http://www.crompton.com/hamradio
Date: Tue, 18 Aug 2015 19:38:06 -0400 From: bdboyle@bdboyle.com To: doug@crompton.com Subject: Re: [App_rpt-users] modified custom nodenames
Doug:
When running...line 42: 35: while IFS='|' read f1 f2 f3 f4 36: do 37: 38: echo "Processing Node Number: $f1 - Callsign: $f2" 39: 40: STRING="" 41: 42: foo=${f2,,} 43: for (( i=0; i<${#foo}; i++ )); do 44: char=${foo:$i:1} 45:
gives me:
[root@WB0YLE scripts]# ./makenodenames Processing Node Number: 2000 - Callsign: WB6NIL ./makenodenames: line 42: ${f2,,}: bad substitution
?
I'm usually able to suss that out, but, this doesn't make sense (of course, it's been 4 years since I did any sort of bash programming...)
Thanks for insight.
-- Bryan In this world, you must be oh so smart or oh so pleasant. Well, for years I was smart. I recommend pleasant. You may quote me.
Sent from my MacBook Pro.