Is it a "sign-in"? feature or? "sing-in"? feature as you posted?
|
adding a work wifi SSD and password
I have my shari node at home and would like to take it to work so while I'm at work for 10 hours a day I could get a chance to use it, right now it sits at home not even turned on, my question is how do I add the work wifi info, I want it to be additional to my home info so it will still work there. I can't even remember how to access the Shari
|
Node randomly keying up on allstar
All of a sudden my node started to key itself up randomly.? I have tried increasing the squelch and changing the frequency on it.? If I leave it connected to a parrot node that is the sound it broadcasts but when I listen to the frequency input I never hear any rf going into the pi4U.? Tried replacing power supply and even tried a new pi but still having issues.? Not sure If it's time for a new pi4U or what else it could be.
|
Re: Cannot key node with ASL3
In simpleusb be sure you set CTCSS FROM to 'no'
?
Here is a link to our suggested settings for ASL3 on SHARI
?
|
Cannot key node with ASL3
I have 2 nodes that were running hamvoip. I downloaded a fresh asl3 image and went through the config. Everything looks good, but the node does not key up. I tried my other node, same thing. Not sure what im missing.? confirmed the simpleusb settings, node registered and showing on asl page, the serial dev to /dev/ttyUSB0 etc...? No luck.? Any help would be greatly appreciated.
|
Re: SHARI doesn't recieve with ASL3
I wanted to update this thread. I was able to resolve the issue by trying another SD card and downloading the very latest image from ASL. I did try updating the image I downloaded a couple weeks ago, but it still wasn't working. The green light on the PIhat was steady and not blinking.
I reloaded the image and set CTCSS=NO and it just worked! Strange, but true. My node is on the air and working fine. Thanks Steve for your help with this!
|
Re: Connection failures to some reflectors, some of the time
It was, but the problem seems to be fixed.
73 Steve KL7SB?
Sent via the Samsung Galaxy S24 Ultra, an AT&T 5G smartphone
toggle quoted message
Show quoted text
-------- Original message -------- From: "N4BUT via groups.io" <nick@...> Date: 11/15/24 10:50 AM (GMT-09:00) Subject: Re: [SHARI] Connection failures to some reflectors, some of the time
It wouldnt happen to have been the East Coast Reflector, would it?
there were fiber issues with their ndoes yesterday, and still lingering today...
|
Re: Connection Failed Issue
Patrick, your spotting of the IP address conflict was the issue.? Nice work!!? The problem has been resolved.??
I just spoke with the node operator, KB0P, and it turned out the IP conflict was caused by his Hamvoip proxy configuration on his server.? AllStarLink Helpdesk just today issued a Server Configuration Update procedure to the registered node operators that run with a proxy IP address.? Apparently the server settings have a manual IP field that overrides the node registration IP address.? When the manual field is out of date, the connection failure results.
So you were spot on!!? KB0P said if I hadn't written him alerting the problem, he would have ignored today's?Helpdsk?email thinking it?didn't apply to him.? What a coincidence.
So case closed and thank you to everyone for your responses and ideas.? It worked!!!
73,
MJ, WO9B
On Thu, Nov 14, 2024 at 11:02?PM Patrick Perdue via <borrisinabox= [email protected]> wrote:
Good luck. That node has been up for a long time, so maybe just
restarting it will magically fix the registration thing.
On 11/14/2024 9:23 PM, Michael Johnson
via wrote:
Thanks for the excellent suggestions.
1.? Confirming "Connection Failed":? Thanks for trying the
connection.? Others having the same problem is somehow a good
thing?? lol
2.? ASL3 Update Node List & Node Lookup Method = File:?
I had already done both of those and I reconfirmed them
again.? No joy.
3.? I sent another note to the node op...maybe the second
time will be the charm.
Fingers crossed that Item 3 will yield a positive.? ?Thanks
again.
On Thu, Nov 14, 2024 at
3:39?PM Patrick Perdue via <borrisinabox= [email protected]>
wrote:
Greetings:
For some reason, the reported address is not correct
using
for node 48579.
resolves
to 204.38.204.189. This works.
,
which ASL is using, resolves to 204.38.204.187, which
doesn't.
Try the following:
Make sure the asl3-update-nodelist package is installed.
sudo apt update
sudo apt install asl3-update-nodelist
Then, in /etc/asterisk/rpt.conf, change the line
node_lookup_method = both?????????? ;method used to
lookup nodes
to
node_lookup_method = file ????????? ;method used to
lookup nodes
and then restart Asterisk.
It seems like ASL's DNS sometimes doesn't update when
an IP address changes. I don't know why.
73
N2DYI
On 11/14/2024 11:41 AM, Michael Johnson via wrote:
I'm not sure this is an appropriate issue for this
group, but I have to start somewhere.... redirect prod's
are welcome.
?
I've got a SHARI node which has been stellar for the
past year.? I like to experiment and ended up messing up
the Hamvoip software a few months back so I plunged
ahead with an ASL3 update.? That has been a satisfying
experience and with one exception, has been very
successful.
?
The exception:? Since making the change to ASL3, I
cannot successfully connect to talk group #48579.? Every
attempt results in a Connection Failed message.? I
communicated with the node owner and he could find
nothing on his end wrong on his end and reported his
linked repeater system is working like a champ.? I have
not tried reinstalling Hamvoip to see if that would
correct the situation, bad me.? So I am wondering how to
go about troubleshooting the problem.? Where to look for
log entries or what not.? I have no idea why the
connection fails repeatedly.
?
BTW, I don't really explore the ASL Node Network
extensively, but I have zero connection issues with any
of my other dozen or so favorite nodes.? Just #48579.??
?
Any assistance is appreciated.??
?
Thanks
?
MJ, WO9B
|
Re: Connection failures to some reflectors, some of the time
It wouldnt happen to have been the East Coast Reflector, would it?
there were fiber issues with their ndoes yesterday, and still lingering today...
|
Re: Connection Failed Issue
Good luck. That node has been up for a long time, so maybe just
restarting it will magically fix the registration thing.
On 11/14/2024 9:23 PM, Michael Johnson
via groups.io wrote:
toggle quoted message
Show quoted text
Thanks for the excellent suggestions.
1.? Confirming "Connection Failed":? Thanks for trying the
connection.? Others having the same problem is somehow a good
thing?? lol
2.? ASL3 Update Node List & Node Lookup Method = File:?
I had already done both of those and I reconfirmed them
again.? No joy.
3.? I sent another note to the node op...maybe the second
time will be the charm.
Fingers crossed that Item 3 will yield a positive.? ?Thanks
again.
On Thu, Nov 14, 2024 at
3:39?PM Patrick Perdue via <borrisinabox= [email protected]>
wrote:
Greetings:
For some reason, the reported address is not correct
using
for node 48579.
resolves
to 204.38.204.189. This works.
,
which ASL is using, resolves to 204.38.204.187, which
doesn't.
Try the following:
Make sure the asl3-update-nodelist package is installed.
sudo apt update
sudo apt install asl3-update-nodelist
Then, in /etc/asterisk/rpt.conf, change the line
node_lookup_method = both?????????? ;method used to
lookup nodes
to
node_lookup_method = file ????????? ;method used to
lookup nodes
and then restart Asterisk.
It seems like ASL's DNS sometimes doesn't update when
an IP address changes. I don't know why.
73
N2DYI
On 11/14/2024 11:41 AM, Michael Johnson via wrote:
I'm not sure this is an appropriate issue for this
group, but I have to start somewhere.... redirect prod's
are welcome.
?
I've got a SHARI node which has been stellar for the
past year.? I like to experiment and ended up messing up
the Hamvoip software a few months back so I plunged
ahead with an ASL3 update.? That has been a satisfying
experience and with one exception, has been very
successful.
?
The exception:? Since making the change to ASL3, I
cannot successfully connect to talk group #48579.? Every
attempt results in a Connection Failed message.? I
communicated with the node owner and he could find
nothing on his end wrong on his end and reported his
linked repeater system is working like a champ.? I have
not tried reinstalling Hamvoip to see if that would
correct the situation, bad me.? So I am wondering how to
go about troubleshooting the problem.? Where to look for
log entries or what not.? I have no idea why the
connection fails repeatedly.
?
BTW, I don't really explore the ASL Node Network
extensively, but I have zero connection issues with any
of my other dozen or so favorite nodes.? Just #48579.??
?
Any assistance is appreciated.??
?
Thanks
?
MJ, WO9B
|
Connection failures to some reflectors, some of the time
Hi all,
?
I am getting many "connection failed" when attempting to connect to different reflectors, but not always, and I don't see much of a pattern.
?
I'm unable to connect to the East Coast reflector at all.
?
?
Any ideas,
?
73
Steve KL7SB
?
|
Re: Connection Failed Issue
Thanks for the excellent suggestions.
1.? Confirming "Connection Failed":? Thanks for trying the connection.? Others having the same problem is somehow a good thing?? lol 2.? ASL3 Update Node List & Node Lookup Method = File:? I had already done both of those and I reconfirmed them again.? No joy. 3.? I sent another note to the node op...maybe the second time will be the charm.
Fingers crossed that Item 3 will yield a positive.? ?Thanks again.
On Thu, Nov 14, 2024 at 3:39?PM Patrick Perdue via <borrisinabox= [email protected]> wrote:
Greetings:
For some reason, the reported address
is not correct using for node 48579.
resolves to
204.38.204.189. This works.
, which ASL
is using, resolves to 204.38.204.187, which doesn't.
Try the following:
Make sure the asl3-update-nodelist package is installed.
sudo apt update
sudo apt install asl3-update-nodelist
Then, in /etc/asterisk/rpt.conf, change the line
node_lookup_method = both??????????
;method used to lookup nodes
to
node_lookup_method = file ?????????
;method used to lookup nodes
and then restart Asterisk.
It seems like ASL's DNS sometimes
doesn't update when an IP address changes. I don't know why.
73
N2DYI
On 11/14/2024 11:41 AM, Michael Johnson
via wrote:
I'm not sure this is an appropriate issue for this group, but
I have to start somewhere.... redirect prod's are welcome.
?
I've got a SHARI node which has been stellar for the past
year.? I like to experiment and ended up messing up the Hamvoip
software a few months back so I plunged ahead with an ASL3
update.? That has been a satisfying experience and with one
exception, has been very successful.
?
The exception:? Since making the change to ASL3, I cannot
successfully connect to talk group #48579.? Every attempt
results in a Connection Failed message.? I communicated with the
node owner and he could find nothing on his end wrong on his end
and reported his linked repeater system is working like a
champ.? I have not tried reinstalling Hamvoip to see if that
would correct the situation, bad me.? So I am wondering how to
go about troubleshooting the problem.? Where to look for log
entries or what not.? I have no idea why the connection fails
repeatedly.
?
BTW, I don't really explore the ASL Node Network extensively,
but I have zero connection issues with any of my other dozen or
so favorite nodes.? Just #48579.??
?
Any assistance is appreciated.??
?
Thanks
?
MJ, WO9B
|
Re: Connection Failed Issue
Greetings:
For some reason, the reported address
is not correct using nodes.allstarlink.org for node 48579.
48579.ip.hamvoip.org resolves to
204.38.204.189. This works.
48579.nodes.allstarlink.org, which ASL
is using, resolves to 204.38.204.187, which doesn't.
Try the following:
Make sure the asl3-update-nodelist package is installed.
sudo apt update
sudo apt install asl3-update-nodelist
Then, in /etc/asterisk/rpt.conf, change the line
node_lookup_method = both??????????
;method used to lookup nodes
to
node_lookup_method = file ?????????
;method used to lookup nodes
and then restart Asterisk.
It seems like ASL's DNS sometimes
doesn't update when an IP address changes. I don't know why.
73
N2DYI
On 11/14/2024 11:41 AM, Michael Johnson
via groups.io wrote:
toggle quoted message
Show quoted text
I'm not sure this is an appropriate issue for this group, but
I have to start somewhere.... redirect prod's are welcome.
?
I've got a SHARI node which has been stellar for the past
year.? I like to experiment and ended up messing up the Hamvoip
software a few months back so I plunged ahead with an ASL3
update.? That has been a satisfying experience and with one
exception, has been very successful.
?
The exception:? Since making the change to ASL3, I cannot
successfully connect to talk group #48579.? Every attempt
results in a Connection Failed message.? I communicated with the
node owner and he could find nothing on his end wrong on his end
and reported his linked repeater system is working like a
champ.? I have not tried reinstalling Hamvoip to see if that
would correct the situation, bad me.? So I am wondering how to
go about troubleshooting the problem.? Where to look for log
entries or what not.? I have no idea why the connection fails
repeatedly.
?
BTW, I don't really explore the ASL Node Network extensively,
but I have zero connection issues with any of my other dozen or
so favorite nodes.? Just #48579.??
?
Any assistance is appreciated.??
?
Thanks
?
MJ, WO9B
|
Re: Connection Failed Issue
I have attempted to connect to that node from two of my nodes that are on different networks and I could not connect either. I would see if the owner of 48579 would consider a reboot of his node to see if that clears it us.?
Just my 2 cents
Fred McGuire - KD5FMU/WRUT923 Ham Radio Crusader YouTube Channel http://www.youtube.com/@HamRadioCrusader fred.mcguire.jr@...
toggle quoted message
Show quoted text
On Nov 14, 2024, at 10:41?AM, Michael Johnson via groups.io <mike@...> wrote:
I'm not sure this is an appropriate issue for this group, but I have to start somewhere.... redirect prod's are welcome.
?
I've got a SHARI node which has been stellar for the past year.? I like to experiment and ended up messing up the Hamvoip software a few months back so I plunged ahead with an ASL3 update.? That has been a satisfying experience and with one exception, has been very successful.
?
The exception:? Since making the change to ASL3, I cannot successfully connect to talk group #48579.? Every attempt results in a Connection Failed message.? I communicated with the node owner and he could find nothing on his end wrong on his end and reported his linked repeater system is working like a champ.? I have not tried reinstalling Hamvoip to see if that would correct the situation, bad me.? So I am wondering how to go about troubleshooting the problem.? Where to look for log entries or what not.? I have no idea why the connection fails repeatedly.
?
BTW, I don't really explore the ASL Node Network extensively, but I have zero connection issues with any of my other dozen or so favorite nodes.? Just #48579.??
?
Any assistance is appreciated.??
?
Thanks
?
MJ, WO9B
|
Re: Connection Failed Issue
Thanks Steve...
I am using AllScan for the most part.? I have tried the DTMF method which gives the same results.? DTMF works fine for other nodes.
Are you connecting using DTMF?? If so, have you verified that DTMF is decoding correctly?? Can you connect using Supermon?
?
Also, I would like to remind our SHARI users that our recommended settings for using ASL3 with SHARI can be found at /g/SHARI/files/ASL3?
Steve - N8AR
?
|
Re: Connection Failed Issue
Are you connecting using DTMF?? If so, have you verified that DTMF is decoding correctly?? Can you connect using Supermon?
?
Also, I would like to remind our SHARI users that our recommended settings for using ASL3 with SHARI can be found at /g/SHARI/files/ASL3?
Steve - N8AR
?
|
I'm not sure this is an appropriate issue for this group, but I have to start somewhere.... redirect prod's are welcome.
?
I've got a SHARI node which has been stellar for the past year.? I like to experiment and ended up messing up the Hamvoip software a few months back so I plunged ahead with an ASL3 update.? That has been a satisfying experience and with one exception, has been very successful.
?
The exception:? Since making the change to ASL3, I cannot successfully connect to talk group #48579.? Every attempt results in a Connection Failed message.? I communicated with the node owner and he could find nothing on his end wrong on his end and reported his linked repeater system is working like a champ.? I have not tried reinstalling Hamvoip to see if that would correct the situation, bad me.? So I am wondering how to go about troubleshooting the problem.? Where to look for log entries or what not.? I have no idea why the connection fails repeatedly.
?
BTW, I don't really explore the ASL Node Network extensively, but I have zero connection issues with any of my other dozen or so favorite nodes.? Just #48579.??
?
Any assistance is appreciated.??
?
Thanks
?
MJ, WO9B
|
The following items have been updated in the Files area of the [email protected] group.
By: N8AR <n8ar73@...>
Description:
Corrected mis-spelling of dtparam (was dtparm)
The following items have been updated in the Files area of the [email protected] group.
By: N8AR <n8ar73@...>
Description:
This document contains Kits 4 Hams recommended settings for the SA818 and simpleusb in SHARI Allstar hotspots. Revision 1.02 adds the commands to invoke SA818 programming and simpleusb setup. Revision 1.03 fixes typos. Revision 1.04 corrected mis-spelling of dtparam (was dtparm)
The following items have been updated in the Files area of the [email protected] group.
By: N8AR <n8ar73@...>
Description:
This document contains Kits 4 Hams recommended settings for the SA818 and simpleusb in SHARI Allstar hotspots. Revision 1.02 adds the commands to invoke SA818 programming and simpleusb setup. Revision 1.03 fixes typos. Revision 1.04 corrected mis-spelling of dtparam (was dtparm)
|
Re: SHARI doesn't recieve with ASL3
I never bothered writing anything with sa818-menu program on ASL3, so that program just comes up with default blank values on my node. However, the radio was programmed already in HAMVOIP. The only thing I needed to do was to to go into 'Node Settings/AllStar Node Setup/Update Node XXXXXX/Interface Tune CLI' and set From CTCSS to 'no'.
|
Re: Node Connections Fail for direct call to HT
He corrected me, he has a T-MOBILE gateway/modem.
But I suppose that the issue is still that he cannot open the port that he needs.
?
Glen, WB4KTF
|
colin humphries
Steve-N8AR
Charles , W1CRB
N4BUT
Freddie McGuire
Glen Jenkins WB4KTF