Date   

Re: BrandMeister to XLX

Steve KC1AWV
 

Yes Lito, you have the right idea.

If you run the two programs for the XLX side in the foreground, can you copy and paste the output to me? Maybe I can diagnose what's going on before I complete the documentation. Day job is taking precedence over it right now.


Re: BrandMeister to XLX

Valentino
 

Yesterday, by testing with the XLX067 system, I was able to make reception and transmission work with the DMRplus system.
I passed it through the HBlink system. I think it is also possible for the BM DMR.
At this moment my system XLX067 Module E can be done qso in Dmr Plus.
Best regards 73' - EA1HNC


Re: BrandMeister to XLX

Lito - WI6Y
 

Hi Steve (AWV),

First of all there's a lot of Steves here 😄, jk.

So in reference to what you said, would it look like this:

BM TG xxxx <--> MMDVM Bridge BM <-----> MMDVM Bridge XLX <------> DMRGateway <----> XLX

I tried this but could not get the MMDVM Bridge XLX <--->DMRGateway <--->XLX to work

That write up would help a lot.

73,

Lito


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve KC1AWV <smiller@...>
Sent: Tuesday, February 26, 2019 10:48 AM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] BrandMeister to XLX
 
Ben,

Well yeah, for an interlink. If you don't need an interlink, 2 instances of MMDVM_Bridge and a DMRGateway will work, which is the instruction set I'm putting together.

If you need AMBE vocoding on top, that can be done with ambed, AMBEServer, or Analog_Bridge. Each comes with its own configuration, so to each their own.

On Tue, Feb 26, 2019 at 1:32 PM Ben Fogt <n5amd@...> wrote:
Ooo how does that work? Someone on their end has to approve the connection I thought? 

On Mon, Feb 25, 2019 at 4:19 PM Steve KC1AWV <smiller@...> wrote:
I used this as a guideline, but if all of your connections are DMR, there's no need for the AMBE dongles.

Only really need the AMBE dongles when going from IMBE to AMBE.

I'm coming up with a step-by-step Debian 9 install of XLX with a BM TG for those that don't want to wait for the BM guys to answer to an interlink helpdesk ticket.

Steve KC1AWV



--
Ben Fogt
N5AMD



--
Steve Miller
KC1AWV


Re: BrandMeister to XLX

Steve KC1AWV
 

Ben,

Well yeah, for an interlink. If you don't need an interlink, 2 instances of MMDVM_Bridge and a DMRGateway will work, which is the instruction set I'm putting together.

If you need AMBE vocoding on top, that can be done with ambed, AMBEServer, or Analog_Bridge. Each comes with its own configuration, so to each their own.

On Tue, Feb 26, 2019 at 1:32 PM Ben Fogt <n5amd@...> wrote:
Ooo how does that work? Someone on their end has to approve the connection I thought? 

On Mon, Feb 25, 2019 at 4:19 PM Steve KC1AWV <smiller@...> wrote:
I used this as a guideline, but if all of your connections are DMR, there's no need for the AMBE dongles.

Only really need the AMBE dongles when going from IMBE to AMBE.

I'm coming up with a step-by-step Debian 9 install of XLX with a BM TG for those that don't want to wait for the BM guys to answer to an interlink helpdesk ticket.

Steve KC1AWV



--
Ben Fogt
N5AMD



--
Steve Miller
KC1AWV


Re: BrandMeister to XLX

Ben Fogt
 

Ooo how does that work? Someone on their end has to approve the connection I thought? 


On Mon, Feb 25, 2019 at 4:19 PM Steve KC1AWV <smiller@...> wrote:
I used this as a guideline, but if all of your connections are DMR, there's no need for the AMBE dongles.

Only really need the AMBE dongles when going from IMBE to AMBE.

I'm coming up with a step-by-step Debian 9 install of XLX with a BM TG for those that don't want to wait for the BM guys to answer to an interlink helpdesk ticket.

Steve KC1AWV



--
Ben Fogt
N5AMD


Re: Blog with P25<->DMR Info

mike@...
 

Thanks Mike for the catch - I've updated the information in the tutorial. 

73,
Mike - N6MIK


On Sat, Feb 23, 2019 at 5:10 AM Mike AE4ML <mike.lussier@...> wrote:
I followed the instructions in the Blog, It was all correct. However there was one flaw that I found. That was a failure in the Analog_bridge_P25.ini file
It wouldn't let me leave gatewayDmrId = 0 & repeaterID = 0 as per the instructions. I had to add my gateway DMRID and the repeaterID and then the system came to life.
I will say that you must take your time and the port numbers MUST be correct and as Steve has pointed out. running the programs in the foreground at each step is an absolute must. The log files are an asset to help pull it all together.  Now on to the web page...


Analog_Bridge P25.ini file

[AMBE_AUDIO]
server = 127.0.0.1
fromDMRPort = 34100 {IMPORTANT}
toDMRPort = 34103 {IMPORTANT}
ambeMode = P25 {IMPORTANT}
minTxTimeMS = 2000
gatewayDmrId = 0
repeaterID = 0

txTg = {YOUR P25 TALKGROUP from P25Hosts.txt HERE}
txTs = 1 
colorCode = 1


Linking BM to XLX DMR mode

Lito - WI6Y
 

Hi Steve,

If I needed to link a [BM TG]<--> [XLX DMR mode TG 6], what would be the best way to do it?

73,

Lito


Re: looking at my options

Steve N4IRS
 

Without going through each group, yes

On 2/25/19 5:21 PM, Mike AE4ML wrote:

So my central reflector would look something like this

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34103     32010         42020                      41000
34100     42020         32010

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34203   32110           42120                      41010
34200   42120           32110      

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34303     32210          42220                   41020
34300     42220          32210

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34403     32310          42320                 41030
34400     42320          32310



Re: looking at my options

Mike AE4ML
 


So my central reflector would look something like this

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34103     32010         42020                      41000
34100     42020         32010

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34203   32110           42120                      41010
34200   42120           32110      

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34303     32210          42220                   41020
34300     42220          32210

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector
34403     32310          42320                 41030
34400     42320          32310


Re: BrandMeister to XLX

Steve KC1AWV
 

I used this as a guideline, but if all of your connections are DMR, there's no need for the AMBE dongles.

Only really need the AMBE dongles when going from IMBE to AMBE.

I'm coming up with a step-by-step Debian 9 install of XLX with a BM TG for those that don't want to wait for the BM guys to answer to an interlink helpdesk ticket.

Steve KC1AWV


Re: BrandMeister to XLX

Ben Fogt
 

On Sat, Feb 23, 2019 at 3:34 PM John MI0AAZ via Groups.Io <mi0aaz=yahoo.co.uk@groups.io> wrote:
Would there be any chance of one of you publishing a step by step tutorial for people like myself who cant seem to get their head around doing this, something along the lines of the ASL to DMR tutorial ? I have a NW Digital Radio Pi DV hat which i would like to use for the project, example being have the Pi here at home as an ambeserver and in turn linked online to my existing ASL server ?

73 John Mi0AAZ.



--
Ben Fogt
N5AMD


Re: looking at my options

Steve N4IRS
 

Yes you can. Simply run multiple instances of P25Reflector with each ini file edited to taste.
You can have one executable and 4 ini files.
P25Reflector repeater1.ini
P25Reflector repeater2.ini
...

On 2/25/2019 2:37 PM, Mike AE4ML wrote:
I like the idea,
I had originally give a thought to local reflectors ( Repeater <-> Quantar_Bridge <-> MMDVM_Bridge <-> P25Gateway <-> P25Reflector
However the issue that comes up is this. All of these sites are fire-walled and denying most inbound ports.

The next step was to create a reflector for a test. I created a AWS site to host a single reflector. Then  I expanded on that reflector to include a functional DMR to P25 Bridge.

Can we expand your idea of local reflectors to a central reflector.
Can I host multiple reflectors on a single AWS instance ? using multiple port numbers i.e.
repeater 1  41000
repeater 2  41010 
repeater 3  41020
repeater 4  41030



Re: looking at my options

Mike AE4ML
 

I like the idea,
I had originally give a thought to local reflectors ( Repeater <-> Quantar_Bridge <-> MMDVM_Bridge <-> P25Gateway <-> P25Reflector
However the issue that comes up is this. All of these sites are fire-walled and denying most inbound ports.

The next step was to create a reflector for a test. I created a AWS site to host a single reflector. Then  I expanded on that reflector to include a functional DMR to P25 Bridge.

Can we expand your idea of local reflectors to a central reflector.
Can I host multiple reflectors on a single AWS instance ? using multiple port numbers i.e.
repeater 1  41000
repeater 2  41010 
repeater 3  41020
repeater 4  41030


Re: looking at my options

Steve N4IRS
 

Mike,
 So, let's drop out DMR and YSF for now and concentrate on P25. We are talking about any to any connectivity. A repeater (or node) can connect to any other repeater. The model for this that I'm familiar with is AllStarLink. Not only can any node connect to any other node, any node can have multiple nodes connected to it at the same time. If node A is connected to node B and node C, traffic from node B is sent to node C via node A. Effectively, each node is a conference bridge.   MMDVM nodes are outbound only devices and only one connection at a time. We will need a method for a MMDVM node to be able to accept a inbound authenticated connection. That would take care of the one to one requirement. I think the easiest place to look is P25Gateway, it's current operating mode is simple. P25Gateway looks at the TG being sent by MMDVM_Bridge (and MMDVMHost in a hotspot) and "connects" to a IP address and port as defined in the host file. From that point, any TG number transmitted by MMDVM_Bridge, that is not in the host file is sent to the target reflector. The reflector dutifully reflects that TG to all connected nodes. About as simple as it gets.

 To me, it make the most sense to not modify MMDVM_Bridge, but to replace P25Gateway. The replacement would need to do 3 things. 1: Route outbound traffic to a IP/PORT based on a TG lookup in the host file. 2: Accept inbound authenticated traffic. 3: Route traffic to all connected nodes. The TG becomes a issue that would have to be worked out. As a side note, the host file should be replaced with a DDNS system. When a gateway comes online it reports it's IP address to a DDNS (authenticated of course) that way when a node wants a outbound connection to another node, it's a simple DNS lookup. The inbound traffic would be authenticated against the DDNS. This is what I proposed to AllStarLink a couple of years ago but I was unable to convince people it was a better way.

So, what do we do today? I'm picturing each node has it's own local reflector. If the outbound traffic from MMDVM_Bridge is intended for a shared reflector (10200) the existing P25Gateway simply routes traffic to the shared reflector. If another repeater want to connect inbound it connects just like it's connecting to a shared reflector. The difference is it connects to the local reflector of the distant repeater. If the distant repeater is not currently connected to a shared repeater, it's connected to the local reflector and the traffic is passed to the local repeater. No e-mail from me is complete without a flow diagram:

MMDVM_Bridge <-> P25Gateway <-> Local_P25Reflector

Outbound traffic goes from MMDVM_Bridge to P25Gateway to the distant reflector which can be someones local reflector or a shared reflector. Hotspots would not be changed, they would be outbound nodes only.

I would love to see other thoughts. That is the reason I answered your question that way I did. If we can design a workable method and break it up into sections, it could be built. I know there are enough people lurking that might have some ideas.          

Steve

On 2/25/2019 11:10 AM, Mike AE4ML wrote:

 That opens up a lot Steve,  Ok not looking at the existing tools.
I would like to have access directly to the trio or each individual UHF repeaters and/or the VHF repeater via MMDVM Hotspot (DMR or P25, YSF*) and the same abilities with the VHF. We would like to link in the VHF repeater with the others as needed but not full time. Key here is to allow connection with MMDVM hot spots.  There has been interest in the use of YSF access to the system as well but that is on the back burner right now.



 


Re: looking at my options

Mike AE4ML
 


 That opens up a lot Steve,  Ok not looking at the existing tools.
I would like to have access directly to the trio or each individual UHF repeaters and/or the VHF repeater via MMDVM Hotspot (DMR or P25, YSF*) and the same abilities with the VHF. We would like to link in the VHF repeater with the others as needed but not full time. Key here is to allow connection with MMDVM hot spots.  There has been interest in the use of YSF access to the system as well but that is on the back burner right now.



 


Re: Courtesy tones

Chris WB4ULK
 

You caaaaannn have a courtesy tone if you choose to. You could let Allstar generate it. Just know, that if you do, you will be pushing that tone across anything that you are connected to. Depending on where you connect, you might tick some other repeater owners off.

On my network, I have my allstar portion of my bridge “id”. What I mean is, I set my node ID to “r” so I get a short ._. at 18wpm every 10 minutes when we are talking. I have it fairly low and fast. I have mine set this way to help remind DMR users to ID every 10 minutes.

We don’t mind this as it’s unobtrusive and if others don’t like it... well they don’t have to connect.

Chris

On Feb 24, 2019, at 10:04 AM, K4VL <73dek4vl@...> wrote:

True about t by e commercial repeaters. I think what I am missing is the tail at unkey. It's just strange and will take some getting used to. 

On Sat, Feb 23, 2019, 7:50 AM JJ Cummings <cummingsj@...> wrote:
The only way to know that your call “went through” on DMR would be to get a full duplex hotspot and setup admit criteria so that your radio gives you the admit tone on sync.

This all said even a courtesy tone or admit tone don’t indicate a successful voice call, only that the repeater heard you at that exact moment or just after.  Ever notice that there is no courtesy tone and rarely even hang time on public service and/or commercial analog repeaters?

Sent from the iRoad

On Feb 23, 2019, at 06:30, Corey Dean N3FE <n3fe@...> wrote:

Dmr was never intended to have anything like that.  The radio controls that.  Program in a end of transmission tone on your radio and you are all set.

Corey n3fe

On Sat, Feb 23, 2019 at 7:27 AM K4VL <73dek4vl@...> wrote:
I have an ASL to DMR bridge running. It connects my repeater to my own talk group. One thing I don't like is that on the DMR side I don't have a courtesy to and I have to wonder if my call went through. I have found this an issue on other talk groups as well. (When running my jumbospot through my cellphone hotspot) Is there a way to turn on a courtesy tone? I have changed a few settings but had no luck. 


Re: Courtesy tones

K4VL
 

True about t by e commercial repeaters. I think what I am missing is the tail at unkey. It's just strange and will take some getting used to. 


On Sat, Feb 23, 2019, 7:50 AM JJ Cummings <cummingsj@...> wrote:
The only way to know that your call “went through” on DMR would be to get a full duplex hotspot and setup admit criteria so that your radio gives you the admit tone on sync.

This all said even a courtesy tone or admit tone don’t indicate a successful voice call, only that the repeater heard you at that exact moment or just after.  Ever notice that there is no courtesy tone and rarely even hang time on public service and/or commercial analog repeaters?

Sent from the iRoad

On Feb 23, 2019, at 06:30, Corey Dean N3FE <n3fe@...> wrote:

Dmr was never intended to have anything like that.  The radio controls that.  Program in a end of transmission tone on your radio and you are all set.

Corey n3fe

On Sat, Feb 23, 2019 at 7:27 AM K4VL <73dek4vl@...> wrote:
I have an ASL to DMR bridge running. It connects my repeater to my own talk group. One thing I don't like is that on the DMR side I don't have a courtesy to and I have to wonder if my call went through. I have found this an issue on other talk groups as well. (When running my jumbospot through my cellphone hotspot) Is there a way to turn on a courtesy tone? I have changed a few settings but had no luck. 


Re: looking at my options

Steve N4IRS
 

Mike,
As I read this, the VHF repeater would have access to either the "trio" reflector (with DMR bridge) or the MMDVM reflectors (NA etc). As you laid out you could add a reflector to be used to bridge the VHF repeater to DMR on it's own.
Everything you laid out will work. That all being said, IF you were not limited to the existing tools, how would you want to configure?

Steve N4IRS

On 2/23/19 8:55 PM, Mike AE4ML wrote:
I have 2 Quantar repeaters up at a mountain site.One VHF & one UHF both of them are setup with routers and PI's. The VHF is currently not connected to the internet.
I have the UHF Quantar at the site linked to two other UHF Quantars linked via Private reflector. This trio is also bridged P25 to DMR.   This allows others in our group to connect either via Private reflector or via DMR.
Now the next item on my list is what to do with the VHF Quantar.  I dont want it as a full time member of the UHF Trio. at the same time I want to setup a reflector and another P25 to DMR bridge as I did with the UHF repeaters.

Mike


looking at my options

Mike AE4ML
 

I have 2 Quantar repeaters up at a mountain site.One VHF & one UHF both of them are setup with routers and PI's. The VHF is currently not connected to the internet.
I have the UHF Quantar at the site linked to two other UHF Quantars linked via Private reflector. This trio is also bridged P25 to DMR.   This allows others in our group to connect either via Private reflector or via DMR.
Now the next item on my list is what to do with the VHF Quantar.  I dont want it as a full time member of the UHF Trio. at the same time I want to setup a reflector and another P25 to DMR bridge as I did with the UHF repeaters.

Mike


Re: Multiple MMDVM _Bridge instances with brandmeister?

Skyler Fennell
 

Mike, the radio ID's are different.

Thank you Steve that solved the problem! Changing the local port fixed it. 


On Sat, Feb 23, 2019 at 4:53 PM Mike KB8JNM <groupio@...> wrote:
Which DMR ID's are you using to connect to the desired talkgroup ?
Those are what I am referring to no matter the number.
'I would be guessing' that if they are the same, only the first connect
will be allowed.

On 2/23/2019 5:07 PM, Skyler Fennell wrote:
> 310847 is the talk-group I want to connect to not a DMR ID. If I try
> 31084701, it does not talk on the proper talk-group since that is not even
> a valid talk group.
>
> So again, here is my audio desired flowcharts:
>
> YSF REFLECTOR < -- > MMDVM_BRIDGE <---> BRANDMEISTER TALKGROUP <-->
> MMDVM_BRIDGE <--> ANALOG_BRIDGE <--> ASL
>
> BRANDMEISTER TALKGROUP --->  MMDVM_BRIDGE --> ANALOG_BRIDGE --> ASL
> &&BRANDMEISTER TALKGROUP --->  MMDBM_BRIDGE --> YSF REFLECTOR
>
>
> I already have tried appending different DMR digits, and even am using
> someone elses call for the second bridge with the DMR ID. I also changed
> all of the DVSWITCH ports so there is no conflict on the local ports.
>
> 1St MMDVM_BRIDGE.ini
>
>
> [General]
>
> Callsign=KG0SKY
>
> Id=MY_ID with 01 at the end
>
> Timeout=180
>
> Duplex=0
>
> RFModeHang=10
>
> NetModeHang=3
>
>
> [DMR Network]
>
> Enable=1
>
> Address=107.191.99.14
>
> Port=62031
>
> Jitter=360
>
> Local=62032
>
> Password=passw0rd
>
> Slot1=1
>
> Slot2=1
>
> Debug=0
>
> 2nd MMDVM_Bridge.ini
>
> [General]
>
> Callsign=KE0VH
>
> Id=KE0VH's ID NUMBER HERE
>
> Timeout=180
>
> Duplex=0
>
> RFModeHang=10
>
> NetModeHang=3
>
>
> [DMR Network]
>
> Enable=1
>
> Address=3102.repeater.net
>
> Port=62031
>
> Jitter=360
>
> Local=62032
>
> Password=passw0rd
>
> Slot1=1
>
> Slot2=1
>
> Debug=0
>
>
>
> 1st DVSwitch.ini
>
> [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
>
>
> 2nd DVSwitch.ini
>
> [DMR]
>
> Address = 127.0.0.1             ; Address to send AMBE TLV frames to
> (export)
>
> TXPort = 31106                  ; Port to send AMBE TLV frames to (export)
>
> RXPort = 31109                  ; Port to listen on (import)
>
> Slot = 1                        ; Export slot
>
> [YSF]
>
>
> Address = 127.0.0.1             ; Address to send AMBE TLV frames to
> (export)
>
> TXPort = 31109                  ; Port to send AMBE TLV frames to (export)
>
> RXPort = 31106                  ; Port to listen on (import)
>
> FallbackID = MY_ID_IS_HERE            ; In case we can not find a valid DMR
> id in the database, export this one
>
> ExportTG = 310847                 ; Which TG to export
>
> Slot = 1                        ; Export slot
>
>
>
> Analog_Bridge
>
> [AMBE_AUDIO]
>
> address = 127.0.0.1                     ; IP address of xx_Bridge
>
> txPort = 31103                          ; Transmit TLV frames to partner on
> this port
>
> rxPort = 31100                          ; Listen for TLV frames from
> partner on this port
>
> ambeMode = DMR
>
> minTxTimeMS = 100                      ; Minimum time in MS for hang delay
> (0-10000)
>
>
> ; The metadata below is used when ASL is the source since it does not have
> any concept of digital$
>
> gatewayDmrId = MY_ID                        ; ID to use when transmitting
> from Analog_Bridge
>
> repeaterID = MY_ID_WITH_01_AFTER_IT                          ; ID of source
> repeater
>
> txTg = 310847                              ; TG to use for all frames sent
> from Analog_Bridge -> $
>
> txTs = 1                                ; Slot to use for frames sent from
> Analog_Bridge -> xx_Br$
>
> colorCode = 1                           ; Color Code to assign DMR frames
>
>
> Could this be a port conflict on the DMR master registration and are there
> alternate ports I can use?
>
>
> On Sat, Feb 23, 2019 at 2:35 PM Mike KB8JNM <groupio@...> wrote:
>
>> I think you need to append your dmr id's with extra 1 or 2 digits and
>> make them different.
>>
>> 310847 =
>> 31084701
>> 31084702
>>
>> On 2/23/2019 4:31 PM, Skyler Fennell wrote:
>>> I am attempting to run TWO instances of MMDVM bridge. I made separate
>>> folders for each, and now am trying to run them both from command line.
>>>
>>> ONE is for DMR  310847 -->> ANALOG AllStar
>>>
>>> The OTHER is for YSF --> DMR 310847.
>>>
>>> Both YSF and Analog need to talk to the same DMR Brandmeister talkgroup.
>> I
>>> am using separate ID callsigns for the YSF bridge and the Analog_Bridge
>>>
>>> They both work perfectly standalone, but, when I try to run both, I get
>>> registration errors on Brandmeister:
>>>
>>> W: 2019-02-23 21:28:40.566 DMR, Login to the master has failed, retrying
>>> login ...
>>>
>>>
>>>
>>>
>>> Is it possible to have TWO nodes connected to a brandmeister talkgroup
>> from
>>> the same server?
>>>
>>>
>>> Skyler
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>



6841 - 6860 of 10139