OK-DMR / Hytera_Homebrew_Bridge

[BETA] protocol translator between Hytera repeaters 8.x and 9.x and MMDVM / Homebrew servers (hblink3, freedmr, ...)
GNU Affero General Public License v3.0
27 stars 26 forks source link

Ping Pong with Repeater and Update the QRG and RadioID #7

Closed do1kbl closed 3 years ago

do1kbl commented 3 years ago

If the Repeater lost the network connection, it looks like the software will not detect it and is not logoff from mmdvm_Server

do1kbl commented 3 years ago

The Radio ID and Frequency will not overwrite the data from .ini file

This is WORKING, it was my Fault!

smarek commented 3 years ago

If the Repeater lost the network connection, it looks like the software will not detect it and is not logoff from mmdvm_Server

You mean, when MMDVM/HBlink disconnects, HHBridge does not reconnect, or when repeater disconnects it should disconnect from MMDVM/HBlink server? Former should not happen, there is maintenance routine Latter is not meant to happen, as losing repeater connection does not mean it should disconnect from mmdvm/hblink master

smarek commented 3 years ago

The Radio ID and Frequency will not overwrite the data from .ini file

This is WORKING, it was my Fault!

Different issue probably? Please keep one ticket for one issue/topic. Glad this is not a problem, again, if it was your fault, how did you fix it? I'd like to add that to FAQ

do1kbl commented 3 years ago

If the Repeater lost the network connection, it looks like the software will not detect it and is not logoff from mmdvm_Server

You mean, when MMDVM/HBlink disconnects, HHBridge does not reconnect, or when repeater disconnects it should disconnect from MMDVM/HBlink server? Former should not happen, there is maintenance routine Latter is not meant to happen, as losing repeater connection does not mean it should disconnect from mmdvm/hblink master

Yes HBLink its not the Problem. I mean if the Hytera Repeater lost the connection, we have no information about it in the logging. Maybe Its a solution if the Hytera disconnected or lost connection we have a information into the logging or the HBlink will also disconnect that we can see something with the Repeater its not OK.

smarek commented 3 years ago

Well, it does not exactly disconnect. It's UDP transport not TCP server. I can log if there was no packet (keepalive/IPSC heartbeat) received for a long time (that would mean the repeater lost connectivity / was turned off / ...) I can send REPEATER_CLOSING message to HBLINK/MMDVM and wait for repeater to connect again under such conditions. Would that be helpful?

do1kbl commented 3 years ago

maybe with a config bit? ClosedHBIfRepeaterlost ? yes/no I think the logging its very Helpfull. Closed the hb connection its an option maybe with confing? What you think?

if the repeater is somewhere, you cannot check whether it is working, you can only see that HB_Client is connected to the server but the repeater no longer sends.

smarek commented 3 years ago

I think I can close the MMDVM if no Hytera repeater is connected, not on disconnect of single one, because i'm planning on adding support for bridging multiple repeaters, see #5 Yes, the config will be necessary, thank you

smarek commented 3 years ago

I've added logging the SNMP obtained configuration and breakdown of MMDVM sent configuration, so you can check if the data merges correctly within HHB settings

smarek commented 3 years ago

I've added the request to #5 on todo-list, so this can be closed now