[Dxspider-support] Joke or bug?

[Eric Carling]

A user from Dorset called me today to ask if his call was 'stuck' in my
cluster - he is working in Kent and his attempts to use DXK were being
thwarted with 'simultaneous connections not allowed'. His call was not stuck
here but does appear on the backbone in EDX. However when I connected to EDX
to leave a message for Darren to dump the phantom call I found that the real
EDX configuration was nothing like what the backbone is reporting and the
call was not listed in a show/users. Also I found several other extreme
cases for other clusters as well. The real and false configurations are
listed below. What is going on here? Is somebody deliberately injecting this
stuff into the network?

 

Callsigns connected to GB7EDX

CE4UYP-3 DK3WW G0TSM G0CGL G4UCJ

G4YTM M1SJX M3GMN ON4KST

 

 from a sh/c:

GB7EDX 2E0BRI 2E1HJS 2I0UCS 9A3GX CE4UYP-3

DK3WW DK7YY F1MAC F8ASY F8DQL

G0EGT G0MFR G0MJW G0PSE G0PZA

G0TSM G0TSM-1 G0TSM-10 G0TSM-11 G0TSM-12

G0TSM-13 G0TSM-14 G0TSM-15 G0TSM-16 G0TSM-17

G0TSM-18 G0TSM-19 G0TSM-2 G0TSM-20 G0TSM-21

G0TSM-22 G0TSM-23 G0TSM-24 G0TSM-25 G0TSM-26

G0TSM-27 G0TSM-28 G0TSM-29 G0TSM-3 G0TSM-30

G0TSM-31 G0TSM-32 G0TSM-33 G0TSM-34 G0TSM-35

G0TSM-36 G0TSM-37 G0TSM-38 G0TSM-39 G0TSM-4

G0TSM-40 G0TSM-41 G0TSM-42 G0TSM-43 G0TSM-44

G0TSM-45 G0TSM-46 G0TSM-47 G0TSM-48 G0TSM-49

G0TSM-5 G0TSM-50 G0TSM-6 G0TSM-7 G0TSM-8

G0URR G0WFT (G2JL) G4DXG G4KFT

G4UCJ G4YPV G4YTM G7VRK GM4NFC

GW4OGO HB9LA HG5OHT KB4SHK LA9VBA

M0CKE M0DHO M0JCC M1SJX M3LUC

ON4RK ON7UZ OO7UZ PY2BRZ VK6VZ

W7HPW