[arm-allstar] connection announcement uses incorrect call sign
Patrick Perdue
borrisinabox at gmail.com
Fri Mar 29 09:19:15 EDT 2024
Mark:
Is this a node you put together yourself, or was it built from a
pre-existing image, I.E. G7RPG, G4XYR, etc?
Sounds like the write_node_callsigns.sh script has been run at least
once on your node, and there is no job in crontab to keep it up-to-date.
Do you have a file called
/var/lib/asterisk/sounds/rpt/nodenames/<your-node-number>.gsm, where
<your-node-number> is your actual node number?
From bash, you can run
write_node_callsigns.sh -ao
which will overwrite all the files in /var/lib/asterisk/rpt/nodenames,
using the calls as set for each node number according to
allstarlink.org. This will take a few minutes.
Or, you can overwrite just a single node number by issuing
write_node_callsigns.sh -n <specific-node-number> to just update a
single node.
HTH.
73
N2DYI
On 3/28/2024 11:35 PM, Mark Harris via ARM-allstar wrote:
> Good afternoon to all.
>
> I have noticed that my node is using a different call sign than the
> nodes registered call sign when doing a connection.
>
> The call sign that it uses is an old one that I no longer have and I
> am wanting to change it to the correct one being the nodes registered
> call sign.
>
> I have tried to find where the reference for this connection call sign
> is but have not had any luck and hoping someone can point me in the
> correct direction.
>
> the announcement that comes over my radio is: " other node number "
> connected to " my incorrect call sign ".
>
>
> Regards
>
> Mark VK3EME
>
> Bendigo, Vic AU
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
More information about the ARM-allstar
mailing list