-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't process/forward packets from repeater if RF call sign is blank. #51
Comments
When I connect the system to my URFd reflector I see the following, so it seems the call sign isn't being sent out the wire too.
|
And, just as I write that last comment, a different user started using the system and their callsign shows up fine. |
Never mind, my radio somehow changed to a local call that was configured to be blank. I'm going to leave this open as I suspect if the call sign is blank, either the packet shouldn't be processed, or at the very least shouldn't be forwarded to reflectors. |
Thanks for the heads up. This behavior is the same as in ircddbGateway. IMHO it is better to forward to the reflector maybe the operator might get a reply from other that his radio his misconfigured. |
Since there's no operator call sign in the DStar data packet, neither the repeater, nor the reflector has any contact details to work with. I don't know the DStar RF spec, but in reality, if there's no CallSign set, I'd expect the repeater to return some kind of error. Makes me wonder what the ICOM service would have done. |
Well, the audio will make it through end other operators on the other end might be able to signal the issue to the "blank station" via voice. |
Yeah, maybe the gateway shouldn't see the frames. I'm on iCOM gear so it sends the frames to the controller, which in my case is the gateway. I'll do some more experiments with my team here to see what happens. I can't test the iCOM gateway tho. |
It seems the RF side call signs seem to be missing in for the
Repeater header
at least when connected to icom repeater gear.The text was updated successfully, but these errors were encountered: