Home Messages Hashtags Subgroups Wiki

Welcome to DVSwitch

DVSwitch is a set of tools and programs related to provisioning and operating Amateur Radio digital voice networks.

Purpose

The purpose of DVSwitch is as follows:

1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).

Mission Statement/Position

Our stated position is:

WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.

(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].

BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.

Between

and

Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Rudy N6DOZ #6540 That's awesome Steve! How about for those folks who aren't on a Rasberry Pi? :P My services are on the cloud running Ubuntu 18.04.4 LTS. If the updates apply, which one do I grab from Github? Thanks for all the hard work Steve!
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Eric-K6KWB #6539 Steve N4IRS, That latest update on MB means we dont need to set up static TG on self care? set TG on DVSwitch.ini is enough? Appreciated. best and 73, Eric
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Eric-K6KWB #6538 Yes you need two MB one connect to BM and one for YSF Gateway. Almost similar to the first one you create use YSF Gateway and select FCS. BM-TG??<->MB_BM<->MB_YSF<->YSF Gateway<->FCS003 Did you download from DVSwitch System Builder a complete package: https://github.com/DVSwitch/DVSwitch-System-Builder Looks like Steve have developed a new update to steer TGs in MB, will see how does it work, thank you Steve for this update. :) 73, Eric
More All Messages By This Member
Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge Steve N4IRS #6537 To connect to FCS, you will need to use YSFGateway. (today) Steve N4IRS toggle quoted messageShow quoted text On 5/16/20 4:42 PM, Rudy N6DOZ wrote: I currently have a successful bridge between my YSF reflector to DMR through MMDVM_Bridge. Is it possible to emulate the same idea, but to an FCS reflector? BM_TG <-> MB <-> FCS00457 Here's my attempt at this (just realized, there's no entry for me to put the reflector number): MMDVM.ini [General] Callsign=N6DOZ Id=315069250 Timeout=180 Duplex=0 [DMR] Enable=1 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [DMR Network] ; to DMR Enable=1 Address=3103.repeater.net Port=62031 Jitter=360 Local=62032 Password=passw0rd Slot1=0 Slot2=1 Debug=0 [System Fusion Network] ; FCS Enable=1 LocalAddress=0 LocalPort=3201 GatewayAddress=fcs004.xreflector.net GatewayPort=62500 Debug=0 DVSwitch.ini ; Configure the DMR Partner ; Audio format is AMBE 72 bit [DMR] Address = 127.0.0.1 TXPort = 33100 RXPort = 33103 Slot = 2 ; Slot = 1 ; Configure the Yaesu Fusion Partner ; Audio format is AMBE 72 bit ; Audio format is IMBE 88 bit [YSF] Address = 127.0.0.1 TXPort = 33103 RXPort = 33100 FallbackID = 3135404 ExportTG = 311620 Slot = 2 Q. Is this even possible? Or is there a different method to this? Thanks in advance, 7-3 N6DOZ.
More All Messages By This Member
Re: Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge Rudy N6DOZ #6536 Edited When I transmit to the TG, it looks like MB sees it, but no audio on the other end. I: 2020-05-16 20:36:39.678 MMDVM_Bridge: I: 2020-05-16 20:36:39.679 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2020-05-16 20:36:39.679 Hacks by Mike N4IRR and Steve N4IRS I: 2020-05-16 20:36:39.679 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I: 2020-05-16 20:36:39.679 This software is for use on amateur radio networks only, I: 2020-05-16 20:36:39.679 it is to be used for educational purposes only. Its use on I: 2020-05-16 20:36:39.679 commercial networks is strictly prohibited. I: 2020-05-16 20:36:39.679 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2020-05-16 20:36:39.679 MMDVM_Bridge-20191105_V1.4.1 is starting M: 2020-05-16 20:36:39.679 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac) I: 2020-05-16 20:36:39.679 General Parameters I: 2020-05-16 20:36:39.679 Callsign: N6DOZ I: 2020-05-16 20:36:39.679 Id: 315069250 I: 2020-05-16 20:36:39.679 Duplex: no I: 2020-05-16 20:36:39.679 Timeout: 180s I: 2020-05-16 20:36:39.679 DMR: enabled I: 2020-05-16 20:36:39.680 YSF: enabled M: 2020-05-16 20:36:39.681 Opening the MMDVM I: 2020-05-16 20:36:39.681 Display Parameters I: 2020-05-16 20:36:39.681 Type: I: 2020-05-16 20:36:39.681 DMR Network Parameters I: 2020-05-16 20:36:39.681 Address: 3103.repeater.net I: 2020-05-16 20:36:39.681 Port: 62031 I: 2020-05-16 20:36:39.681 Local: 62032 I: 2020-05-16 20:36:39.681 Jitter: 360ms I: 2020-05-16 20:36:39.681 Slot 1: disabled I: 2020-05-16 20:36:39.682 Slot 2: enabled I: 2020-05-16 20:36:39.683 Info Parameters I: 2020-05-16 20:36:39.683 Callsign: N6DOZ M: 2020-05-16 20:36:39.684 DMR, Opening DMR Network I: 2020-05-16 20:36:39.684 System Fusion Network Parameters I: 2020-05-16 20:36:39.684 Local Address: 0 I: 2020-05-16 20:36:39.684 Local Port: 3201 I: 2020-05-16 20:36:39.684 Gateway Address: fcs004.xreflector.net I: 2020-05-16 20:36:39.684 Gateway Port: 62500 I: 2020-05-16 20:36:39.684 Mode Hang: 3s M: 2020-05-16 20:36:39.684 Opening YSF network connection I: 2020-05-16 20:36:39.684 RSSI I: 2020-05-16 20:36:39.684 Mapping File: RSSI.dat W: 2020-05-16 20:36:39.685 Cannot open the RSSI data file - RSSI.dat I: 2020-05-16 20:36:39.685 DMR Id Lookups I: 2020-05-16 20:36:39.685 File: /var/lib/mmdvm/DMRIds.dat I: 2020-05-16 20:36:39.685 Reload: 24 hours I: 2020-05-16 20:36:39.847 Loaded 164578 Ids to the DMR callsign lookup table I: 2020-05-16 20:36:39.847 DMR RF Parameters I: 2020-05-16 20:36:39.847 Id: 315069250 I: 2020-05-16 20:36:39.847 Color Code: 1 I: 2020-05-16 20:36:39.847 Self Only: no I: 2020-05-16 20:36:39.847 Embedded LC Only: yes I: 2020-05-16 20:36:39.848 Dump Talker Alias Data: no I: 2020-05-16 20:36:39.848 Prefixes: 0 I: 2020-05-16 20:36:39.848 Call Hang: 3s I: 2020-05-16 20:36:39.848 TX Hang: 3s I: 2020-05-16 20:36:39.848 Mode Hang: 10s M: 2020-05-16 20:36:39.848 DMR, Opening INI file: DVSwitch.ini M: 2020-05-16 20:36:39.848 DMR, Setting [DMR] Address -> 127.0.0.1 M: 2020-05-16 20:36:39.848 DMR, Setting [DMR] TXPort -> 33100 M: 2020-05-16 20:36:39.848 DMR, Setting [DMR] RXPort -> 33103 M: 2020-05-16 20:36:39.848 DMR, Setting [DMR] Slot -> 2 M: 2020-05-16 20:36:39.848 DMR, Transmitting on 127.0.0.1:33100 and listening on port 33103. Result = 1 I: 2020-05-16 20:36:39.848 YSF RF Parameters I: 2020-05-16 20:36:39.848 Low Deviation: no I: 2020-05-16 20:36:39.848 Remote Gateway: no I: 2020-05-16 20:36:39.848 Self Only: no I: 2020-05-16 20:36:39.848 DSQ: no I: 2020-05-16 20:36:39.849 Mode Hang: 10s M: 2020-05-16 20:36:39.849 YSF, Opening INI file: DVSwitch.ini M: 2020-05-16 20:36:39.849 YSF, Setting [YSF] Address -> 127.0.0.1 M: 2020-05-16 20:36:39.849 YSF, Setting [YSF] TXPort -> 33103 M: 2020-05-16 20:36:39.849 YSF, Setting [YSF] RXPort -> 33100 M: 2020-05-16 20:36:39.849 YSF, Setting [YSF] FallbackID -> 3135404 M: 2020-05-16 20:36:39.849 YSF, Setting [YSF] ExportTG -> 311620 M: 2020-05-16 20:36:39.849 YSF, Setting [YSF] Slot -> 2 M: 2020-05-16 20:36:39.849 YSF, Transmitting on 127.0.0.1:33103 and listening on port 33100. Result = 1 M: 2020-05-16 20:36:39.849 MMDVM_Bridge-20191105_V1.4.1 is running I: 2020-05-16 20:36:39.849 Started the DMR Id lookup reload thread D: 2020-05-16 20:36:49.858 DMR, Sending authorisation D: 2020-05-16 20:36:49.863 DMR, Sending configuration M: 2020-05-16 20:36:49.868 DMR, Logged into the master successfully M: 2020-05-16 20:37:35.663 DMR Slot 2, received network late entry from N6DOZ to TG 311620 M: 2020-05-16 20:37:35.663 YSF, TX state = ON I: 2020-05-16 20:37:35.663 YSF, Begin TX: src=3135404 rpt=0 dst=311620 slot=2 cc=0 metadata=N6DOZ I: 2020-05-16 20:37:35.724 YSF, Narrow transmit (72 bit) M: 2020-05-16 20:37:36.264 DMR Talker Alias (Data Format 1, Received 6/10 char): 'N6DOZ ' M: 2020-05-16 20:37:36.982 DMR Talker Alias (Data Format 1, Received 10/10 char): 'N6DOZ Rudy' M: 2020-05-16 20:37:38.182 DMR Slot 2, received network end of voice transmission, 2.6 seconds, 0% packet loss, BER: 0.0% M: 2020-05-16 20:37:38.182 YSF, TX state = OFF
More All Messages By This Member
Is it possible to bridge an FCS reflector to DMR? (2020) #mmdvm_bridge Rudy N6DOZ #6535 Edited I currently have a successful bridge between my YSF reflector to DMR through MMDVM_Bridge. Is it possible to emulate the same idea, but to an FCS reflector? BM_TG <-> MB <-> FCS00457 Here's my attempt at this (just realized, there's no entry for me to put the reflector number): MMDVM.ini [General] Callsign=N6DOZ Id=315069250 Timeout=180 Duplex=0 [DMR] Enable=1 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [DMR Network] ; to DMR Enable=1 Address=3103.repeater.net Port=62031 Jitter=360 Local=62032 Password=passw0rd Slot1=0 Slot2=1 Debug=0 [System Fusion Network] ; FCS Enable=1 LocalAddress=0 LocalPort=3201 GatewayAddress=fcs004.xreflector.net GatewayPort=62500 Debug=0 DVSwitch.ini ; Configure the DMR Partner ; Audio format is AMBE 72 bit [DMR] Address = 127.0.0.1 TXPort = 33100 RXPort = 33103 Slot = 2 ; Slot = 1 ; Configure the Yaesu Fusion Partner ; Audio format is AMBE 72 bit ; Audio format is IMBE 88 bit [YSF] Address = 127.0.0.1 TXPort = 33103 RXPort = 33100 FallbackID = 3135404 ExportTG = 311620 Slot = 2 Q. Is this even possible? Or is there a different method to this? Thanks in advance, 7-3 N6DOZ. ====== TL;DR Got it working based with help from Eric K6KWB and Steve N4IRS. This is what I ended up with: BM <-> MB <-> YSFGateway <-> FCS Reflector MMDVM_Bridge.ini [General] Callsign=N6DOZ Id=315069220 Timeout=180 Duplex=0 [Log] # Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal DisplayLevel=1 FileLevel=2 FilePath=/var/log/mmdvm FileRoot=MMDVM_Bridge-DMX [DMR] Enable=1 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [System Fusion] Enable=1 [DMR Network] ; to DMR Enable=1 Address=3103.repeater.net Port=62031 Jitter=360 Password=passw0rd Slot1=0 Slot2=1 Debug=0 [System Fusion Network] Enable=1 LocalAddress=0 LocalPort=62045 GatewayAddress=127.0.0.1 GatewayPort=62046 Debug=0 DVSwitch.ini [DMR] Address = 127.0.0.1 TXPort = 34100 RXPort = 34103 Slot = 2 [YSF] Address = 127.0.0.1 TXPort = 34103 RXPort = 34100 FallbackID = 3135404 ExportTG = 311620 Slot = 2 YSFGateway.ini [General] Callsign=N6DOZ #Suffix=RPT # Suffix=ND Id=3150692 RptAddress=127.0.0.1 RptPort=62045 LocalAddress=127.0.0.1 LocalPort=62046 Daemon=0 [Network] Startup=FCS00457 InactivityTimeout=10 Revert=0 Debug=0 [FCS Network] Enable=1 Rooms=/var/lib/mmdvm/FCSRooms.txt Port=42001
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Steve N4IRS #6534 Edited Ernie, If you are running your bridge on a Pi (armhf) we have added the ability to steer TGs (just like slots) in MB. I have pushed the change to github. See the added parameter in dvswitch.ini {DMR] stanza. Try it if you want to. 3, Steve N4IRS
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Rudy N6DOZ #6533 Thanks Eric for taking the time. I do have a working setup of this, which I set aside so that the XLX and YSF reflectors can connect to two different BM TGs at the same time (when needed), then go back to the old setup when not in need to do so. Do you think I can use MMDVM_Bridge to remotely link my FCS003 reflector to DMR? That's what I am trying to do now. Cheers! 7-3
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Eric-K6KWB #6532 Rudy, In this set up you will NOT use DMRGateway anymore. BM-TG-A<->MB1<->YSF >>>this one looks good! the second one will be: XLX<->MB2<->YSF >>> both your instance will connect to YSF Ref. make sure to pay attention to the port. Looks like this: BM-TG??set on BM self care<->MB1<-.>YSF That is done deal, make sure cross the port on DVSwitch.ini (working Sample) MB1 [DMR Network] Enable=1 Address=3103.repeater.net Port=62031 Jitter=360 Local=62032 Password=passw0rd # for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md # for XLX the syntax is: Options=XLX:4009 # Options= Slot1=0 Slot2=1 Debug=0 [System Fusion Network] Enable=1 LocalAddress=127.0.0.1 LocalPort=0 GatewayAddress=point to your ysf reflector GatewayPort=42000 >>port of your reflector Debug=0 DVS.ini [DMR] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 35103 ; Port to send AMBE TLV frames to (export) RXPort = 35100 ; Port to listen on (import) Slot = 2 [YSF] Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export) TXPort = 35100 ; Port to send AMBE TLV frames to (export) RXPort = 35103 ; Port to listen on (import) FallbackID = your id ; In case we can not find a valid DMR id in the database, export this one ExportTG = TG ; Which TG to export Slot = 2 ; Export slot Thats it for MB1, you can create your existing MB to connect to XLX to YSF just point your MB.ini to your XLX so with your YSF Ref and just do similar cross port on DVS.ini . I hope this help, what I want to accomplish is to bridge DMR,YSF and XLX Dstar. 73, Eric
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Rudy N6DOZ #6531 Edited Eric, Thanks for that. I initially had this setup, but wanted the XLX and YSF to be independent if I wanted to switch one reflector to a different TG. The setup below, YSF is acting as the gateway to DMR? BM-TG <->MB1<->YSF<->MB2<->XLX Is that what you are talking about? I wanted them to stand alone for the scenario below if necessary: BM-TG-A<->MB1<->YSF BM-TG-B<->DMRGateway<->MB<->MB<->XLX However, I do understand my prior setup is more efficient. Is there a more efficient way of achieving the scenario above? Thanks again for getting back. 7-3 --- My next project is to get the FCS reflector bridged to DMR, since you mentioned FCS... I guess I can search and look for answers or start a new thread for that.
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Eric-K6KWB #6530 Rudy, Also if you have a FCS you can do the same way by replacing DMRGateway to YSFGateway. Bridging XLX I only use one instance of MB but I point to YSF reflector looks like this: First instance: XLX<->BM<->YSF this is very efficient To bridge BM -TG I also use one instance of MB and also point to YSF reflector. Second instance: BM-TG<->MB<->YSF This is not a chain both instances run independently in one box. The downside is if you dont have YSF reflector then you go back to square one : ( 73, Eric
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Rudy N6DOZ #6529 Edited I ended up doing what Ernie Gm7kbk suggested, which is basically running the MB_BM through DMRGateway to change TG9 to my target TG. BM <-> DMRGateway <-> MB_BM <-> MB_XLX <-> XLX Works great! Now I have audio both ways. Thanks everyone! 7-3 === for reference === DMRGateway DMRGateway.ini [General] Timeout=10 # RFTimeout=10 # NetTimeout=7 RptAddress=127.0.0.1 RptPort=62052 LocalAddress=127.0.0.1 LocalPort=62051 RuleTrace=0 Daemon=0 Debug=0 # BrandMeister [DMR Network 1] Enabled=1 Name=BM Address=3103.repeater.net # 74.91.118.251 Change to the address for your Master Port=62031 # Local=3352 # Local cluster TGRewrite=1,9,1,9,1 # Reflector TG on to slot 2 TG9 # TGRewrite=2,9,2,9,1 TGRewrite=2,9,2,311620,1 # ROUTES TG9 to target TG on BM # XLX TG 6 on to slot 2 BM TG12345 # Change 12345 to desired BM TG # TGRewrite=2,6,2,12345,1 # Reflector control command slot 2 94000->4000 to 95000->5000 PCRewrite=2,94000,2,4000,1001 # Echo on RF slot 1 TG9990 to network slot 1 9990 TypeRewrite=1,9990,1,9990 SrcRewrite=1,9990,1,9990,1 # Reflector status returns SrcRewrite=2,4000,2,9,1001 # Pass all of the other private traffic on slot 1 and slot 2 PassAllPC=1 PassAllPC=2 Password="passw0rd" # Make sure the password is passw0rd for BM Location=1 Debug=0 MB_BM MMDVM_Bridge.ini [DMR] Enable=1 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [DMR Network] ; to DMR Enable=1 Address=127.0.0.1 Port=62051 Jitter=360 Local=62052 Password=passw0rd Slot1=0 Slot2=1 Debug=0 DVSwitch.ini [DMR] Address = 127.0.0.1 TXPort = 32103 RXPort = 32100 Slot = 2 ; Slot = 1 MB_XLX MMDVM_Bridge.ini [DMR] Enable=1 ColorCode=1 EmbeddedLCOnly=1 DumpTAData=0 [DMR Network] ; to DMR Enable=1 Address=45.77.186.5 # IP Address of XLX reflector Port=62030 Jitter=360 #Local=62033 #Password=passw0rd Password=PASSWORD # for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md # for XLX the syntax is: Options=XLX:4009 # Options= Options=XLX:4001 # Option for module A Slot1=0 Slot2=1 Debug=0 DVSwitch.ini [DMR] Address = 127.0.0.1 TXPort = 32100 RXPort = 32103 Slot = 2 ; Slot = 1
More All Messages By This Member
Re: agile Allstar node from MMDVM Patrick Perdue #6528 I would’ve thought that as well, although if I Chi up on a digital radio and start sending DTMF, it sounds pretty pure on other DMR radios, as well as on the other side of MMDVM bridge. I was pretty surprised about that. apparently, it works well enough if you are sending baseband analog audio directly to ASL through a FOB when sent through fusion, but this person was hoping for a software solution entirely. toggle quoted messageShow quoted text On May 16, 2020, at 02:02, Brad N8PC <bradn8pc@gmail.com> wrote: no cause once converted to digital sounds funny to analog and does not work. On 5/16/2020 12:37 AM, Patrick Perdue wrote: Hi: I was just asked by someone if it was possible to pass DTMF from YSF to DMR to an Allstar node such that it can be driven remotely from MMDVM, rather than what most people want going the other way around, sending DTMF commands to an Allstar node to change modes and digital talkgroups/reflectors. My first thought is no, because USRP seems to just pass DTMF through as audio, and there is no DSP to process incoming audio to send to Asterisk as commands, such as would be the case with the SimpleUSB driver and an analog radio. Has anyone here done this, and is this at all possible?
More All Messages By This Member
Re: agile Allstar node from MMDVM Brad N8PC #6527 no cause once converted to digital sounds funny to analog and does not work. toggle quoted messageShow quoted text On 5/16/2020 12:37 AM, Patrick Perdue wrote: Hi: I was just asked by someone if it was possible to pass DTMF from YSF to DMR to an Allstar node such that it can be driven remotely from MMDVM, rather than what most people want going the other way around, sending DTMF commands to an Allstar node to change modes and digital talkgroups/reflectors. My first thought is no, because USRP seems to just pass DTMF through as audio, and there is no DSP to process incoming audio to send to Asterisk as commands, such as would be the case with the SimpleUSB driver and an analog radio. Has anyone here done this, and is this at all possible?
More All Messages By This Member
agile Allstar node from MMDVM Patrick Perdue #6526 Hi: I was just asked by someone if it was possible to pass DTMF from YSF to DMR to an Allstar node such that it can be driven remotely from MMDVM, rather than what most people want going the other way around, sending DTMF commands to an Allstar node to change modes and digital talkgroups/reflectors. My first thought is no, because USRP seems to just pass DTMF through as audio, and there is no DSP to process incoming audio to send to Asterisk as commands, such as would be the case with the SimpleUSB driver and an analog radio. Has anyone here done this, and is this at all possible?
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Rudy N6DOZ #6523 Forum keeps chopping my message, so I'm posting this separately: MB_XLX I: 2020-05-15 07:06:41.725 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGINT I: 2020-05-15 07:06:48.212 MMDVM_Bridge: I: 2020-05-15 07:06:48.212 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2020-05-15 07:06:48.212 Hacks by Mike N4IRR and Steve N4IRS I: 2020-05-15 07:06:48.212 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I: 2020-05-15 07:06:48.213 This software is for use on amateur radio networks only, I: 2020-05-15 07:06:48.213 it is to be used for educational purposes only. Its use on I: 2020-05-15 07:06:48.213 commercial networks is strictly prohibited. I: 2020-05-15 07:06:48.213 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2020-05-15 07:06:48.213 MMDVM_Bridge-20191105_V1.4.1 is starting M: 2020-05-15 07:06:48.213 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac) I: 2020-05-15 07:06:48.213 General Parameters I: 2020-05-15 07:06:48.213 Callsign: N6DOZ I: 2020-05-15 07:06:48.213 Id: 3150692 I: 2020-05-15 07:06:48.213 DMR: enabled I: 2020-05-15 07:06:48.215 Display Parameters I: 2020-05-15 07:06:48.215 Type: I: 2020-05-15 07:06:48.215 DMR Network Parameters I: 2020-05-15 07:06:48.215 Address: 45.77.186.5 I: 2020-05-15 07:06:48.215 Port: 62030 I: 2020-05-15 07:06:48.215 Local: 62033 I: 2020-05-15 07:06:48.215 Slot 1: disabled I: 2020-05-15 07:06:48.215 Slot 2: enabled I: 2020-05-15 07:06:48.215 Options: XLX:4001 I: 2020-05-15 07:06:48.215 Info Parameters I: 2020-05-15 07:06:48.215 Callsign: N6DOZ I: 2020-05-15 07:06:48.384 DMR RF Parameters I: 2020-05-15 07:06:48.384 Id: 3150692 I: 2020-05-15 07:06:48.384 Color Code: 1 M: 2020-05-15 07:06:48.384 DMR, Opening INI file: DVSwitch.ini M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] Address -> 127.0.0.1 M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] TXPort -> 32100 M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] RXPort -> 32103 M: 2020-05-15 07:06:48.385 DMR, Setting [DMR] Slot -> 1 M: 2020-05-15 07:06:48.385 DMR, Transmitting on 127.0.0.1:32100 and listening on port 32103. Result = 1 M: 2020-05-15 07:06:48.385 MMDVM_Bridge-20191105_V1.4.1 is running I: 2020-05-15 07:06:48.385 Started the DMR Id lookup reload thread M: 2020-05-15 07:07:08.405 DMR, Logged into the master successfully M: 2020-05-15 07:07:08.405 DMR, Remote CMD: txTg=4000 M: 2020-05-15 07:07:08.405 DMR, Tune: id=3150692, tg=4000, mode=Group M: 2020-05-15 07:07:08.405 DMR, Remote CMD: txTg=4001 M: 2020-05-15 07:07:08.405 DMR, Tune: id=3150692, tg=4001, mode=Group M: 2020-05-15 07:07:08.456 DMR Slot 2, received network voice header from N6DOZ to TG 9 M: 2020-05-15 07:07:08.461 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0% M: 2020-05-15 07:12:26.479 DMR, TX state = ON I: 2020-05-15 07:12:26.479 DMR, Begin TX: src=3135404 rpt=0 dst=311620 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:12:30.077 DMR, TX state = OFF, DMR frame count was 62 frames M: 2020-05-15 07:12:33.743 DMR Slot 2, received network voice header from N6DOZ to TG 9 M: 2020-05-15 07:12:37.402 DMR Slot 2, received network end of voice transmission, 3.9 seconds, 1% packet loss, BER: 0.0% M: 2020-05-15 07:12:46.739 DMR Slot 2, received network voice header from N6DOZ to TG 9 M: 2020-05-15 07:12:49.226 DMR Slot 2, received network end of voice transmission, 3.1 seconds, 11% packet loss, BER: 0.0% M: 2020-05-15 07:13:15.060 Closing the MMDVM I: 2020-05-15 07:13:15.417 Stopped the DMR Id lookup reload thread M: 2020-05-15 07:13:15.418 DMR, Closing DMR Network I: 2020-05-15 07:13:15.418 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGINT
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Rudy N6DOZ #6522 Edited Steve, I apologize, I believe I did post the same log twice. I'm going to try again and emulating you by only providing the important lines. Third time's a charm? :p MB_BM I: 2020-05-15 07:06:45.626 MMDVM_Bridge: I: 2020-05-15 07:06:45.626 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2020-05-15 07:06:45.626 Hacks by Mike N4IRR and Steve N4IRS I: 2020-05-15 07:06:45.626 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I: 2020-05-15 07:06:45.626 This software is for use on amateur radio networks only, I: 2020-05-15 07:06:45.626 it is to be used for educational purposes only. Its use on I: 2020-05-15 07:06:45.626 commercial networks is strictly prohibited. I: 2020-05-15 07:06:45.626 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2020-05-15 07:06:45.626 MMDVM_Bridge-20191105_V1.4.1 is starting M: 2020-05-15 07:06:45.626 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac) I: 2020-05-15 07:06:45.626 General Parameters I: 2020-05-15 07:06:45.626 Callsign: N6DOZ I: 2020-05-15 07:06:45.626 Id: 315069220 I: 2020-05-15 07:06:45.626 DMR: enabled I: 2020-05-15 07:06:45.626 Display Parameters I: 2020-05-15 07:06:45.626 Type: I: 2020-05-15 07:06:45.626 DMR Network Parameters I: 2020-05-15 07:06:45.626 Address: 3103.repeater.net I: 2020-05-15 07:06:45.626 Port: 62031 I: 2020-05-15 07:06:45.626 Local: 62044 I: 2020-05-15 07:06:45.626 Slot 1: disabled I: 2020-05-15 07:06:45.626 Slot 2: enabled I: 2020-05-15 07:06:45.628 Info Parameters I: 2020-05-15 07:06:45.628 Callsign: N6DOZ I: 2020-05-15 07:06:45.807 DMR RF Parameters I: 2020-05-15 07:06:45.807 Id: 315069220 I: 2020-05-15 07:06:45.807 Color Code: 1 M: 2020-05-15 07:06:45.807 DMR, Opening INI file: DVSwitch.ini M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] Address -> 127.0.0.1 M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] TXPort -> 32103 M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] RXPort -> 32100 M: 2020-05-15 07:06:45.808 DMR, Setting [DMR] Slot -> 1 M: 2020-05-15 07:06:45.808 DMR, Transmitting on 127.0.0.1:32103 and listening on port 32100. Result = 1 M: 2020-05-15 07:06:45.808 MMDVM_Bridge-20191105_V1.4.1 is running I: 2020-05-15 07:06:45.808 Started the DMR Id lookup reload thread M: 2020-05-15 07:06:55.827 DMR, Logged into the master successfully M: 2020-05-15 07:07:08.461 DMR, TX state = ON I: 2020-05-15 07:07:08.461 DMR, Begin TX: src=3150692 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:07:08.466 DMR, TX state = OFF, DMR frame count was 2 frames M: 2020-05-15 07:12:26.479 DMR Slot 2, received network voice header from N6DOZ to TG 311620 M: 2020-05-15 07:12:27.074 DMR Talker Alias (Data Format 1, Received 6/10 char): 'N6DOZ ' M: 2020-05-15 07:12:27.797 DMR Talker Alias (Data Format 1, Received 10/10 char): 'N6DOZ Rudy' M: 2020-05-15 07:12:30.077 DMR Slot 2, received network end of voice transmission, 3.7 seconds, 0% packet loss, BER: 0.0% M: 2020-05-15 07:12:33.744 DMR, TX state = ON I: 2020-05-15 07:12:33.744 DMR, Begin TX: src=3135404 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:12:37.402 DMR, TX state = OFF, DMR frame count was 64 frames M: 2020-05-15 07:12:46.744 DMR, TX state = ON I: 2020-05-15 07:12:46.744 DMR, Begin TX: src=3135404 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:12:49.231 DMR, TX state = OFF, DMR frame count was 45 frames M: 2020-05-15 07:16:53.065 DMR, TX state = ON I: 2020-05-15 07:16:53.065 DMR, Begin TX: src=3150692 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:16:53.070 DMR, TX state = OFF, DMR frame count was 2 frames M: 2020-05-15 07:18:24.956 Closing the MMDVM I: 2020-05-15 07:18:25.862 Stopped the DMR Id lookup reload thread M: 2020-05-15 07:18:25.863 DMR, Closing DMR Network I: 2020-05-15 07:18:25.863 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGINT
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Steve N4IRS #6521 I stripped these down to the important parts: I bolded the important lines. In short: Both instances of MB are transmitting on 32103 Both instances of MB are receiving on 32100 OR You sent the same log twice Look at the time stamps of each "log" MB_XLX I: 2020-05-15 07:06:45.626 MMDVM_Bridge: M: 2020-05-15 07:06:45.626 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac) I: 2020-05-15 07:06:45.626 General Parameters I: 2020-05-15 07:06:45.626 Callsign: N6DOZ I: 2020-05-15 07:06:45.626 Id: 315069220 I: 2020-05-15 07:06:45.626 DMR: enabled I: 2020-05-15 07:06:45.626 DMR Network Parameters I: 2020-05-15 07:06:45.626 Address: 3103.repeater.net I: 2020-05-15 07:06:45.626 Port: 62031 I: 2020-05-15 07:06:45.626 Local: 62044 I: 2020-05-15 07:06:45.626 Slot 1: disabled I: 2020-05-15 07:06:45.626 Slot 2: enabled I: 2020-05-15 07:06:45.628 Callsign: N6DOZ M: 2020-05-15 07:06:45.629 DMR, Opening DMR Network I: 2020-05-15 07:06:45.807 DMR RF Parameters I: 2020-05-15 07:06:45.807 Id: 315069220 I: 2020-05-15 07:06:45.807 Color Code: 1 M: 2020-05-15 07:06:45.807 DMR, Opening INI file: DVSwitch.ini M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] Address -> 127.0.0.1 M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] TXPort -> 32103 M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] RXPort -> 32100 M: 2020-05-15 07:06:45.808 DMR, Setting [DMR] Slot -> 1 M: 2020-05-15 07:06:45.808 DMR, Transmitting on 127.0.0.1:32103 and listening on port 32100. Result = 1 M: 2020-05-15 07:06:45.808 MMDVM_Bridge-20191105_V1.4.1 is running M: 2020-05-15 07:06:55.827 DMR, Logged into the master successfully M: 2020-05-15 07:07:08.461 DMR, TX state = ON I: 2020-05-15 07:07:08.461 DMR, Begin TX: src=3150692 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:07:08.466 DMR, TX state = OFF, DMR frame count was 2 frames M: 2020-05-15 07:12:26.479 DMR Slot 2, received network voice header from N6DOZ to TG 311620 M: 2020-05-15 07:12:27.074 DMR Talker Alias (Data Format 1, Received 6/10 char): 'N6DOZ ' M: 2020-05-15 07:12:27.797 DMR Talker Alias (Data Format 1, Received 10/10 char): 'N6DOZ Rudy' M: 2020-05-15 07:12:30.077 DMR Slot 2, received network end of voice transmission, 3.7 seconds, 0% packet loss, BER: 0.0% M: 2020-05-15 07:12:33.744 DMR, TX state = ON I: 2020-05-15 07:12:33.744 DMR, Begin TX: src=3135404 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:12:37.402 DMR, TX state = OFF, DMR frame count was 64 frames M: 2020-05-15 07:12:46.744 DMR, TX state = ON I: 2020-05-15 07:12:46.744 DMR, Begin TX: src=3135404 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:12:49.231 DMR, TX state = OFF, DMR frame count was 45 frames M: 2020-05-15 07:16:53.065 DMR, TX state = ON I: 2020-05-15 07:16:53.065 DMR, Begin TX: src=3150692 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:16:53.070 DMR, TX state = OFF, DMR frame count was 2 frames M: 2020-05-15 07:18:24.956 Closing the MMDVM I: 2020-05-15 07:18:25.862 Stopped the DMR Id lookup reload thread M: 2020-05-15 07:18:25.863 DMR, Closing DMR Network I: 2020-05-15 07:18:25.863 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGINT ################################################################################# MB_BM I: 2020-05-15 07:06:45.626 MMDVM_Bridge: M: 2020-05-15 07:06:45.626 MMDVM_Bridge-20191105_V1.4.1 is starting M: 2020-05-15 07:06:45.626 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac) I: 2020-05-15 07:06:45.626 General Parameters I: 2020-05-15 07:06:45.626 Callsign: N6DOZ I: 2020-05-15 07:06:45.626 Id: 315069220 I: 2020-05-15 07:06:45.626 DMR: enabled I: 2020-05-15 07:06:45.626 DMR Network Parameters I: 2020-05-15 07:06:45.626 Address: 3103.repeater.net I: 2020-05-15 07:06:45.626 Port: 62031 I: 2020-05-15 07:06:45.626 Local: 62044 I: 2020-05-15 07:06:45.626 Slot 1: disabled I: 2020-05-15 07:06:45.626 Slot 2: enabled I: 2020-05-15 07:06:45.628 Info Parameters I: 2020-05-15 07:06:45.628 Callsign: N6DOZ M: 2020-05-15 07:06:45.629 DMR, Opening DMR Network I: 2020-05-15 07:06:45.807 DMR RF Parameters I: 2020-05-15 07:06:45.807 Id: 315069220 I: 2020-05-15 07:06:45.807 Color Code: 1 M: 2020-05-15 07:06:45.807 DMR, Opening INI file: DVSwitch.ini M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] Address -> 127.0.0.1 M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] TXPort -> 32103 M: 2020-05-15 07:06:45.807 DMR, Setting [DMR] RXPort -> 32100 M: 2020-05-15 07:06:45.808 DMR, Setting [DMR] Slot -> 1 M: 2020-05-15 07:06:45.808 DMR, Transmitting on 127.0.0.1:32103 and listening on port 32100. Result = 1 M: 2020-05-15 07:06:45.808 MMDVM_Bridge-20191105_V1.4.1 is running M: 2020-05-15 07:06:55.827 DMR, Logged into the master successfully M: 2020-05-15 07:07:08.461 DMR, TX state = ON I: 2020-05-15 07:07:08.461 DMR, Begin TX: src=3150692 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:07:08.466 DMR, TX state = OFF, DMR frame count was 2 frames M: 2020-05-15 07:12:26.479 DMR Slot 2, received network voice header from N6DOZ to TG 311620 M: 2020-05-15 07:12:27.074 DMR Talker Alias (Data Format 1, Received 6/10 char): 'N6DOZ ' M: 2020-05-15 07:12:27.797 DMR Talker Alias (Data Format 1, Received 10/10 char): 'N6DOZ Rudy' M: 2020-05-15 07:12:30.077 DMR Slot 2, received network end of voice transmission, 3.7 seconds, 0% packet loss, BER: 0.0% M: 2020-05-15 07:12:33.744 DMR, TX state = ON I: 2020-05-15 07:12:33.744 DMR, Begin TX: src=3135404 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:12:37.402 DMR, TX state = OFF, DMR frame count was 64 frames M: 2020-05-15 07:12:46.744 DMR, TX state = ON I: 2020-05-15 07:12:46.744 DMR, Begin TX: src=3135404 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:12:49.231 DMR, TX state = OFF, DMR frame count was 45 frames M: 2020-05-15 07:16:53.065 DMR, TX state = ON I: 2020-05-15 07:16:53.065 DMR, Begin TX: src=3150692 rpt=0 dst=9 slot=1 cc=0 metadata=N6DOZ M: 2020-05-15 07:16:53.070 DMR, TX state = OFF, DMR frame count was 2 frames M: 2020-05-15 07:18:24.956 Closing the MMDVM I: 2020-05-15 07:18:25.862 Stopped the DMR Id lookup reload thread M: 2020-05-15 07:18:25.863 DMR, Closing DMR Network I: 2020-05-15 07:18:25.863 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGINT
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Mike Zingman - N4IRR #6520 That sucks. I will add an export talkgroup in the future so you no longer need to run through dmrgateway just to adjust the destination.
More All Messages By This Member
Re: Bridging XLX to BM DMR (New Way 2020) #mmdvm_bridge Rudy N6DOZ #6519 Ernie, So do you have your setup like this? BM <-> DMRGateway <-> MB <-> MB <-> XLX? I'll have to play with that setup. Thanks for the tip. 7-3
More All Messages By This Member

3521 - 3540 of 9882

Home Hashtags Subgroups Wiki About Features Pricing Updates Terms Help Twitter