You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the older MMDVM_Host some time before 2018 ( Sorry I don't have a version ), when a user radio keys on P25 Talk group 1, the system does not unlink and stays in it's current state. This was useful when user radios were programmed with No talk group ( Motorola Defaults no talkgroup to talk group 1 ) to keep the system linked up to the current P25 Reflector without causing a disconnect.
The users on Talk Group 1 could still get out over the network to whatever Talk Group the system was connected to.
Some time later, MMDVM_Host stopped exhibiting this behavior and now whenever a user P25 radio keys on TG 1, this causes the system to unlink from the current reflector and attempt to link to a non-existent reflector on TG 1.
This issue is the request for either a fix, or some pointers on where in the source code this happens, and the exact changes needed to be made, so users can compile a custom build of MMDVM_Host with the requested behavior.
The text was updated successfully, but these errors were encountered:
On the older MMDVM_Host some time before 2018 ( Sorry I don't have a version ), when a user radio keys on P25 Talk group 1, the system does not unlink and stays in it's current state. This was useful when user radios were programmed with No talk group ( Motorola Defaults no talkgroup to talk group 1 ) to keep the system linked up to the current P25 Reflector without causing a disconnect.
The users on Talk Group 1 could still get out over the network to whatever Talk Group the system was connected to.
Some time later, MMDVM_Host stopped exhibiting this behavior and now whenever a user P25 radio keys on TG 1, this causes the system to unlink from the current reflector and attempt to link to a non-existent reflector on TG 1.
This issue is the request for either a fix, or some pointers on where in the source code this happens, and the exact changes needed to be made, so users can compile a custom build of MMDVM_Host with the requested behavior.
The text was updated successfully, but these errors were encountered: