[arm-allstar] making Allstar Manager report different call for a node

[David McGough]

Patrick,

AllStar only knows your node by the node number and that's what's used 
during Asterisk Manager operations.  Yes, it looks like the ID "*BLIND*" 
is coming from the astdb.txt file. As mentioned, Asterisk Manager doesn't 
interact with this file at all....I'm suspecting that Analog_Reflector 
is directly grabbing the contents of the astdb.txt file, via some 
mechanism??  I don't know if A_R is looking at the local copy of this 
file, or if it's grabbing the node data via a query over the Internet?

If A_R is grabbing the data from the local astdb.txt file, you should be
modify it on your local system (the box where dvswitch is running) and 
resolve the issue that way.....This would probably be a question to ask 
Steve, N4IRS?

If you want to modify the astdb.txt file, directly after it's downloaded, 
you could follow the download process with something like this command:

### Set the ASTDB variable to the path to the astdb.txt file.
ASTDB="/var/log/asterisk/astdb.txt"
cd /tmp
cat $ASTDB | sed 's/506317|\*BLIND\*/506317|N2DYI/g' > astdb.tmp
mv astdb.tmp $ASTDB


73, David K4FXC


On Sun, 3 Dec 2023, Patrick Perdue via ARM-allstar wrote:

> Greetings:
> 
> I am using HamVoIP in combination with DVSwitch Server.
> 
> One node on my system has the call *BLIND* rather than a call sign to 
> indicate the conference it's connected to.
> 
> Analog_Reflector grabs metadata using Asterisk Manager and forwards it 
> to the digital modes, I.E. DMR, DSTAR and YSF.
> 
> However, it doesn't know what to do with the call *BLIND* and 
> transmissions from that particular node are not translated to the XLX 
> reflector.
> 
> Currently, A_R doesn't have a mechanism for this, so I was wondering if 
> there is a way to change what Asterisk Manager itself reports locally 
> from the node to a valid call, so that A_R is happy. I assume it gets 
> this info from astdb.txt, but I'm not sure how to override specific 
> entries in a way that won't get overwritten by astdb updates.
> 
> I could change the call associated with the node in the Allstarlink 
> portal, but I don't want to handle it that way.
> 
> 
> Thanks and 73
> 
> N2DYI
> 
> _______________________________________________
> 
> 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
>