Statuses

Partition Failure

by

The JL Applied Technologies web server suffered a partition failure because of a script that I wrote that went horribly wrong! As a result, we lost some data. I’m working on restoring the missing RasLink documentation.
RasLink and Debian node owners will *not* be affected by this problem on their systems! This failure only affects this server.
If you try to log in, and your account doesn’t work after the second attempt, please RE-REGISTER. Do *not* try to log in more then five (5) times! If you do, your IP address may be banned.
I apologize for any inconvenience. I’m working as quickly as I can to restore as much missing data as is recoverable. The RasLink image is the latest version.
If you have any questions, or need assistance, please Contact Us.

Messed Up Usbradio Configuration File Makes Crazy Large Log File!

by

Hi everyone.
From the land of oops, I’m writing to suggest that you make a careful study of your /etc/asterisk/usbradio.conf file.
When I put comments into the file for explaining the low pass and high pass filters, I got a little rushed and forgot to put “;” (semicolons) on a few lines.
So, if you’re using the filters, here’s what you need to do:
There are two ways to fix this.
1. run:
cd /usr/src/utils
git pull
cp /usr/src/utils/AllStar-build/configs/usbradio.conf /etc/asterisk
Reset your configuration by editing the file.
Note: The fixed configuration will not be loaded until you run service asterisk restart or reboot your node.
2. If you don’t want to reconfigure usbradio.conf, run the following commands:
nano /etc/asterisk/usbradio.conf
CTRL+w
CTRL+r
Audio from internet
; Audio from internet
CTRL+w
CTRL+r
Audio to internet
; Audio to internet
CTRL+x, y, enter
I patched the files in the update repository, as well as released a new image so that new users won’t have to deal with this.
Also, if you try to run nano /var/log/asterisk/messages, and it seams to hang, don’t freak out! Your node *isn’t* broken! Your log has probably gotten huge from Asterisk trying, and failing to read those four lines you just fixed as variables.
I apologize for any inconvenience this has caused.
If you need help, use the contact form.
73,
Jeremy W0JRl

Catching up with our listeners

by

Hi there,
After over two months of saying we’re going to record more podcast episodes, here we are.
We are actually, finally, definitely, going to record one today.
On behalf of Jl Applied Technologies, I would like to extend my own personal apology to our listeners for keeping you all waiting. We didn’t forget about you, but we had some technical issues to overcome, as well as and let’s all be honest here, procrastination.
This episode will be entitled “No Windows, no problem!”
Now that that’s taken care of, I would like to let everybody know that we now have a Zello channel.
If you would like to connect with us, we are willing to have a preshow chat with anybody who wishes to join.
Search for jltech and come right in, and have some fun. All we ask is that you obey the rules and respect everyone in the channel.
So with that said, we’ll be seeing you on Zello, and thanks for sticking around after so long without any news from us, we really appreciate it.

JL Applied Technologies