Date   

locked Re: Zello interface will NOT happen.

Corey Dean N3FE <n3fe@...>
 

As a follow up to this.  The US BM masters owners just talked about this and Zello is NOT to be used on a US BM master .  This is the first and last warning anyone will receive and will be added to the BM wiki in the very near future!

Corey N3FE

On Sat, Oct 20, 2018 at 11:08 AM Steve N4IRS <szingman@...> wrote:
Let me be VERY clear, we are NOT working on Zello in any way, shape or form. That is for someone else to do. NOT US.
Please drop this.

Steve N4IRS

On 10/20/2018 11:05 AM, EA5GVK Joaquin wrote:
Hi. I would like to know if there is any progress to interconnect ZELLO to Analog_Bridge or MMDVM_Bridge, to interconnect a Zello Group with DMR, DSTAR, NXDN, FUSION, P25 etc ...


locked Zello interface will NOT happen.

Steve N4IRS
 

I want to be very clear on this:
We are NOT interested in working on a interface to Zello. Not now, not ever.

Please stop asking for it here.

I will delete any thread on this subject. I will moderate anyone bringing it up.

For DVSwitch

Steve N4IRS


Re: Analog_Bridge Ignore TX

Dylan KI7SBI
 

Calls do come in from other talkers, and audio is outputting to the soundcard. The "Ignore TX" issue is not a blocker for me, although I'm still curious.
I did need Steve's advised latency timer fix for the DV3000 usb.
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer

I: 2018-10-20 00:00:08.287 Begin TX: src=3153775 rpt=13153679 dst=8951 slot=2 cc=1

I: 2018-10-20 00:00:26.306 Begin TX: src=3153775 rpt=13153679 dst=310 slot=2 cc=1

I: 2018-10-20 00:00:40.567 Begin TX: src=3144026 rpt=13153679 dst=310 slot=2 cc=1

I: 2018-10-20 00:00:47.779 Begin TX: src=3153775 rpt=13153679 dst=310 slot=2 cc=1

I: 2018-10-20 00:00:55.027 Begin TX: src=3101849 rpt=13153679 dst=310 slot=2 cc=1

I: 2018-10-20 00:01:00.428 Begin TX: src=1139941 rpt=13153679 dst=310 slot=2 cc=1


KI7SBI


Analog_Bridge Ignore TX

Dylan KI7SBI
 

Anyone experienced this Ignore TX condition with Analog_Bridge before? 

I: 2018-10-19 21:43:01.111 Begin TX: src=3153682 rpt=13153679 dst=9 slot=2 cc=1

I: 2018-10-19 21:43:01.611 Ignore TX: src=3153682 rpt=13153679 dst=9 slot=2 cc=1 (2)

I: 2018-10-19 21:43:02.111 Ignore TX: src=3153682 rpt=13153679 dst=9 slot=2 cc=1 (2)

I: 2018-10-19 21:43:02.611 Ignore TX: src=3153682 rpt=13153679 dst=9 slot=2 cc=1 (2)


Analog_Bridge <=> HB_Bridge client1 <=> HB_Bridge master
HT <=> pistar connects to the same <=> HB_Bridge master

Above, is Analog_Bridge output of a call from the HT. The rpt id is the pistar hotspot. The src id is the HT. I've attempted changing the pistar's id, without success.

Thanks.

KI7SBI


Re: IPSC Peers not Registering with each other

Cort N0MJS <n0mjs@...>
 



On Oct 19, 2018, at 11:13 AM, Michael Eckhoff <mreckhof@...> wrote:


I'm attempting to add a second IPSC peer to an existing peer group and finding that when the two peers attempt to register with each other, it's not working.  In addition, after a while, they drop their connection to the master as well.

On one peer, I get the following in the logs:

INFO 2018-10-15 22:25:17,060 (MASTER) Registering with the Master: x.x.x.x:64835
WARNING 2018-10-15 22:25:17,702 (MASTER) Registration response (we requested reg) from the Master: 1315835, x.x.x.x:64835 (1 peers)
INFO 2018-10-15 22:25:22,064 (MASTER), No Peer List - Requesting One From the Master
INFO 2018-10-15 22:25:24,171 (MASTER) Peer List Received from Master: 2 peers in this IPSC
INFO 2018-10-15 22:25:27,063 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:32,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:37,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:42,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:47,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000

And on the other peer, there's no registration attempt after it gets the alert that there's an additional peer from the master.

I can see in the debug logs that both peers are getting a new peer list and that each of the peers is on it.  It's just that the one peer never tries to do the registration with the other, but the second peer does.

It would have been handy to have included full debug log traces from both peers and the master if you want someone to try and figure out what’s going on. Common reasons for registration problems include two peers who have the same registration IP address (ie behind the same NAT), two peers trying to use the same radio ID… I can think of several other things that would tend to mess things up, but you’ve not included remotely adequate debug log output to look for them.

From the DO_NOT_README file, it makes it clear that all peers try to register with each other, and that process is part of the reason as to how the pinholes get setup in the NATs/FWs.  But if one of the peers doesn't try, then the pinholes never get setup, which is I assume why the peer that is trying to register isn't actually able to do it.

1.  Why wouldn't one of the two peers be attempting to reach out to the other, but one does?  Is there some kind of election by highest/lowest ID or something that dictates who goes first or should they both always blinding just reach out to each other?

First off, thanks for reading it. I renamed it DO_NOT_README in the hopes people would actually read it if I said not to. Trying to get folks to read it before asking for help turned out to not work at all :) :)

They both reach out to each other. Each peer has to register with each other…. you registering with me doesn’t mean I registered with you. We both have to actively register with each other. IPSC is very straightforward in this way.

2.  Why does the master drop the connection to both peers because the two peers can't talk to each other?  I would expect the master to stay connected and the peers just end up being islands.  Note:  I don't see anything in the logs when the master does this, however, I can see on the C-Bridge that they've been disconnected.

Both peers have the same radio ID, both peers coming from the same IP address. Port conflicts. The master will drop them if it doesn’t seen master keep-alive requests for a matter of time. Watch the debug logs to see if the peers are still sending master keep alives and the master to see if it’s receiving them.

3.  I only have a configuration for the MASTER.  I have no configuration setup for PEERS, as it appears to be getting that info from the master.  Do I need a peer configuration?

NO. If you manually had to configure every peer in the IPSC, there’d be no need for the master. That’s its only special role -- to maintain a list of registered peers to allow new systems to bootstrap – that’s what the peer list is all about. You can glean most of that from the MOTOTRBO system planner, BTW._._,_._,_


0x49 DE N0MJS

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






IPSC Peers not Registering with each other

Michael Eckhoff (K5MRE)
 


I'm attempting to add a second IPSC peer to an existing peer group and finding that when the two peers attempt to register with each other, it's not working.  In addition, after a while, they drop their connection to the master as well.

On one peer, I get the following in the logs:

INFO 2018-10-15 22:25:17,060 (MASTER) Registering with the Master: x.x.x.x:64835
WARNING 2018-10-15 22:25:17,702 (MASTER) Registration response (we requested reg) from the Master: 1315835, x.x.x.x:64835 (1 peers)
INFO 2018-10-15 22:25:22,064 (MASTER), No Peer List - Requesting One From the Master
INFO 2018-10-15 22:25:24,171 (MASTER) Peer List Received from Master: 2 peers in this IPSC
INFO 2018-10-15 22:25:27,063 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:32,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:37,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:42,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000
INFO 2018-10-15 22:25:47,065 (MASTER) Registering with Peer 315835, 165.231.210.13:50000

And on the other peer, there's no registration attempt after it gets the alert that there's an additional peer from the master.

I can see in the debug logs that both peers are getting a new peer list and that each of the peers is on it.  It's just that the one peer never tries to do the registration with the other, but the second peer does.

From the DO_NOT_README file, it makes it clear that all peers try to register with each other, and that process is part of the reason as to how the pinholes get setup in the NATs/FWs.  But if one of the peers doesn't try, then the pinholes never get setup, which is I assume why the peer that is trying to register isn't actually able to do it.

1.  Why wouldn't one of the two peers be attempting to reach out to the other, but one does?  Is there some kind of election by highest/lowest ID or something that dictates who goes first or should they both always blinding just reach out to each other?
2.  Why does the master drop the connection to both peers because the two peers can't talk to each other?  I would expect the master to stay connected and the peers just end up being islands.  Note:  I don't see anything in the logs when the master does this, however, I can see on the C-Bridge that they've been disconnected.
3.  I only have a configuration for the MASTER.  I have no configuration setup for PEERS, as it appears to be getting that info from the master.  Do I need a peer configuration?

I've tried this with both the branches and get the same result - and it's always the same peer that tries to reach out to the other.

Thanks!


Re: Newbie Problem

K4VL
 

Success I just talked to a friend in England. He was on DMR and I was on an analog handheld.

Thanks for everything you guys do making this successful


On Thu, Oct 18, 2018 at 8:07 AM Steve N4IRS <szingman@...> wrote:
Russell is correct. You should use this as your template <https://dvswitch.groups.io/g/allstarlink/wiki/home>
The howto document is pointed to in <https://dvswitch.groups.io/g/allstarlink/topic/first_draft_of_asl_dmr/21794260?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,21794260>

Steve N4IRS

On 10/18/2018 9:04 AM, Russell, KV4S wrote:
you may need to turn off your node telemetry, I had some issues with this as well. I'll see if i can find the guide i got... i think i got it from this group.

On Wed, Oct 17, 2018 at 10:33 AM AA4II <aa4ii@...> wrote:
For what it's worth hoseline is working again also.

On Wed, Oct 17, 2018 at 8:35 AM Corey Dean N3FE <n3fe@...> wrote:
Hoseline is a totally separate service and is not part of a master server.  The masters only send the audio to hoseline.  Hoseline is managed overseas and the master owners do not have access to it.
Corey

On Wed, Oct 17, 2018 at 9:29 AM AA4II <aa4ii@...> wrote:
It just came back up but I cannot hear my audio coming through hoseline anymore

On Wed, Oct 17, 2018 at 8:26 AM <jeff@...> wrote:
3108 has been off line all night, as as of one hour ago as well....


Re: Newbie Problem

K4VL
 

OK thanks for the howto. I just went through it and made changes to reflect the howto. Unfortunately I just ordered a DMR radio and can't test it out my self. I will have to wait for some of my friends to get home from work.

Thanks and 73
AA4II
Allstar 47424 (Not bridge)
DMR  tlkgrp 310286

On Thu, Oct 18, 2018 at 8:07 AM Steve N4IRS <szingman@...> wrote:
Russell is correct. You should use this as your template <https://dvswitch.groups.io/g/allstarlink/wiki/home>
The howto document is pointed to in <https://dvswitch.groups.io/g/allstarlink/topic/first_draft_of_asl_dmr/21794260?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,21794260>

Steve N4IRS

On 10/18/2018 9:04 AM, Russell, KV4S wrote:
you may need to turn off your node telemetry, I had some issues with this as well. I'll see if i can find the guide i got... i think i got it from this group.

On Wed, Oct 17, 2018 at 10:33 AM AA4II <aa4ii@...> wrote:
For what it's worth hoseline is working again also.

On Wed, Oct 17, 2018 at 8:35 AM Corey Dean N3FE <n3fe@...> wrote:
Hoseline is a totally separate service and is not part of a master server.  The masters only send the audio to hoseline.  Hoseline is managed overseas and the master owners do not have access to it.
Corey

On Wed, Oct 17, 2018 at 9:29 AM AA4II <aa4ii@...> wrote:
It just came back up but I cannot hear my audio coming through hoseline anymore

On Wed, Oct 17, 2018 at 8:26 AM <jeff@...> wrote:
3108 has been off line all night, as as of one hour ago as well....


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

EA5GVK Joaquin
 

Many thx. always grateful

On Thu, Oct 18, 2018 at 05:47 AM, Steve N4IRS wrote:
Glad to hear it is fixed. We will leave Zello to someone else to implement.


Re: Newbie Problem

Meinke, Rich
 

The telemetry should be off. Its is set when you are setting up the Private node (Node 1999, in the example documents)

[1999]

rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf

                                       ; 127.0.0.1 = IP of the target application

                                       ; 34001 = UDP port the target application is listening on

                                       ; 32001 = UDP port ASL is listening on


duplex = 0                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!


hangtime = 0                            ; squelch tail hang time 0

althangtime = 0                         ; longer squelch tail hang time 0


holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or from connected nodes

                                       ; except when an ID needs to be done and there is a signal coming from a connected node.


telemdefault = 0                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.


telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with a COP command,


linktolink = no                         ; disables forcing physical half-duplex operation of main repeater while

                                       ; still keeping half-duplex semantics (optional)


nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.


totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)


idrecording = |ie                       ; id recording or morse string see http://ohnosec.org/drupal/node/87

idtalkover = |ie                        ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

 


Re: Newbie Problem

Steve N4IRS
 

On 10/18/2018 9:04 AM, Russell, KV4S wrote:
you may need to turn off your node telemetry, I had some issues with this as well. I'll see if i can find the guide i got... i think i got it from this group.

On Wed, Oct 17, 2018 at 10:33 AM AA4II <aa4ii@...> wrote:
For what it's worth hoseline is working again also.

On Wed, Oct 17, 2018 at 8:35 AM Corey Dean N3FE <n3fe@...> wrote:
Hoseline is a totally separate service and is not part of a master server.  The masters only send the audio to hoseline.  Hoseline is managed overseas and the master owners do not have access to it.
Corey

On Wed, Oct 17, 2018 at 9:29 AM AA4II <aa4ii@...> wrote:
It just came back up but I cannot hear my audio coming through hoseline anymore

On Wed, Oct 17, 2018 at 8:26 AM <jeff@...> wrote:
3108 has been off line all night, as as of one hour ago as well....


Re: Newbie Problem

 

you may need to turn off your node telemetry, I had some issues with this as well. I'll see if i can find the guide i got... i think i got it from this group.


On Wed, Oct 17, 2018 at 10:33 AM AA4II <aa4ii@...> wrote:
For what it's worth hoseline is working again also.

On Wed, Oct 17, 2018 at 8:35 AM Corey Dean N3FE <n3fe@...> wrote:
Hoseline is a totally separate service and is not part of a master server.  The masters only send the audio to hoseline.  Hoseline is managed overseas and the master owners do not have access to it.
Corey

On Wed, Oct 17, 2018 at 9:29 AM AA4II <aa4ii@...> wrote:
It just came back up but I cannot hear my audio coming through hoseline anymore

On Wed, Oct 17, 2018 at 8:26 AM <jeff@...> wrote:
3108 has been off line all night, as as of one hour ago as well....


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

Steve N4IRS
 

Glad to hear it is fixed. We will leave Zello to someone else to implement.

Steve N4IRS

On 10/18/2018 8:45 AM, EA5GVK Joaquin wrote:
PERFECT. MANY THX. WORKING PERFECTLY TWO INSTANCES MMDVM_BRIDGE.
In 2ª Instance add # in Local=62032.
One question Steve. Is possible connect Zello to DMR with MMDVM_Bridge and Analog Bridge, as with Allstarlink?
Many thx. Congratulations.

On Thu, Oct 18, 2018 at 05:36 AM, Steve N4IRS wrote:
Joaquin,
I think this is your issue.
In your first MMDVM_Bridge.ini
[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032 <-----------------------
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

In your second MMDVM_Bridge.ini
[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032 <---------------------------
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

Either comment out the Local value so that MMDVM_Bridge can pick a local port or make sure the 2 instances are not using the same port. The outbound port value (62031) is fine.


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

EA5GVK Joaquin
 

PERFECT. MANY THX. WORKING PERFECTLY TWO INSTANCES MMDVM_BRIDGE.
In 2ª Instance add # in Local=62032.
One question Steve. Is possible connect Zello to DMR with MMDVM_Bridge and Analog Bridge, as with Allstarlink?
Many thx. Congratulations.


On Thu, Oct 18, 2018 at 05:36 AM, Steve N4IRS wrote:
Joaquin,
I think this is your issue.
In your first MMDVM_Bridge.ini
[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032 <-----------------------
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

In your second MMDVM_Bridge.ini
[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032 <---------------------------
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

Either comment out the Local value so that MMDVM_Bridge can pick a local port or make sure the 2 instances are not using the same port. The outbound port value (62031) is fine.


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

Steve N4IRS
 

Joaquin,
I think this is your issue.
In your first MMDVM_Bridge.ini
[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032 <-----------------------
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

In your second MMDVM_Bridge.ini
[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032 <---------------------------
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

Either comment out the Local value so that MMDVM_Bridge can pick a local port or make sure the 2 instances are not using the same port. The outbound port value (62031) is fine.

Steve N4IRS

On 10/18/2018 7:46 AM, EA5GVK Joaquin wrote:
IF only working one instance MMDVM_Bridge, perfect, but problem is working two mmdvm_bridge.
1º MMDVM_Bridge installed
/opt/MMDVM_Bridge   --> It is DMR to ASL

MMDVM_Bridge.ini
[General]
Callsign=EA5GVK
Id=214501673
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
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[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

2º MMDVM_Bridge installed
/opt/nxdndmr/MMDVM_Bridge   --> It is DMR to NXDN
[General]
Callsign=EA5GVK
Id=214501660
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_Bridge1

[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=1
RAN=1
Id=45007

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[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=1
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

EA5GVK Joaquin
 

Ok, perfect.
DVSwicth.ini --> DMR to ASL.

; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
[QUANTAR]
logFilePath = /var/log/Quantar_Bridge.log
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 34103                  ; Port to send AMBE TLV frames to (export)
RXPort = 34100                  ; Port to listen on (import)
quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)

; Configure the DMR Partner
; Audio format is AMBE 72 bit
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31100                  ; Port to send AMBE TLV frames to (export)
RXPort = 31103                  ; Port to listen on (import)
Slot = 2                        ; Export slot

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32100                  ; Port to send AMBE TLV frames to (export)
RXPort = 32103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 9                    ; Which TG to export
Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 33100                  ; Port to send AMBE TLV frames to (export)
RXPort = 33103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
NXDNFallbackID  = 12345         ; Use this ID when the input DMR ID is not found in the database
Translate = 1234=4321           ; Translate NXDN TG < -- > DMR TG (bidirectional)
Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
[P25]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 34100                  ; Port to send AMBE TLV frames to (export)
RXPort = 34103                  ; Port to listen on (import)
Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 35100                  ; Port to send AMBE TLV frames to (export)
RXPort = 35103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 1234                 ; Which TG to export
Slot = 2                        ; Export slot

DVSwicth.ini --> DMR to NXDN

; MMDVM_Bridge export / import configuration file.
;   This file should be placed along side of MMDVM_Bridge or it can be
;   supplied as a path on the MMDVM_BRIDGE environment variable.

; Configure the Quantar Repeater Partner
; Note that the TX and RX ports are already reversed for MMDVM_Bridge <--> Quantar_Bridge
[QUANTAR]
logFilePath = /var/log/Quantar_Bridge.log
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 34103                  ; Port to send AMBE TLV frames to (export)
RXPort = 34100                  ; Port to listen on (import)
quantarPort = 1994              ; HDLC frames To/From the Quantar repeater
logLevel = 2                    ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
debug = 0                       ; Debug 0 = off, 1 = on (adds lots of additional messages)

; Configure the DMR Partner
; Audio format is AMBE 72 bit
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31300                  ; Port to send AMBE TLV frames to (export)
RXPort = 31303                  ; Port to listen on (import)
Slot = 2                        ; Export slot

; Configure the D-Star Partner
; Audio format is AMBE 48 bit (DSAMBE)
[DSTAR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 32100                  ; Port to send AMBE TLV frames to (export)
RXPort = 32103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 9                    ; Which TG to export
Slot = 2                        ; Export slot

; Configure the NXDN Partner
; Audio format is AMBE 72 bit
[NXDN]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31303                  ; Port to send AMBE TLV frames to (export)
RXPort = 31300                  ; Port to listen on (import)
FallbackID = 2142346            ; In case we can not find a valid DMR id in the database, export this one
NXDNFallbackID  = 49999         ; Use this ID when the input DMR ID is not found in the database
Translate = 10302=21461           ; Translate NXDN TG < -- > DMR TG (bidirectional)
Slot = 2                        ; Export slot

; Configure the P25 Partner
; Audio format is IMBE 88 bit
[P25]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 34100                  ; Port to send AMBE TLV frames to (export)
RXPort = 34103                  ; Port to listen on (import)
Slot = 2                        ; Export slot

; Configure the Yaesu Fusion Partner
; Audio format is AMBE 72 bit
; Audio format is IMBE 88 bit
[YSF]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 35100                  ; Port to send AMBE TLV frames to (export)
RXPort = 35103                  ; Port to listen on (import)
FallbackID = 1234567            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 1234                 ; Which TG to export
Slot = 2                        ; Export slot


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

Steve N4IRS
 

I need to see the output of the 2 instances of MMDVM_Bridge and the 2 DVSwitch.ini files.

On 10/18/2018 7:46 AM, EA5GVK Joaquin wrote:
IF only working one instance MMDVM_Bridge, perfect, but problem is working two mmdvm_bridge.
1º MMDVM_Bridge installed
/opt/MMDVM_Bridge   --> It is DMR to ASL

MMDVM_Bridge.ini
[General]
Callsign=EA5GVK
Id=214501673
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
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[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

2º MMDVM_Bridge installed
/opt/nxdndmr/MMDVM_Bridge   --> It is DMR to NXDN
[General]
Callsign=EA5GVK
Id=214501660
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_Bridge1

[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=1
RAN=1
Id=45007

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[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=1
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

EA5GVK Joaquin
 

IF only working one instance MMDVM_Bridge, perfect, but problem is working two mmdvm_bridge.
1º MMDVM_Bridge installed
/opt/MMDVM_Bridge   --> It is DMR to ASL

MMDVM_Bridge.ini
[General]
Callsign=EA5GVK
Id=214501673
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
Id=12345

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[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

2º MMDVM_Bridge installed
/opt/nxdndmr/MMDVM_Bridge   --> It is DMR to NXDN
[General]
Callsign=EA5GVK
Id=214501660
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_Bridge1

[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=1
RAN=1
Id=45007

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=84.232.5.113
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0

[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=1
#LocalAddress=127.0.0.1
Debug=0
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


Re: Why no working 2 instancies different MMDVM_Bridge in one machine?

Steve N4IRS
 

What hardware platform?
What OS?
Please show startup output from each instance.
Please show MMDVM_Bridge.ini from each instance.

Do each work properly if they are the only instance running?

Steve n4IRS

On 10/18/2018 06:36 AM, EA5GVK Joaquin wrote:
 because Why if I have running 2 instances of MMDVM_Bridge with DMR to NXDN, one and the other with DMR and YSF, they can not be working.
Disconnecting continuously from the DMR server.
Each instance is in different directories.
Many thx.


Why no working 2 instancies different MMDVM_Bridge in one machine?

EA5GVK Joaquin
 

 because Why if I have running 2 instances of MMDVM_Bridge with DMR to NXDN, one and the other with DMR and YSF, they can not be working.
Disconnecting continuously from the DMR server.
Each instance is in different directories.
Many thx.

6881 - 6900 of 9203