Currently the Hylink Socket handler can only handle a single repeater. It would be useful to have support for multiple repeater connections on a single dispatch console.
This will require additions to the hylink.socket code to do the following:
Track active repeater connections
Identify the repeater which originated an incoming packet
Allow the target repeater to be specified when sending packets
Manage heartbeats and timeouts on a per-repeater basis (this will probably require the timing fluff to be moved into per-repeater timer threads)
Currently the Hylink Socket handler can only handle a single repeater. It would be useful to have support for multiple repeater connections on a single dispatch console.
This will require additions to the
hylink.socketcode to do the following: