It was actually my attempt to give MMDVM users the "party line" feature from Motorola's IPSC... which feels like one of IPSC's worst "features"... until you don't have it anymore. But left it

Cort, Thanks for the definitive answer. I was "out of pocket" for a couple of hours. In other news... I am troubleshooting hb_parrot and working on the scripting for the Talker

Okay, I think I have it, but to clarify; each system listed in the rules in the hb_confbridge._rules.py needs to be listed as a Master in the hblink.cfg file? How are the ports and IP

[HBlink] MODE: MASTER ENABLED: True REPEAT: True EXPORT_AMBE: False IP: PORT: 62031 PASSPHRASE: passw0rd GROUP_HANGTIME: 5 [Parrot] MODE: MASTER

I don't know of anyway that 2 Peers connected to 1 Master can have rules applied. I would setup hb_confbridge with 2 masters and then you could control the traffic between the 2 Peers. Both

I had a look at the code and as it stands with Repeat=True DMR frames are simply forwarded to all connected clients. One of my objectives would be to 'block' unused talk groups to prevent someone

I can see the use case for a whitelist of TS/TG when hblink.py is used in the simple configuration of being a single Master. Once you have something working, submit a pull request so it can be looked

I would ask that functionality be *added* without removing either of the two simple options with the master today. Also, for anyone adding functionality — especially things that go directly into

I should also add that it’s important to understand the sub-classing and inheritance used with these applications. Please, please, please consider calling hblink.py or dmrlink.py as modules,

Hi Cort, Thanks for the advice. I consider myself a 'novice' python user, but the current code is very clear so I'm sure I can follow your current methodology. I will have a play in my own private

Works fine. Now to do some experiments. Matthew Pitts N8OHU

Tested my mmdvm repeater on reflector.dvswitch.org port 62031. Works OK on 9900 parrot and on 3167 . Looked on Brandmeister Last Heard list , Callsign are showing OK… But no luck

Richard, Analog_bridge, HB_bridge and IPSC_bridge are going through multiple changes every day. A number of things that we originally thought have been changed. The code has been refactored

Thanks . You guys are doing a fantastic job..... Richard

All, I understand from Yaesu that the new version of the Fusion repeater is to have an ethernet interface as standard, and that they are including a protocol to link repeaters like IPSC, referred to

Knowing Yaesu, it will be closed. All I can say is let the fun continue... On 6/7/2017 8:56 AM, Peter Martin wrote:

Steve, Yaesu uses the same vocoder as DMR for DN, and a vocoder similar to P-25 for the higher rate voice. Someone will have to wireshark the rest of the protocol though. Matthew Pitts N8OHU

Same setup this morning , Hoseline is working OK .... Richard Provenance : Courrier pour Windows 10

Keep in mind, hoseline broke a little over a week ago. There are many behind the scenes hoseline servers that feed to a master almost like a proxy. Right now most are feeds no directly from Italy.

Mike squashed a major bug in HB_bridge today. As of now it LOOKS like MMDVM Repeater <---> HB_bridge <---> IPSC_bridge <---> c-Bridge is working. There is still a bug in DMO we hope to find and