It seems unlikely the problems are caused by the current issues of multiple non-gateways/hotspots trying to link from the same IP or using the same callsign. I also see your DStar repeater was put up in Sept 2008 – so it was part of helping DStar become what it is today. I see from that your repeater is running G3, is syncing normally with the Trust Server, and is running authentic DPlus. I am simply an admin at a DStar Gateway and have looked into some recent issues because people registered at our gateway have asked. So please don't connect multiple hotspots to those reflectors. Developers have been contacted and have or will be changing their software, but until your hotspot has been updated, REF001C and REF030C may permanently block your IP or callsign from linking to these reflectors. Some hotspots have had a flaw in their software that repeatedly attempts to re-connect, even when the reflector returns a "busy" code, using up network bandwidth. If you do, the system will notice this and block multiple hotspots at the same IP address or callsign. Special note regarding reflectors REF001C and REF030C : Once registered, if you have more than one hotspot at the same IP address (usually meaning at the same location) or using the same callsign, DO NOT LINK MORE THAN 1 HOTSPOT to REF001C or REF030 C. After learning more, I posted a note about it on our main registration page at and I just updated it. They had been complaining their IP or callsigns were being blocked from linking to the above reflectors. This is a minor update - I am getting fewer linking problem reports from hams whose callsigns are registered at the W6CX D-STAR Gateway that I administer.
0 Comments
Leave a Reply. |