svxlink
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
svxlink [2024/06/18 16:46] – Change to link g4nab | svxlink [2024/07/09 20:18] (current) – g4nab | ||
---|---|---|---|
Line 18: | Line 18: | ||
The current system provides that in a passive state, a node has talkgroup 0 or ‘off’ selected. By calling by DTMF 91235#, on a node… 91 meaning ‘standby, a talk group follows’ 235 ‘ talk group’s # ‘activate’, | The current system provides that in a passive state, a node has talkgroup 0 or ‘off’ selected. By calling by DTMF 91235#, on a node… 91 meaning ‘standby, a talk group follows’ 235 ‘ talk group’s # ‘activate’, | ||
- | Materially each node has a built in fail safe that times out after a period of disuse, returning it to default passive state. | + | Materially each node has a built-in fail safe that times out a module |
- | Each repeater is independent and can be used locally, with the addition of regional or national capability as required, dependant on the prevailing talkgroups. More than one connection by different talkgroups can be achieved on the reflector. | + | Each repeater is independent and can be used locally, with the addition of regional or national capability as required, dependant on the prevailing talkgroups. More than one connection |
There is a proviso that if any of the independent EchoLink or Metar services are in use, the passive reflector link is for the time being suspended, returning to default when those other services are terminated. | There is a proviso that if any of the independent EchoLink or Metar services are in use, the passive reflector link is for the time being suspended, returning to default when those other services are terminated. | ||
Line 27: | Line 27: | ||
First of all, SvxLink is designed by Tobias Bloomberg SM0SVX, firstly around 2006/7, as a means to access EchoLink via a Linux platform, but linking analog modes. AllStar is built around 2013 from Asterisk a PABX package for telephones. (Linking the two systems together while possible is inadvisable.) | First of all, SvxLink is designed by Tobias Bloomberg SM0SVX, firstly around 2006/7, as a means to access EchoLink via a Linux platform, but linking analog modes. AllStar is built around 2013 from Asterisk a PABX package for telephones. (Linking the two systems together while possible is inadvisable.) | ||
- | In Svxlink, no node numbers are required, just the natural callsign, and password provided to the reflector keeper for the passive connectivity. The reflector maintains the callsign information in a dataset that is displayed by another software package called SvxPortal that can be viewed publicly here [[http:// | + | In Svxlink, no node numbers are required, just the natural callsign, and password provided to the reflector keeper |
Each node user can update an entry on the svxportal to describe his station for public view, to further enhance his/her presence. HubNet is already available on the UK portal svxportal-uk.ddns.net. | Each node user can update an entry on the svxportal to describe his station for public view, to further enhance his/her presence. HubNet is already available on the UK portal svxportal-uk.ddns.net. | ||
Line 33: | Line 33: | ||
To build a node, all that is required is almost any spare transceiver, | To build a node, all that is required is almost any spare transceiver, | ||
- | You will need access to a Mac/PC, with a card slot to write the operating system in the first instance, and an internet connection. Only a little knowledge of Linux and Shell script is required, but it’s very simple, provided the directions are followed carefully. | + | You will need access to a Mac/PC, with a card slot to write the operating system |
Because there are so many different systems, it is not possible to provide a “one size-fits all” image, that is capable of being updated, so some technical knowledge is required. | Because there are so many different systems, it is not possible to provide a “one size-fits all” image, that is capable of being updated, so some technical knowledge is required. | ||
Line 39: | Line 39: | ||
There are so many sources of the software that have been adulterated by others to fit particular devices, that I would recommend sticking with the main source of svxlink that of SM0SVX. Within my pages I refer to scripts of my own making that can help a user build this system. | There are so many sources of the software that have been adulterated by others to fit particular devices, that I would recommend sticking with the main source of svxlink that of SM0SVX. Within my pages I refer to scripts of my own making that can help a user build this system. | ||
- | **Full instructions** are found on [[https:// | + | **Full instructions** are found on [[https:// |
| | ||
Line 50: | Line 50: | ||
- | ((The current version of the SVXLink package is Version 24-02.1 and is not yet current | + | ((The current version of the SVXLink package is Version 24-02.1 and is not yet currently |
Other versions of SVXLink have existed including one from the OpenRepeaterProject in the US, but again this version is also out of date, although that group is working on the next version.)) | Other versions of SVXLink have existed including one from the OpenRepeaterProject in the US, but again this version is also out of date, although that group is working on the next version.)) |
svxlink.1718729165.txt.gz · Last modified: 2024/06/18 16:46 by g4nab