Protocol 2 of the SVXReflector is available in the latest edition of SVXLink from the Github. It is not backwards compatible with the Protocol 1, so those running an image of SpotNik or another early version may change up, they will lose the connectivity with the servers on Protocol 1. However those on Protocol 1 can still connect to the new SVXReflector, and follow the procedures to link with the proposed new ‘Rooms’ or Talk Groups as they would prefer to be known.

This will be the procedure for those who have an existing compilation with the original build files in place.

In terminal, log in as pi with password and cd svxlink.

Go to this page and carry out the instructions in red. Once you have done that, come back here.

Whilst still in this folder type sudo git pull then press return.

When the terminal finishes the changes, cd src/build, then sudo make. At this stage it will be necessary to shutdown your existing node or repeater to permit it restart eventually with the new configuration. (sudo killall svxlink).

When the build is complete then sudo make install.

Finally end the compilation with sudo ldconfig.

The first thing to note is that the original configuration files such as svxlink.conf will be unchanged. However there are new files that will be incorporated into the build of that you will need to be aware. Firstly a new logic has been added in /usr/share/svxlink/events.d called ReflectorLogic.tcl. You might wish to copy this to the local folder that you may already have created in the original build. If not it would be a good idea to do this now. with terminal in the events.d folder (cd /usr/share/svxlink/events.d) make a new folder local (sudo mkdir local , sudo cp * local) and put in the files that you can later edit, when the need arises, leaving the originals intact.

Those who have a SpotNik image will not be able to do this, so a read of this page in its entirety with a new SDcard may be a good idea.

The next stage requires some editing of the svxlink.conf file with some new additions and changes. you can do this by sudo /etc/svxlink/svxlink.conf.

This is in several blocks: The necessary additions to your existing svxlink.conf are in red.

[GLOBAL]

MODULE_PATH=/usr/lib/arm-linux-gnueabihf/svxlink

LOGICS=SimplexLogic,ReflectorLogic

CFG_DIR=svxlink.d

TIMESTAMP_FORMAT=”%c”

TIME_FORMAT=”12″

CARD_SAMPLE_RATE=48000

CARD_CHANNELS=2

LOCATION_INFO=LocationInfo

LINKS=LinkToReflector

[ReflectorLogic]

TYPE=Reflector

HOST=192.168.1.213

PORT=5300

CALLSIGN=”yourcallsign

AUTH_KEY=”to be obtained from the sysop of the reflector

DEFAULT_LANG=en_GB or the language of your choice. There are new voice samples to be added.

JITTER_BUFFER_DELAY=0

DEFAULT_TG=0 (or a talk group of your choice). See below.

MONITOR_TGS=208*,235**,240,262,505,2085,2350,2351,23561,20887,20823 (a listening list if these are ever activated ** means a primary group * means a secondary group in priority.)

TG_SELECT_TIMEOUT=90

ANNOUNCE_REMOTE_MIN_INTERVAL=300

EVENT_HANDLER=/usr/share/svxlink/events.tcl

NODE_INFO_FILE=/etc/svxlink/node_info.json

MUTE_FIRST_TX_LOC=0

MUTE_FIRST_TX_REM=0

TMP_MONITOR_TIMEOUT=0

[LinkToReflector]

CONNECT_LOGICS=SimplexLogic:9:,ReflectorLogic

DEFAULT_ACTIVE=1

OPTIONS=DEFAULT_CONNECT,NO_DISCONNECT

These are the only changes that are needed, however once you have been granted access to a portal, the registration to it gives you access to a tool on the portal to create the node_info.json, that you download and insert in the /etc/svxlink folder that promotes your node on the portal.

Important Information.

Having access to the SVXreflector does not mean that your link will be transmitting over any other link at this stage. It merely has a ‘stand-by’ connection. Until a TalkGroup is activated, the node will operate as a completely stand-alone unit on TalkGroup 0. However activating a TalkGroup does not create a link with another node unless the same group is a ‘listening’ group on the other node or nodes.

For example if all nodes in the UK had 235 as a listening group, but no fixed group, they would all be ‘stand-alone’ nodes, until someone called and activated 235 as an active TalkGroup.

A further example would be that if all nodes in the NorthEast of England had listed 235 and 23560 in the listening list, then this TalkGroup 23560 could be activated by anyone on the whole network, but only the nodes in the North East would hear the call, and the node on which the original call was made.

A further example would be that All the repeaters on the network would have TalkGroup 235 as a fixed group and always activated whenever anyone called, but an automatic QSY facility would shift the two immediate users after a brief introduction to a Chat TalkGroup, leaving the network free on 235.

This system has already been tried and tested on the DMR Networks, hence the terminology.

You will see from This portal that the system is already active on a small scale. There are other such portals active in Europe and elsewhere. You will see that there are two French repeaters here already, but they will migrate back to the French Repeater network when their Protocol 1 system has been upgraded to Protocol 2.

How does it work?

From the users point of view, not unlike EchoLink, which by the way can still be used (with a slight modification.)

When a user calls to open a network call he sends a DTMF string 91 plus the TalkGroup number followed by ‘#’. With the sound samples upgraded, the repeater will respond with ‘TalkGroup’ plus the number confirming the link. On the next transmission the user’s voice will go to any node with the TalkGroup in the listening group, and will be transmitted there too. To kill a connection he will send 9# (or 910# to reset to TalkGroup 0). There are other codes as well, but they will be published when the network enlarges.

How do I join my node to the SVXReflector?

Just send me an email and I will arrange the changes to incorporate your node or repeater.

Leave a Reply