Date   

Re: ircddbgateway install command line only

TG9AOR
 

Hello. If you compiled from DL5DI's repository it is then possible to run without GUI by running the command ./ircddbgatewayd

You will need to configure it beforehand, this is done by running ./ircddbgw_config or ./ircddbgw_cfg (if my memory serves me right) this allows for you to configure it via the terminal.


Hope this helps. 73
--
José Roberto Ruíz García Salas
TG9AOR


Re: ircddbgateway install command line only

Mike KB8JNM
 

I missed the original issue by not seeing enough of the email for some reason.

I could not get mine installed for the lack of ability to install wxwidgets.
Seems like a massive install requirement for a little install.
Not sure why, but wxwidgets will not compile for me so I put it aside.


Re: ircddbgateway install command line only

Steve N4IRS
 

Skyler,
Here is template you can use
<http://dvswitch.org/files/HAM/ircddbgateway>

Depending on the parameters ircddbgatewayd will look in /etc/opendv.
Be aware G4KLX has been updating his own github directory for ircDDBGateway.

73, Steve N4IRS

On 2/3/19 1:15 PM, Skyler Fennell wrote:
I am currently in the process of ASL <--> DSTAR.

I've been pulling my hair out this weekend attempting to install ircDDBGateway as part of the bridge. I have no GUI available on my server, and don't want to run the extra resources to put a desktop environment on it.

I have grabbed the source code from the following github link:

I then used these instructions to compile:

Including the configure without using GUI followed by make and make install.
./configure --without-gui
make
make install

After this, I have performed a deep search on the system attempting to find the config files and what to run, however, I am unable to find anything except programs complaining that I need to have a display.

root@stn3764:/# /usr/local/bin/ircddbgatewayconfig
11:13:09: Error: Unable to initialize GTK+, is DISPLAY set properly?

I have searched the whole system for any plain text file with the keywords ircddbgateway that looks like a config file, but have not found anything.

Does anybody here have any suggestions on running ircddbgateway on a server with NO GUI?

Thank You
Skyler KG0SKY


Re: ircddbgateway install command line only

Mike KB8JNM
 

Yet one more piece of software to install.
It is found on github as well.
https://github.com/g4klx/ircDDBGateway

On 2/3/2019 1:15 PM, Skyler Fennell wrote:
I am currently in the process of ASL <--> DSTAR.
I've been pulling my hair out this weekend attempting to install
ircDDBGateway as part of the bridge. I have no GUI available on my server,
and don't want to run the extra resources to put a desktop environment on
it.
I have grabbed the source code from the following github link:
https://github.com/dl5di/OpenDV.git
I then used these instructions to compile:
https://g0wfv.wordpress.com/2016/12/02/how-to-install-ircddb-gateway-from-latest-source-code/
Including the configure without using GUI followed by make and make
install.
./configure --without-gui
make
make install
After this, I have performed a deep search on the system attempting to find
the config files and what to run, however, I am unable to find anything
except programs complaining that I need to have a display.
root@stn3764:/# /usr/local/bin/ircddbgatewayconfig
11:13:09: Error: Unable to initialize GTK+, is DISPLAY set properly?
I have searched the whole system for any plain text file with the keywords
ircddbgateway that looks like a config file, but have not found anything.
Does anybody here have any suggestions on running ircddbgateway on a server
with NO GUI?
Thank You
Skyler KG0SKY


ircddbgateway install command line only

Skyler Fennell
 

I am currently in the process of ASL <--> DSTAR.

I've been pulling my hair out this weekend attempting to install ircDDBGateway as part of the bridge. I have no GUI available on my server, and don't want to run the extra resources to put a desktop environment on it.

I have grabbed the source code from the following github link:

I then used these instructions to compile:

Including the configure without using GUI followed by make and make install.
./configure --without-gui
make
make install

After this, I have performed a deep search on the system attempting to find the config files and what to run, however, I am unable to find anything except programs complaining that I need to have a display.

root@stn3764:/# /usr/local/bin/ircddbgatewayconfig
11:13:09: Error: Unable to initialize GTK+, is DISPLAY set properly?

I have searched the whole system for any plain text file with the keywords ircddbgateway that looks like a config file, but have not found anything.

Does anybody here have any suggestions on running ircddbgateway on a server with NO GUI?

Thank You
Skyler KG0SKY


Re: DStar/DMR XRF or DCS for testing

Skyler Fennell
 

Thanks Steve. I created my own private XRF.


On Sat, Feb 2, 2019 at 4:47 PM Steve N4IRS <szingman@...> wrote:
I can't speak to the XRF but use your DMR ID for the TG

On 2/2/19 6:21 PM, Skyler Fennell wrote:
I need to perform lots of tests with long transmissions. I am working on a digital mode mobile/multipath comparison experiment. I need to link some stuff together for the experiment.


What is a good DCS/XRF reflector # I can use that will not be bothered by me talking for a while.
What is a good Brandmeister Talkgroup # that I can use that will not be bothered by me talking for a while.


Thank You,
Skyler


Re: one way audio - time out

Mike KB8JNM
 

Going to take a guess that one instance is running in the foreground and one in the background.
I don't think he is running anything more than 1 dmr bridge. Perhaps I'm wrong.

suggested to kill one by pid and recheck / reboot / recheck
see if it is reloading
???

On 2/2/2019 9:29 PM, Steve N4IRS wrote:
This seems to be a reoccurring theme...
On 2/2/19 9:24 PM, Mike KB8JNM wrote:


On 2/2/2019 9:21 PM, Kevin Halton wrote:
udp        0      0 0.0.0.0:31003           0.0.0.0:* 1531/MMDVM_Bridge
udp        0      0 0.0.0.0:31003 0.0.0.0:* 1451/./MMDVM_Bridge


Re: one way audio - time out

Steve N4IRS
 

This seems to be a reoccurring theme...

On 2/2/19 9:24 PM, Mike KB8JNM wrote:


On 2/2/2019 9:21 PM, Kevin Halton wrote:
udp        0      0 0.0.0.0:31003           0.0.0.0:* 1531/MMDVM_Bridge
udp        0      0 0.0.0.0:31003 0.0.0.0:*                           1451/./MMDVM_Bridge


Re: one way audio - time out

Mike KB8JNM
 

On 2/2/2019 9:21 PM, Kevin Halton wrote:
udp 0 0 0.0.0.0:31003 0.0.0.0:* 1531/MMDVM_Bridge
udp 0 0 0.0.0.0:31003 0.0.0.0:* 1451/./MMDVM_Bridge


Re: one way audio - time out

Steve N4IRS
 

You have 2 copies of MMDVM_Bridge running.

On 2/2/19 9:21 PM, Kevin Halton wrote:
Here is the output;


[root@Node45593 mmdvm]# ps ax | grep MM
PID TTY STAT TIME COMMAND
1341 pts/0 T 0:00 tail -f MMDVM_Bridge-2019-02-03.log
1451 pts/1 Tl 0:01 ./MMDVM_Bridge MMDVM_Bridge.ini
1531 ? Ssl 0:02 /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini
1546 pts/1 T 0:00 tail -f MMDVM_Bridge-2019-02-03.log
1557 pts/1 S+ 0:00 grep MM
[root@Node45593 mmdvm]#


[root@Node45593 mmdvm]# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:4571 0.0.0.0:* 341/asterisk
udp 0 0 192.168.1.38:53 0.0.0.0:* 296/named
udp 0 0 127.0.0.1:53 0.0.0.0:* 296/named
udp 0 0 192.168.1.38:68 0.0.0.0:* 279/systemd-network
udp 0 0 0.0.0.0:62032 0.0.0.0:* 1531/MMDVM_Bridge
udp 0 0 0.0.0.0:62032 0.0.0.0:* 1451/./MMDVM_Bridge
udp 0 0 0.0.0.0:34001 0.0.0.0:* 1524/Analog_Bridge
udp 0 0 127.0.0.1:32001 0.0.0.0:* 341/asterisk
udp 0 0 0.0.0.0:31000 0.0.0.0:* 1524/Analog_Bridge
udp 0 0 0.0.0.0:31003 0.0.0.0:* 1531/MMDVM_Bridge
udp 0 0 0.0.0.0:31003 0.0.0.0:* 1451/./MMDVM_Bridge
udp 0 0 0.0.0.0:2470 0.0.0.0:* 1517/md380-emu

-----Original Message-----
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Saturday, February 02, 2019 8:55 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] one way audio - time out

Kevin,
Maybe you have a second copy of MMDVM_Bridge running.
try ps ax | grep MM
netstat -unap will show you all of the programs listening on UDP ports.

Run both tests with MMDVM_Host shutdown.

Steve

On 2/2/19 8:50 PM, Kevin Halton wrote:
Mike,

The strange thing is that everything was working fine last night, woke up today and this is what I have! I looked at the rpt.conf, that looks fine and I have tried all the masters!!

-----Original Message-----
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Mike KB8JNM
Sent: Saturday, February 02, 2019 8:39 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] one way audio - time out

Port conflict ? Just floating ideas.

On 2/2/2019 8:36 PM, Kevin Halton wrote:
Still trying to figure it out. I changed every US master and I am timing out from all of them? Any ideas what would cause this? I am stumped!

,_._,_

Here is another snippet from the log



E: 2019-02-03 01:15:45.950 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:15:45.950 DMR, Closing DMR Network

M: 2019-02-03 01:15:45.950 DMR, Opening DMR Network

D: 2019-02-03 01:15:55.990 DMR, Sending authorisation

D: 2019-02-03 01:15:56.031 DMR, Sending configuration

M: 2019-02-03 01:15:56.067 DMR, Logged into the master successfully

E: 2019-02-03 01:17:56.116 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:17:56.116 DMR, Closing DMR Network

M: 2019-02-03 01:17:56.116 DMR, Opening DMR Network

D: 2019-02-03 01:18:06.157 DMR, Sending authorisation

D: 2019-02-03 01:18:06.193 DMR, Sending configuration

M: 2019-02-03 01:18:06.234 DMR, Logged into the master successfully

E: 2019-02-03 01:20:06.285 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:20:06.285 DMR, Closing DMR Network

M: 2019-02-03 01:20:06.286 DMR, Opening DMR Network

D: 2019-02-03 01:20:16.324 DMR, Sending authorisation

D: 2019-02-03 01:20:16.365 DMR, Sending configuration

M: 2019-02-03 01:20:16.400 DMR, Logged into the master successfully

E: 2019-02-03 01:22:16.444 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:22:16.444 DMR, Closing DMR Network

M: 2019-02-03 01:22:16.444 DMR, Opening DMR Network

D: 2019-02-03 01:22:26.492 DMR, Sending authorisation

D: 2019-02-03 01:22:26.533 DMR, Sending configuration

M: 2019-02-03 01:22:26.569 DMR, Logged into the master successfully

E: 2019-02-03 01:24:26.626 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:24:26.627 DMR, Closing DMR Network

M: 2019-02-03 01:24:26.627 DMR, Opening DMR Network

D: 2019-02-03 01:24:36.670 DMR, Sending authorisation

D: 2019-02-03 01:24:36.711 DMR, Sending configuration

M: 2019-02-03 01:24:36.747 DMR, Logged into the master successfully

M: 2019-02-03 01:25:17.492 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-03 01:25:17.998 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-03 01:25:18.402 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 0% packet loss, BER: 0.0%

E: 2019-02-03 01:26:36.807 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:26:36.807 DMR, Closing DMR Network

M: 2019-02-03 01:26:36.807 DMR, Opening DMR Network

D: 2019-02-03 01:26:46.844 DMR, Sending authorisation

D: 2019-02-03 01:26:46.880 DMR, Sending configuration

M: 2019-02-03 01:26:46.916 DMR, Logged into the master successfully

M: 2019-02-03 01:27:58.746 DMR, TX state = ON

I: 2019-02-03 01:27:58.746 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-03 01:28:01.758 DMR, TX state = OFF, DMR frame count was 53 frames

E: 2019-02-03 01:28:46.971 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:28:46.971 DMR, Closing DMR Network

M: 2019-02-03 01:28:46.971 DMR, Opening DMR Network

D: 2019-02-03 01:28:57.009 DMR, Sending authorisation

D: 2019-02-03 01:28:57.045 DMR, Sending configuration

M: 2019-02-03 01:28:57.091 DMR, Logged into the master successfully

E: 2019-02-03 01:30:57.143 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:30:57.143 DMR, Closing DMR Network

M: 2019-02-03 01:30:57.143 DMR, Opening DMR Network

D: 2019-02-03 01:31:07.181 DMR, Sending authorisation

D: 2019-02-03 01:31:07.217 DMR, Sending configuration

M: 2019-02-03 01:31:07.252 DMR, Logged into the master successfully

E: 2019-02-03 01:33:07.307 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:33:07.307 DMR, Closing DMR Network

M: 2019-02-03 01:33:07.308 DMR, Opening DMR Network

D: 2019-02-03 01:33:17.344 DMR, Sending authorisation

D: 2019-02-03 01:33:17.385 DMR, Sending configuration

M: 2019-02-03 01:33:17.421 DMR, Logged into the master successfully










Re: one way audio - time out

Kevin Halton
 

Here is the output;


[root@Node45593 mmdvm]# ps ax | grep MM
PID TTY STAT TIME COMMAND
1341 pts/0 T 0:00 tail -f MMDVM_Bridge-2019-02-03.log
1451 pts/1 Tl 0:01 ./MMDVM_Bridge MMDVM_Bridge.ini
1531 ? Ssl 0:02 /opt/MMDVM_Bridge/MMDVM_Bridge /opt/MMDVM_Bridge/MMDVM_Bridge.ini
1546 pts/1 T 0:00 tail -f MMDVM_Bridge-2019-02-03.log
1557 pts/1 S+ 0:00 grep MM
[root@Node45593 mmdvm]#


[root@Node45593 mmdvm]# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:4571 0.0.0.0:* 341/asterisk
udp 0 0 192.168.1.38:53 0.0.0.0:* 296/named
udp 0 0 127.0.0.1:53 0.0.0.0:* 296/named
udp 0 0 192.168.1.38:68 0.0.0.0:* 279/systemd-network
udp 0 0 0.0.0.0:62032 0.0.0.0:* 1531/MMDVM_Bridge
udp 0 0 0.0.0.0:62032 0.0.0.0:* 1451/./MMDVM_Bridge
udp 0 0 0.0.0.0:34001 0.0.0.0:* 1524/Analog_Bridge
udp 0 0 127.0.0.1:32001 0.0.0.0:* 341/asterisk
udp 0 0 0.0.0.0:31000 0.0.0.0:* 1524/Analog_Bridge
udp 0 0 0.0.0.0:31003 0.0.0.0:* 1531/MMDVM_Bridge
udp 0 0 0.0.0.0:31003 0.0.0.0:* 1451/./MMDVM_Bridge
udp 0 0 0.0.0.0:2470 0.0.0.0:* 1517/md380-emu

-----Original Message-----
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Steve N4IRS
Sent: Saturday, February 02, 2019 8:55 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] one way audio - time out

Kevin,
Maybe you have a second copy of MMDVM_Bridge running.
try ps ax | grep MM
netstat -unap will show you all of the programs listening on UDP ports.

Run both tests with MMDVM_Host shutdown.

Steve

On 2/2/19 8:50 PM, Kevin Halton wrote:
Mike,

The strange thing is that everything was working fine last night, woke up today and this is what I have! I looked at the rpt.conf, that looks fine and I have tried all the masters!!

-----Original Message-----
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Mike KB8JNM
Sent: Saturday, February 02, 2019 8:39 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] one way audio - time out

Port conflict ? Just floating ideas.

On 2/2/2019 8:36 PM, Kevin Halton wrote:
Still trying to figure it out. I changed every US master and I am timing out from all of them? Any ideas what would cause this? I am stumped!

,_._,_

Here is another snippet from the log



E: 2019-02-03 01:15:45.950 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:15:45.950 DMR, Closing DMR Network

M: 2019-02-03 01:15:45.950 DMR, Opening DMR Network

D: 2019-02-03 01:15:55.990 DMR, Sending authorisation

D: 2019-02-03 01:15:56.031 DMR, Sending configuration

M: 2019-02-03 01:15:56.067 DMR, Logged into the master successfully

E: 2019-02-03 01:17:56.116 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:17:56.116 DMR, Closing DMR Network

M: 2019-02-03 01:17:56.116 DMR, Opening DMR Network

D: 2019-02-03 01:18:06.157 DMR, Sending authorisation

D: 2019-02-03 01:18:06.193 DMR, Sending configuration

M: 2019-02-03 01:18:06.234 DMR, Logged into the master successfully

E: 2019-02-03 01:20:06.285 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:20:06.285 DMR, Closing DMR Network

M: 2019-02-03 01:20:06.286 DMR, Opening DMR Network

D: 2019-02-03 01:20:16.324 DMR, Sending authorisation

D: 2019-02-03 01:20:16.365 DMR, Sending configuration

M: 2019-02-03 01:20:16.400 DMR, Logged into the master successfully

E: 2019-02-03 01:22:16.444 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:22:16.444 DMR, Closing DMR Network

M: 2019-02-03 01:22:16.444 DMR, Opening DMR Network

D: 2019-02-03 01:22:26.492 DMR, Sending authorisation

D: 2019-02-03 01:22:26.533 DMR, Sending configuration

M: 2019-02-03 01:22:26.569 DMR, Logged into the master successfully

E: 2019-02-03 01:24:26.626 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:24:26.627 DMR, Closing DMR Network

M: 2019-02-03 01:24:26.627 DMR, Opening DMR Network

D: 2019-02-03 01:24:36.670 DMR, Sending authorisation

D: 2019-02-03 01:24:36.711 DMR, Sending configuration

M: 2019-02-03 01:24:36.747 DMR, Logged into the master successfully

M: 2019-02-03 01:25:17.492 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-03 01:25:17.998 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-03 01:25:18.402 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 0% packet loss, BER: 0.0%

E: 2019-02-03 01:26:36.807 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:26:36.807 DMR, Closing DMR Network

M: 2019-02-03 01:26:36.807 DMR, Opening DMR Network

D: 2019-02-03 01:26:46.844 DMR, Sending authorisation

D: 2019-02-03 01:26:46.880 DMR, Sending configuration

M: 2019-02-03 01:26:46.916 DMR, Logged into the master successfully

M: 2019-02-03 01:27:58.746 DMR, TX state = ON

I: 2019-02-03 01:27:58.746 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-03 01:28:01.758 DMR, TX state = OFF, DMR frame count was 53 frames

E: 2019-02-03 01:28:46.971 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:28:46.971 DMR, Closing DMR Network

M: 2019-02-03 01:28:46.971 DMR, Opening DMR Network

D: 2019-02-03 01:28:57.009 DMR, Sending authorisation

D: 2019-02-03 01:28:57.045 DMR, Sending configuration

M: 2019-02-03 01:28:57.091 DMR, Logged into the master successfully

E: 2019-02-03 01:30:57.143 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:30:57.143 DMR, Closing DMR Network

M: 2019-02-03 01:30:57.143 DMR, Opening DMR Network

D: 2019-02-03 01:31:07.181 DMR, Sending authorisation

D: 2019-02-03 01:31:07.217 DMR, Sending configuration

M: 2019-02-03 01:31:07.252 DMR, Logged into the master successfully

E: 2019-02-03 01:33:07.307 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:33:07.307 DMR, Closing DMR Network

M: 2019-02-03 01:33:07.308 DMR, Opening DMR Network

D: 2019-02-03 01:33:17.344 DMR, Sending authorisation

D: 2019-02-03 01:33:17.385 DMR, Sending configuration

M: 2019-02-03 01:33:17.421 DMR, Logged into the master successfully








Re: one way audio - time out

Steve N4IRS
 

Kevin,
Maybe you have a second copy of MMDVM_Bridge running.
try ps ax | grep MM
netstat -unap will show you all of the programs listening on UDP ports.

Run both tests with MMDVM_Host shutdown.

Steve

On 2/2/19 8:50 PM, Kevin Halton wrote:
Mike,

The strange thing is that everything was working fine last night, woke up today and this is what I have! I looked at the rpt.conf, that looks fine and I have tried all the masters!!

-----Original Message-----
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Mike KB8JNM
Sent: Saturday, February 02, 2019 8:39 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] one way audio - time out

Port conflict ? Just floating ideas.

On 2/2/2019 8:36 PM, Kevin Halton wrote:
Still trying to figure it out. I changed every US master and I am timing out from all of them? Any ideas what would cause this? I am stumped!

,_._,_

Here is another snippet from the log


E: 2019-02-03 01:15:45.950 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:15:45.950 DMR, Closing DMR Network

M: 2019-02-03 01:15:45.950 DMR, Opening DMR Network

D: 2019-02-03 01:15:55.990 DMR, Sending authorisation

D: 2019-02-03 01:15:56.031 DMR, Sending configuration

M: 2019-02-03 01:15:56.067 DMR, Logged into the master successfully

E: 2019-02-03 01:17:56.116 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:17:56.116 DMR, Closing DMR Network

M: 2019-02-03 01:17:56.116 DMR, Opening DMR Network

D: 2019-02-03 01:18:06.157 DMR, Sending authorisation

D: 2019-02-03 01:18:06.193 DMR, Sending configuration

M: 2019-02-03 01:18:06.234 DMR, Logged into the master successfully

E: 2019-02-03 01:20:06.285 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:20:06.285 DMR, Closing DMR Network

M: 2019-02-03 01:20:06.286 DMR, Opening DMR Network

D: 2019-02-03 01:20:16.324 DMR, Sending authorisation

D: 2019-02-03 01:20:16.365 DMR, Sending configuration

M: 2019-02-03 01:20:16.400 DMR, Logged into the master successfully

E: 2019-02-03 01:22:16.444 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:22:16.444 DMR, Closing DMR Network

M: 2019-02-03 01:22:16.444 DMR, Opening DMR Network

D: 2019-02-03 01:22:26.492 DMR, Sending authorisation

D: 2019-02-03 01:22:26.533 DMR, Sending configuration

M: 2019-02-03 01:22:26.569 DMR, Logged into the master successfully

E: 2019-02-03 01:24:26.626 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:24:26.627 DMR, Closing DMR Network

M: 2019-02-03 01:24:26.627 DMR, Opening DMR Network

D: 2019-02-03 01:24:36.670 DMR, Sending authorisation

D: 2019-02-03 01:24:36.711 DMR, Sending configuration

M: 2019-02-03 01:24:36.747 DMR, Logged into the master successfully

M: 2019-02-03 01:25:17.492 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-03 01:25:17.998 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-03 01:25:18.402 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 0% packet loss, BER: 0.0%

E: 2019-02-03 01:26:36.807 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:26:36.807 DMR, Closing DMR Network

M: 2019-02-03 01:26:36.807 DMR, Opening DMR Network

D: 2019-02-03 01:26:46.844 DMR, Sending authorisation

D: 2019-02-03 01:26:46.880 DMR, Sending configuration

M: 2019-02-03 01:26:46.916 DMR, Logged into the master successfully

M: 2019-02-03 01:27:58.746 DMR, TX state = ON

I: 2019-02-03 01:27:58.746 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-03 01:28:01.758 DMR, TX state = OFF, DMR frame count was 53 frames

E: 2019-02-03 01:28:46.971 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:28:46.971 DMR, Closing DMR Network

M: 2019-02-03 01:28:46.971 DMR, Opening DMR Network

D: 2019-02-03 01:28:57.009 DMR, Sending authorisation

D: 2019-02-03 01:28:57.045 DMR, Sending configuration

M: 2019-02-03 01:28:57.091 DMR, Logged into the master successfully

E: 2019-02-03 01:30:57.143 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:30:57.143 DMR, Closing DMR Network

M: 2019-02-03 01:30:57.143 DMR, Opening DMR Network

D: 2019-02-03 01:31:07.181 DMR, Sending authorisation

D: 2019-02-03 01:31:07.217 DMR, Sending configuration

M: 2019-02-03 01:31:07.252 DMR, Logged into the master successfully

E: 2019-02-03 01:33:07.307 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:33:07.307 DMR, Closing DMR Network

M: 2019-02-03 01:33:07.308 DMR, Opening DMR Network

D: 2019-02-03 01:33:17.344 DMR, Sending authorisation

D: 2019-02-03 01:33:17.385 DMR, Sending configuration

M: 2019-02-03 01:33:17.421 DMR, Logged into the master successfully







Re: one way audio - time out

Kevin Halton
 

Mike,

The strange thing is that everything was working fine last night, woke up today and this is what I have! I looked at the rpt.conf, that looks fine and I have tried all the masters!!

-----Original Message-----
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Mike KB8JNM
Sent: Saturday, February 02, 2019 8:39 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] one way audio - time out

Port conflict ? Just floating ideas.

On 2/2/2019 8:36 PM, Kevin Halton wrote:
Still trying to figure it out. I changed every US master and I am timing out from all of them? Any ideas what would cause this? I am stumped!

,_._,_

Here is another snippet from the log



E: 2019-02-03 01:15:45.950 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:15:45.950 DMR, Closing DMR Network

M: 2019-02-03 01:15:45.950 DMR, Opening DMR Network

D: 2019-02-03 01:15:55.990 DMR, Sending authorisation

D: 2019-02-03 01:15:56.031 DMR, Sending configuration

M: 2019-02-03 01:15:56.067 DMR, Logged into the master successfully

E: 2019-02-03 01:17:56.116 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:17:56.116 DMR, Closing DMR Network

M: 2019-02-03 01:17:56.116 DMR, Opening DMR Network

D: 2019-02-03 01:18:06.157 DMR, Sending authorisation

D: 2019-02-03 01:18:06.193 DMR, Sending configuration

M: 2019-02-03 01:18:06.234 DMR, Logged into the master successfully

E: 2019-02-03 01:20:06.285 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:20:06.285 DMR, Closing DMR Network

M: 2019-02-03 01:20:06.286 DMR, Opening DMR Network

D: 2019-02-03 01:20:16.324 DMR, Sending authorisation

D: 2019-02-03 01:20:16.365 DMR, Sending configuration

M: 2019-02-03 01:20:16.400 DMR, Logged into the master successfully

E: 2019-02-03 01:22:16.444 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:22:16.444 DMR, Closing DMR Network

M: 2019-02-03 01:22:16.444 DMR, Opening DMR Network

D: 2019-02-03 01:22:26.492 DMR, Sending authorisation

D: 2019-02-03 01:22:26.533 DMR, Sending configuration

M: 2019-02-03 01:22:26.569 DMR, Logged into the master successfully

E: 2019-02-03 01:24:26.626 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:24:26.627 DMR, Closing DMR Network

M: 2019-02-03 01:24:26.627 DMR, Opening DMR Network

D: 2019-02-03 01:24:36.670 DMR, Sending authorisation

D: 2019-02-03 01:24:36.711 DMR, Sending configuration

M: 2019-02-03 01:24:36.747 DMR, Logged into the master successfully

M: 2019-02-03 01:25:17.492 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-03 01:25:17.998 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-03 01:25:18.402 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 0% packet loss, BER: 0.0%

E: 2019-02-03 01:26:36.807 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:26:36.807 DMR, Closing DMR Network

M: 2019-02-03 01:26:36.807 DMR, Opening DMR Network

D: 2019-02-03 01:26:46.844 DMR, Sending authorisation

D: 2019-02-03 01:26:46.880 DMR, Sending configuration

M: 2019-02-03 01:26:46.916 DMR, Logged into the master successfully

M: 2019-02-03 01:27:58.746 DMR, TX state = ON

I: 2019-02-03 01:27:58.746 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-03 01:28:01.758 DMR, TX state = OFF, DMR frame count was 53 frames

E: 2019-02-03 01:28:46.971 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:28:46.971 DMR, Closing DMR Network

M: 2019-02-03 01:28:46.971 DMR, Opening DMR Network

D: 2019-02-03 01:28:57.009 DMR, Sending authorisation

D: 2019-02-03 01:28:57.045 DMR, Sending configuration

M: 2019-02-03 01:28:57.091 DMR, Logged into the master successfully

E: 2019-02-03 01:30:57.143 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:30:57.143 DMR, Closing DMR Network

M: 2019-02-03 01:30:57.143 DMR, Opening DMR Network

D: 2019-02-03 01:31:07.181 DMR, Sending authorisation

D: 2019-02-03 01:31:07.217 DMR, Sending configuration

M: 2019-02-03 01:31:07.252 DMR, Logged into the master successfully

E: 2019-02-03 01:33:07.307 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:33:07.307 DMR, Closing DMR Network

M: 2019-02-03 01:33:07.308 DMR, Opening DMR Network

D: 2019-02-03 01:33:17.344 DMR, Sending authorisation

D: 2019-02-03 01:33:17.385 DMR, Sending configuration

M: 2019-02-03 01:33:17.421 DMR, Logged into the master successfully





Re: one way audio - time out

Mike KB8JNM
 

Port conflict ? Just floating ideas.

On 2/2/2019 8:36 PM, Kevin Halton wrote:
Still trying to figure it out. I changed every US master and I am timing out from all of them? Any ideas what would cause this? I am stumped!
,_._,_
Here is another snippet from the log
E: 2019-02-03 01:15:45.950 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:15:45.950 DMR, Closing DMR Network
M: 2019-02-03 01:15:45.950 DMR, Opening DMR Network
D: 2019-02-03 01:15:55.990 DMR, Sending authorisation
D: 2019-02-03 01:15:56.031 DMR, Sending configuration
M: 2019-02-03 01:15:56.067 DMR, Logged into the master successfully
E: 2019-02-03 01:17:56.116 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:17:56.116 DMR, Closing DMR Network
M: 2019-02-03 01:17:56.116 DMR, Opening DMR Network
D: 2019-02-03 01:18:06.157 DMR, Sending authorisation
D: 2019-02-03 01:18:06.193 DMR, Sending configuration
M: 2019-02-03 01:18:06.234 DMR, Logged into the master successfully
E: 2019-02-03 01:20:06.285 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:20:06.285 DMR, Closing DMR Network
M: 2019-02-03 01:20:06.286 DMR, Opening DMR Network
D: 2019-02-03 01:20:16.324 DMR, Sending authorisation
D: 2019-02-03 01:20:16.365 DMR, Sending configuration
M: 2019-02-03 01:20:16.400 DMR, Logged into the master successfully
E: 2019-02-03 01:22:16.444 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:22:16.444 DMR, Closing DMR Network
M: 2019-02-03 01:22:16.444 DMR, Opening DMR Network
D: 2019-02-03 01:22:26.492 DMR, Sending authorisation
D: 2019-02-03 01:22:26.533 DMR, Sending configuration
M: 2019-02-03 01:22:26.569 DMR, Logged into the master successfully
E: 2019-02-03 01:24:26.626 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:24:26.627 DMR, Closing DMR Network
M: 2019-02-03 01:24:26.627 DMR, Opening DMR Network
D: 2019-02-03 01:24:36.670 DMR, Sending authorisation
D: 2019-02-03 01:24:36.711 DMR, Sending configuration
M: 2019-02-03 01:24:36.747 DMR, Logged into the master successfully
M: 2019-02-03 01:25:17.492 DMR Slot 2, received network voice header from KA1MXL to TG 31444
M: 2019-02-03 01:25:17.998 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'
M: 2019-02-03 01:25:18.402 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 0% packet loss, BER: 0.0%
E: 2019-02-03 01:26:36.807 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:26:36.807 DMR, Closing DMR Network
M: 2019-02-03 01:26:36.807 DMR, Opening DMR Network
D: 2019-02-03 01:26:46.844 DMR, Sending authorisation
D: 2019-02-03 01:26:46.880 DMR, Sending configuration
M: 2019-02-03 01:26:46.916 DMR, Logged into the master successfully
M: 2019-02-03 01:27:58.746 DMR, TX state = ON
I: 2019-02-03 01:27:58.746 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL
M: 2019-02-03 01:28:01.758 DMR, TX state = OFF, DMR frame count was 53 frames
E: 2019-02-03 01:28:46.971 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:28:46.971 DMR, Closing DMR Network
M: 2019-02-03 01:28:46.971 DMR, Opening DMR Network
D: 2019-02-03 01:28:57.009 DMR, Sending authorisation
D: 2019-02-03 01:28:57.045 DMR, Sending configuration
M: 2019-02-03 01:28:57.091 DMR, Logged into the master successfully
E: 2019-02-03 01:30:57.143 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:30:57.143 DMR, Closing DMR Network
M: 2019-02-03 01:30:57.143 DMR, Opening DMR Network
D: 2019-02-03 01:31:07.181 DMR, Sending authorisation
D: 2019-02-03 01:31:07.217 DMR, Sending configuration
M: 2019-02-03 01:31:07.252 DMR, Logged into the master successfully
E: 2019-02-03 01:33:07.307 DMR, Connection to the master has timed out, retrying connection
M: 2019-02-03 01:33:07.307 DMR, Closing DMR Network
M: 2019-02-03 01:33:07.308 DMR, Opening DMR Network
D: 2019-02-03 01:33:17.344 DMR, Sending authorisation
D: 2019-02-03 01:33:17.385 DMR, Sending configuration
M: 2019-02-03 01:33:17.421 DMR, Logged into the master successfully


one way audio - time out

Kevin Halton
 

Still trying to figure it out. I changed every US master and I am timing out from all of them? Any ideas what would cause this? I am stumped!

,_._,_

Here is another snippet from the log

 

E: 2019-02-03 01:15:45.950 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:15:45.950 DMR, Closing DMR Network

M: 2019-02-03 01:15:45.950 DMR, Opening DMR Network

D: 2019-02-03 01:15:55.990 DMR, Sending authorisation

D: 2019-02-03 01:15:56.031 DMR, Sending configuration

M: 2019-02-03 01:15:56.067 DMR, Logged into the master successfully

E: 2019-02-03 01:17:56.116 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:17:56.116 DMR, Closing DMR Network

M: 2019-02-03 01:17:56.116 DMR, Opening DMR Network

D: 2019-02-03 01:18:06.157 DMR, Sending authorisation

D: 2019-02-03 01:18:06.193 DMR, Sending configuration

M: 2019-02-03 01:18:06.234 DMR, Logged into the master successfully

E: 2019-02-03 01:20:06.285 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:20:06.285 DMR, Closing DMR Network

M: 2019-02-03 01:20:06.286 DMR, Opening DMR Network

D: 2019-02-03 01:20:16.324 DMR, Sending authorisation

D: 2019-02-03 01:20:16.365 DMR, Sending configuration

M: 2019-02-03 01:20:16.400 DMR, Logged into the master successfully

E: 2019-02-03 01:22:16.444 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:22:16.444 DMR, Closing DMR Network

M: 2019-02-03 01:22:16.444 DMR, Opening DMR Network

D: 2019-02-03 01:22:26.492 DMR, Sending authorisation

D: 2019-02-03 01:22:26.533 DMR, Sending configuration

M: 2019-02-03 01:22:26.569 DMR, Logged into the master successfully

E: 2019-02-03 01:24:26.626 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:24:26.627 DMR, Closing DMR Network

M: 2019-02-03 01:24:26.627 DMR, Opening DMR Network

D: 2019-02-03 01:24:36.670 DMR, Sending authorisation

D: 2019-02-03 01:24:36.711 DMR, Sending configuration

M: 2019-02-03 01:24:36.747 DMR, Logged into the master successfully

M: 2019-02-03 01:25:17.492 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-03 01:25:17.998 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-03 01:25:18.402 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 0% packet loss, BER: 0.0%

E: 2019-02-03 01:26:36.807 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:26:36.807 DMR, Closing DMR Network

M: 2019-02-03 01:26:36.807 DMR, Opening DMR Network

D: 2019-02-03 01:26:46.844 DMR, Sending authorisation

D: 2019-02-03 01:26:46.880 DMR, Sending configuration

M: 2019-02-03 01:26:46.916 DMR, Logged into the master successfully

M: 2019-02-03 01:27:58.746 DMR, TX state = ON

I: 2019-02-03 01:27:58.746 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-03 01:28:01.758 DMR, TX state = OFF, DMR frame count was 53 frames

E: 2019-02-03 01:28:46.971 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:28:46.971 DMR, Closing DMR Network

M: 2019-02-03 01:28:46.971 DMR, Opening DMR Network

D: 2019-02-03 01:28:57.009 DMR, Sending authorisation

D: 2019-02-03 01:28:57.045 DMR, Sending configuration

M: 2019-02-03 01:28:57.091 DMR, Logged into the master successfully

E: 2019-02-03 01:30:57.143 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:30:57.143 DMR, Closing DMR Network

M: 2019-02-03 01:30:57.143 DMR, Opening DMR Network

D: 2019-02-03 01:31:07.181 DMR, Sending authorisation

D: 2019-02-03 01:31:07.217 DMR, Sending configuration

M: 2019-02-03 01:31:07.252 DMR, Logged into the master successfully

E: 2019-02-03 01:33:07.307 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-03 01:33:07.307 DMR, Closing DMR Network

M: 2019-02-03 01:33:07.308 DMR, Opening DMR Network

D: 2019-02-03 01:33:17.344 DMR, Sending authorisation

D: 2019-02-03 01:33:17.385 DMR, Sending configuration

M: 2019-02-03 01:33:17.421 DMR, Logged into the master successfully


Re: DStar/DMR XRF or DCS for testing

Steve N4IRS
 

I can't speak to the XRF but use your DMR ID for the TG

On 2/2/19 6:21 PM, Skyler Fennell wrote:
I need to perform lots of tests with long transmissions. I am working on a digital mode mobile/multipath comparison experiment. I need to link some stuff together for the experiment.


What is a good DCS/XRF reflector # I can use that will not be bothered by me talking for a while.
What is a good Brandmeister Talkgroup # that I can use that will not be bothered by me talking for a while.


Thank You,
Skyler


DStar/DMR XRF or DCS for testing

Skyler Fennell
 

I need to perform lots of tests with long transmissions. I am working on a digital mode mobile/multipath comparison experiment. I need to link some stuff together for the experiment.


What is a good DCS/XRF reflector # I can use that will not be bothered by me talking for a while.
What is a good Brandmeister Talkgroup # that I can use that will not be bothered by me talking for a while.


Thank You,
Skyler


one way audio - time out

Kevin Halton
 

Everything was working fine, woke up today and noticed the link was quiet. I am able to intermittently keyup  from ASL (hamvoip version) to digital (DMR-YSF-Dstar-NXDN) I can key up fusion-Dstar-nxdn to analog but NOT DMR! I have tried changing masters, rebooting EVERYTHING I have and still the same. No hair left to pull out. I am seeing that it is not staying connected to the master or it times out?

 

Here is a copy of the mmdvm log

I: 2019-02-02 22:06:21.471 Portions Copyright (C) 2018 DVSwitch, INAD.

I: 2019-02-02 22:06:21.471 Hacks by Mike N4IRR and Steve N4IRS

I: 2019-02-02 22:06:21.472 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

I: 2019-02-02 22:06:21.472 This software is for use on amateur radio networks only,

I: 2019-02-02 22:06:21.472 it is to be used for educational purposes only. Its use on

I: 2019-02-02 22:06:21.472 commercial networks is strictly prohibited.

I: 2019-02-02 22:06:21.472 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others

M: 2019-02-02 22:06:21.472 MMDVM_Bridge-20180423 is starting

M: 2019-02-02 22:06:21.472 Built 19:26:19 Jul 26 2018 (GitID #903ae69)

I: 2019-02-02 22:06:21.472 General Parameters

I: 2019-02-02 22:06:21.472     Callsign: KA1MXL

I: 2019-02-02 22:06:21.472     Id: 314400903

I: 2019-02-02 22:06:21.472     Duplex: no

I: 2019-02-02 22:06:21.472     Timeout: 180s

I: 2019-02-02 22:06:21.472     D-Star: disabled

I: 2019-02-02 22:06:21.472     DMR: enabled

I: 2019-02-02 22:06:21.472     YSF: disabled

I: 2019-02-02 22:06:21.472     P25: disabled

I: 2019-02-02 22:06:21.472     NXDN: disabled

I: 2019-02-02 22:06:21.472 Modem Parameters

I: 2019-02-02 22:06:21.472     Port: /dev/null

I: 2019-02-02 22:06:21.472     RX Invert: no

I: 2019-02-02 22:06:21.472     TX Invert: no

I: 2019-02-02 22:06:21.472     PTT Invert: no

I: 2019-02-02 22:06:21.472     TX Delay: 100ms

I: 2019-02-02 22:06:21.472     RX Offset: 0Hz

I: 2019-02-02 22:06:21.472     TX Offset: 0Hz

I: 2019-02-02 22:06:21.473     RX DC Offset: 0

I: 2019-02-02 22:06:21.473     TX DC Offset: 0

I: 2019-02-02 22:06:21.473     RF Level: 100.0%

I: 2019-02-02 22:06:21.473     DMR Delay: 0 (0.0ms)

I: 2019-02-02 22:06:21.473     RX Level: 50.0%

I: 2019-02-02 22:06:21.473     CW Id TX Level: 50.0%

I: 2019-02-02 22:06:21.473     D-Star TX Level: 50.0%

I: 2019-02-02 22:06:21.473     DMR TX Level: 50.0%

I: 2019-02-02 22:06:21.473     YSF TX Level: 50.0%

I: 2019-02-02 22:06:21.473     P25 TX Level: 50.0%

I: 2019-02-02 22:06:21.473     NXDN TX Level: 50.0%

I: 2019-02-02 22:06:21.473     RX Frequency: 436100000Hz (436100000Hz)

I: 2019-02-02 22:06:21.473     TX Frequency: 436100000Hz (436100000Hz)

M: 2019-02-02 22:06:21.473 Opening the MMDVM

I: 2019-02-02 22:06:21.473 Display Parameters

I: 2019-02-02 22:06:21.473     Type: None

I: 2019-02-02 22:06:21.474 DMR Network Parameters

I: 2019-02-02 22:06:21.474     Address: 107.191.99.14

I: 2019-02-02 22:06:21.474     Port: 62031

I: 2019-02-02 22:06:21.474     Local: 62032

I: 2019-02-02 22:06:21.474     Jitter: 750ms

I: 2019-02-02 22:06:21.474     Slot 1: disabled

I: 2019-02-02 22:06:21.474     Slot 2: enabled

I: 2019-02-02 22:06:21.474     Mode Hang: 0s

I: 2019-02-02 22:06:21.474 Info Parameters

I: 2019-02-02 22:06:21.474     Callsign: KA1MXL

I: 2019-02-02 22:06:21.474     RX Frequency: 436100000Hz

I: 2019-02-02 22:06:21.474     TX Frequency: 436100000Hz

I: 2019-02-02 22:06:21.474     Power: 1W

I: 2019-02-02 22:06:21.474     Latitude: 41.750599deg N

I: 2019-02-02 22:06:21.474     Longitude: -71.389603deg E

I: 2019-02-02 22:06:21.474     Height: 0m

I: 2019-02-02 22:06:21.474     Location: "Warwick, RI"

I: 2019-02-02 22:06:21.474     Description: "MMDVM_Bridge"

I: 2019-02-02 22:06:21.474     URL: "https://groups.io/g/DVSwitch"

M: 2019-02-02 22:06:21.474 DMR, Opening DMR Network

I: 2019-02-02 22:06:21.474 RSSI

I: 2019-02-02 22:06:21.475     Mapping File: RSSI.dat

W: 2019-02-02 22:06:21.475 Cannot open the RSSI data file - RSSI.dat

I: 2019-02-02 22:06:21.475 DMR Id Lookups

I: 2019-02-02 22:06:21.475     File: /var/lib/mmdvm/DMRIds.dat

I: 2019-02-02 22:06:21.475     Reload: 24 hours

I: 2019-02-02 22:06:22.089 Loaded 118119 Ids to the DMR callsign lookup table

I: 2019-02-02 22:06:22.089 DMR RF Parameters

I: 2019-02-02 22:06:22.089     Id: 314400903

I: 2019-02-02 22:06:22.089     Color Code: 1

I: 2019-02-02 22:06:22.089     Self Only: no

I: 2019-02-02 22:06:22.089     Embedded LC Only: no

I: 2019-02-02 22:06:22.089     Dump Talker Alias Data: no

I: 2019-02-02 22:06:22.089     Prefixes: 0

I: 2019-02-02 22:06:22.089     Call Hang: 0s

I: 2019-02-02 22:06:22.089     TX Hang: 0s

I: 2019-02-02 22:06:22.089     Mode Hang: 0s

M: 2019-02-02 22:06:22.089 DMR, Opening INI file: DVSwitch.ini

I: 2019-02-02 22:06:22.089 Started the DMR Id lookup reload thread

M: 2019-02-02 22:06:22.089 DMR, Setting [DMR] Address -> 127.0.0.1

M: 2019-02-02 22:06:22.089 DMR, Setting [DMR] TXPort -> 31000

M: 2019-02-02 22:06:22.089 DMR, Setting [DMR] RXPort -> 31003

M: 2019-02-02 22:06:22.089 DMR, Setting [DMR] Slot -> 2

M: 2019-02-02 22:06:22.090 DMR, Transmitting on 127.0.0.1:31000 and listening on port 31003.  Result = 1

M: 2019-02-02 22:06:22.090 MMDVM_Bridge-20180423 is running

M: 2019-02-02 22:06:28.740 DMR, Logged into the master successfully

M: 2019-02-02 22:06:32.182 DMR, Logged into the master successfully

E: 2019-02-02 22:07:28.745 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:07:28.745 DMR, Closing DMR Network

M: 2019-02-02 22:07:28.745 DMR, Opening DMR Network

W: 2019-02-02 22:07:32.230 DMR, Login to the master has failed, retrying login ...

M: 2019-02-02 22:07:38.835 DMR, Logged into the master successfully

E: 2019-02-02 22:08:32.231 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:08:32.231 DMR, Closing DMR Network

M: 2019-02-02 22:08:32.231 DMR, Opening DMR Network

M: 2019-02-02 22:08:42.316 DMR, Logged into the master successfully

M: 2019-02-02 22:09:38.148 DMR, TX state = ON

I: 2019-02-02 22:09:38.148 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

E: 2019-02-02 22:09:38.888 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:09:38.888 DMR, Closing DMR Network

M: 2019-02-02 22:09:38.888 DMR, Opening DMR Network

M: 2019-02-02 22:09:41.177 DMR, TX state = OFF, DMR frame count was 53 frames

W: 2019-02-02 22:09:42.357 DMR, Login to the master has failed, retrying login ...

M: 2019-02-02 22:09:49.057 DMR, Logged into the master successfully

M: 2019-02-02 22:09:49.277 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-02 22:09:50.509 DMR Talker Alias (Data Format 0, Received 0/0 char): ''

M: 2019-02-02 22:09:50.898 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 9% packet loss, BER: 0.0%

M: 2019-02-02 22:10:27.967 DMR, TX state = ON

I: 2019-02-02 22:10:27.967 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:10:32.035 DMR, TX state = OFF, DMR frame count was 71 frames

M: 2019-02-02 22:10:35.968 DMR, TX state = ON

I: 2019-02-02 22:10:35.968 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:10:38.998 DMR, TX state = OFF, DMR frame count was 54 frames

M: 2019-02-02 22:10:42.246 DMR, TX state = ON

I: 2019-02-02 22:10:42.246 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

E: 2019-02-02 22:10:42.359 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:10:42.359 DMR, Closing DMR Network

M: 2019-02-02 22:10:42.359 DMR, Opening DMR Network

M: 2019-02-02 22:10:45.596 DMR, TX state = OFF, DMR frame count was 59 frames

M: 2019-02-02 22:10:48.194 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-02 22:10:48.726 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-02 22:10:49.426 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-02 22:10:51.128 DMR Slot 2, received network end of voice transmission, 3.2 seconds, 0% packet loss, BER: 0.0%

M: 2019-02-02 22:10:52.457 DMR, Logged into the master successfully

M: 2019-02-02 22:10:56.998 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-02 22:10:57.545 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-02 22:10:58.241 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-02 22:11:02.739 DMR Slot 2, received network end of voice transmission, 5.9 seconds, 0% packet loss, BER: 0.0%

M: 2019-02-02 22:11:08.929 DMR, TX state = ON

I: 2019-02-02 22:11:08.929 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:11:13.095 DMR, TX state = OFF, DMR frame count was 73 frames

M: 2019-02-02 22:11:34.150 DMR, TX state = ON

I: 2019-02-02 22:11:34.150 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:11:37.159 DMR, TX state = OFF, DMR frame count was 53 frames

E: 2019-02-02 22:11:49.121 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:11:49.122 DMR, Closing DMR Network

M: 2019-02-02 22:11:49.122 DMR, Opening DMR Network

W: 2019-02-02 22:11:52.499 DMR, Login to the master has failed, retrying login ...

M: 2019-02-02 22:11:59.206 DMR, Logged into the master successfully

M: 2019-02-02 22:12:15.050 DMR, TX state = ON

I: 2019-02-02 22:12:15.050 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:12:18.393 DMR, TX state = OFF, DMR frame count was 59 frames

M: 2019-02-02 22:12:20.429 DMR, TX state = ON

I: 2019-02-02 22:12:20.429 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:12:23.442 DMR, TX state = OFF, DMR frame count was 53 frames

M: 2019-02-02 22:12:25.009 DMR, TX state = ON

I: 2019-02-02 22:12:25.009 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:12:28.017 DMR, TX state = OFF, DMR frame count was 54 frames

M: 2019-02-02 22:12:31.626 DMR, TX state = ON

I: 2019-02-02 22:12:31.626 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:12:35.715 DMR, TX state = OFF, DMR frame count was 71 frames

M: 2019-02-02 22:12:44.130 DMR, TX state = ON

I: 2019-02-02 22:12:44.130 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:12:47.600 DMR, TX state = OFF, DMR frame count was 61 frames

E: 2019-02-02 22:12:52.506 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:12:52.506 DMR, Closing DMR Network

M: 2019-02-02 22:12:52.506 DMR, Opening DMR Network

M: 2019-02-02 22:13:02.587 DMR, Logged into the master successfully

M: 2019-02-02 22:13:54.082 DMR Slot 2, received network voice header from DF9FP to TG 31444

M: 2019-02-02 22:13:54.807 DMR, TX state = ON

I: 2019-02-02 22:13:54.807 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:13:55.340 DMR Slot 2, received network end of voice transmission, 0.1 seconds, 0% packet loss, BER: 0.0%

E: 2019-02-02 22:13:59.251 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:13:59.251 DMR, Closing DMR Network

M: 2019-02-02 22:13:59.251 DMR, Opening DMR Network

M: 2019-02-02 22:13:59.556 DMR, TX state = OFF, DMR frame count was 82 frames

W: 2019-02-02 22:14:02.638 DMR, Login to the master has failed, retrying login ...

M: 2019-02-02 22:14:08.270 DMR, TX state = ON

I: 2019-02-02 22:14:08.270 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:14:09.348 DMR, Logged into the master successfully

M: 2019-02-02 22:14:12.998 DMR, TX state = OFF, DMR frame count was 82 frames

M: 2019-02-02 22:14:18.606 DMR, TX state = ON

I: 2019-02-02 22:14:18.606 DMR, Begin TX: src=3144009 rpt=314400903 dst=31444 slot=2 cc=1 metadata=KA1MXL

M: 2019-02-02 22:14:21.795 DMR, TX state = OFF, DMR frame count was 57 frames

M: 2019-02-02 22:14:29.200 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-02 22:14:29.742 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-02 22:14:30.453 DMR Talker Alias (Data Format 1, Received 6/10 char): 'KA1MXL'

M: 2019-02-02 22:14:31.439 DMR Slot 2, received network end of voice transmission, 2.5 seconds, 0% packet loss, BER: 0.0%

M: 2019-02-02 22:14:42.900 DMR Slot 2, received network voice header from KA1MXL to TG 31444

M: 2019-02-02 22:14:43.789 DMR Talker Alias (Data Format 1, Received 6/8 char): 'KA1MXL'

M: 2019-02-02 22:14:44.514 DMR Talker Alias (Data Format 1, Received 8/8 char): 'KA1MXL  '

M: 2019-02-02 22:14:44.760 DMR Slot 2, received network end of voice transmission, 1.6 seconds, 0% packet loss, BER: 0.0%

M: 2019-02-02 22:14:58.228 DMR Slot 2, received network voice header from 44022 to TG 31444

M: 2019-02-02 22:15:00.298 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 2% packet loss, BER: 0.0%

E: 2019-02-02 22:15:02.640 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:15:02.640 DMR, Closing DMR Network

M: 2019-02-02 22:15:02.640 DMR, Opening DMR Network

M: 2019-02-02 22:15:12.734 DMR, Logged into the master successfully

E: 2019-02-02 22:16:09.382 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:16:09.382 DMR, Closing DMR Network

M: 2019-02-02 22:16:09.382 DMR, Opening DMR Network

W: 2019-02-02 22:16:12.765 DMR, Login to the master has failed, retrying login ...

M: 2019-02-02 22:16:19.482 DMR, Logged into the master successfully

E: 2019-02-02 22:17:12.768 DMR, Connection to the master has timed out, retrying connection

M: 2019-02-02 22:17:12.768 DMR, Closing DMR Network

M: 2019-02-02 22:17:12.768 DMR, Opening DMR Network

M: 2019-02-02 22:17:22.845 DMR, Logged into the master successfully

M: 2019-02-02 22:18:04.244 Closing the MMDVM

I: 2019-02-02 22:18:05.144 Stopped the DMR Id lookup reload thread

M: 2019-02-02 22:18:05.145 DMR, Closing DMR Network

I: 2019-02-02 22:18:05.145 MMDVM_Bridge-20180423 exited on receipt of SIGINT

W: 2019-02-02 22:18:09.536 DMR, Login to the master has failed, retrying login ...

M: 2019-02-02 22:18:19.617 DMR, Logged into the master successfully

 

_._,_._,_


Re: MMDVM_Bridge timeout to DMRGateway

Steve N4IRS
 

OK,
Just in case here is my slightly redacted test

On 1/31/19 5:24 PM, Steve KC1AWV wrote:
I figured you'd pick up on what I was working with. Good lord, I didn't think of checking the open ports. I noticed some services running in the background after closing the ones I was running in the foreground. Cleaned those up, and it seems to be stable now.

"If it's not DNS, then it's occupied ports" is my new mantra.

I'll keep an eye on things and have the guys test again.

Thanks, Steve!


Re: MMDVM_Bridge timeout to DMRGateway

Steve KC1AWV
 

I figured you'd pick up on what I was working with. Good lord, I didn't think of checking the open ports. I noticed some services running in the background after closing the ones I was running in the foreground. Cleaned those up, and it seems to be stable now.

"If it's not DNS, then it's occupied ports" is my new mantra.

I'll keep an eye on things and have the guys test again.

Thanks, Steve!

6641 - 6660 of 9797