[arm-allstar] connection announcement uses incorrect call sign

[Dave Petrie]

here is a better more detailed explanation from Doug.
http://lists.hamvoip.org/pipermail/arm-allstar/2020-June/015149.html


On Fri, Mar 29, 2024 at 8:42 AM Dave Petrie <wa2kjc at gmail.com> wrote:

> FOUND IT, yea now i can take the rest of the day off.
> after you do the updates as i put in previous comments then
> here is what fixed it, putty, menu 9 and then type,
> write_node_callsigns.sh -n 44099 -o   and hit enter
> do the same for any other node not announcing correctly.
> Dave
> wa2kjc
>
>
>
> On Fri, Mar 29, 2024 at 8:18 AM Dave Petrie <wa2kjc at gmail.com> wrote:
>
>> ok, i just deleted my astdb.txt and ran astdb.php and then i searched my
>> new astdb.txt for
>> your nodes 44099 and 470820 and they both showed up with callsign VK3EME
>> but when i issue a connect monitor to 44099 i hear VK3RME announced and
>> when i connect to 470820 monitor i get the node announced but no callsign,
>> soooo it is someone else's turn to try and figure this out.
>> Dave
>> wa2kjc
>>
>> On Fri, Mar 29, 2024 at 7:32 AM Dave Petrie <wa2kjc at gmail.com> wrote:
>>
>>> login to you node with putty, menu 9, type   astdb.php and hit enter
>>> that should update your node info on your raspberry.
>>> If you need to see below and make sure you privatenodes.txt is correct,
>>> also if need be delete the astdb.txt before running the astdb.php
>>> command.
>>>
>>> To update your allstar node daily, add this in /etc/asterisk/rpt.conf
>>> Place this in your allstar node [schedule] area.
>>> 15 03 * * * /usr/local/sbin/astdb.php cron
>>> It simply calls the update everyday at 3:15 AM. The "cron" parameter also
>>> tells the script to stagger the actual downloading of the data randomly.
>>> The script downloads the data and also the private nodes info located in
>>> /etc/asterisk/local/privatenodes.txt, sorts it and writes it to
>>> /var/log/asterisk/astdb.txt
>>> Edited by WA2KJC
>>>
>>>
>>>
>>> On Fri, Mar 29, 2024 at 7:25 AM Mark Harris via ARM-allstar <
>>> arm-allstar at hamvoip.org> 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
>>>>
>>>