toggle quoted messageShow quoted text
Well, I ran into that problem myself and just got it fixed. My node WAV file was telling people I was in England instead of Korea. And since I'm moving it to the states soon, I'll have to do it again. Good luck.
From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> On Behalf Of larry_n7fm
Sent: Thursday, October 10, 2019 5:19 PM
Subject: Re: [IRLP] Irlp Custom connect wav files
You are correct. Just not what the new owner wants but may have to live with. Either that or do a rebuild with a new node number.
Make me curious how they dealt with the reclaimed node numbers that had custom connect files that propagated previously. Maybe some fellow in Canada was issued a reclaimed node number that has a stnxxxx file that propagated saying he lives in Miami and he doesn't know it.
Larry - N7FM
On 10/9/19 11:31 PM, dale.tongue wrote:
If you create/edit a file for stnXXXXon and stnxxxxoff and do the
upload per the manual, it will take care of it for you if I’m not mistaken.
It’ll wipe your other files and add the new files, which will get
populated through the network..
*From:*IRLP@irlp.groups.io <IRLP@irlp.groups.io> *On Behalf Of
*Sent:* Thursday, October 10, 2019 2:28 PM
*Subject:* [IRLP] Irlp Custom connect wav files
I recently sold one of my IRLP nodes.
Sadly when I was new to IRLP years ago. I didn't realize that creating
a custom connect wav file would become a problem.
I was foolish enough to created a custom connect wav file which
included my callsign not realizing once it was activated there was no
option to stop or revert back to normal.
Bet most everyone reading this is already thinking "Dummy" and can
visualize my problem.
Yup ... when the new owner I sold the node to.connects ... it
announces/identifies on the other end with my callsign.
I do realize creating a new custom file will replace my problem file.
However the new owner would like the node to revert to original
Which it can't as long as a stnxxxx wave file exists.
Has anyone come up with a way to reverse or stop the custom
stn(node_number) from spreading to other newly connected nodes?
Is it possible for IRLP support to delete custom stnxxxx wav files if
Once deleted from the IRLP server it would stop any *further*
propagation of that particular custom connect file.
Suggestions or solution? New install with a New number isn't something
he wants or is able to do.
What would really be nice ... is a script mod with an option flag "IF
EXIST delete" when checking for a new stnxxxx files for those of us
who want to revert back.
Larry - N7FM