[arm-allstar] Echolink hangup

[Doug Crompton]

Dennis,

  Yes, if you want to put Allstar on a separate node it could be a private
node on your server. So lets say your main node is 40000 and you had 1999
as the second node which is the default. You could attach Echolink to 1999
in echolink.conf and then connect or disconnect 40000 to/from 1999 to
activate or deactivate Echolink.

I do this here but I use a registered node in place of a private one for
the exclusive Echolink connect. It works either way.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Sat, Mar 9, 2019 at 8:35 PM Dennis Ramos <m0tfg at dx1mk.org> wrote:

> Hello Doug, is it possible to put in a private node, like 1999 or 1998?
> May I know what is the simplest config please...
>
> Thanks
>
> Dennis
>
> On 6 March 2019 20:52:42 GMT, "Doug Crompton via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>>
>> Rick,
>>
>>    Echolink can be a problem and thus many don't even support it. You might
>> try putting echolink on its own node. It can be on the same server but its
>> own node. Then you can connect and disconnect it from the main node at
>> will. If someone hangs it up you can just disconnect it.
>>
>> On the time out yes it should time out and release the PTT but in a
>> situation like yours where it is connected to another controller I am not
>> sure what would have happened. It it dropeed for even a few seconds it
>> would have reset. You should run a test and make sure it does in fact
>> timeout. Set the TX timeout to some shorter value like 30000 - 1/2 minute
>> and see what happens. 240000 is 4 minutes.
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>> On Wed, Mar 6, 2019 at 2:14 PM "Rick Harkins via ARM-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>>  Our repeater was stuck transmitting this morning. A quick look at the
>>>  connect log showed that someone had connected via Echolink at 22:00 last
>>>  night, and was still connected. We were unable to disconnect them, so we
>>>  rebooted the node. That fixed the problem but didn't leave us with much to
>>>  look at.
>>>
>>>  I have tx_timeout set to 240,000 in rpt.conf. Shouldn't this have unkeyed
>>>  the repeater after 4 minutes? Is there another parameter I should use?
>>>
>>>  Our node feeds a controller, and that should have caught this, but didn't.
>>>  We're reviewing the controller config.
>>>
>>>  Thanks!
>>>  Rick Harkins WØYGH
>>> ------------------------------
>>>
>>>
>>>  ARM-allstar mailing list
>>>  ARM-allstar at hamvoip.org
>>>  http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>>  Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>>
>> ------------------------------
>>
>>
>> ARM-allstar mailing list
>> ARM-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>>