Keyboard Shortcuts
Likes
- SHARI
- Messages
Search
Re: Inbound connections to SHARI node are rejected
#ConnectionFailed
The call request is geting there.? IAX sends the call to context [radio secure] in your extensions.conf
Look for that context and make sure you have an entry for your node.? |
Re: Inbound connections to SHARI node are rejected
#ConnectionFailed
52477@radio-secure' does not exist |
Re: Inbound connections to SHARI node are rejected
#ConnectionFailed
Hi, Chris, Thanks for the reply.
Yes, 4569 is forwarded to the IP of my node. |
Re: Inbound connections to SHARI node are rejected
#ConnectionFailed
Thanks, Steve. I'll ask over there. I've checked the bind address, and the port is forwarded, so I'm stumped.
You know what? I was in Ypsi a couple of months ago. I think I missed a prime opportunity to buy you lunch at Zingerman's. Oh well, next time, buddy. |
Re: Inbound connections to SHARI node are rejected
#ConnectionFailed
¿ªÔÆÌåÓýYou have port 4569 forwarded in your router? ? ? ? 73, Chris ? ? From: [email protected] <[email protected]> On Behalf Of Curt Faulk
Sent: December 22, 2022 4:16 PM To: [email protected] Subject: [SHARI] Inbound connections to SHARI node are rejected #ConnectionFailed ? Hello everyone: [Dec 22 13:32:37] NOTICE[13003] chan_iax2.c: Rejected connect attempt from xx.xxx.xx.xxx, request '52477@radio-secure' does not exist
|
Re: Inbound connections to SHARI node are rejected
#ConnectionFailed
This can be caused by improper assignment of nodes to servers on Allstarlink.com.? For most of us, there should be a unique server with a unique binding address (4569, 4568, 4567, etc) for each node.? The binding address in iax.conf must match the binding address in the server.? The binding address must be port forwarded (UDP) in your router.
It is possible to have more than one node per server but I leave that to the experts:<) Also consider asking your question on the arm-allstar list used to support the HamVOIP image.?? You can search the list archive at? |
Inbound connections to SHARI node are rejected
#ConnectionFailed
Hello everyone:
I've been researching this for a couple of days and have also searched this group and not yet resolved this problem. My SHARI node will connect outbound to anything I ask it to. It works great and has for years. Inbound connections are 100% rejected and my astlog.php will shows entries like this: [Dec 22 13:32:37] NOTICE[13003] chan_iax2.c: Rejected connect attempt from xx.xxx.xx.xxx, request '52477@radio-secure' does not exist I've spent hours looking for clues online and... nothing. I figure that with the SHARI being a HamVoIP system, it would be best to pursue answers in this group. |
Locked
Re: SHARI PiHatU ... Red & Yellow led's not working - Solved
Gary,
I agree, that's why I've bought over 6 kits from Steve. I'm sure he'd be selling more if there wasn't parts shortages. and Raspberry? PI's classified as UNOBTAINIUM. Last heard from Steve is that he has SA818's on Back ordered...One bright spot ---especially for us poor hams and this is only supposition on my part is that the Raspberry PI (RPI) foundation founder in a blog about last August stated that they were producing 1/2 million RPI's per month in their Wales factory, but he has given priority to his big commercial sellers over individuals..because they have "families that need to be fed"... Well I took offense to that as the original intent of the RPI Foundation was to supply low cost computing to young people, 3rd world countries, students and experimenters.? Anyhow many RPI's were placed into BITCOIN MINING and clusters of RPI's with as many as 1000 RPI's are being sold to investors to mine bitcoins. and the rich get richer, as they say.. Well, everyone knows the big BITCOIN dealer has been charged with a PONZI scheme and I'm sure that BITCOIN mining cluster sames have dropped to ZERO or close to it. That means that those big orders RPI foundation has been taking are ending and the Foundation is going to revert back to selling them to students and experimenters. Some have all ready come available and immediately sold out. Something that has not been seen since before summer. I did notice that mouser.com is posting an availability date for various RPI's in January and February.. I am not sure, but I think you can pre-order.. Newark.com (the USA importer) has them back-ordered with a lead time of August 2024... Merry Christmas to all, Larry W8LM... ? |
Re: Node Connected Announcement
¿ªÔÆÌåÓýYou can't do that through app.rpt. Telemetry isn't really
configurable other than if it's on all the time, off, or on for a
couple of minutes after each command. One could theoretically
write a script that replaces that functionality, which is then
tied to connpgm and discpgm in rpt.conf, then set telemdefault=0.
Not something I've tried to do, but I know how it might work in
theory. That being said, I use the write_node_callsigns script on my
nodes, which runs every morning at 3:16 AM EST on cron to pick up
new node numbers for the day. I have it run at 3:16 AM, because
this is one minute after the astdb.php job runs, which is a local
list of all nodes on the allstarlink.org registration system, not
just active nodes. Ideally, I would use a local TTS engine and have everything in
one utterance rather than using pre-recorded sound files, which
could give you the same or more information in a lot less time
without losing clarity, but there aren't really any good local TTS
options that will actually run on a Raspberry Pi, and don't depend
on someone's online API. I don't count eSpeak. There are the
Cepstral voices, I guess, but I don't like their version of
diphone concatenation. It's very choppy. As it is, I replaced Allison on my nodes a long time ago using a very fast formant synthesis by rule engine, in this case, the Apple Fred voice. Not something you'd want to use on a repeater, but as a daily user of TTS (I'm blind and use a screen reader,) it became tedious very, very quickly listening to the stock voice. Yes, I could have sped it up, but with all or most of the sound files already being compressed with a lossy codec, I didn't want to add even more artifacts. Anyway, that's probably way more than you asked for without actually telling you what you wanted to know.
On 12/21/2022 1:58 PM, Johnnie Smith
wrote:
|
Re: Node Connected Announcement
I do not think you can do that, but why don¡¯t you change it to say call signs instead of no numbers makes it a lot less annoying On Wed, Dec 21, 2022 at 12:49 PM KB9WOO <kb9woo@...> wrote: I swore I saw this when I first installed Allstar (HamVoip).? I want to disable the announcement of my local node number when a connection is established.? Currently the announcement states "node xxxx connected to node xxxx".? I'd rather it only announce the remote node number is connected and leave out the local node number.? Am I imagining seeing this? --
ne5l |
Node Connected Announcement
I swore I saw this when I first installed Allstar (HamVoip).? I want to disable the announcement of my local node number when a connection is established.? Currently the announcement states "node xxxx connected to node xxxx".? I'd rather it only announce the remote node number is connected and leave out the local node number.? Am I imagining seeing this?
|
Locked
SHARI PiHatU ... Red & Yellow led's not working - Solved
Thought I would put this out there....Ever since I put my PiHatU kit together, the Red and Yellow led's would not work.? Steve (N8AR) was kind enough to have a Zoom session, and we discovered that the led's themselves were damaged...one was almost completely missing.? I shipped the entire assembled kit to Steve and he immediately took a look.? He had to remove the remnants of the damaged led's (no idea how it happened, but there was no apparent damage to the rest of the PiHat board....weird !), and replace them.? He quickly sent everything back to me, and it's been in service now for about a week with no problems.
Have to say I'm thrilled about the level of support provided here....way over and above what most other kit suppliers would typically provide.... Here's wishing everyone a great holiday, and I'm going to spend some quality time with my middle grandson giving this unit a thorough workout for some linked nets. Gary / WB8ZGV |
Re: Severe hum that was not there before - SOLVED
¿ªÔÆÌåÓýThank you for the update! It was a mystery for sure.73 Fred McGuire, KD5FMU fred.mcguire.jr@... On Dec 20, 2022, at 12:43 PM, Scott VA4SMC <smcmbca@...> wrote:
|
Re: Severe hum that was not there before - SOLVED
Hi, thank you all for all the suggestions. After having a Zoom meeting with Steve N8AR, it was determined to be poor solder joints on pins 9, 10 and 11 on the SA818 radio module. The solder didn't flow into the castellated hole wall properly and therefore the ground was insufficient. After wicking the solder out and and reapplying solder the node worked better than ever. Steve did a wonderful job in troubleshooting this for me and he really stands by his product. Rightfully so. I look forward to many years of using my Pi3U and again thank Steve and everyone else with the issue, albeit caused by me as this was a kit purchase. Please check those joints carefully when assembling your kit and it should work like a charm.
Sincerely, Scott VA4SMC |
Re: Severe hum that was not there before - SOLVED
Be sure to use ferrite bead and several turns on the PI power cord ,. This helped me with him..?? On Sun, Dec 18, 2022, 3:20 PM Teton Amateur Radio Repeater Association (TARRA) <tarra@...> wrote:
|
Re: Severe hum that was not there before - SOLVED
¿ªÔÆÌåÓýKeep in mind that just a change in the load of a switching power
supply will change the frequencies in that supply. So it could
still be something that you may have changed and never thought it
would be a problem and then it is. Just wait until after Christmas when everyone gets new
thing-a-ma-bob electronics and make more noise again! ----- Original Message -----
From: "Scott VA4SMC" To: [email protected] Sent: Sunday, December 18, 2022 11:43:46 AM Subject: Re: [SHARI] Severe hum that was not there before > Well when I get home I will reprogram the radio module to another freq and see what happens. Probably something simple like that. Just funny it wasn't there before but maybe a neighbor got something that is loud. > > > > > > --
|