[Dxspider-support] RBN Callsign Rejection

Bill Shell wshell at wshell.org
Wed Oct 7 19:49:43 CEST 2020


Jim,

I think I failed to do the load/prefix command after I ran the script to 
download the updated files.  I redid the update and issued the command, 
and it is working now.

TU es 73,
Bill
N6WS


On 10/7/2020 9:40 AM, Jim Reisert AD1C via Dxspider-support wrote:
> You should not need to edit any files.  4U74UN is already in the latest CTY.DAT:
>
>      https://www.country-files.com/cty-3017-02-october-2020/
>
> That release was announced on this reflector on October 2.
>
> On Mon, Oct 5, 2020 at 12:40 PM Dirk Koopman via Dxspider-support
> <dxspider-support at tobit.co.uk> wrote:
>> There is a node wide definition of a "valid" callsign. It is a
>> large(ish) perl regex. It is used very frequently. It also uses the
>> CTY.DAT data and if that is not up to date or a special callsign isn't
>> in there then if both these checks fail then you will get this message.
>> Or, just maybe (and whisper this quietly) there is a bug!.  There are
>> certainly 'features' some of which might be a problem :-)
>>
>> I am already aware of some issues with blizzards of leading and trailing
>> '/' characters which needs attention both in this area and in sh/dx.
>>
>> These and other issues will be dealt with when I finally finish my (now
>> several weeks of) antibiotics. I am feeling much better - but not
>> actually well.
>>
>> In the meantime, however, I need to say that will be no "white" list as
>> such for RBN. You can have your own local copy of cty.dat (lower case)
>> in /spider/local_data, add callsigns to the correct entity and then run
>> /spider/perl/create_prefix.pl  + 'load/prefix' in the console. That
>> *should* fix it - at least until the next cty.dat comes out.
>>
>> 73 Dirk G1TLH
>>
>> On 05/10/2020 17:03, Bill Shell - N6WS via Dxspider-support wrote:
>>> Here is an example of the 4U75UN callsign rejection.
>>>
>>> 16:00:17 (*) RBN: ERROR invalid prefix/callsign 4U75UN from VE6JY-# on
>>> 18071.6, dumped
>>>
>>> 73, Bill
>>> N6WS
>>>
>>> On 10/5/2020 6:53 AM, Bill Shell - N6WS via Dxspider-support wrote:
>>>> Hello All,
>>>>
>>>> I noticed in the N6WS-6 debug log the callsign 4U75UN is being
>>>> rejected as a bad callsign as a RBN spot.  Is there a way I can allow
>>>> some known callsigns to pass?  Is there a RBN callsign whitelist?
>>>>
>>>> TU es 73,
>>>> Bill
>>>> N6WS
>>>>
>>>> p.s. The newest version of DXSpider is running without any problems
>>>> here, except as noted above.
>>>>
>>>>
>>>> _______________________________________________
>>>> Dxspider-support mailing list
>>>> Dxspider-support at tobit.co.uk
>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>



More information about the Dxspider-support mailing list