Re: HBlink and DMRlink questions.
Cort N0MJS <n0mjs@...>
HBlink contains a program called hb_parrot – it does not handle private calls at this time.
DMRlink has a program called playback.py that can be configured for group or private calls.
HBlink uses a callback function for ‘DMRD’ packets (contains all user-land types, voice & data). You can write any kind of processor for them you like calling the HBSYSTEM class from hblink.py and overriding the dmrd_received class method. I’ve considered parsing out the type of call in a DMRD and registering separate callbacks for those types. I’d be interested in whether or not that sounds more useful to folks?
DMRlink uses callback functions for (listed by class method name) group_voice, private_voice, group_data and private_data. You can write any kind of processor you like by calling the IPSC class from darling.py and overriding any/all of those methods.
dmrlink.py doesn’t pass anything between systems. If you’re talking about the program “confbridge.py” in dmrlink, confbridge stands specifically for “conference bridge”, and is intended to be analogous to a telephone conference bridge. Processing data calls would be out of scope for that application.