You've seen my code (lash up!!) and i think you barfed :)
Sent from Outlook
From: DVSwitch@groups.io <DVSwitch@groups.io> on behalf of Cort N0MJS <n0mjs@...>
Sent: 29 June 2017 21:49:20
Subject: Re: [DVSwitch] Brandmeister
It could as soon as someone writes code for it :)
I’ve been thinking about this. There’s still a lot about RCM I don’t know very well, but as I get a little better handle on it in reality, could look into having it generate RCM.
Can i ask, could DMRlink generate RCM type traffic? I have a downstream user who hosts their own DMRlink, but as i use rcm_db_log, i don't get any logging from it.
Sent from Outlook
Well crap… Guess I should have fixed that! I’ll get it in the next general update.
Here’s the real deal with CON_APP.
The connection to DMRmonitor and RCM is that “repeater call monitor” (RCM) messages sent by repeaters to 3rd party console apps are different than the ones sent to non-3rd party console apps (or at least they were back when I first wrote this).
If you leave “CON-APP” enabled, you’re telling all of the peers in the IPSC system that you’re not a repeater, but some other piece of software…. disabling it was an attempt to look like a repeater and the default I *personally* ended up using.
Brandmeister already knows DMRlink it’s a Motorola repeater because it doesn’t talk XCMP, and thus thinks DMRlink is SmartPTT anyway… and I don’t think a c-Bridge cares… so it may not matter much in reality.
On Jun 29, 2017, at 12:14 PM, Steve N4IRS <szingman@...
They are both set true in the sample config. I set them to false in the IPSC_Bridge branch.
I do remember this in the comments:
# CON_APP: Third Party Console App - exactly what DMRlink is, should
# be set to True, and must be if you intend to process RCM
On 6/29/2017 1:05 PM, Cort N0MJS wrote:
Those tell me Steve is running DMRmonitor also — you should set both to False unless you’re using DMRmonitor also, or know exactly what they do and know you need them.
On Jun 29, 2017, at 11:40 AM, Steve N4IRS <szingman@...