Date   

Connect Fusion repeater to DMR

Chris WB4ULK
 

This is just a general question about YSF.
We have a Fusion machine here in town linked to my local DMR TG using an Open Spot.

If we wanted to move it off the Open Spot to a server based solution what in the wide world of sports do we connect the Fusion repeater too?

What does the Fusion machine point to?
How does it get there? (Interface)

I understand the concept of a bridge server taking DMR to C4FM and back.
I am just missing the fundemental block of making the Fusion machine talk to some THING.

Do we need one of the “Yaesu” boxes to get the machine into a network, or is there another more elegant way of getting it there?

Chris
WB4ULK


Re: Documentation feedback

Mike Zingman - N4IRR
 

I also updated the dmr to dstar section of the doc. See if it helps. 


Documentation feedback

TG9AOR
 

It does help very much. Thank you for your detailed response. I will review everything and report back. 
--
José Roberto Ruíz García Salas
TG9AOR


locked Re: First draft of overall DVSwitch documentation.

Mike Zingman - N4IRR
 

José,

So because of your document, I was able to implement the DMR to YSF interconnect.
Thank you for your feedback, we are still adding information to the outline as well as creating concrete example documents (ASL <-> DMR), etc.  Your comments help us improve the doc and every question adds to the group knowledge base.  

I did, however, had to mkdir another completely separate directory and copy the contents of MMDVM_Bridge into it, because I figured the instance already running ASL<-->Echolink<---->DMR might get affected, as the DVSwitch ini needs modification to reflect the fact that I am going to use ports 35100 and 35103 for YSF and not the 31100 and 31103 for DMR and ASL.
There are several ways to segment ini files.  Each application (AB, MB, etc) takes command line arguments to help you.  Some people prefer to have separate directories, others prefer to use one directory and name the ini files unique names.  It is up to you.  You are correct, a single instance of MB can not service two bridges with a common mode (in your case ASL <-> DMR and YSFn <-> DMR).  For this to work, you need two instances of MB and two DVSwitch.ini files.  If you wanted to have them in the same directory, you would need to use the environment variable DVSWITCH to point each instance at its ini file.  If you created ini files with names to represent your intended activity, It would look like:

DVSWITCH=./DVSwitch_ASLtoDMR.ini MMDVM_Bridge ./MMDVM_Bridge_ASLtoDMR.ini
and
DVSWITCH=./DVSwitch_YSFtoDMR.ini MMDVM_Bridge ./MMDVM_Bridge_YSFtoDMR.ini

But, your method works just fine and I would not change it.
Does each Analog Bridge instance needs its own DV300U?
Yes.  In order to encode or decode in a specific mode (DMR, DSATR, etc) you must dedicate a DV3000U to that process.  However, in your case, do not forget that you also have the emulator for AMBE encodes/decodes.  Like the DV3000U you should dedicate a "process" to each AB instance, but that just means you have to launch each emulator with a unique port to communicate to AB through.

I could not make out the diagram that explains the port assignment.
Sorry!  A really need to use a real drawing program rather than ASCII art.  It main point of the diagram is that each step along the way needs to communicate with its "partner" through a common set of ports.  Transmit (TXPort) on one side is the same as RXPort on the other.  Regardless of the data type moving from one process to another, just select a complementary set of ports and you will be good.  Make sure that you do not reuse those ports someplace else in your system by using netstat -unap. 

but the audio never went out over to DMR 

This is where the ini and log files are needed to debug.  The ini files will show us the ports you assigned to each step and the log files will show us what happens when data is presented to a port.
I had the wrong audio format

Whenever you see this message you are sending the wrong audio type (TLV) to MB.  For that mode look at the RXPort.  Now go find all TXPorts in your system that match it.  Are they all the same AMBE/IMBE/DSAMBE type?  If AB is sending type A and MB is expecting type B you will see this message.  Look at the sender.

Hope this helps
Mike


locked Re: First draft of overall DVSwitch documentation.

TG9AOR
 

So because of your document, I was able to implement the DMR to YSF interconnect. The explanation helped me very much. I did, however, had to mkdir another completely separate directory and copy the contents of MMDVM_Bridge into it, because I figured the instance already running ASL<-->Echolink<---->DMR might get affected, as the DVSwitch ini needs modification to reflect the fact that I am going to use ports 35100 and 35103 for YSF and not the 31100 and 31103 for DMR and ASL. Many thanks, and my appreciation to Corey Dean N3FE for giving me a link for YSFReflector Guatemala all this time. I am now able to do this by means of the DVSwitch program. I only had to run one instance of MMDVM_Bridge to accomplish the link from BrandMeister to the YSFReflector, I did not interpret your drawing this way, however. The drawing I take it to be two instances of MMDVM_Bridge running, one for the BM side and the other for the YSFn. I do reiterate that without this document I would not have been able to accomplish this and I thank you very much.

Now, I do have questions regarding the transcoding process from BrandMeister over to DSTAR:
  1. Does each Analog Bridge instance needs its own DV300U? I do have two and ran Analog Bridge AB1.ini bound to /dev/ttyUSB0 and Analog Bridge AB2.ini bound to /dev/ttyUSB1 However, each one does its thing but it does not pass data on to the other side, as if PCM stays there but does not get exported on to the other network. AB1.ini is on the DSTAR side and I used the DSTAR recommended ports (32100 32103) and does light up when TXing on DSTAR HT. Same thing on AB2.ini, DMR gets in and the ThumbDV lights up, but no audio goes through on to DSTAR. Also, AB1 has DSTAR on ambeMode and AB2.ini has DMR on the ambeMode setting.
  2. I could not make out the diagram that explains the port assignment. I gave it the last try by assigning the 31100 and 31103 ports on the AMBE AUDIO section of AB1.ini(DSTAR AB) but same results.
  3. I also tried running one instance of MMDVM_Bridge enabling DMR and DSTAR, both networks get logged in, I am able to switch reflector modules with ircddbgateway and also assign a static talk group with BrandMeister Selfcare.
  4. XLX502 already has four transcoding channels available, and as I keyed up on DSTAR the transcoders lit up as well as the ThumbDV on AB1, but the audio never went out over to DMR, at least the DMR radio never lit up.
Before doing all this, I was able to use the YSFn instance of MMDVM_Bridge with DSTAR enabled and was able to link up to the reflector but the output said that I had the wrong audio format (I do not recall the exact long line but said something like expecting AMBE and got DSAMBE or something similar, sorry, not wanting to paste a long log here)

Thanks Steve and hopefully I did not make you fall asleep with my sad story here hi.

73 

--
José Roberto Ruíz García Salas
TG9AOR


locked Re: First draft of overall DVSwitch documentation.

Pablo <ea4fvb@...>
 

Great Job Steve

73 Pablo - EA4FVB


locked Re: First draft of overall DVSwitch documentation.

EA5GVK Joaquin
 

Excellent, Many Thx.
Joaquin Madrid
EA5GVK.


Re: Building a private network with (mostly) MMDVM P25 repeaters

Steve N4IRS
 

One thing I forgot to mention is that we have broken out subgroups for more topic centric discussions. That is not to say that you can't discuss whatever you want in the main group. By keeping the conversation in subgroups it may make it a little easier to find something. Here is the link for the Quantar subgroup: https://dvswitch.groups.io/g/Quantar-Bridge


73, Steve 


locked Re: First draft of overall DVSwitch documentation.

TG9AOR
 

Excellent! Many thanks. Will go and read now.
--
José Roberto Ruíz García Salas
TG9AOR


locked First draft of overall DVSwitch documentation.

Steve N4IRS
 

We have created the first overall document covering all of the new DVSwitch programs. This started as an outline and grew. It is in Google Docs so that people always have access to the latest and greatest. We are putting the first howto together for a simple bridge and will expand after that. Neither Mike or I are document writers so please bare with us. 

DVSwitch Documentation

73, Steve N4IRS 


Re: Building a private network with (mostly) MMDVM P25 repeaters

Robert Johnson
 

Steve,

Thanks!

The transcode bridge is the part I’m -least- interested in - I work for a major console vendor - I know what that sounds like, and even on a well optimized, designed for the purpose system, it ‘good' is not a primary descriptor I would use to describe how it sounds - somewhere between ‘ok’ and ‘potato’ would be a more apt descriptor.

Also, I’m very pleased to see you guys support Debian/Ubuntu, my fear was RHEL/CentOS, which I hate administering ;-)

Robert Johnson
---
Telegram: @alohawolf
Telephone:+1-562-286-4255
C*NET: 18219881
Email:aloha@blastpuppy.com
--
"Follow the path of the unsafe, independent thinker. Expose your ideas to the danger of controversy. Speak your mind and fear less the label of "crackpot" than the stigma of conformity."

- Thomas J. Watson Sr.

On Jun 5, 2018, at 7:50 PM, Steve N4IRS <szingman@msgstor.com> wrote:

Robert,
Well, I can tell you in a half hour you pretty much got it. The short answer to your questions is yes. Now the fun begins. I suggest you build out slowly and take the transcode bridge last.

Welcome to the group.

73, Steve N4IRS

On 06/05/2018 10:43 PM, Robert Johnson wrote:
So, I've been searching thru the message archive for a half an hour, without much luck, and I'm wondering some things.

There are about 10 of us in the larger pacific northwest who are potentially interested in building our own little semi-private MMDVM based network - all of us have P25 hardware, but some of us are getting on the DMR bandwagon now too - those of us with DMR are using the local (and wonderful may I note) DCI PNW DMR network - but we're all rag chewers, and (I at least) feel bad about chewing up someone elses resources to sit and flap our gums. We more or less all have needed hardware to build an MMDVM based network.

So, what we're wondering is, how hard is it to do the following, and is DVSwitch the missing link we've been looking for to link ourselves together by:

Creating a heterogeneous linked P25 network (some Quantars, but mostly MMDVM based repeaters).
Optionally, adding DMR based sites in as well (which I know comes with the pain of transcoding).
Creating a linked DMR only network of repeaters.
Doing this without having an always on tie up to a larger established network - without closing the door to a connection to brandmeister or some other network.

I discovered the MMDVM project about three months ago, and I've been looking for the missing link to tie MMDVM repeaters together on P25 - and today I discovered this - can DVSwitch be the missing link we've been looking for?

Thanks and 73's
Robert Johnson
K6WLF


Re: "Blocked" Message on Brandmeister

Steven Blackford
 

Hey Steve,
    We have had this problem on 2 ASL<->DMR bridges when there was a lot of traffic going on. iE, nets on TheGuild TG & ASL node 47374. I installed a the bridge in a secondary node that’s connected most of the time. but several times when the Morning Net was going on that’s attached to EchoLink & IRLP besides ALS, they were having the problem with being blocked on DMR. The loopban tool took it as too many key ups on n a short amount of time, you’d have to shutdown the MMDVM side of the bridge for an hour. I’ve also had the same problem on TG 31444 with a similar problem.  Jason talked to Corey about it. Since making the changes to both bridges, the problem hasn’t returned yet. Just passing on the info while waiting for an array to boot up. 73 de K4SQI!

Steve, K4SQI 

On Tue, Jun 5, 2018 at 22:51 Steve N4IRS <szingman@...> wrote:
So,
I have a couple of questions:
1: What type of bridges are experiencing the problem? Analog to digital? digital to digital?
The default hang value is 2000 ms in Analog_Bridge.ini Which equates to the minimum time presented to BM. A signal can not be less then this value. This was implemented to alleviate the loop detector issue.

Here is the default output from MMDVM Bridge:
I: 2018-06-06 01:57:23.512 DMR Network Parameters
I: 2018-06-06 01:57:23.512     Mode Hang: 3s
I: 2018-06-06 02:26:55.222 DMR RF Parameters
I: 2018-06-06 01:57:23.558     Call Hang: 3s
I: 2018-06-06 01:57:23.558     TX Hang: 3s
I: 2018-06-06 01:57:23.558     Mode Hang: 10s

I won't paste the default MMDVM_Bridge.ini but you will find that the values already mirror the suggested values.
We appreciate your efforts, however since we already dealt with the loop detector we could have helped trouble shoot this.

73, Steve N4IRS


On 06/05/2018 09:35 PM, Steven Blackford wrote:
Try these settings for a way to deal with the loop fixer on the BM Network. We have noticed it on a couple of bridges & has solved the issue so far for us.  Hope it helps. 73 de K4SQI!

Steve @ work. :-)



---------- Forwarded message ---------
From: Jason Ford <w4jmf@...>
Date: Wed, May 30, 2018 at 13:57
Subject: "Blocked" Message on Brandmeister
To: Steven Blackford <kb7sqi@...>, Wayne Cornish <g7oki@...>, Jeffrey Lehman, KC8QCH <kc8qch@...>


Greetings Gents:
After much research and a chat with the BM Admins, I have discovered the source of the problem for the blocked message.

All BM Masters run LoopBan.  If the server sees 5 calls shorter than 2 seconds over a 1 minute time, it will think it is a loop and place a 10 minute ban on the call.  LoopBans are in place for 1 hour automatically.  

With this in mind I went into the MMDVM_Bridge settings and made a couple of adjustments to the settings:
[General]
RFModeHang=0 . changed to 10
NetModeHang=0, changed to 3
[DMR]
CallHang=0, changed to 3
TXHang=0, changed to 3

My thought process here is that if the 2 second mark is key, just make all TX's at least 2 secs.  So far today, I have not seen the issues from before.

Just sharing my experiments for future reference.

Jason Ford, W4JMF
Executive Director
World Wide Amateur Radio Guild Inc.

CONFIDENTIALITY NOTICE:
The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. 

--
-----
Steve, kb7sqi@...

--
-----
Steve, kb7sqi@...


Re: "Blocked" Message on Brandmeister

Steve N4IRS
 

So,
I have a couple of questions:
1: What type of bridges are experiencing the problem? Analog to digital? digital to digital?
The default hang value is 2000 ms in Analog_Bridge.ini Which equates to the minimum time presented to BM. A signal can not be less then this value. This was implemented to alleviate the loop detector issue.

Here is the default output from MMDVM Bridge:
I: 2018-06-06 01:57:23.512 DMR Network Parameters
I: 2018-06-06 01:57:23.512     Mode Hang: 3s
I: 2018-06-06 02:26:55.222 DMR RF Parameters
I: 2018-06-06 01:57:23.558     Call Hang: 3s
I: 2018-06-06 01:57:23.558     TX Hang: 3s
I: 2018-06-06 01:57:23.558     Mode Hang: 10s

I won't paste the default MMDVM_Bridge.ini but you will find that the values already mirror the suggested values.
We appreciate your efforts, however since we already dealt with the loop detector we could have helped trouble shoot this.

73, Steve N4IRS

On 06/05/2018 09:35 PM, Steven Blackford wrote:
Try these settings for a way to deal with the loop fixer on the BM Network. We have noticed it on a couple of bridges & has solved the issue so far for us.  Hope it helps. 73 de K4SQI!

Steve @ work. :-)



---------- Forwarded message ---------
From: Jason Ford <w4jmf@...>
Date: Wed, May 30, 2018 at 13:57
Subject: "Blocked" Message on Brandmeister
To: Steven Blackford <kb7sqi@...>, Wayne Cornish <g7oki@...>, Jeffrey Lehman, KC8QCH <kc8qch@...>


Greetings Gents:
After much research and a chat with the BM Admins, I have discovered the source of the problem for the blocked message.

All BM Masters run LoopBan.  If the server sees 5 calls shorter than 2 seconds over a 1 minute time, it will think it is a loop and place a 10 minute ban on the call.  LoopBans are in place for 1 hour automatically.  

With this in mind I went into the MMDVM_Bridge settings and made a couple of adjustments to the settings:
[General]
RFModeHang=0 . changed to 10
NetModeHang=0, changed to 3
[DMR]
CallHang=0, changed to 3
TXHang=0, changed to 3

My thought process here is that if the 2 second mark is key, just make all TX's at least 2 secs.  So far today, I have not seen the issues from before.

Just sharing my experiments for future reference.

Jason Ford, W4JMF
Executive Director
World Wide Amateur Radio Guild Inc.

CONFIDENTIALITY NOTICE:
The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. 

--
-----
Steve, kb7sqi@...


Re: Building a private network with (mostly) MMDVM P25 repeaters

Steve N4IRS
 

Robert,
Well, I can tell you in a half hour you pretty much got it. The short answer to your questions is yes. Now the fun begins. I suggest you build out slowly and take the transcode bridge last.

Welcome to the group.

73, Steve N4IRS

On 06/05/2018 10:43 PM, Robert Johnson wrote:
So, I've been searching thru the message archive for a half an hour, without much luck, and I'm wondering some things.

There are about 10 of us in the larger pacific northwest who are potentially interested in building our own little semi-private MMDVM based network - all of us have P25 hardware, but some of us are getting on the DMR bandwagon now too - those of us with DMR are using the local (and wonderful may I note) DCI PNW DMR network - but we're all rag chewers, and (I at least) feel bad about chewing up someone elses resources to sit and flap our gums. We more or less all have needed hardware to build an MMDVM based network.

So, what we're wondering is, how hard is it to do the following, and is DVSwitch the missing link we've been looking for to link ourselves together by:

Creating a heterogeneous linked P25 network (some Quantars, but mostly MMDVM based repeaters).
Optionally, adding DMR based sites in as well (which I know comes with the pain of transcoding).
Creating a linked DMR only network of repeaters.
Doing this without having an always on tie up to a larger established network - without closing the door to a connection to brandmeister or some other network.

I discovered the MMDVM project about three months ago, and I've been looking for the missing link to tie MMDVM repeaters together on P25 - and today I discovered this - can DVSwitch be the missing link we've been looking for?

Thanks and 73's
Robert Johnson
K6WLF


Building a private network with (mostly) MMDVM P25 repeaters

Robert Johnson
 

So, I've been searching thru the message archive for a half an hour, without much luck, and I'm wondering some things.

There are about 10 of us in the larger pacific northwest who are potentially interested in building our own little semi-private MMDVM based network - all of us have P25 hardware, but some of us are getting on the DMR bandwagon now too - those of us with DMR are using the local (and wonderful may I note) DCI PNW DMR network - but we're all rag chewers, and (I at least) feel bad about chewing up someone elses resources to sit and flap our gums. We more or less all have needed hardware to build an MMDVM based network.

So, what we're wondering is, how hard is it to do the following, and is DVSwitch the missing link we've been looking for to link ourselves together by:

Creating a heterogeneous linked P25 network (some Quantars, but mostly MMDVM based repeaters).
Optionally, adding DMR based sites in as well (which I know comes with the pain of transcoding).
Creating a linked DMR only network of repeaters.
Doing this without having an always on tie up to a larger established network - without closing the door to a connection to brandmeister or some other network.

I discovered the MMDVM project about three months ago, and I've been looking for the missing link to tie MMDVM repeaters together on P25 - and today I discovered this - can DVSwitch be the missing link we've been looking for?

Thanks and 73's
Robert Johnson
K6WLF


"Blocked" Message on Brandmeister

Steven Blackford
 

Try these settings for a way to deal with the loop fixer on the BM Network. We have noticed it on a couple of bridges & has solved the issue so far for us.  Hope it helps. 73 de K4SQI!

Steve @ work. :-)



---------- Forwarded message ---------
From: Jason Ford <w4jmf@...>
Date: Wed, May 30, 2018 at 13:57
Subject: "Blocked" Message on Brandmeister
To: Steven Blackford <kb7sqi@...>, Wayne Cornish <g7oki@...>, Jeffrey Lehman, KC8QCH <kc8qch@...>


Greetings Gents:
After much research and a chat with the BM Admins, I have discovered the source of the problem for the blocked message.

All BM Masters run LoopBan.  If the server sees 5 calls shorter than 2 seconds over a 1 minute time, it will think it is a loop and place a 10 minute ban on the call.  LoopBans are in place for 1 hour automatically.  

With this in mind I went into the MMDVM_Bridge settings and made a couple of adjustments to the settings:
[General]
RFModeHang=0 . changed to 10
NetModeHang=0, changed to 3
[DMR]
CallHang=0, changed to 3
TXHang=0, changed to 3

My thought process here is that if the 2 second mark is key, just make all TX's at least 2 secs.  So far today, I have not seen the issues from before.

Just sharing my experiments for future reference.

Jason Ford, W4JMF
Executive Director
World Wide Amateur Radio Guild Inc.

CONFIDENTIALITY NOTICE:
The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. 

--
-----
Steve, kb7sqi@...


Re: Intermittent No Audio

WillieB <will@...>
 

Ok, I have some more info. I was just able to listen to a long net so I did a little more troubleshooting.

To be clear I'm using a DMR HT connected to the bridge, connected to AllStar node 45221.

When the issue is happening, one of 2 things happen. My hotspot transmits and shows my DMR ID the entire time, and it's either completely silent on the HT or there is a low audio digital type sound coming out of the DMR HT. It may happen in the middle of someone talking, or at the beginning. It's usually at the beginning though.

Also, I can hear the audio fine on Brandmeister hoseline. See below for a link to a video of the issue happening (with the low digital sound). The audio you will hear in the background is hoseline (My DMR ID) playing on a computer right next to me. All that's coming out of the HT is the digital signal you hear. When it drops and starts back talking then you can hear the audio fine out of the HT. And the next time it does it, it may be completely silent or may have the low audio digital signal again.

Seems to me it's between Brandmeister and my hotspot, but I'm not sure what triggers it. I guess it could be related to how the audio is converted, not sure. I don't have the same issues listening to other DMR TGs.

Hopefully that helps.



On Tue, Jun 5, 2018 at 5:38 PM, Steve N4IRS <szingman@...> wrote:
Will,
Mike and I have been discussing where we think the issue might be. Don't reduce the minimum hang time or you will run into the BM "loop detector"
You mentioned that you are listening on a hot spot. Do you have the log for the time period that is the same as the other 2 logs you posted? When this happen, does your DMR radio still display the proper data while listening to silence?

Steve

On 06/05/2018 04:16 PM, WillieB wrote:
Any ideas on the intermittent audio issue? The only setting I see in Analog_Bridge.ini is below. Could changing this help at all?

minTxTimeMS = 2000                      ; Minimum time in MS for hang delay



On Mon, Jun 4, 2018 at 2:14 PM, WillieB <will@...> wrote:

I’ve been busy but finally had a chance to catch it this morning. See attached logs. It happened right at the end of each log. I believe all the extended hang times at the end are related. It doesn’t seem to show much else but maybe that will give us some ideas…?

 

From: main@DVSwitch.groups.io [mailto:main@...o] On Behalf Of Steve N4IRS
Sent: Saturday, June 2, 2018 6:59 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Intermittent No Audio

 

Will,
Since the data flows from ASL to MB through AB, it's good to tail both the AB and MB logs. You should see waht is happening in "real time"

Steve

On 06/01/2018 08:08 PM, WillieB wrote:

My bridge is working very well, however I do have one main problem.

 

Sometimes when one person stops talking and another person takes their turn, my hotspot transmits but there's no audio coming out. Then next time it drops and someone else starts talking I hear the audio. It may do this in about 1 out of 5 transmissions or so. It varies per person and AllStar node I'm connected to. I'm not sure if it's when they key up fast or what.

 

I can listen on the AllStar node and I hear the audio there, but not on DMR.

 

Anyone else having that problem? I was going to go check out the Analog_Bridge.ini file and see if there are any settings in there that might make sense changing but maybe someone can give me some ideas before I go poking around and changing things (after backing up the ini of course!).

 

I can also tail -f the 2 log files when it's happening and see if that gives me any clues to what might be going on.

 

-Will

KE4IAJ

 

 





Re: Intermittent No Audio

Steve N4IRS
 

Will,
Mike and I have been discussing where we think the issue might be. Don't reduce the minimum hang time or you will run into the BM "loop detector"
You mentioned that you are listening on a hot spot. Do you have the log for the time period that is the same as the other 2 logs you posted? When this happen, does your DMR radio still display the proper data while listening to silence?

Steve

On 06/05/2018 04:16 PM, WillieB wrote:
Any ideas on the intermittent audio issue? The only setting I see in Analog_Bridge.ini is below. Could changing this help at all?

minTxTimeMS = 2000                      ; Minimum time in MS for hang delay



On Mon, Jun 4, 2018 at 2:14 PM, WillieB <will@...> wrote:

I’ve been busy but finally had a chance to catch it this morning. See attached logs. It happened right at the end of each log. I believe all the extended hang times at the end are related. It doesn’t seem to show much else but maybe that will give us some ideas…?

 

From: main@DVSwitch.groups.io [mailto:main@....io] On Behalf Of Steve N4IRS
Sent: Saturday, June 2, 2018 6:59 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Intermittent No Audio

 

Will,
Since the data flows from ASL to MB through AB, it's good to tail both the AB and MB logs. You should see waht is happening in "real time"

Steve

On 06/01/2018 08:08 PM, WillieB wrote:

My bridge is working very well, however I do have one main problem.

 

Sometimes when one person stops talking and another person takes their turn, my hotspot transmits but there's no audio coming out. Then next time it drops and someone else starts talking I hear the audio. It may do this in about 1 out of 5 transmissions or so. It varies per person and AllStar node I'm connected to. I'm not sure if it's when they key up fast or what.

 

I can listen on the AllStar node and I hear the audio there, but not on DMR.

 

Anyone else having that problem? I was going to go check out the Analog_Bridge.ini file and see if there are any settings in there that might make sense changing but maybe someone can give me some ideas before I go poking around and changing things (after backing up the ini of course!).

 

I can also tail -f the 2 log files when it's happening and see if that gives me any clues to what might be going on.

 

-Will

KE4IAJ

 

 




Re: Intermittent No Audio

WillieB <will@...>
 

Any ideas on the intermittent audio issue? The only setting I see in Analog_Bridge.ini is below. Could changing this help at all?

minTxTimeMS = 2000                      ; Minimum time in MS for hang delay



On Mon, Jun 4, 2018 at 2:14 PM, WillieB <will@...> wrote:

I’ve been busy but finally had a chance to catch it this morning. See attached logs. It happened right at the end of each log. I believe all the extended hang times at the end are related. It doesn’t seem to show much else but maybe that will give us some ideas…?

 

From: main@DVSwitch.groups.io [mailto:main@....io] On Behalf Of Steve N4IRS
Sent: Saturday, June 2, 2018 6:59 AM
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] Intermittent No Audio

 

Will,
Since the data flows from ASL to MB through AB, it's good to tail both the AB and MB logs. You should see waht is happening in "real time"

Steve

On 06/01/2018 08:08 PM, WillieB wrote:

My bridge is working very well, however I do have one main problem.

 

Sometimes when one person stops talking and another person takes their turn, my hotspot transmits but there's no audio coming out. Then next time it drops and someone else starts talking I hear the audio. It may do this in about 1 out of 5 transmissions or so. It varies per person and AllStar node I'm connected to. I'm not sure if it's when they key up fast or what.

 

I can listen on the AllStar node and I hear the audio there, but not on DMR.

 

Anyone else having that problem? I was going to go check out the Analog_Bridge.ini file and see if there are any settings in there that might make sense changing but maybe someone can give me some ideas before I go poking around and changing things (after backing up the ini of course!).

 

I can also tail -f the 2 log files when it's happening and see if that gives me any clues to what might be going on.

 

-Will

KE4IAJ

 

 



Re: New member, few questions regarding hblink/hb_bridge/hb_confbridge

Colby Ross W1BSB <colbypr@...>
 

So, on repeat, it repeats everything the clients send to the master to the other clients. So if I want to only pass traffic to the clients that they want to hear. i.e. subscription to a specific talk group,  So if we have Server A, and Client B, and Client C, and Client C starts talking on TG300, Client B will receive it when it is just on Repeat. In the same scenario, we have 4 clients, B, C, D, and E. B and E want to have a conversation on TG350, while C and D want to have one on TG300, without the talk group traffic on 300 or 350 being forwarded to systems that aren't interested in it. I think thats the basis of what I'm trying to do.

8281 - 8300 of 9801