Hi, I downloaded the latest DMRIds.dat file from github and it's the mmdvm_bride.ini file is pointing to the right file path. Do I need to do anything with permissions? The log at /var/log/mmdvm is re

#mmdvm_bridge

Is the user database up to date? Please post MB log when there is traffic.

#mmdvm_bridge

On the fusion reflector no DMR callsigns are being translated to the callsign, and when someone transmits on the fusion side, it just shows my DMRID on the pistar. dashboard is here http://18.134.217.

#mmdvm_bridge

Hi Steve, I figured out the issue. I was following the guide made by KV4S - https://kv4s.com/2018/05/23/hosting-an-allstar-node-and-an-allstardmr-bridge-in-the-cloud/ - but using dmr<>ysf, I had to ve

#mmdvm_bridge

Hi everyone I have a link running between YSF and DMR. I'd like to be able to pass the callsigns between the two, right now it's just using the fallback ID. Any tips or tricks to share? Thanks 73

#mmdvm_bridge

Please post your MMDVM_Bridge.ini and DVSwitch.ini and MMDVM_Bridge log. if you are using YSFGateway, show YSFGateway.ini

#mmdvm_bridge

Ok yes its true. Anyway i solve the initial issue about mb1 and mb2 crash .

#mmdvm_bridge

Looking at your logs, I see that the station transmitting with dmr2ysf is placing the users DMR ID in the callsign field. I would bet that their dmr id database is not up to date so it is just sending

#mmdvm_bridge

Yes i point each mbridge to her dmrid path. But i dont use analogue bridge her . Its only mbridge

#mmdvm_bridge

MMDMV_Briidge looks for DMRIds.dat and Analog_Bridge looks for subscriber_ids.csv. Since these are both static text files you need a copy for each instance in /var/lib. The initial install puts DMRIds

#mmdvm_bridge

ok tonight i re update latest bin and now they work without crash but they have a issue with the id. look my mb1 and mb2 log with the id.my id is 3022260 but one of them missing the last digit, 302226

#mmdvm_bridge

Ok tonight i re downlaod the binary . Change my mmdvmbridge binary for the latest download. Now they work both way without crash but mb1 show the right dmrid associated to the right callsign but mb2 a

#mmdvm_bridge

O.K. That explains the problem better but leaves me without an answer. I have some suspicions and I have a hot spot that I can play and packet analyzer software so if you don't get it resolved let me

#mmdvm_bridge

Hi Steve. All set this way. Different path for .ini and log. The system work well its not a issue to start and run mb1 and mb2. I runnning it in ysf without any issue and no crash in mb1 or2 if i only

#mmdvm_bridge

Didn't see this error before sorry, I really need to be more attentive: Segmentation fault (core dumped) Caused by trying to write to the same log file from two different instances of mmdvm_bridge. Fi

#mmdvm_bridge

Ok, I have some idea of what you're trying to accomplish. Sorry if some of this is redundant but others may want to understand: Here's my take: Install DVSwitch from the repository to /opt/ which crea

#mmdvm_bridge

in another way i have a nxdn reflector.he is linked to my ysfreflector and when i use my openspot2 nxdn to ysf they work flawlesly and no crash from mb1 or mb2

#mmdvm_bridge

Maybe i can try to change the in each mb path to start ex mmdvmbridge1 and 2

#mmdvm_bridge

I create new .service for each mb .mb1 and mb2 differenf path .in and .ini2

#mmdvm_bridge

Yes . I stop everything disable them and built my .ini I already try to change rebuilt purge reinstall update bimary try many other port . With the same issue.

#mmdvm_bridge