I don't think this has anything to do with the repeater duplex configuration. FWIW; mine was apparently wrong for a couple of weeks and I never actually noticed.
Are you sure your node is registered and connected to things? If this were some kind of sound configuration issue; then you shouldn't be able to hear even the beeps since those are all generated by asterisk. I haven't encountered a connect failure to know if you get a voice announcement.
I suppose an update could have broken something that put your node in to a disabled/non-registered state.
It's working because when I go to 55553 I can hear something when I transmit, but there are so many courtesy beeps that I can't hear my voice echo back to me. Also, when I get on something like the East Coast Reflector, many curtesy beeps are heard when I'm listening to others transmit.
I'll have to say that I've also been disconnected from the East Coast Reflector a couple of times. I also don't hear the many curtesy beeps when I'm listening to the TGIF 9050 talk group.
I just went back in and double checked the AllStar Node Setup in asl-menu, and it all looked fine. Duplex type was set to 1 there.
I'm very comfortable with DMR, code plugs and the Linux command line interface. So, if I can enter a command or go to a menu from Linux to fix this, I can do it. Otherwise, I'll probably have re-image my SHARI pi node again.
It looks like node 65754 is connected to other nodes than just 55553. This could be causing some of the problem I'm hearing on 55553 and other nodes that they may be connected to.
This is correct. I think I was globally monitoring 580871 (W1LFH, connected to Ham Radio 2.0), but I was surely locally monitoring other stuff so that shouldn't have even gotten into much of the mix unless you were to transmit from my node directly...
It all started because I noticed how damn loud I was on there (I was also connected to 548730 which is another friend of mine's node which I was hearing), so I went to 55553 and put W1LFH in monitor. I then tested around and what not and that turned out a little odd because I sounded fine after that. I use IaxRpt to transmit and also RepeaterPhone when I'm away from the computer. Anyway, no matter... I had lowered my node in IaxRpt and didn't realize that this was still going, so thanks for mentioning my node number as now it should be cleared from all that mess. It now says "Repeat-only" when on *70. I'm usually better about these things, too, so yeah... I guess sometimes my own brain can be crazy and I honestly only just saw this and got around to it now.
Thanks Chris. I'm not noticing any repeater-like connections on the East Cost Reflector today. But, on the parrot, 55553, it still sounds like something is keying up after my transmission because I can't hear my report from the parrot node. Node 65019 has a connect to 55553, but also has a connection which goes to two other nodes.
There was someone connected to the parrot and East Coast Reflector today when I was connected, but that went away. My AllStar Link connection to the East Coast Reflector is now working as expected.
I'm thinking of getting into reflectors using DMR on TGIF may be a good way to go since I don't hear the AllStar Link problems there.
Can you record what you are hearing on 55553? That's my node, and I'm not hearing any unusual telemetry on it today. Do you have anything similar with node 2002, the official ASL parrot?
Just to butt in here with my two cents; I connected to your parrot yesterday, Patrick; in addition to the talking man evaluating my audio, I got some CW played back at me. 30 years ago, I'd almost hit 30 WPM comprehension, but nowadays I'd be lucky to do 5, so I don't know WTH it said (just in case that was the "beeping" the OP was referring to).
Just to butt in here with my two cents; I connected to your parrot yesterday, Patrick; in addition to the talking man evaluating my audio, I got some CW played back at me. 30 years ago, I'd almost hit 30 WPM comprehension, but nowadays I'd be lucky to do 5, so I don't know WTH it said (just in case that was the "beeping" the OP was referring to).
The parrot is working fine today. I was able to check my mic level and received the parrot audio back just fine with no interruption. I think that somebody had their node connected to other nodes other than 55553. Thank you for providing this service!
|