Re: Adding hb_confbridge Into the Mix
Existing:toggle quoted messageShow quoted text
3 MMDVM nodes---->HBLink----->HB_Bridge---->IPSC Bridge--->CBridge---> TRBO Repeaters
MMDVM1 <---> hb_confbridge_M1
MMDVM2 <---> hb_confbridge_M2
MMDVM3 <---> hb_confbridge_M3
hb_confbridge_C1 <---> HB_Bridge---->IPSC Bridge--->CBridge---> TRBO Repeaters
M1, M2, M3 are MASTERS defined in hblink.cfg for the confbridge
C1 is a CLIENT defined in hblink.cfg for the confbridge
You would continue to start the HB <---> IPSC Bridge with "python HB_Bridge.py" and "python IPSC_Bridge.py" Just as before
The hb_confbridge_rules would be used to control the traffic between the MMDVM Clients and the traffic from the MMDVM Clients to HB_Bridge.
You would start hb_confbridge with "python hb_confbridge.py"
You will have 2 instances of hblink.py running. You can control this by keeping them in separate directories or by passing the name of the config file on the command line.
As with all bridges, build from the outside in. Since you already have most of this running, build up the confbridge get the MMDVM clients connected and the rules defined.
When that all works, make the confbridge to HB_Bridge connection. This off the top of my head and others may have input as to a better way.
73, Steve N4IRS
On 5/29/2018 2:31 PM, James - K4JK wrote: