Adrian,
Two things come to mind on your problem.
The first thing is to make sure you have a really good 5 volt power supply source for your Pi.
The second issue could be upon startup establishing your permanent link to the hub node.
May try disabling the permanent connections on startup and see if your problem goes away.
Marshall - ke6pcv
···
From: Adrian VE7NZ via AllStarLink Discussion Groups [mailto:noreply@community.allstarlink.org]
Sent: Friday, April 03, 2020 8:51 AM
To: ke6pcv@cal-net.org
Subject: [AllStarLink Discussion Groups] [App_rpt-users] Asterisk doesn’t boot consistently, PTT stuck on, COS not working,
VE7NZ
April 3
Elaborating on the subject: I have a Pi with three RA-42 interfaces from Master Communications. Two provide Allstar access to repeaters, the third one provides that plus is acting as the full duplex repeater controller for that repeater (my 220 MHz repeater)
When I boot the system, about half the time it works perfectly. The other half of the time, the 220 repeater goes into permanent transmit and the repeater is non-responsive to incoming signals. It will not time out.
When this happens, I reboot the system and try again. Usually after one or two retries, the system starts up as it should again.
The only thing I am doing is the reboot so not sure why the behaviour would vary seemingly randomly.
If it’s relevant, I should point out that upon bootup I register an Allstar NNX node for each of the three repeaters and a fourth node that is a dahdi/pseudo node used as a hub. Each of the repeaters, upon startup, establishes a permanent link to the hub node. This works, but I mention it because the only variable I can think of is perhaps internet latency changing from one bootup to the next.
Thanks, 73, Adrian VE7NZ
Visit Topic or reply to this email to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, click here.