Skip to content
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

Repeater Timeout notification #660

Open
f5vmr opened this issue Jan 17, 2024 · 0 comments
Open

Repeater Timeout notification #660

f5vmr opened this issue Jan 17, 2024 · 0 comments

Comments

@f5vmr
Copy link

f5vmr commented Jan 17, 2024

When implementing in [Rx1] SQL_TIMEOUT=300 (for example), a repeater installation simply issues a rgr-beep and goes into 'boing mode' until shutdown, or the person causing the timeout releases the PTT. All other participants have no idea at the present time, what has occured, but clearly any further transmissions would be ineffective, until the caller drops his transmission. I think it would be beneficial at this moment to perhaps consider that a variable "TIMEOUT" be added to the $reason list in the c++ to be able to be read in the RepeaterLogic.tcl and passed to Logic.tcl to a playMsg "Core" "timeout" announcing that the initial caller had overrun. (enabling the others to call him out on speaking for too long - LOL.) Only if another station stronger in RF than the blocking station can perhaps reset the timer?

Would this be a simple fix in the RepeaterLogic.cpp or other connected file to enable this addition.

73 - Chris.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant