Date   

Re: YSFGateway with FCS bridging

David Young
 

Steve,

Ok, I downloaded the new MMDVM_Bridge off github and replaced the old with new for FCS00479 bridge.  After reboot I setup a test and looking at the FCS00479 MMDVM_Bridge log I see that now, yes I received the EOT message after the Network Watchdog timeout on the FCS00479 bridge.  Here's the problem, the EOT is not being passed to the NXDN MMDVM_Bridge log, only the Network Watchdog timeout message.  Thus, NXDN stays in receive mode waiting for the EOT.  If I key up DMR from the TGIF MMDVM_Bridge that will then clear the NXDN MMDVM_Bridge and NXDN will then Tx through the bridge until I Tx again on FCS00479, which then causes NXDN to stay in listening mode again.  The other bridges don't have this problem, XLX, P25, or DMR, only NXDN, maybe it is an ID issue since NXDN uses a unique ID, just a thought.
--
Dave WB6DTB


Re: YSFGateway with FCS bridging

Steve N4IRS
 

David,
Thanks for the offer. We are not setup for that at this time.
I have updated MMDVM_Bridge on github and built updated apt packages for all 4 architectures. 
Please let me know when you have had a chance to test it.

73, Steve N4IRS

On 11/5/2020 7:46 PM, David Young wrote:
Hi Steve,
Thank you for looking into this.  I know you are busy and I appreciate all the work you and your team put into the DVSwitch project.
Even before the new release of DVSwitch Server your team has developed an amazing set of bridges for use by the digital ham community.  If you have a PayPal contribution account I would be happy to contribute money to your efforts.
--
Dave WB6DTB


Re: Filter connections

Steve N4IRS
 

I  assume that you mean you want to not hear a DMR ID or callsign. No you can not filter out a ID or callsign.

Steve N4IRS

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of is0gqx Bruno via groups.io <is0gqx@...>
Sent: Friday, November 6, 2020 2:39:32 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Filter connections
 

 

Hello, in the files of the DVSwitch server is there the possibility to filter the connections with the callsign or the DMR ID like XLX?

 

73, Bruno IS0GQX


Mail priva di virus. www.avast.com


Filter connections

is0gqx Bruno
 

 

Hello, in the files of the DVSwitch server is there the possibility to filter the connections with the callsign or the DMR ID like XLX?

 

73, Bruno IS0GQX


Mail priva di virus. www.avast.com


Re: Problem with Motorola Repeater on HBLink3

Kim-Benjamin Lütkemeier
 

Ok, but hblink work without Problem:
That’s means all mmdvm hotspots work without problems.

But I observed on longer tx duration the Motorola repeater has also Problems.

A hytera with mmdvm gateway works also fine.

73
Do1KBL 



Am 05.11.2020 um 23:19 schrieb Charles Wiant via groups.io <kd8itc@...>:

It might be better if you asked your question in the hblink group


On Nov 5, 2020, at 12:17 PM, Kim-Benjamin Lütkemeier via groups.io <kbluetkemeier@...> wrote:



[Edited Message Follows]

Hello guys,
I have a small question why the first 3 seconds are not ok from IPSC--->HB_bridge

My Hardware looks like this:
Motorola SLR5500 <--->IPSC_Bridge<--->HB_Bridge<--->HBLink3<--->MMDVM_Hotspots

The IPSC_Bridge is the Master and the SLR5500 the Slave.

Connection is OK but the NF ist not working on the beginning (3-4 seconds)

I press PTT on a hotspot and the repeater goes to TX I see very my Callsign, then channel screen about 2-3 seconds again my callsign and then all is ok.

Only in the Direction from IPSC ---> HB_Bridge. Other Direction I have no problem for now.

ERROR 2020-11-05 15:49:39,123 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:49:54,135 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:09,146 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:24,158 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:39,170 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:54,181 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:09,193 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:24,205 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:39,217 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:51:53,567 (Mototrbo) Begin AMBE encode STREAM ID: 3778157481 SUB: 2623266 (2623266) REPEATER: 1234567 (1234567) TGID 9 (9), TS 2
ERROR 2020-11-05 15:51:54,229 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:52:09,082 Voice Transmission Start on TS 2 and TG 9 (9) from 2623266 (2623266)
ERROR 2020-11-05 15:52:09,240 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:52:13,162 Voice Transmission End 4.08 seconds loss rate: 97.06% (2/68)
ERROR 2020-11-05 15:52:24,253 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000

2623266 = DO1KBL Radio ID
2622007 = DO1KBL Repeater ID (TestID)

******************UPDATE********************
When I make a Parrot and speak over repeater the playback is without this problem
For now the problem is from every MMDVMHost Hotspot but why?
The analogbridge make also no problem.

i will be nice if you give me some tipps

73,
Do1KBL, Kim


Re: YSFGateway with FCS bridging

David Young
 

Hi Steve,
Thank you for looking into this.  I know you are busy and I appreciate all the work you and your team put into the DVSwitch project.
Even before the new release of DVSwitch Server your team has developed an amazing set of bridges for use by the digital ham community.  If you have a PayPal contribution account I would be happy to contribute money to your efforts.
--
Dave WB6DTB


Re: ASL-DMR boot will not login to "Master Server"

Steve N4IRS
 

Gary,
Glad to hear you resolved the issue. Below is page 5 of the doc. We will look into improving
The info so it is more clear.

BM Password (Required)
 If you enabled a hotspot security password in Brandmeister
SelfCare, enter it here in order to access the Brandmeister
network, otherwise accept the default (i.e., passw0rd). For
more information, see: http://wiki.pistar.uk/PiStar_Brandmeister_Hotspot_Security.

On 11/5/20 5:19 PM, Gary wrote:

Thanks for the speedy reply Steve.

The problem turned out to be Brandmeister Hotspot password.

The install doc did not mention the need to do anything at BM with passwords. The one in the install ("passw0rd") worked just fine.

(As a matter of fact, I never considered that I was creating a "Hotspot" with the ASL-DMR Bridge.)

After entering a Hotspot password of "passw0rd" at BM, all was AOK.

I have since changed it, of course, to maintain security.

Gary W5BI

On 11/4/2020 15:21, Steve N4IRS wrote:
ping 3102.repeater.net what is the result?

Sent by smoke signal (AT&T)



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Wednesday, November 4, 2020, 4:42 PM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] ASL-DMR boot will not login to "Master Server"

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.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=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Re: Problem with Motorola Repeater on HBLink3

Charles Wiant
 

It might be better if you asked your question in the hblink group


On Nov 5, 2020, at 12:17 PM, Kim-Benjamin Lütkemeier via groups.io <kbluetkemeier@...> wrote:



[Edited Message Follows]

Hello guys,
I have a small question why the first 3 seconds are not ok from IPSC--->HB_bridge

My Hardware looks like this:
Motorola SLR5500 <--->IPSC_Bridge<--->HB_Bridge<--->HBLink3<--->MMDVM_Hotspots

The IPSC_Bridge is the Master and the SLR5500 the Slave.

Connection is OK but the NF ist not working on the beginning (3-4 seconds)

I press PTT on a hotspot and the repeater goes to TX I see very my Callsign, then channel screen about 2-3 seconds again my callsign and then all is ok.

Only in the Direction from IPSC ---> HB_Bridge. Other Direction I have no problem for now.

ERROR 2020-11-05 15:49:39,123 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:49:54,135 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:09,146 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:24,158 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:39,170 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:54,181 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:09,193 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:24,205 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:39,217 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:51:53,567 (Mototrbo) Begin AMBE encode STREAM ID: 3778157481 SUB: 2623266 (2623266) REPEATER: 1234567 (1234567) TGID 9 (9), TS 2
ERROR 2020-11-05 15:51:54,229 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:52:09,082 Voice Transmission Start on TS 2 and TG 9 (9) from 2623266 (2623266)
ERROR 2020-11-05 15:52:09,240 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:52:13,162 Voice Transmission End 4.08 seconds loss rate: 97.06% (2/68)
ERROR 2020-11-05 15:52:24,253 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000

2623266 = DO1KBL Radio ID
2622007 = DO1KBL Repeater ID (TestID)

******************UPDATE********************
When I make a Parrot and speak over repeater the playback is without this problem
For now the problem is from every MMDVMHost Hotspot but why?
The analogbridge make also no problem.

i will be nice if you give me some tipps

73,
Do1KBL, Kim


Re: ASL-DMR boot will not login to "Master Server"

Gary
 

Thanks for the speedy reply Steve.

The problem turned out to be Brandmeister Hotspot password.

The install doc did not mention the need to do anything at BM with passwords. The one in the install ("passw0rd") worked just fine.

(As a matter of fact, I never considered that I was creating a "Hotspot" with the ASL-DMR Bridge.)

After entering a Hotspot password of "passw0rd" at BM, all was AOK.

I have since changed it, of course, to maintain security.

Gary W5BI


    
On 11/4/2020 15:21, Steve N4IRS wrote:
ping 3102.repeater.net what is the result?

Sent by smoke signal (AT&T)



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Wednesday, November 4, 2020, 4:42 PM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] ASL-DMR boot will not login to "Master Server"

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.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=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Problem with Motorola Repeater on HBLink3

Kim-Benjamin Lütkemeier
 
Edited

Hello guys,
I have a small question why the first 3 seconds are not ok from IPSC--->HB_bridge

My Hardware looks like this:
Motorola SLR5500 <--->IPSC_Bridge<--->HB_Bridge<--->HBLink3<--->MMDVM_Hotspots

The IPSC_Bridge is the Master and the SLR5500 the Slave.

Connection is OK but the NF ist not working on the beginning (3-4 seconds)

I press PTT on a hotspot and the repeater goes to TX I see very my Callsign, then channel screen about 2-3 seconds again my callsign and then all is ok.

Only in the Direction from IPSC ---> HB_Bridge. Other Direction I have no problem for now.

ERROR 2020-11-05 15:49:39,123 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:49:54,135 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:09,146 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:24,158 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:39,170 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:50:54,181 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:09,193 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:24,205 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
ERROR 2020-11-05 15:51:39,217 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:51:53,567 (Mototrbo) Begin AMBE encode STREAM ID: 3778157481 SUB: 2623266 (2623266) REPEATER: 1234567 (1234567) TGID 9 (9), TS 2
ERROR 2020-11-05 15:51:54,229 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:52:09,082 Voice Transmission Start on TS 2 and TG 9 (9) from 2623266 (2623266)
ERROR 2020-11-05 15:52:09,240 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000
INFO 2020-11-05 15:52:13,162 Voice Transmission End 4.08 seconds loss rate: 97.06% (2/68)
ERROR 2020-11-05 15:52:24,253 (Mototrbo) Unknown Message - Type: f0 From: 2622007 Packet: f00028023700000000

2623266 = DO1KBL Radio ID
2622007 = DO1KBL Repeater ID (TestID)

******************UPDATE********************
When I make a Parrot and speak over repeater the playback is without this problem
For now the problem is from every MMDVMHost Hotspot but why?
The analogbridge make also no problem.

i will be nice if you give me some tipps

73,
Do1KBL, Kim


Re: YSFGateway with FCS bridging

Steve N4IRS
 

David,
What we are seeing is that a FCS reflector unlike a YSF reflector is not always sending a EOT. The issue is not in the gateway or MB. to alleviate the issue, MB synthesizes a EOT sent across the bridge.
We have changed the message to keep the logs cleaner. I will push out the change this weekend.

Steve N4IRS

On 11/4/2020 5:20 PM, David Young wrote:
Hi Steve,

I downloaded your latest MMDVM_Bridge files off github and replaced the MMDVM_Bridge.amd64 new over to my FCS to DMR bridge.  Also replaced the old with new MMDVM_Bridge.ini and DVSwitch.ini files.  I still receive the Network Watchdog timeout error after each FCS transmission.  Yes, I did rename the MMDVM_Bridge.amd64 to MMDVM_Bridge.
We are using DVSwitch apps to bridge multiple modes over to a HBLink3 virtual server also running on an NFO cloud server.  I before updating to the new MMDVM_Bridge files which seem to have the same Watchdog error I tried various other configuration changes to both YSFGateway.ini and MMDVM_Bridge.ini files with no success, always generating the Network Watchdog error message when transmitting from any FCS room we have bridged to the HBLink3 server.  The best solution I could come up with was bridging the FCS rooms to our XLX server and then bridging the XLX server to DMR using DVSwitch modules.  This cut down my Network Watchdog errors to only approximately 30 percent of the time.  Kind of a round-about way of doing the bridging but still not completely eliminating the errors.  Going to attach a PDF file block diagram of how we are doing our bridging system.  Hope this will help.
--
Dave WB6DTB


Re: ASL-DMR boot will not login to "Master Server"

Tito Lopez - YN1OB
 

I have run into that problem before, I fixed it by typing the Ip address of the master server instead of the name. You will get that number once ping the name as Steve prompted.


On Wed, Nov 4, 2020, 14:23 Steve N4IRS <szingman@...> wrote:
ping 3102.repeater.net what is the result?

Sent by smoke signal (AT&T)



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Wednesday, November 4, 2020, 4:42 PM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] ASL-DMR boot will not login to "Master Server"

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.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=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Re: YSFGateway with FCS bridging

David Young
 

I have been using FCS00479 to test with.


Re: YSFGateway with FCS bridging

Steve N4IRS
 

What FCS room can I point MB at to see the error?

On 11/4/20 5:20 PM, David Young wrote:
Hi Steve,

I downloaded your latest MMDVM_Bridge files off github and replaced the MMDVM_Bridge.amd64 new over to my FCS to DMR bridge.  Also replaced the old with new MMDVM_Bridge.ini and DVSwitch.ini files.  I still receive the Network Watchdog timeout error after each FCS transmission.  Yes, I did rename the MMDVM_Bridge.amd64 to MMDVM_Bridge.
We are using DVSwitch apps to bridge multiple modes over to a HBLink3 virtual server also running on an NFO cloud server.  I before updating to the new MMDVM_Bridge files which seem to have the same Watchdog error I tried various other configuration changes to both YSFGateway.ini and MMDVM_Bridge.ini files with no success, always generating the Network Watchdog error message when transmitting from any FCS room we have bridged to the HBLink3 server.  The best solution I could come up with was bridging the FCS rooms to our XLX server and then bridging the XLX server to DMR using DVSwitch modules.  This cut down my Network Watchdog errors to only approximately 30 percent of the time.  Kind of a round-about way of doing the bridging but still not completely eliminating the errors.  Going to attach a PDF file block diagram of how we are doing our bridging system.  Hope this will help.
--
Dave WB6DTB


Re: #mmdvm_bridge #mmdvm_bridge

swinger72@...
 

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


Re: ASL-DMR boot will not login to "Master Server"

Steve N4IRS
 

ping 3102.repeater.net what is the result?

Sent by smoke signal (AT&T)



From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Wednesday, November 4, 2020, 4:42 PM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] ASL-DMR boot will not login to "Master Server"

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.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=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Re: YSFGateway with FCS bridging

David Young
 

Hi Steve,

I downloaded your latest MMDVM_Bridge files off github and replaced the MMDVM_Bridge.amd64 new over to my FCS to DMR bridge.  Also replaced the old with new MMDVM_Bridge.ini and DVSwitch.ini files.  I still receive the Network Watchdog timeout error after each FCS transmission.  Yes, I did rename the MMDVM_Bridge.amd64 to MMDVM_Bridge.
We are using DVSwitch apps to bridge multiple modes over to a HBLink3 virtual server also running on an NFO cloud server.  I before updating to the new MMDVM_Bridge files which seem to have the same Watchdog error I tried various other configuration changes to both YSFGateway.ini and MMDVM_Bridge.ini files with no success, always generating the Network Watchdog error message when transmitting from any FCS room we have bridged to the HBLink3 server.  The best solution I could come up with was bridging the FCS rooms to our XLX server and then bridging the XLX server to DMR using DVSwitch modules.  This cut down my Network Watchdog errors to only approximately 30 percent of the time.  Kind of a round-about way of doing the bridging but still not completely eliminating the errors.  Going to attach a PDF file block diagram of how we are doing our bridging system.  Hope this will help.
--
Dave WB6DTB


ASL-DMR boot will not login to "Master Server"

Gary
 

Attached snippets from MMDVM_Bridge.ini and log file. Boot stalls at Master login. What is awry?

[General]
Callsign=w5bi
Id=316229205
Timeout=180
Duplex=0
.
.
[DMR Network]
Enable=1
Address=3102.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=1
.
.
/var/log/mmdvm
.
.
M: 2020-11-04 21:05:35.728 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103.  Result = 1
M: 2020-11-04 21:05:35.728 MMDVM_Bridge-20200309_V1.5.1 is running
E: 2020-11-04 21:05:47.369 DMR, Login to the master has failed, retrying network ...
M: 2020-11-04 21:05:47.369 DMR, Closing DMR Network
M: 2020-11-04 21:05:47.369 DMR, Opening DMR Network
E: 2020-11-04 21:05:57.528 DMR, Login to the master has failed, retrying network ...


Re: YSFGateway with FCS bridging

Steve N4IRS
 

Can you tell me what HBlink you are connecting to so I can try to recreate it?

On 11/4/2020 2:14 PM, David Young wrote:
With the new DVSwitch Server package, is it still required to use YSFGateway when bridging an FCS room to DMR?
Reason I'm asking, when bridging FCS to DMR with the previous DVSwitch, YSFGateway was required but I would get Network Watchdog timeout errors after each FCS transmission. 
--
Dave WB6DTB


Re: YSFGateway with FCS bridging

Steve N4IRS
 

Yes, you need YSFGateway. Let us know if you see the timeout message.

On 11/4/2020 2:14 PM, David Young wrote:
With the new DVSwitch Server package, is it still required to use YSFGateway when bridging an FCS room to DMR?
Reason I'm asking, when bridging FCS to DMR with the previous DVSwitch, YSFGateway was required but I would get Network Watchdog timeout errors after each FCS transmission. 
--
Dave WB6DTB

2201 - 2220 of 9598