Re: DMRId lookup possible bug? #mmdvm_bridge

Steve N4IRS

It actually not a bug. Here is why.
When the network data is received from YSF in this case "   3167057" The lookup is looking for a call sign, Since DMR IDs are not used in YSF. Had the string been "KC3PLD to        ALL at NC4CL then the lookup would have resolved to 3167057 and been passed to DMR. The lookup did try to resolve "   3167057". Since call signs are a max if 6 characters, lookup tried to lookup 316705. This is still not a valid call sign, so the fallback ID was used.

Hope this helps,
73, Steve N4IRS

On 6/20/20 4:03 PM, Roland W9HPX wrote:
In the log file for MMDVM_Bridge I noticed these two lines:

M: 2020-06-20 18:12:54.164 YSF, received network data from    3167057 to        ALL at NC4CL    

I: 2020-06-20 18:12:54.164 YSF, Lookup call 316705 returned id 0 -> 3146443
It appears all 7 digits of the DMR ID were received, yet only the first 6 digits were used and the bridge default ID was substituted.  I verified 3167057 was in the DMRId.dat file located in /var/lib/mmdvm.  Is this explainable by something that is not a software bug?  Or is it a bug?
73 de Roland W9HPX

Join to automatically receive all group messages.