Date   

Re: Help linking P25 to DMR

mike@...
 

Thanks Steve. I'll grab those components and start experimenting! 

I have an existing P25Reflector that connects a couple of MMDVM repeaters (primarily P25 users) and wish to bridge a talk group with one on Brandmeister.

I'm going to try this on a R-pi 3b+; do you think that's going to be robust enough to run everything? 

73,
Mike - N6MIK

On Mon, Jan 14, 2019 at 7:58 PM Steve N4IRS <szingman@...> wrote:
Mike,
Yes you will need those things also. here is a basic diagram:
P25Reflector <-> P25Gateway <-> MMDVM_Bridge <-> Analog_Bridge <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR Master (BM, HB etc)
You will need 2 instances of Analog_Bridge
The 2 MMDVM_Bridges can be done as one instance.

The question is, what exactly are you trying to bridge? That will tell us more about the ends of the bridge.

73, Steve N4IRS

On 1/14/19 10:51 PM, mike@... wrote:
Hey all, 

I'm brand new to the group, but have been experimenting with DMR and P25 for a while. I am looking to build a bridge between P25 and DMR, and have found just enough to confuse me on the 'web. :) 

It looks like I'll need MMDVM_Bridge for sure - but I am unclear what other components I need. I have also seen a post (possibly outdated) that talks about needing gateways, reflectors and a couple of analog bridges... but something is telling me that may not be the case. 

Am I on the right track? Any pointers are appreciated!

Thanks and 73, 
Mike - N6MIK


Re: Help linking P25 to DMR

Steve N4IRS
 

Mike,
Yes you will need those things also. here is a basic diagram:
P25Reflector <-> P25Gateway <-> MMDVM_Bridge <-> Analog_Bridge <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR Master (BM, HB etc)
You will need 2 instances of Analog_Bridge
The 2 MMDVM_Bridges can be done as one instance.

The question is, what exactly are you trying to bridge? That will tell us more about the ends of the bridge.

73, Steve N4IRS

On 1/14/19 10:51 PM, mike@... wrote:
Hey all, 

I'm brand new to the group, but have been experimenting with DMR and P25 for a while. I am looking to build a bridge between P25 and DMR, and have found just enough to confuse me on the 'web. :) 

It looks like I'll need MMDVM_Bridge for sure - but I am unclear what other components I need. I have also seen a post (possibly outdated) that talks about needing gateways, reflectors and a couple of analog bridges... but something is telling me that may not be the case. 

Am I on the right track? Any pointers are appreciated!

Thanks and 73, 
Mike - N6MIK


Help linking P25 to DMR

mike@...
 

Hey all, 

I'm brand new to the group, but have been experimenting with DMR and P25 for a while. I am looking to build a bridge between P25 and DMR, and have found just enough to confuse me on the 'web. :) 

It looks like I'll need MMDVM_Bridge for sure - but I am unclear what other components I need. I have also seen a post (possibly outdated) that talks about needing gateways, reflectors and a couple of analog bridges... but something is telling me that may not be the case. 

Am I on the right track? Any pointers are appreciated!

Thanks and 73, 
Mike - N6MIK


Re: DMR vs DSTAR

Pierre Martel
 

Brain fart! Sorry! 


Le lun. 14 janv. 2019 à 17:26, Steve N4IRS <szingman@...> a écrit :
Uh, no P25 is IMBE

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Pierre Martel <petem001@...>
Sent: Monday, January 14, 2019 4:44:54 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR vs DSTAR
 
Yes dmr is AMBE while Dstar is IMBE

Le lun. 14 janv. 2019 à 16:37, Vincenzo Salamone <it9cdu@...> a écrit :
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

Steve N4IRS
 

My 1841 is here <https://dvswitch.groups.io/g/Quantar-Bridge/topic/router_config/23325590?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,23325590>
There are also a couple in the wiki in the Quantar_Bridge sub group

On 1/14/19 7:29 PM, Mike Clay wrote:
Speaking of P25, does anyone have a Cisco router configuration file for networking a Quantar repeater?
Thanks

Mike AC5XV


Re: DMR vs DSTAR

Mike Clay <Mclay2005@...>
 

Speaking of P25, does anyone have a Cisco router configuration file for networking a Quantar repeater?
Thanks

Mike AC5XV


Re: If you use HBlink OR dmr_utils, you need to read this

Cort N0MJS <n0mjs@...>
 

A bit more now the I’m on a real computer. The way those streams get processed on the TX side, I’ve not found a really efficient way to terminate them with the call end. The efficient place would be right before the stream metadata is used for forwarding, necessitating another check fo the same condition again after forwarding… I’m trying to find a better way, but letting them timeout isn’t a problem. It just keeps entries in a list a few seconds longer.

On Jan 14, 2019, at 4:26 PM, Cort N0MJS via Groups.Io <n0mjs@...> wrote:

Not an error. TX streams have to time out for not. There’s no explicit end for OBP TX streams yet


On Jan 14, 2019, at 2:41 PM, JJ Cummings <cummingsj@...> wrote:

Cort - great stuff I just switched over so the stack now looks like this (for those that care)

DMRLink <-> IPSC_Bridge <-> HB_Bridge <-> hblink3(bridge) <-> Analog_Bridge <-> ASL

On a separate note, I noted a an error in the log specifically related  to openbridge (outbound only connections) looks like it's not registering that the END event has occurred when it happens and thusly it times out?.  Posting here but hopefully I can post a pull request if ever I get time to debug at all.

INFO 2019-01-14 14:16:30,526 (ANALOG_BRIDGE) *CALL END*   STREAM ID: 2752969323 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1, Duration: 3.02
INFO 2019-01-14 14:16:35,780 (OBP-3103) *TIME OUT*   STREAM ID: 2752969323 SUB: 1108389 PEER: 310885350 TGID: 310815 TS 1 Duration: 3.02
INFO 2019-01-14 14:19:21,827 (ANALOG_BRIDGE) *CALL START* STREAM ID: 205043449 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1
INFO 2019-01-14 14:19:21,878 (ANALOG_BRIDGE) Conference Bridge: 310815, Call Bridged to OBP System: OBP-3103 TS: 1, TGID: 310815
INFO 2019-01-14 14:19:24,859 (ANALOG_BRIDGE) *CALL END*   STREAM ID: 205043449 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1, Duration: 3.03
INFO 2019-01-14 14:19:30,780 (OBP-3103) *TIME OUT*   STREAM ID: 205043449 SUB: 1108389 PEER: 310885350 TGID: 310815 TS 1 Duration: 3.03

On Fri, Jan 11, 2019 at 11:04 AM Cort N0MJS via Groups.Io <n0mjs=me.com@groups.io> wrote:
Folks,

PYTHON2 BASED VERSIONS OF HBLINK AND DMR_UTILS ARE NOW SUNSET – ONLY BUG FIXES WILL BE OFFERED.



If you go looking at my repos on GitHub, you’ll see a couple of new things:

HBlink3 and dmr_utils3

These are Python3 versions of HBlink and dmr_utils. Currently, dmr_utils3 does not include ambe_bridge.py and HBlink3 does not include parrot or bridge_all – effectively leaving it as the base stack and the conference bridge application… there have also been some things renamed. I removed “hb_” from the beginning of all of the files, and I also renamed hb_confbridge.py to bridge.py. Likewise I renamed hb_confbridge_rules.py to rules.py. The main goal with the name changes is to make the first character or few unique. I’m a shitty typist to begin with, so being able to type b(tab) and get bridge.py is a lot easier than having to type out hb_confbridge.py all of the time… and I have to type those things a lot when I’m in full-on coding mode :)

As for the future of the other HBlink programs – some of that is going to be dependent on community support. I would love to see someone step up and port all_bridge.py and parrot.py to Python3. I will eventually get to them, but not soon because….

The master branch of HBlink3 is stable and has been running on the K0USY Group’s “KS-DMR” network all week. On our particular system, with the things we have configured, just moving to Python3 (ok, a few bits of refactoring as well) has given us a 15-20% performance boost (measured in time between packet ingress and processing completion). You will also notice another branch of HBlink3 called uvloop. With this branch I’m swapping out the venerable Twisted module for Python3’s built-in Asyncio module, and a “drop in replacement” for portions of it called uvLoop, an ultra-fast drop-in replacement for parts of Asyncio… just moving to Python3 gave us a nice bump. My hope is that the move to uvloop makes HBlink work much faster – potentially rivaling statically compiled to machine-code software.

I’ve already moved off of the master branch to work on the uvloop branch. This development will be rapid – because the goal is to have hblink.py and bridge.py working on uvloop ASAP. Once that is completed, I will go back and start filling in the gaps as well as adding features. I do not intend to back-port new features to the Python2 versions.

The HBlink3 master branch will support the existing python2 hbmonitor software. The uvloop branch will not. I intend to “burn down” the reporting “stuff” and start over with HBlink3 on uvloop. I am looking for javascript (and related browser code) developers to help with this. Hbmonitor is a bandwidth HOG. It renders the entirety of the HTML tables on the server for every incremental change, and pushes all of that HTML out to the browser. A busy system on HBmonitor can use close to 1Mbps of bandwidth for a single browser connected. The goal is to send much less information to the browser, and let the browser build the tables… but I don’t have a clue about programming that stuff. Co-developers welcome!!!

0x49 DE N0MJS



Cort Buffington
785-865-7206





Cort Buffington
785-865-7206


Re: DMR vs DSTAR

Matt Ames
 

Actually, DMR is AMBE2+ while DSTAR is AMBE.

The only protocol that uses IMBE is P25 Phase 1.


On Tue, 15 Jan 2019 at 08:45, Pierre Martel <petem001@...> wrote:
Yes dmr is AMBE while Dstar is IMBE

Le lun. 14 janv. 2019 à 16:37, Vincenzo Salamone <it9cdu@...> a écrit :
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: If you use HBlink OR dmr_utils, you need to read this

Cort N0MJS <n0mjs@...>
 

Not an error. TX streams have to time out for not. There’s no explicit end for OBP TX streams yet


On Jan 14, 2019, at 2:41 PM, JJ Cummings <cummingsj@...> wrote:

Cort - great stuff I just switched over so the stack now looks like this (for those that care)

DMRLink <-> IPSC_Bridge <-> HB_Bridge <-> hblink3(bridge) <-> Analog_Bridge <-> ASL

On a separate note, I noted a an error in the log specifically related  to openbridge (outbound only connections) looks like it's not registering that the END event has occurred when it happens and thusly it times out?.  Posting here but hopefully I can post a pull request if ever I get time to debug at all.

INFO 2019-01-14 14:16:30,526 (ANALOG_BRIDGE) *CALL END*   STREAM ID: 2752969323 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1, Duration: 3.02
INFO 2019-01-14 14:16:35,780 (OBP-3103) *TIME OUT*   STREAM ID: 2752969323 SUB: 1108389 PEER: 310885350 TGID: 310815 TS 1 Duration: 3.02
INFO 2019-01-14 14:19:21,827 (ANALOG_BRIDGE) *CALL START* STREAM ID: 205043449 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1
INFO 2019-01-14 14:19:21,878 (ANALOG_BRIDGE) Conference Bridge: 310815, Call Bridged to OBP System: OBP-3103 TS: 1, TGID: 310815
INFO 2019-01-14 14:19:24,859 (ANALOG_BRIDGE) *CALL END*   STREAM ID: 205043449 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1, Duration: 3.03
INFO 2019-01-14 14:19:30,780 (OBP-3103) *TIME OUT*   STREAM ID: 205043449 SUB: 1108389 PEER: 310885350 TGID: 310815 TS 1 Duration: 3.03

On Fri, Jan 11, 2019 at 11:04 AM Cort N0MJS via Groups.Io <n0mjs=me.com@groups.io> wrote:
Folks,

PYTHON2 BASED VERSIONS OF HBLINK AND DMR_UTILS ARE NOW SUNSET – ONLY BUG FIXES WILL BE OFFERED.



If you go looking at my repos on GitHub, you’ll see a couple of new things:

HBlink3 and dmr_utils3

These are Python3 versions of HBlink and dmr_utils. Currently, dmr_utils3 does not include ambe_bridge.py and HBlink3 does not include parrot or bridge_all – effectively leaving it as the base stack and the conference bridge application… there have also been some things renamed. I removed “hb_” from the beginning of all of the files, and I also renamed hb_confbridge.py to bridge.py. Likewise I renamed hb_confbridge_rules.py to rules.py. The main goal with the name changes is to make the first character or few unique. I’m a shitty typist to begin with, so being able to type b(tab) and get bridge.py is a lot easier than having to type out hb_confbridge.py all of the time… and I have to type those things a lot when I’m in full-on coding mode :)

As for the future of the other HBlink programs – some of that is going to be dependent on community support. I would love to see someone step up and port all_bridge.py and parrot.py to Python3. I will eventually get to them, but not soon because….

The master branch of HBlink3 is stable and has been running on the K0USY Group’s “KS-DMR” network all week. On our particular system, with the things we have configured, just moving to Python3 (ok, a few bits of refactoring as well) has given us a 15-20% performance boost (measured in time between packet ingress and processing completion). You will also notice another branch of HBlink3 called uvloop. With this branch I’m swapping out the venerable Twisted module for Python3’s built-in Asyncio module, and a “drop in replacement” for portions of it called uvLoop, an ultra-fast drop-in replacement for parts of Asyncio… just moving to Python3 gave us a nice bump. My hope is that the move to uvloop makes HBlink work much faster – potentially rivaling statically compiled to machine-code software.

I’ve already moved off of the master branch to work on the uvloop branch. This development will be rapid – because the goal is to have hblink.py and bridge.py working on uvloop ASAP. Once that is completed, I will go back and start filling in the gaps as well as adding features. I do not intend to back-port new features to the Python2 versions.

The HBlink3 master branch will support the existing python2 hbmonitor software. The uvloop branch will not. I intend to “burn down” the reporting “stuff” and start over with HBlink3 on uvloop. I am looking for javascript (and related browser code) developers to help with this. Hbmonitor is a bandwidth HOG. It renders the entirety of the HTML tables on the server for every incremental change, and pushes all of that HTML out to the browser. A busy system on HBmonitor can use close to 1Mbps of bandwidth for a single browser connected. The goal is to send much less information to the browser, and let the browser build the tables… but I don’t have a clue about programming that stuff. Co-developers welcome!!!

0x49 DE N0MJS



Cort Buffington
785-865-7206





Re: DMR vs DSTAR

Steve N4IRS
 

Uh, no P25 is IMBE

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Pierre Martel <petem001@...>
Sent: Monday, January 14, 2019 4:44:54 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] DMR vs DSTAR
 
Yes dmr is AMBE while Dstar is IMBE

Le lun. 14 janv. 2019 à 16:37, Vincenzo Salamone <it9cdu@...> a écrit :
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

philippe st-cyr
 

I look that tonight 


Le lun. 14 janv. 2019 5:03 p.m., JJ Cummings <cummingsj@...> a écrit :
You are correct, I think that you have to use the DV3000... too many transcode projects right now and I mixed them up lol... though to be fair I have not tried it with md380emu

On Mon, Jan 14, 2019 at 2:58 PM Steve KC1AWV <smiller@...> wrote:
JJ -
I've tried doing something similar on xlxd with md380-emu, but the issue I ran into was that ambed looks for a hardware device(s) for transcoding, and the startup for xlxd looks for an ambed service running to perform transcoding. I was unable to fit md380-emu in there.

Unless there's another path or setup that I'm overlooking that ignores ambed, which I would be really interested in.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:50 PM JJ Cummings <cummingsj@...> wrote:
I think that md380-emu, as I noted before, (included in the DVSwitch package install) will do this, that's what we are using...

On Mon, Jan 14, 2019 at 2:48 PM Steve KC1AWV <smiller@...> wrote:
Correct. The reason is that there does not exist a good open software codec to transcode D-Star (AMBE) and DMR (AMBE2+) as far as I know. So, some sort of AMBE hardware chip, like the DV3000, is used instead.

For example, I run two NW Digital ThumbDV dongles in my ambed server to transcode D-Star <-> DMR. I haven't used YSF (AMBE2+) or P25 (IMBE) but the idea may be the same, just would need more dongles to transcode more streams on the same module.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:37 PM Vincenzo Salamone <it9cdu@...> wrote:
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

Steve KC1AWV
 

No worries, but you did give me an idea! I'll whip up a couple tests and see what I can think of to try and transcode sans-DV3000.

Steve KC1AWV


On Mon, Jan 14, 2019 at 5:03 PM JJ Cummings <cummingsj@...> wrote:
You are correct, I think that you have to use the DV3000... too many transcode projects right now and I mixed them up lol... though to be fair I have not tried it with md380emu

On Mon, Jan 14, 2019 at 2:58 PM Steve KC1AWV <smiller@...> wrote:
JJ -
I've tried doing something similar on xlxd with md380-emu, but the issue I ran into was that ambed looks for a hardware device(s) for transcoding, and the startup for xlxd looks for an ambed service running to perform transcoding. I was unable to fit md380-emu in there.

Unless there's another path or setup that I'm overlooking that ignores ambed, which I would be really interested in.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:50 PM JJ Cummings <cummingsj@...> wrote:
I think that md380-emu, as I noted before, (included in the DVSwitch package install) will do this, that's what we are using...

On Mon, Jan 14, 2019 at 2:48 PM Steve KC1AWV <smiller@...> wrote:
Correct. The reason is that there does not exist a good open software codec to transcode D-Star (AMBE) and DMR (AMBE2+) as far as I know. So, some sort of AMBE hardware chip, like the DV3000, is used instead.

For example, I run two NW Digital ThumbDV dongles in my ambed server to transcode D-Star <-> DMR. I haven't used YSF (AMBE2+) or P25 (IMBE) but the idea may be the same, just would need more dongles to transcode more streams on the same module.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:37 PM Vincenzo Salamone <it9cdu@...> wrote:
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

JJ Cummings
 

You are correct, I think that you have to use the DV3000... too many transcode projects right now and I mixed them up lol... though to be fair I have not tried it with md380emu


On Mon, Jan 14, 2019 at 2:58 PM Steve KC1AWV <smiller@...> wrote:
JJ -
I've tried doing something similar on xlxd with md380-emu, but the issue I ran into was that ambed looks for a hardware device(s) for transcoding, and the startup for xlxd looks for an ambed service running to perform transcoding. I was unable to fit md380-emu in there.

Unless there's another path or setup that I'm overlooking that ignores ambed, which I would be really interested in.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:50 PM JJ Cummings <cummingsj@...> wrote:
I think that md380-emu, as I noted before, (included in the DVSwitch package install) will do this, that's what we are using...

On Mon, Jan 14, 2019 at 2:48 PM Steve KC1AWV <smiller@...> wrote:
Correct. The reason is that there does not exist a good open software codec to transcode D-Star (AMBE) and DMR (AMBE2+) as far as I know. So, some sort of AMBE hardware chip, like the DV3000, is used instead.

For example, I run two NW Digital ThumbDV dongles in my ambed server to transcode D-Star <-> DMR. I haven't used YSF (AMBE2+) or P25 (IMBE) but the idea may be the same, just would need more dongles to transcode more streams on the same module.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:37 PM Vincenzo Salamone <it9cdu@...> wrote:
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

Steve KC1AWV
 

JJ -
I've tried doing something similar on xlxd with md380-emu, but the issue I ran into was that ambed looks for a hardware device(s) for transcoding, and the startup for xlxd looks for an ambed service running to perform transcoding. I was unable to fit md380-emu in there.

Unless there's another path or setup that I'm overlooking that ignores ambed, which I would be really interested in.

Steve KC1AWV


On Mon, Jan 14, 2019 at 4:50 PM JJ Cummings <cummingsj@...> wrote:
I think that md380-emu, as I noted before, (included in the DVSwitch package install) will do this, that's what we are using...

On Mon, Jan 14, 2019 at 2:48 PM Steve KC1AWV <smiller@...> wrote:
Correct. The reason is that there does not exist a good open software codec to transcode D-Star (AMBE) and DMR (AMBE2+) as far as I know. So, some sort of AMBE hardware chip, like the DV3000, is used instead.

For example, I run two NW Digital ThumbDV dongles in my ambed server to transcode D-Star <-> DMR. I haven't used YSF (AMBE2+) or P25 (IMBE) but the idea may be the same, just would need more dongles to transcode more streams on the same module.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:37 PM Vincenzo Salamone <it9cdu@...> wrote:
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

JJ Cummings
 

I think that md380-emu, as I noted before, (included in the DVSwitch package install) will do this, that's what we are using...


On Mon, Jan 14, 2019 at 2:48 PM Steve KC1AWV <smiller@...> wrote:
Correct. The reason is that there does not exist a good open software codec to transcode D-Star (AMBE) and DMR (AMBE2+) as far as I know. So, some sort of AMBE hardware chip, like the DV3000, is used instead.

For example, I run two NW Digital ThumbDV dongles in my ambed server to transcode D-Star <-> DMR. I haven't used YSF (AMBE2+) or P25 (IMBE) but the idea may be the same, just would need more dongles to transcode more streams on the same module.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:37 PM Vincenzo Salamone <it9cdu@...> wrote:
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

Steve KC1AWV
 

Correct. The reason is that there does not exist a good open software codec to transcode D-Star (AMBE) and DMR (AMBE2+) as far as I know. So, some sort of AMBE hardware chip, like the DV3000, is used instead.

For example, I run two NW Digital ThumbDV dongles in my ambed server to transcode D-Star <-> DMR. I haven't used YSF (AMBE2+) or P25 (IMBE) but the idea may be the same, just would need more dongles to transcode more streams on the same module.

Steve KC1AWV


On Mon, Jan 14, 2019 at 4:37 PM Vincenzo Salamone <it9cdu@...> wrote:
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: DMR vs DSTAR

Pierre Martel
 

Yes dmr is AMBE while Dstar is IMBE


Le lun. 14 janv. 2019 à 16:37, Vincenzo Salamone <it9cdu@...> a écrit :
Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV


Re: If you use HBlink OR dmr_utils, you need to read this

JJ Cummings
 

Cort - great stuff I just switched over so the stack now looks like this (for those that care)

DMRLink <-> IPSC_Bridge <-> HB_Bridge <-> hblink3(bridge) <-> Analog_Bridge <-> ASL

On a separate note, I noted a an error in the log specifically related  to openbridge (outbound only connections) looks like it's not registering that the END event has occurred when it happens and thusly it times out?.  Posting here but hopefully I can post a pull request if ever I get time to debug at all.

INFO 2019-01-14 14:16:30,526 (ANALOG_BRIDGE) *CALL END*   STREAM ID: 2752969323 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1, Duration: 3.02
INFO 2019-01-14 14:16:35,780 (OBP-3103) *TIME OUT*   STREAM ID: 2752969323 SUB: 1108389 PEER: 310885350 TGID: 310815 TS 1 Duration: 3.02
INFO 2019-01-14 14:19:21,827 (ANALOG_BRIDGE) *CALL START* STREAM ID: 205043449 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1
INFO 2019-01-14 14:19:21,878 (ANALOG_BRIDGE) Conference Bridge: 310815, Call Bridged to OBP System: OBP-3103 TS: 1, TGID: 310815
INFO 2019-01-14 14:19:24,859 (ANALOG_BRIDGE) *CALL END*   STREAM ID: 205043449 SUB: 1108389 (1108389) PEER: 310857 (310857) TGID 310815 (310815), TS 1, Duration: 3.03
INFO 2019-01-14 14:19:30,780 (OBP-3103) *TIME OUT*   STREAM ID: 205043449 SUB: 1108389 PEER: 310885350 TGID: 310815 TS 1 Duration: 3.03

On Fri, Jan 11, 2019 at 11:04 AM Cort N0MJS via Groups.Io <n0mjs=me.com@groups.io> wrote:
Folks,

PYTHON2 BASED VERSIONS OF HBLINK AND DMR_UTILS ARE NOW SUNSET – ONLY BUG FIXES WILL BE OFFERED.



If you go looking at my repos on GitHub, you’ll see a couple of new things:

HBlink3 and dmr_utils3

These are Python3 versions of HBlink and dmr_utils. Currently, dmr_utils3 does not include ambe_bridge.py and HBlink3 does not include parrot or bridge_all – effectively leaving it as the base stack and the conference bridge application… there have also been some things renamed. I removed “hb_” from the beginning of all of the files, and I also renamed hb_confbridge.py to bridge.py. Likewise I renamed hb_confbridge_rules.py to rules.py. The main goal with the name changes is to make the first character or few unique. I’m a shitty typist to begin with, so being able to type b(tab) and get bridge.py is a lot easier than having to type out hb_confbridge.py all of the time… and I have to type those things a lot when I’m in full-on coding mode :)

As for the future of the other HBlink programs – some of that is going to be dependent on community support. I would love to see someone step up and port all_bridge.py and parrot.py to Python3. I will eventually get to them, but not soon because….

The master branch of HBlink3 is stable and has been running on the K0USY Group’s “KS-DMR” network all week. On our particular system, with the things we have configured, just moving to Python3 (ok, a few bits of refactoring as well) has given us a 15-20% performance boost (measured in time between packet ingress and processing completion). You will also notice another branch of HBlink3 called uvloop. With this branch I’m swapping out the venerable Twisted module for Python3’s built-in Asyncio module, and a “drop in replacement” for portions of it called uvLoop, an ultra-fast drop-in replacement for parts of Asyncio… just moving to Python3 gave us a nice bump. My hope is that the move to uvloop makes HBlink work much faster – potentially rivaling statically compiled to machine-code software.

I’ve already moved off of the master branch to work on the uvloop branch. This development will be rapid – because the goal is to have hblink.py and bridge.py working on uvloop ASAP. Once that is completed, I will go back and start filling in the gaps as well as adding features. I do not intend to back-port new features to the Python2 versions.

The HBlink3 master branch will support the existing python2 hbmonitor software. The uvloop branch will not. I intend to “burn down” the reporting “stuff” and start over with HBlink3 on uvloop. I am looking for javascript (and related browser code) developers to help with this. Hbmonitor is a bandwidth HOG. It renders the entirety of the HTML tables on the server for every incremental change, and pushes all of that HTML out to the browser. A busy system on HBmonitor can use close to 1Mbps of bandwidth for a single browser connected. The goal is to send much less information to the browser, and let the browser build the tables… but I don’t have a clue about programming that stuff. Co-developers welcome!!!

0x49 DE N0MJS



Cort Buffington
785-865-7206





Re: ASL to XLX in DSTAR mode ?

Ken KE2N
 

Hi Santu,

 

The point of my posting was to say that you can run the transcoder on a separate PC (and that you should use hardware for DSTAR).

 

My setup is probably not what you want.  The ASL link is to a DMR talk group:

Asterisk <-> chan_USRP <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR TG

I have used the emulator with this, but right now I am running it with a ThumbDV.  That dongle is plugged directly into the DVSwitch PC.

 

The remotely-accessed AMBED setup is for another system that links DSTAR to C4FM. 

That one uses the XLX reflector to connect to C4FM by means of an Open Spot which translates DMRmmdvm to C4FM (RF) at the Fusion repeater location.

The XLX reflector runs in the Cloud and accesses any required transcoding from a Raspberry Pi running AMBED and with a 6 channel fob from NW Digital.

Two AMBE channels are required for my link, leaving 4 channels for up to 2 additional links by other users.

DV Switch is not used at all for that link.

 

73

Ken

 

From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Santu OTTAVI (TK1BI)
Sent: Monday, January 14, 2019 3:10 PM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] ASL to XLX in DSTAR mode ?

 

Hi Ken,

Le 13/01/2019 à 17:59, Ken KE2N via Groups.Io a écrit :

We do that for XLX725, for example - it seems to be pretty reliable, at least with the services we use....    


Are you using the following setup for linking ASL with XLX using D-Star ?

Asterisk <-> chan_USRP <-> Analog_Bridge <-> MMDVM_Bridge <-> ircddbgatewayd <-> XLX


Tht's what I'm trying to do, with hardware AMBE encoder (AMBEServer on rPi with a ThumbDV), but it seems I'm still missing something :

When talking in D-Star on XLX, I can see on MMDVM_Bridge :

M: 2019-01-14 19:48:02.113 D-Star, received network header from TK1BI   /X755 to CQCQCQ   via XRF755 K
D: 2019-01-14 19:48:02.716 D-Star, lost audio for 300ms filling in, elapsed: 603ms, expected: 30, received: 0
D: 2019-01-14 19:48:03.023 D-Star, lost audio for 300ms filling in, elapsed: 910ms, expected: 45, received: 28
D: 2019-01-14 19:48:03.324 D-Star, lost audio for 300ms filling in, elapsed: 1211ms, expected: 60, received: 43
M: 2019-01-14 19:48:03.616 D-Star, network watchdog has expired, 1.2 seconds,  98% packet loss, BER: 0.0%


And when talking on the analog side, lots of

D: 2019-01-14 19:55:21.379 D-Star Network Data Sent
D: 2019-01-14 19:55:21.379 0000:  44 53 52 50 21 18 70 01 00 0E 46 12 2B 23 06 7C    *DSRP!.p...F.+#.|*
D: 2019-01-14 19:55:21.379 0010:  60 F8 16 29 F5  

but no voice at all, and gateway callsign not heard on the XLX side.

In both cases, ircddbgateway does not seem to be much verbose. I didn't manage to get anything in the log after that :

M: 2019-01-14 20:02:06: DCS link to DCS755 K established
M: 2019-01-14 20:02:06: Starting the Callsign Server thread

--
As most of the setups seem to be using DMR, and as my XLX has AMBE transcoding, I may have a try in DMR mode (with DMRGateway instead of ircddbgateway). But before doing that, I'd like to know if the D-Star setup described above works.

Thank you in advance. 73 de TK1BI


Re: DMR vs DSTAR

Vincenzo Salamone <it9cdu@...>
 

Ok, so I need necessarily some hardware for transcode DMR--->Dstar and viceversa?

Il giorno lun 14 gen 2019 alle ore 22:33 Steve KC1AWV <smiller@...> ha scritto:
In my case, I run ambed on a server at home, separate from my XLX server that's in a data center. The ambed service (included with xlxd) runs the transcoding for D-Star <-> DMR for the XLX server. In order to achieve transcoding, some DV3000 dongles are attached to the ambed server.

This setup is a bit more advanced/customized, since I have services running on separate servers. Also, we're talking more along the lines of xlxd now, which is out of scope for the DVSwitch group.

Steve KC1AWV

On Mon, Jan 14, 2019 at 4:04 PM Vincenzo Salamone <it9cdu@...> wrote:
OK Steve,
now all the connections seems to work, but, no audio pass from dstar to dmr .... the transmission is MUTE. Maybe I need some AMBE codec to install ?

Il giorno lun 14 gen 2019 alle ore 19:58 Steve KC1AWV <smiller@...> ha scritto:
The connection between MMDVM_Bridge to DMRGateway here is like this:

---
MMDVM_Bridge.ini

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

---
DMRGateway.ini

[General]
Timeout=10
# RFTimeout=10
# NetTimeout=7
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

I assume you're running both programs on the same machine, so all addresses will be loopback.

Steve KC1AWV

On Mon, Jan 14, 2019 at 1:49 PM Vincenzo Salamone <it9cdu@...> wrote:
Thank's Steve,
XLX connection is ok now. Can you give me an example how to "Set MMDVM_Bridge to send its audio to DMRGateway" ?

tnx

Il giorno lun 14 gen 2019 alle ore 19:03 Steve KC1AWV <smiller@...> ha scritto:
If you are connecting to XLX, I used DMRGateway as well as MMDVM_Bridge. In DMRGateway.ini, you can set the XLX Network stanza similar to this:

[XLX Network]
Enabled=1
File=/var/lib/mmdvm/XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
Slot=2
TG=6
Base=64000
Startup=740
Relink=60
Debug=0
Id=
UserControl=1
Module=B

Of course, use your own DMR ID on the Id= line. Set MMDVM_Bridge to send its audio to DMRGateway.

Steve KC1AWV

On Mon, Jan 14, 2019 at 12:57 PM Vincenzo Salamone <it9cdu@...> wrote:
Hi,
I want to bridge DMR to an XLX module, I understand that I can use the DVSwitch tools and MMDVM_Bridge. I have to create 2 instances of MMDVM_Bridge but I don't understand how connect to a specific module of XLX one instance of MMDVM_Bridge.
Anyone ca help me to better understand?
thank's

73 de IT9CDU



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV



--
Steve Miller
KC1AWV

7721 - 7740 of 10557