I will test it this Wednesday, but I think I got some good spots when in LZ, SV, etc.however I cannot tell, as at the same time I was experiencing RBN not spotting me on 10MHz at all, thus I used my apps to spot.
Your post made me curious, so I will try spotting via RBN-hole at next activation in LA.
Can you give a rough timeframe? I have logs. I can debug things with more information.
In short, CEPT won’t matter, unless your alert doesn’t match the CEPT prefix. Ie, you alert for DL1AAA and RBN sees OK/DL1AAA, then you won’t get spotted because your alert is wrong.
Re timeframe:
I forgot to check when the data was still easily available, but I think that RBNHole did not spot me during the following two activations:
a) Date:20/Mar/2017 Summit:HB/UR-042 (Badus/ Six Madun) Call Used:HB9/DK3IT/
Time ca. 12:25Z - 13:00 Z
b) Date:21/Jun/2017 Summit:OE/TI-358 (Patscherkofel) Call Used:OE/DK3IT/P
Time ca. 10:20Z - 11:44Z
In both cases, sooner or later a kind chaser did spot me, but I think there were additional spots on RBN that did not pass RBNhole, e.g. for additional frequencies I tried.
In case of a), the problem might have been that many skimmers are bad at skimming at low speeds (12 WPM or so), in particular for complicated callsigns (CEPT prefix and /P). In case of b), maybe the manual spot came to quick.
I just wanted to be certain that RBNHole does support prefixed callsigns.
Does it handle the oddities where visitors have to use a variant on the prefix?
The one that comes to mind is CT3 where visitors use CT9/*****. RBNHole didn’t spot me but then that could be my dreadful CW keying