> You're right about DTMF, anyone having the correct codes can connect
> or disconnect the linking.
I've almost finished my work to change the linking of logics. The
functions has been rewritten and removed from the Logic-class. Now it's
possible to define the way of linking the logics, if it shall beeing
connected during the startup of svxlink and not disconnectable by DTMF
anymore or if a connection has a timeout and so on.
Since it's implemented as singleton, it's (theoretically) controlable
from other svxlink-sections, e.g. an aprs command or from an incoming
echolink session too.
It will still take some days to check, then I will upload a branch and
we can discuss the funtionality.
73s de Adi, DL1HRC
> I understand that you've already evaluated the use of Asterisk but
> there's an asterisk application called Rpt and a channel module named
> chan_rpt that can interface the system with a number of radio
> repeaters to make them work as a radio network.
> 73 Erin.
> Gustavo - LU8WFY
> 2011/4/23 Eren Türkay <eren@... <mailto:eren@...>>
> On Sat, Apr 23, 2011 at 07:13:47PM -0300, Gustavo Conrad wrote:
> > Hi Eren,
> Hello Gustavo,
> > Sorry I've made a mistake naming LinkLogic where I wanted to say
> > SimplexLogic. I'm sure this makes a lot of confusion to you.
> It's not a problem. Although I was confused, this mail made it clear.
> Thank you for your clarification.
> > .....
> > #TX_CTCSS=SQL_OPEN
> > MACROS=Macros
> > LINKS=LinkAllSites
> > FX_GAIN_NORMAL=0
> > FX_GAIN_LOW=-12
> > .....
> > .....
> > [LinkAllSites]
> > LOGIC1=SimpĺexLogic_Site_A
> > LOGIC2=SimplexLogic_Site_B
> > LOGIC3=SimplexLogic_Site_C
> > COMMAND=94
> > NAME=ALL_SITES
> > .....
> So, basically, it will do the same thing as I did in previous mail
> "RepeaterLogic"? IMHO, as it's a simplex logic, only one node will be
> able to transmit while others are listening, and the data will not be
> send the node that is transmitting.
> However, I didn't get how I am supposed to configure Rx/Tx section in
> "SimplexLogic_Site_A" (and other nodes) I can guess that it will
> to "Network_Site_A", but where it will send the data to?
> Additionally, I
> cannot grasp how svxlink handles LINKS section. My theory is that
> svxlink detects if there is a signal from one of the Simplex
> nodes. If
> there is, say it's node A, it looks for how they are connected with
> LINKS section. Then, svxlink sends the data to every node *except
> A* by
> looking its TX section for the node. If it's the case, both RX/TX
> section should be the same (Network_Site_A).
> > After this you can enable the link (simultaneous operation of
> all the logics
> > involved) by transmitting the DTMF digits with the command you
> > followed by digit "1". In this example it would be 941#. To
> disable the
> > link send 940#. If you do not operate radios in your system
> you'll need an
> > alternate way to generate DTMF.
> Thanks for this tip! I operate radios in the system. All nodes have RF
> link, and they are connected to Intranet. However, since DTMF signals
> can be guessed, it does not seem to be a secure way to manage the
> Someone can guess the DTMF sequence, send it to the link and cause
> > Let me say that I'm not an expert in these subjects but I
> suspect that your
> > application fits more on another kind of voip technology (such
> as Asterisk,
> > to name one...).
> I don't think so. Although Asterisk is a good solution for voip, I
> think it does squelch detection, activating/deactivating link with
> PTT with serial port, echolink support etc. I'm sure svxlink is
> the tool
> to use, but I have much to learn about its configuration :)
> > 73!
> > Gustavo - LU8WFY
> . Eren