Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: svxreflector #3458

    Further to my last post, you will find svxportal-uk.ddns.net available to view. This possibility is what you might expect when openrepeater developers review the added software requirements in the build of svxlink.conf with reflector.logic inclusive, with talkgroups.
    One interesting aspect to the dashboard is that the vk4tux-t node is digital on TETRA, whilst other nodes are possible.
    Catch me on QRZ.com or g4nab.co.uk.

    in reply to: svxreflector #3445

    Good afternoon again. Following my introductory post I have been conducting further experiments with my “local” svxreflector, two repeaters in France, one in Germany, on in the UK, and my two systems in my home, one a repeater and one a new device called a DJSpot.
    I have settled on DTMF as the means of using TalkGroups, that I have numbered according to the existing MCC system employed by DMR (of which I am also an expert).

    There are three principle ways that sysops of repeaters can involve their community on SVXReflector. Once their callsign and Password are set at the server, and running in the [ReflectorLogic], the connection is solid but no traffic passes over the network, until…
    1. The sysop adds DEFAULT_TALKGROUP=0 and MONITOR_TALKGROUPS=###,##2,###3. This permits connections from outside this repeater to be heard only when those talkgroups are activated.
    2. The sysop adds DEFAULT_TALKGROUP=235 (e.g.) and MONITOR_TALKGROUPS=235,2351,2351 (e.g.). This permits the repeater to be part of a wider network of which TG 235 is common to all. It does not prevent a user Selecting TG0 to discontinue the connection or offering a non-listed talkgroup to which to QSY with a user elsewhere. The other monitoring groups can link certain repeaters as local clusters rather than a national network.
    3. The sysop add only the Default talkgroup to be part of one group, leaving the choice of QSY groups to the users.

    There is a final alternative, whereby the sysop does not activate [ReflectorLogic] at all.

    There is more to this, as to the method of coding, but this has been covered in the original documentation (e.g. 91235# goto TG235, 922351# QSY to 2351, 9# disconnect, or 90# go to default TG0.

    If anyone wants to try it with my server, just offer me a callsign and a password by email, and I’ll set it up and give you the lines to add to make it work – I am qthr on qrz.com – Chris G4NAB

Viewing 2 posts - 1 through 2 (of 2 total)