QRZ Call Sign Lookup

Ref Info

Introduction how to connect Reflectors on GB7SF D-Star

Repeater

comms

This document assumes that your local D-Star Node is:
1. Connected to the K5TIT trust server via the G3 Gateway network.
2. The D-Star Node you are working through needs to be running dplus version 2.16b or later.
3. The local D-Star Sysop has allowed user linking operations in the dplus configuration.
NB. At the time of writing all UK Gateway connected D-Star nodes meet the first two requirements.
Assuming that all of this in place, you should be able to access the Reflectors and link your D-Star
Node to either, another D-Star Node or a Reflector. If you’re not sure, check with local users on the DStar
Node or ask the Sysop for that D-Star Node. There are currently about 90  D-Star Reflectors, the main
ones are listed below:

Introduction
Okay, so what is a dplus Reflector? A Reflector acts as a central conference hub where multiple DStar
Nodes/DV Dongle users can gather and all talk to each other. There was a recent World Wide
Net; the objective of the net was to see how many D-Star Nodes and Dongle Users could connect to a
Reflector to gauge scalability and performance. Twenty eight D-Star Nodes, and eighteen Dongle
users connected to the Net. The system performed perfectly, and no performance issues were noted.
Fig.1 Example dplus Reflector (REF005 A) High Level Overview ref 006B is the Ref of GB7SF for any mobile Station to Chat on and us this Ref for chatting on at any Time they like please us this Ref

dplus Reflectors can be compared to virtual conference rooms, the likes of which you might have
heard if you have used EchoLink, IRLP or eQSO. Once your local D-Star Node is connected to a
Reflector you are able to receive and transmit via your local D-Star Node to every other Node that is
connected to the Reflector. In addition, Dongle Users are also able to connect directly to Reflectors.
Good operating procedure is to make a call through the Reflector announcing which D-Star Node you
are transmitting through. E.g. this is M0ABC on GB7DS port B calling on Reflector Five Alpha, or
similar.
dplus Reflectors have a number of benefits over the standard Icom G2 Multicast facility:
· improved bandwidth utilization for D-Star Node ADSL lines: only the Reflector server needs
enhanced IP connectivity to support multiple simultaneous connections
· direct user control via D-Star radio for linking and unlinking, no need for Sysop to predefine
Multicast Zones
· “sticky connection” so that only one user needs to link to the conference, other local users just
need to ensure that they have programmed G in the RPT2 suffix.

Assuming that all of the prerequisites on page 2 are in place, you should be able to access the
Reflectors and link your D-Star Node to another D-Star Node or a dplus Reflector. If you are not sure,
check with local users on the D-Star Node or ask the Sysop for that D-Star Node. There are currently
six dplus Reflectors for use with D-Star Nodes:
Reflector Location Notes

REF001: USA
REF002: USA
REF003: Australia
REF004: USA

REF005: London module A is preferred for the UK conference
module B is preferred  French , REF006: London module B  this ref was setup for Gb7SF Ref  UK  for mobiles to chat at ant time to  anyone worldwide

As previously mentioned, there are currently six Reflectors. You might see them referred to as
REF001, REF002, REF003 and so on. In addition all the Reflectors have three modules, A, B or C.
So for example, the World Wide Net mentioned above, took place on REF001 module C.

NOTE: In the context of a dplus Reflector the A, B and C references are modules and NOT
ports that you use on a D-Star Node. Reflector modules can be likened to having three
different conference rooms on each of the Reflectors; they can all be active at the same time.
To accommodate many simultaneous connections a Reflector Server requires at least 10Mbit
symmetrical (upstream and downstream) bandwidth. The UK Reflectors run on servers using fast
connections with 100Mbit IP bandwidth. The main UK Reflector is REF005 module A.
Linking D-Star Nodes to each other or being connected to a Reflector does not impact on other
stations connecting up to your local D-Star Node. If your D-Star Node is connected to a Reflector and
there is a call via the Gateway, the caller should be heard on all linked D-Star Nodes/Reflectors.
DV Dongle users can also connect to the Reflectors directly. However,

 if a Dongle user connects to
your D-Star Node whilst it is linked to a Reflector, the Dongle user will not be heard on the Reflector.
You should ask the Dongle user to connect directly to the Reflector; this will enable all users that may
be monitoring to hear both sides of the conversation.
It’s quite frustrating to listen to a one-sided conversation, so please make sure that all RF users have
set their RPT2 suffix to G (G in the eighth position). You can connect to any of the six Reflectors, so
therefore you have a total of eighteen “conference rooms” to use. It is also possible that the number of
Reflectors available will change, although we currently talk about six, you may wake up some morning
and discover eight or three. To monitor the status of the UK-IT hosted dplus Reflectors you can use
the web pages below for REF005 and REF006 respectively:

http://www.ukit.org.uk/ref005.html
http://www.ukit.org.uk/ref006.html


REF001: Reflector 1 is the US Reflector
REF003: Reflector 3 is the Australian Reflector
REF005: Reflector 5 is the UK Reflector


If you’ve managed to programme your D-Star radio already you should be familiar with the format of
programming the four key fields,
MYCALL, YOUR, RPT1 and RPT2.Follow the instructions below to
connect to a Reflector or a D-Star Node. If you get stuck, you can seek help via the Admin Team on GB7SF
Or UK D-Star Yahoo
Group
(http://www.dstar.org.uk )


Ok, so what is a Reflector? A Reflector acts as a central conference hub where multiple D-Star
Nodes/Dongle users can gather and all talk to each other. There was a recent World Wide Net; the
objective of the net was to see how many D-Star Nodes and Dongle Users could connect to a
Reflector and to gauge what sort of capacity it could take. There were 28 D-Star Nodes, and 18
Dongle users connected. The system performed perfectly, and no performance issues were noted.
As previously mentioned, there are currently five Reflectors.

You might see them referred to as
REF001, REF002, REF003 etc. In addition all the Reflectors have three Modules, A, B or C. So for
example, the World Wide Net mentioned above, took place on REF001 C. The main UK Reflector is
REF005 A. Having D-Star Nodes linked to each other, or being connected to a Reflector does not
impact on other stations connecting up to your local D-Star Node. If your D-Star Node is connected to
a Reflector and there is a call via the Gateway, the caller should be heard on all linked D-Star
Nodes/Reflectors.


Dongle users can also connect to the Reflectors directly. However, if a Dongle user connects to your
D-Star Node while you are, in turn connected to a Reflector, the Dongle user will not be heard on the
Reflector. You should ask the Dongle users to connect directly to the Reflector; this will enable all
users that may be monitoring to hear both sides of the conversation. It’s quite frustrating to listen to
only one side of a conversation. Similarly, please make sure that all users on RF have set their RPT2
to GB7?? G (2 spaces before the G).

Linking and Unlinking Nodes and Reflectors
The key thing that all users need to remember to make Reflector access work, is to set your
RPT 2 field to include a G suffix in the 8th position.
For example in the case of users on GB7SF:


Your: CQCQCQ
RPT1: GB7SF C (2 spaces)
RPT 2: GB7SF G (2 spaces)


This way you will be heard by all stations connected to the Reflector or by all stations connected to
the linked D-Star Nodes. This should be your standard setting for working your local D-Star Node.
One of the things you should remember is that you might turn on your radio and not realise that you
are connected up to a Reflector/D-Star Node, so if you put a call out don’t be surprised if you get a
reply that you weren’t expecting. We are still getting used to this new functionality, so far it’s working
very well, and as things develop further functionality may be added. There is a facility currently which
will allow us to make timed announcements to indicate that the D-Star Node is linked. This is useful to
inform local users that the D-Star Node is linked. However, this is not proving totally reliable, as it is
knocking out some transmissions and currently causing more issues then it solves. We are still
playing with this feature and trying to make it work in a non-destructive way. The issue has been
raised with the UK Interconnect Team (UK-IT) and an investigation is underway.
To connect to a Reflector, (Eg. REF005 A from GB7SF) all you need to do is set your routing
up as follows (your D-Star radio does the rest).
To Link:


YOUR: REF005AL (L is in position no. 8)
RPT1: GB7SF C (2 spaces)
RPT2: GB7SF G (2 spaces)


This links your D-Star Node to Reflector No. 5, Module A. Substitute the A with a B or C if you wish to
connect to Module B or C. Or change the 5 to 1,2,3,4 for one of those Reflectors.
To Unlink:


YOUR: *******U (U is in position no. 8, and the * represents spaces)
RPT1: GB7SF C (2 spaces)
RPT2: GB7SF G (2 spaces)


This Unlinks the D-Star Node from the Reflector. NB. The * characters are spaces and this will Unlink
any connected Reflector/D-Star Node. So you only need one memory in your radio to unlink any
Reflector that’s connected.
You can also link directly to another D-Star Node if you wish. So to connect to GB7AA from GB7DS:
YOUR: GB7AA BL (L is in position no. 8, B is the port designator)


RPT1: GB7SF C (2 spaces)
RPT2: GB7SF G (2 spaces)


NOTE: Once you have connected to the Reflector you should revert the YOUR: callsign field to
CQCQCQ, otherwise the local D-Star node will try to re-link every time you transmit.

Local users of a D-Star Node should also note that where two D-Star Nodes are linked. For example,
in the case where GB7AA is linked to GB7BB, if you are on GB7AA and you try to route to GB7BB
with GB7BB in the “Your” callsign field, it won’t work. So if you try to route to a D-Star Node, and its
not working as expected, it’s an indication that you are linked via a reflector to the D-Star Node you
are targeting. So while you are linked, all you need is to do is described above: RPT 2 set to G, and
Your set to CQCQCQ. Just try setting RPT 2 to GB7AA G, and it should work fine. So the message
is, set RPT 2 to G, and enjoy the new functionality that dplus brings to D-Star.
If you are linked to a Reflector/D-Star Node and another station comes in via your Gateway, they will
also be heard via whatever you are linked to.


I’ve input all the Reflectors 1-5 and A-C into my radio memories, so all I’ve got to do is dial it up and
link to any Reflector I wish. D-Star is radio memory hungry .Once you’ve set them all up as memories
in your radio, all you need to do is dial up whichever Reflector/D-Star Node you want to link to and
press the PTT button for 1 second. You will hear a voice announcement saying ” Remote System
linked (or unlinked)” to indicate you’ve been successful.


You are now linked to the Reflector/D-Star Node. Do not stay on this memory as it’s only used to
link/unlink the Reflector/D-Star Node. If you stay on this memory every time you press the PTT you
will hear a message “Link Currently Established”. To transmit via the Reflector, go to whichever
memory you have for GB7?? (your local D-Star Node) ensuring that RPT has GB7?? G set, the
YOUR field should be set to CQCQCQ
Set this up as your standard memory for working your local D Star D-Star Node Eg. GB7DS:
YOUR: CQCQCQ
RPT1: GB7SF C (2 spaces)
RPT2: GB7SF G (2 spaces)

Notes
Not all of the UK D-Star node Sysops have enabled user control of linking to the dplus Reflectors.
A couple of other things to bear in mind are that there will be no indication that you are linked to
somewhere else other then the initial announcement, so local users may not be aware that you are
linked up to a Reflector/D-Star Node. We don’t want to only hear half a conversation so please
remember to state that you are on the Reflector so other users know to have RPT2 set to G.
Automatic GPS beacons that beacon every few minutes will go out on all connected reflectors, these
can clash with other transmissions and prevent voice traffic from making it into the Reflector. I would
encourage users who want to beacon GPS to set their radios to send their beacon on PTT rather then
automatically.

Get into the habit of leaving pauses to allow others to get into the conversation if they wish to join.
Due to the nature of the Reflector and the capacity to have a lot of people connected, there is
potential for a lot of activity on the Reflector, so 3-4 second pauses allow other stations to join.
I hope that this all that makes sense, go and have a play and get used to how it works, there are
plenty of people able to help and support on the Reflectors.


Please let me have any corrections that you may spot.

Send email to Stevem1ers@blueyonder.co.uk  For information