Date   

Re: MMDVM_Bridge connection to XLX

Jon 2E0OPT
 

Eric you sir are a star. I knew something wasn't quite right but couldn't put my finger on it. 


Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

IK7VXC Mike
 

Thank you


Re: DMR -> FCS Reflectors

Keith Mitchell
 

Any answer to this . What ports should I use.I have the same problem


Re: MMDVM_Bridge connection to XLX

Eric-K6KWB
 

Jon

On Tue, Feb 2, 2021 at 02:34 AM, Jon 2E0OPT wrote:
[DMR Network]
Enable=1
Address=127.0.0.1  >>>>>>> make sure you place IP of your XLX or DNS
Port=62030
Jitter=360
Local=62041
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=XLX:4002
Slot1=0
Slot2=1
Debug=1
73, Eric


MMDVM_Bridge connection to XLX

Jon 2E0OPT
 

Hey All.

I've been trying to connect MMDVM_Bridge to my own instance of XLX I believe I have set it up correctly following the various posts I can find on this group but when I start MMDVM_Bridge with ./MMDVM_Bridge MMDVM_Bridge.ini I get the following:

 I: 2021-02-02 09:22:44.660 MMDVM_Bridge:
I: 2021-02-02 09:22:44.661 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD.
I: 2021-02-02 09:22:44.661 Hacks by Mike N4IRR and Steve N4IRS
I: 2021-02-02 09:22:44.661 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2021-02-02 09:22:44.661 This software is for use on amateur radio networks only,
I: 2021-02-02 09:22:44.661 it is to be used for educational purposes only. Its use on
I: 2021-02-02 09:22:44.661 commercial networks is strictly prohibited.
I: 2021-02-02 09:22:44.661 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2021-02-02 09:22:44.661 MMDVM_Bridge-20201129_V1.6.2 is starting
M: 2021-02-02 09:22:44.661 Built 08:55:21 Dec  1 2020 (GitID #89f8998)
I: 2021-02-02 09:22:44.661 General Parameters
I: 2021-02-02 09:22:44.662     Callsign: M7KMW
I: 2021-02-02 09:22:44.662     Id: 2345247
I: 2021-02-02 09:22:44.662     Duplex: no
I: 2021-02-02 09:22:44.662     Timeout: 180s
I: 2021-02-02 09:22:44.662     D-Star: disabled
I: 2021-02-02 09:22:44.662     DMR: enabled
I: 2021-02-02 09:22:44.662     YSF: disabled
I: 2021-02-02 09:22:44.662     P25: disabled
I: 2021-02-02 09:22:44.662     NXDN: disabled
I: 2021-02-02 09:22:44.662 Modem Parameters
I: 2021-02-02 09:22:44.663     Port: /dev/null
I: 2021-02-02 09:22:44.663     RX Invert: no
I: 2021-02-02 09:22:44.663     TX Invert: no
I: 2021-02-02 09:22:44.663     PTT Invert: no
I: 2021-02-02 09:22:44.663     TX Delay: 100ms
I: 2021-02-02 09:22:44.663     RX Offset: 0Hz
I: 2021-02-02 09:22:44.663     TX Offset: 0Hz
I: 2021-02-02 09:22:44.663     RX DC Offset: 0
I: 2021-02-02 09:22:44.663     TX DC Offset: 0
I: 2021-02-02 09:22:44.663     RF Level: 100.0%
I: 2021-02-02 09:22:44.663     DMR Delay: 0 (0.0ms)
I: 2021-02-02 09:22:44.663     RX Level: 50.0%
I: 2021-02-02 09:22:44.664     CW Id TX Level: 50.0%
I: 2021-02-02 09:22:44.664     D-Star TX Level: 50.0%
I: 2021-02-02 09:22:44.664     DMR TX Level: 50.0%
I: 2021-02-02 09:22:44.664     YSF TX Level: 50.0%
I: 2021-02-02 09:22:44.664     P25 TX Level: 50.0%
I: 2021-02-02 09:22:44.664     NXDN TX Level: 50.0%
I: 2021-02-02 09:22:44.664     RX Frequency: 222340000Hz (222340000Hz)
I: 2021-02-02 09:22:44.664     TX Frequency: 224940000Hz (224940000Hz)
M: 2021-02-02 09:22:44.664 Opening the MMDVM
I: 2021-02-02 09:22:44.665 Display Parameters
I: 2021-02-02 09:22:44.665     Type:
I: 2021-02-02 09:22:44.665 DMR Network Parameters
I: 2021-02-02 09:22:44.665     Address: 127.0.0.1
I: 2021-02-02 09:22:44.665     Port: 62030
I: 2021-02-02 09:22:44.665     Local: 62041
I: 2021-02-02 09:22:44.665     Jitter: 360ms
I: 2021-02-02 09:22:44.665     Slot 1: disabled
I: 2021-02-02 09:22:44.665     Slot 2: enabled
I: 2021-02-02 09:22:44.665     Mode Hang: 3s
I: 2021-02-02 09:22:44.665     Options: XLX:4002
I: 2021-02-02 09:22:44.666 Info Parameters
I: 2021-02-02 09:22:44.666     Callsign: M7KMW
I: 2021-02-02 09:22:44.666     RX Frequency: 222340000Hz
I: 2021-02-02 09:22:44.666     TX Frequency: 224940000Hz
I: 2021-02-02 09:22:44.666     Power: 1W
I: 2021-02-02 09:22:44.666     Latitude: 41.733299deg N
I: 2021-02-02 09:22:44.666     Longitude: -50.399899deg E
I: 2021-02-02 09:22:44.666     Height: 0m
I: 2021-02-02 09:22:44.666     Location: "Iceberg, North Atlantic"
I: 2021-02-02 09:22:44.666     Description: "MMDVM_Bridge"
I: 2021-02-02 09:22:44.666     URL: "https://groups.io/g/DVSwitch"
M: 2021-02-02 09:22:44.667 DMR, Opening DMR Network
I: 2021-02-02 09:22:44.667 RSSI
I: 2021-02-02 09:22:44.667     Mapping File: RSSI.dat
W: 2021-02-02 09:22:44.667 Cannot open the RSSI data file - RSSI.dat
I: 2021-02-02 09:22:44.667 DMR Id Lookups
I: 2021-02-02 09:22:44.667     File: /var/lib/mmdvm/DMRIds.dat
I: 2021-02-02 09:22:44.667     Reload: 24 hours
I: 2021-02-02 09:22:44.864 Loaded 186564 Ids to the DMR callsign lookup table
I: 2021-02-02 09:22:44.864 DMR RF Parameters
I: 2021-02-02 09:22:44.864     Id: 2345247
I: 2021-02-02 09:22:44.864     Color Code: 1
I: 2021-02-02 09:22:44.864     Self Only: no
I: 2021-02-02 09:22:44.864     Embedded LC Only: yes
I: 2021-02-02 09:22:44.865     Dump Talker Alias Data: no
I: 2021-02-02 09:22:44.865     Prefixes: 0
I: 2021-02-02 09:22:44.865     Call Hang: 3s
I: 2021-02-02 09:22:44.865     TX Hang: 3s
I: 2021-02-02 09:22:44.865     Mode Hang: 10s
M: 2021-02-02 09:22:44.865 DMR, Opening INI file: DVSwitch.ini
M: 2021-02-02 09:22:44.865 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2021-02-02 09:22:44.865 DMR, Setting [DMR] TXPort -> 31103
M: 2021-02-02 09:22:44.865 DMR, Setting [DMR] RXPort -> 31100
M: 2021-02-02 09:22:44.865 DMR, Setting [DMR] Slot -> 2
M: 2021-02-02 09:22:44.866 DMR, Transmitting on 127.0.0.1:31103, and listening on port 31100.  Result = 1
M: 2021-02-02 09:22:44.866 MMDVM_Bridge-20201129_V1.6.2 is running
I: 2021-02-02 09:22:44.866 Started the DMR Id lookup reload thread
E: 2021-02-02 09:23:54.872 DMR, Connection to the master has timed out, retrying connection
M: 2021-02-02 09:23:54.872 DMR, Closing DMR Network
M: 2021-02-02 09:23:54.872 DMR, Opening DMR Network

MMDVM_Bridge shows no sign of being connected to anything that I can see on the XLX side of things and I've run out of things to try

E: 2021-02-02 09:23:54.872 DMR, Connection to the master has timed out, retrying connection
M: 2021-02-02 09:23:54.872 DMR, Closing DMR Network
M: 2021-02-02 09:23:54.872 DMR, Opening DMR Network

This leads me to belive there is something wrong with the either XLX or MMDVM_Bridge but considering how little there is to edit on the XLX side this is either a problem with MMDVM_Bridge itself or something wrong with the guides/advice I've followed. If anyone could help I'd be truly greatful as it all seems right to my eyes

My MMDVM_Bridge.ini:
[General]
Callsign=**** redacted
Id=**** redacted
Timeout=180
Duplex=0
 
[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Iceberg, North Atlantic
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch
 
[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
 
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24
 
[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0
 
[D-Star]
Enable=0
Module=C
 
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
 
[System Fusion]
Enable=0
 
[P25]
Enable=0
NAC=293
 
[NXDN]
Enable=0
RAN=1

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0
 
[DMR Network]
Enable=1
Address=127.0.0.1
Port=62030
Jitter=360
Local=62041
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=XLX:4002
Slot1=0
Slot2=1
Debug=1
 
[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
Debug=0
[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0
 
[NXDN Network]
Enable=0
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

Steve N4IRS
 

You are running older versions of software. 

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of IK7VXC Mike <gammaproject@...>
Sent: Tuesday, February 2, 2021 3:31:32 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x
 
Well in this case have you checked out the 2 links of my first reply? The answer should be here: https://ibb.co/bmdYyLK

and it says:

pi@....0>opt/AB-SECUNDARIOS/IK7VXC65/dvswitch.sh version all
dvswitch.sh 1.5.9
Analog_Bridge version 1.5.9
MMDVM_Bridge version 20200727_v1.5.9 git #1eb5de7
pi@....0>

Mike


Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

IK7VXC Mike
 

Well in this case have you checked out the 2 links of my first reply? The answer should be here: https://ibb.co/bmdYyLK

and it says:

pi@....0>opt/AB-SECUNDARIOS/IK7VXC65/dvswitch.sh version all
dvswitch.sh 1.5.9
Analog_Bridge version 1.5.9
MMDVM_Bridge version 20200727_v1.5.9 git #1eb5de7
pi@....0>

Mike


Re: Best Route - TG31550 to XLX273 - limited knowledge

Corey Dean N3FE
 

Neil,

You should only bridge into talkgroups that are yours to bridge with or have permission to.  Tacs, statewides, 3100 are all dmr only. 

It is not my policy. It is an agreement with the cbridge owners that I tend to stand by.  

Don’t like it there are other networks you can use as you are well aware.   Everyone has their own talkgroups they can do with as they wish.  

I wonder how the Motorola dmr group would like it if you just got on Their network and started bridging anything under the sun?


On Feb 1, 2021, at 3:05 PM, Neil k8it <k8it@...> wrote:


This is the reason why I do not use BM  anymore. Not sure if this is BM  policy or if it is K3FE  policy. I never saw such a policy on the BM  website.
 
 
Thanks
73 Neil Sablatzky  K8IT
 
 
 

Sent: Monday, February 01, 2021 2:15 PM
Subject: Re: [DVSwitch] Best Route - TG31550 to XLX273 - limited knowledge

Why are you connecting all of that to the Wisconsin TAC channel?  PLEASE do not do this!  That is NOT your talkgroup and is a bm talkgroup.  If you want to interconnect things please use your own talkgroup! 

Corey  N3FE

 


On 2021-02-01 06:37, craig.jump via groups.io wrote:

Greg,  how long did it take to get the BM interconnect ?



AVG logo

This email has been checked for viruses by AVG antivirus software.
www.avg.com



Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

Steve N4IRS
 

DVSwitch Mobile connects to a server.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of IK7VXC Mike <gammaproject@...>
Sent: Monday, February 1, 2021 5:43:03 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x
 
Sorry Steve, I only run DVSwitch mobile on my smartphone. And I couldn't seem to find the /opt directory. Please excuse my inexperience.


Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

IK7VXC Mike
 

Sorry Steve, I only run DVSwitch mobile on my smartphone. And I couldn't seem to find the /opt directory. Please excuse my inexperience.


Re: Best Route - TG31550 to XLX273 - limited knowledge

Neil k8it
 

This is the reason why I do not use BM  anymore. Not sure if this is BM  policy or if it is K3FE  policy. I never saw such a policy on the BM  website.
 
 
Thanks
73 Neil Sablatzky  K8IT
 
 
 

Sent: Monday, February 01, 2021 2:15 PM
Subject: Re: [DVSwitch] Best Route - TG31550 to XLX273 - limited knowledge

Why are you connecting all of that to the Wisconsin TAC channel?  PLEASE do not do this!  That is NOT your talkgroup and is a bm talkgroup.  If you want to interconnect things please use your own talkgroup! 

Corey  N3FE

 


On 2021-02-01 06:37, craig.jump via groups.io wrote:

Greg,  how long did it take to get the BM interconnect ?



AVG logo

This email has been checked for viruses by AVG antivirus software.
www.avg.com



Re: Best Route - TG31550 to XLX273 - limited knowledge

Corey Dean N3FE
 

I am going to ask you nicely to please disconnect all of those links you have to the 31550 Wisconsin TAC talkgroup now.

Corey  N3FE

 


On 2021-02-01 06:37, craig.jump via groups.io wrote:

Greg,  how long did it take to get the BM interconnect ?


Re: Best Route - TG31550 to XLX273 - limited knowledge

Corey Dean N3FE
 

Why are you connecting all of that to the Wisconsin TAC channel?  PLEASE do not do this!  That is NOT your talkgroup and is a bm talkgroup.  If you want to interconnect things please use your own talkgroup! 

Corey  N3FE

 


On 2021-02-01 06:37, craig.jump via groups.io wrote:

Greg,  how long did it take to get the BM interconnect ?


Re: Need help please have issues with connecting to 1999

Vince Pimentel
 

Hey Gents,
Just wanted to follow up and let you know that I was able to rework my system to use my node number with a 1 at the beginning for the private node to make it unique and tested it this weekend. Solved!

Thank you for the time, effort and support that you provide.


Re: Best Route - TG31550 to XLX273 - limited knowledge

craig.jump@...
 

Greg,  how long did it take to get the BM interconnect ?


Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

Steve N4IRS
 

I need the text output from your computer running DVSwitch.
Please show the output of /opt/MMDVM_Bridge/dvswitch.sh version all


On 2/1/21 6:06 AM, IK7VXC Mike wrote:
Thanks Steve for your prompt reply. I'm attaching the screenshots that my friend - who runs the server - sent me. I must specify that he uses dvlink (so I don't know if that is a game changer).

https://ibb.co/1dMXmxZ
https://ibb.co/bmdYyLK


Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

IK7VXC Mike
 
Edited

Thanks Steve for your prompt reply. I'm attaching the screenshots that my friend - who runs the server - sent me. I must specify that he uses dvlink (so I don't know if that is a game changer).

https://ibb.co/1dMXmxZ

https://ibb.co/bmdYyLK


Re: DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

Steve N4IRS
 

Please show the output of:
/opt/MMDVM_Bridge/dvswitch.sh version all

On 1/30/21 4:36 AM, IK7VXC Mike wrote:
Hi guys. This is an issue I ran across while having a QSO in the Italian "Room Italy" (IT-YSFROOM-ITALY). Some hams (on C4FM) hear me just fine (and with excellent audio as well), while others (on Wires-x) claim they hear nothing.
Someone pointed out that transmissions through DVSwitch are not allowed on the Wires-x platform (which to me it's really unfair!). And that's probably a matter of RADIO ID missing or something. Is this true?
Isn't there anything that can be implemented to solve this issue?

Thank you


Re: Best Route - TG31550 to XLX273 - limited knowledge

Daren. 2E0LXY.
 

Hi Greg. 
As Jeff said, by far easiest way is let BM do it. 
Raise ticket here, you'll need to create a separate account to log in.

https://support.brandmeister.network/servicedesk/customer/user/login?destination=portals

Select the correct dept on the ticket. 
Tell them why you want to to do it, your details and they don't use Interlink, it's connected to the xlxd reflector as a peer that they setup. Job done.

I did it only a while ago and got the message back last week it was complete. 
XLX899B to BM TG23530 "Yorkshire" 

Good luck with it. 
Daren 2E0LXY 


Re: Allstar <--> DMR & DVSWITCH Was working... #brandmeister #mmdvm_bridge #analog_bridge

Brent Harding
 

I wonder if they have finally cracked down on all the non-RF modes of getting on? I got a similar issue, but I’ve found it to only happen on group 3100. What happens is that you might get the first transmission, if you are lucky enough to tune in on one, but then they will stop sending traffic to you. Some others on another system I frequent were talking about this the other night. I can still get group 91, Quadnet 31012, or most anything else I’ve tried without issues. If there is something like this going on, how do they identify DVSwitch as opposed to a Pistar or Openspot, or even Dudestar for that matter? Is there a user agent string similar to what our browsers use that MMDVM_Bridge would send to any master we connect to? I suppose losing one talk group stinks, but if they roll this new thing network wide, that will be a hard one.

 

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Mark Simon via groups.io
Sent: Saturday, January 30, 2021 2:14 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Allstar <--> DMR & DVSWITCH Was working... #brandmeister #mmdvm_bridge #analog_bridge

 

You can check if your node is connecting to Brandmeister by logging on to the Brandmeister.network  home page.  Entering your logon/password (BM password not Hotspot password) and clicking on My Hotspots in the left margin.  I saw that my DMR/Allstarlink/DVSwitch was not connecting and figured out that the hotspot that I use in my home network and DVSwitch were set for the same server.  I changed the hotspot (Zumspot) and it started working again.  One BM server per network makes sense.  Just FYI....     Mark 

1561 - 1580 of 9925