Sorry. Your device is not a genuine SHARI.? It is a Chinese clone. It is not supported on this group.

Is it possible to run Ham Clock on a pi 3b+ while also also running All Star, or will one system overwrite the other?

Requesting help with configuration of a Raspi Node.
Thanks in advance!

RPi image: RPi-Z2W-2-3-4_V1.7-01_Allstar.img.xz burned using Raspberry Pi Imager v1.7.2 [Linux]

Node includes a Raspi 3B+ and SHARI. (SR110U - SA818 Ham Allstar Radio Interface)

Node radio:

Adjusted frequency & CTCSS with programming software for SA818 SR110 SR-FRS radio module.
Windows software: SA818_SRFRS.exe
Is 'WriteSA818' the correct programming button ? [tried both]



Jumbospot radio is not detecting a signal. Testing with an HT with CTCSS. Using the COS LED as an indication of received signal.

Configuration: /usr/local/sbin/firsttime.sh

Report Status - Yes
CW ID - No
Bind Port - 4569
Duplex Setting - 1
IAXRPT Password - No
SIMPLE USB CONFIGURATION
EEPROM Setting - eeprom=0
Audio Boost Setting - rxboost=0
Carrier Detection Setting - carrierfrom=usbinvert
COR Inverted - Yes
CTCSS Setting - ctcssfrom=no
PTT Setting - invertptt=0
PL Filter - plfilter=yes
De-emphasis Filter - deemphasis=no
Pre-emphasis Filter - preemphasis=no
RX Audio Delay - rxaudiodelay=0
AUDIO LEVEL SETTINGS
RX Mixer - rxmixerset=500
TX Mixer A - txmixaset=500
TX Mixer B - txmixbset=500

Have also followed instructions to enable the COS LED and configure Supermon v6.2+

Thanks again!

开云体育

Here is what I ultimately want to do.

I want to host one or more voices somewhere, probably a github repository, then create a script that anyone can run direct from their shell via curl piped to bash, or by downloading it for those who don't trust that method. Fair enough if you don't.

This script would do the following:

1. Detect if your system is running HamVoIP, ASL or neither. This can be done programmatically in a few ways. There are some differences between the HamVoIP and ASL sound packs. HamVoIP uses GSM files for everything, while ASL uses a mixture of both ulaw and GSM. Mostly ulaw. In the case of HamVoIP, there are a bunch of scripts that are hard-coded to look for .gsm files. I'll get to that later.

2. Detect if a third party voice has been previously installed already, and if so, which one. This can be written out in a number of ways when a voice has been installed on the system.

3. Display a menu of available voices, assuming more than one, with an option to play a demo file locally to your node, so you have an idea of how things will sound before installing. After all, what I like may not be what you like. I'd like to have at least one male and one female voice, with a couple of variations on speed. One normal, one faster. That kind of thing.

4. Back up your existing /var/lib/asterisk/sounds/ folder before installing a new voice. In the case of HamVoIP, there are also a few sound files outside of this directory that are called with some specific scripts, like saypublicip, sayreg and saydns, I believe.

5. Downloads .ulaw files to the appropriate place. I'm not a fan of the GSM format, and since we don't need the full asterisk sound pack for app.rpt (this can be cut down to a little over 400 samples), with a better edited, faster voice, the files will be of much higher quality, and take up less storage as well.

6. On HamVoIP, do a find/replace on every .sh and .pl file in /usr/local/sbin, replacing .gsm with .ulaw or .sln, which ever file format ends up being used. Ignore this step if using ASL.

6.1. Since HamVoIP likes to redownload all of these scripts for most updates, a mechanism should exist to easily fix things after an update without the need to download a sound pack again. Alternatively, just use .GSM files and cry about the lower audio quality, at least if you're me... I personally can't stand that grainy, washed-out sound. Asterisk actually does better if you use raw linear PCM or ulaw anyway, as it's one less layer of potential transcoding, even for the stack connected to a radio channel driver.

7. After the voice is installed, prompt the user if they would like to run the write-node-callsigns.sh script from HamVoIP (after checking if it exists on the system) with the new audio files. For extra credit, if it doesn't exist, add an option to periodically add new calls on a cronjob if desired.

On day two of having a fully working HamVoIP node back in September of 2019, I made a new, extremely fast sound pack for myself using the Apple Fred voice, because it was easy for me to script. Basically, what I did was write a bash script on Mac OS with a while loop that read a tab delimited text file with all the prompts written out in the first column, then the path to write each file in the second. Since Apple's say command only writes out .aiff files, everything was then processed by SoX to filter, normalize and trim each sample to make it extremely responsive. Since I used .ulaw files, I wrote another script that uses sed recursively to replace any occurrence of .gsm with .ulaw in all .sh and .pl scripts in /usr/local/sbin.

I am a screen reader user, so I listen to fast, synthetic speech every day. It is no exaggeration to say that my node says "N2DYI Disconnected" in only a little more time Allison would say "N2" on a normal setup.

That being said, this voice is not one I would recommend for a wide area repeater, and it has some bugs that I never fixed, because it's for my own personal use, and I don't really care too much about the bits that are broken, but if anyone here wants it, no warranties, let me know.

I have access to many high quality options that are licensed for non-commercial, commercial and broadcast/transmission use, so it's just a matter of painstakingly creating each sample, probably with a few variations each, multiple times for different voices, batch-processing the audio for high intelligibility at the low 8 kHz sampling rate, getting the timing just right, etc. I can do all that. It's part of my profession. But none of that does any good if it's not easy to install on a system.

I would love to get something better out there especially for repeater operators, but really just anyone who is as annoyed at the stock Allison soundpack as I am. BTW, I was a long-time Asterisk user before coming to the world of Allstarlink/HamVoIP, having done managed a few commercial phone systems, so I had about 15 years of personal Allison annoyance behind me before I even built a node.

73

N2DYI

开云体育

开云体育

The audio part is (relatively) easy for me to do. I am less good at packaging something like that for easy distribution. I have lots of ideas, and know about half of what I need to make them a reality, regarding the replacement of the Allison Smith audio files.

开云体育

开云体育

开云体育

Hi:

The file that plays after Allison slowly and painfully says "I... P... address..." the way she slowly and painfully said everything, before the IP address is spoken, is your normal node ID.

If you go through the standard HamVoIP setup procedure USING THE FIRST TIME SCRIPT, and you told it to use a voice ID, this file will exist at /etc/asterisk/local/node-id.gsm by default. You can change the referenced ID to something else in /etc/asterisk/rpt.conf using the idtalkover and idrecording directives.

It just happens to play the ID since the node keyed up to say "I... P... Address..." and that is the first transmission from the node after bootup.

So, unless you want your node to ID with your node number instead of your call every <x> minutes, where <x> is the duration set in rpt.conf for the ID interval (not recommended for obvious reasons, unless it is part of an ID also containing the call)...

I recently downloaded the RPi-Z2W-2-3-4_V1.7-01 image to program a Raspberry Pi Zero.

Correction:?

/etc/asterisk/local/node-id.ul

You may wish to experiment with different ID files and call them in /etc/asterisk/rpt.conf for a little variety

I recently downloaded the RPi-Z2W-2-3-4_V1.7-01 image to program a Raspberry Pi Zero.
The Pi Zero works but I want to make a change.
When booting up or when the Pi Zero makes an announcement, the Pi Zero announces my callsign.?
I would prefer that the node number be announced.?
I am looking for the file or files that need to be edited to make this change.

开云体育

Yes, you will need to change any reference to 59886 with 598860

You don't need to do an entirely new install of your SHARI to change your node number.

Just run admin menu option 3, change the primary node number. Enter your new node number and password.

This isn't actually how I prefer to do it, but it's by far the easiest method. Otherwise, you could do a find/replace in /etc/asterisk/rpt.conf, /etc/asterisk/extensions.conf, /etc/asterisk/iax.conf and /usr/local/etc/allstar.env, replacing your old node number with your new one in all those files with a text editor. I have a lot of customization that many don't have, including running multiple nodes on a single rPi, and using the script to change node numbers would override almost all of them, because I never bother updating the templates.

If you haven't customized much about your node, this is the easiest way to go about things, though.

73

N2DYI

I recently purchased a ClearNode UHF to complement my Shari VHF unit. I went to Allstar to create the node number for the new UHF unit.?
Allstar change my existing Node for my Shari from 59886 to 598860 & the new ClearNode UHF to 598861.?
I understand why Allstar did this to save numbers for growth.?
When I look at my Portal information, it shows extension from base 59886 to two nodes 598860 & 598861.

Existing node 59886 working with no problem. However Allstar shows nodes not registered, but when I do the DTMF command it states node 59886 it
states registered. I assume if I reboot or shutdown 59886, once it comes back online it will state node not registered since Allstar shows 598860.

I assume that all existing node 59886 will need updating to 598860.
Is my logic correct?

Thanks,
Rich H W9ABE

My node appears to not 'hear' my HT on an intermittent basis.

This issue is relatively new. After setting up the node I was able to use it as expected for several months. Recently when I attempted to connect to other nodes (Win System, Parrot, etc.) I get a response from my node to my HT only intermittently. I have updated the node system and rebooted it several times. I have tried different HTs. On some occasions (when I push the PTT on my HT(s)) the node responds as expected, but most times there is no response from the node. On those occasions the red light on the node does NOT illuminate. I have turned off every other transmitter within the shack to eliminate any source of de-sensing. The node antenna is tight. Nothing works.

Any ideas on what I'm missing or what I might try?

W5JVJ Larry

The SHARI set up procedures which are used with the various SHARI nodes to install the HamVOIP Allstar software are in the Files section of this group.? Version 2.01 of the SA818-prog program which is used tp program the SA818 radio module is also in the Files section.

开云体育

At the risk of sound dumb. Where is the Shari program file??


Thank you

Thanks all!!! I am going to try the Shari until I get a separate Pi4b.? I am not going to need the 100's of connections.? Patrick, can you 'splain the sound card addition?? I really need to look at that for another repeater!!!? Links?