toggle quoted messageShow quoted text
If you have two instances running you have to change one of the local ports. Change 62032 to 62033. To test I always run In a terminal. Not as a service. Switch debug=1 then start up one get it going . Stop the working one then start the other and get it working.
Fire up both once you have inverted the ports in the DVSwitch.ini.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Patrick Perdue <patrick@...>
Sent: Sunday, December 1, 2019 9:57:10 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Brandmeister to XLX
This is XLX679 module A.
FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is.
I have two instances of MMDVM_Bridge running -- one connected to Brandmeister, the other to my XLX reflector. Ports are inverted on the second instance of DVSwitch.ini.
Transmissions from Brandmeister make it to the reflector, but outbound from the module doesn't go back to the Brandmeister talkgroup. Do I need to use DMRGateway for talkgroup rewriting in this case?
On 12/1/2019 4:20 AM, Ernie Gm7kbk wrote:
What xlx are you trying to get into. As I set my odroid n2 to do the very same the other day. Just to check if the ports are open.
Right. I wasn't referring directly to the INI file at the time.
My machine is on a VPS, so the IP of ETH0 is a public IP address.
So, it looks like this.
I've tried moving the local port as well.
In DVSwitch.ini, I have differentiated the RXPort and TXPort from my existing DMR to Allstar setup.
Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export)
TXPort = 31200 ; Port to send AMBE TLV frames to (export)
RXPort = 31203 ; Port to listen on (import)
Slot = 2 ; Export slot
On 12/1/2019 3:56 AM, Ernie Gm7kbk wrote:
No that's the port
My address looks like 192.168.1.66 this is the private network ipv4.
Xlx looks at the port of 62030 and the ipv4 address of the device. Or you can put in the external ipv4 address or web address.
Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to?
If so, then the reflector isn't doing much with that, and this is probably not a DVSwitch issue.
On 11/30/2019 5:22 PM, Steve N4IRS wrote:
The network address should point at the xlx reflector
Sent by smoke signal (AT&T)
That was actually the first configuration I tried. Same result either with the Interface IP address, or local loopback. I’ll mess with it some more later. The MMDVM_Bridge part looks easy enough once I can get it talking to XLXD.
Use the ip address of the machine not 127.0.0.1
I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before, but that was a while ago.
The relevant part of MMDVM_Bridge.ini looks like this:
Small part of the MMDVM_Bridge log:
E: 2019-11-30 21:34:28.884 DMR, Connection to the master has timed out, retrying connection
tcpdump shows active connections on UDP 62030, so XLXD should be accepting the connection from MMDVM_Bridge on that port.
On 11/30/2019 4:20 PM, Ernie Gm7kbk wrote:
latest version of MMDVM_bridge works with no problems. Use the options XLX:4005 this being the module you want to connect to. 4001 for A 4002 for B etc. latest version is here https://github.com/DVSwitch/MMDVM_Bridge