Jim Gifford - K9AGR
I left this running without tinkering over the weekend, and everything stayed rock solid. The audio issue disappeared for the most part. I even updated the MD-9600 to have the same settings for listening to the MMDVM box. It’s worth noting that the MMDVM “repeater” in this case is a cheap duplex chinaspot that I’m running on my coordinated frequency while I finish building my real MMDVM repeater. The chinaspot can’t be heard more than 25 feet away, and I haven’t dialed in the frequency with mmdvmcal yet. I’m still learning how to use my service monitor. It’s adequate to prove the concept, but not adequate to use for an extended QSO yet.
Watching the pi-star dashboard, I saw very few incidents of any packet loss, and in every case I followed up on, the same loss was reflected in the cBridge, so it was lacking in the source signal.
Even though it goes against my OCD-like nature, I’m ignoring the log files from IPSC_Bridge that say extremely high packet loss, as I suspect it’s a reporting bug, not a real bug. Every single transmission only shows 3 received out of all the ones transmitted. I’m assuming packets.
Example (times in UTC):
INFO 2018-11-26 12:22:16,271 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3110063 (3110063)
INFO 2018-11-26 12:22:24,371 Voice Transmission End 8.10 seconds loss rate: 97.78% (3/135)
INFO 2018-11-26 12:22:27,791 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3110037 (3110037)
INFO 2018-11-26 12:22:38,412 Voice Transmission End 10.62 seconds loss rate: 98.31% (3/177)
INFO 2018-11-26 12:22:40,691 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3110063 (3110063)
INFO 2018-11-26 12:22:54,551 Voice Transmission End 13.86 seconds loss rate: 98.70% (3/231)
INFO 2018-11-26 12:23:10,871 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3110037 (3110037)
INFO 2018-11-26 12:23:17,172 Voice Transmission End 6.30 seconds loss rate: 97.14% (3/105)
INFO 2018-11-26 12:23:19,571 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3110063 (3110063)
INFO 2018-11-26 12:23:36,671 Voice Transmission End 17.10 seconds loss rate: 98.95% (3/285)
INFO 2018-11-26 12:23:37,631 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3110037 (3110037)
INFO 2018-11-26 12:23:41,771 Voice Transmission End 4.14 seconds loss rate: 95.65% (3/69)
INFO 2018-11-26 12:26:05,230 Voice Transmission Start on TS 2 and TG 3151 (3151) from 3151152 (3151152)
INFO 2018-11-26 12:26:08,648 Voice Transmission End 3.42 seconds loss rate: 94.74% (3/57)
INFO 2018-11-26 12:51:53,708 Voice Transmission Start on TS 2 and TG 3151 (3151) from 3151584 (3151584)
INFO 2018-11-26 12:51:54,967 Voice Transmission End 1.26 seconds loss rate: 85.71% (3/21)
INFO 2018-11-26 13:07:20,770 Voice Transmission Start on TS 2 and TG 3151 (3151) from 3151406 (3151406)
INFO 2018-11-26 13:07:26,346 Voice Transmission End 5.58 seconds loss rate: 96.77% (3/93)
INFO 2018-11-26 13:26:16,994 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3120699 (3120699)
INFO 2018-11-26 13:26:20,411 Voice Transmission End 3.42 seconds loss rate: 94.74% (3/57)
INFO 2018-11-26 13:30:37,633 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3110037 (3110037)
INFO 2018-11-26 13:30:41,772 Voice Transmission End 4.14 seconds loss rate: 95.65% (3/69)
INFO 2018-11-26 13:31:53,650 Voice Transmission Start on TS 2 and TG 3151 (3151) from 3151090 (3151090)
INFO 2018-11-26 13:31:54,547 Voice Transmission End 0.90 seconds loss rate: 80.00% (3/15)
Now, since it is *always* (3/X), this must be an artifact within the code, not the signal, since I can copy the entire transmission on the radio at the endpoint. Definitely not enough of an issue to bother tracking down at this point.
This software works great, and the CPU usage stats for my virtual server show it doesn’t even break idle. I’m ready to start making the setup a little more complex now that I have a feel for how it all works together.
Thank you to everyone that has helped me get to this point. Reading through the archive of topics was educational, but not as much as actually getting some piece of the system operational. I especially want to thank Corey for his off-list assistance and helping me understand I wasn’t really ready to do what I was attempting to do, and that I needed to start smaller and work my way up.
On Nov 23, 2018, at 7:52 PM, Corey Dean N3FE <n3fe@...
I have seen that same thing happen when the audio lets are not set correctly. The 868 and 878 are pretty picky on audio levels.
On Fri, Nov 23, 2018 at 7:14 PM Jim Gifford - KD4PPG <jim@...
I spent time today going back and forth with Corey, and he has been most helpful. Since he’s using things not yet intended for general consumption, I’ve decided to hold off until that’s out, and instead focus my attention on simplifying the model so that I can finally get my head around how all the pieces glue together.
I’ve spent quite a lot of time today working with IPSC_Bridge and HB_Bridge, and now have the simplest possible setup I could do. I’ve passed audio traffic through from end to end in both directions, but have some issues still.
MMDVM Repeater <-> HB_Bridge <-> IPSC_Bridge <-> K4USD cBridge
So far, it all looks good, but I have a few concerns. Earlier today, I was having a QSO over 8802 via the MMDVM repeater, when it stopped making it through the pipeline all the way to K4USD. I wasn’t able to determine where it was failing, and switched to a direct RF link to a known operational repeater to finish the QSO.
I eventually decided it must’ve been an errant talkgroup from the cBridge, and sent the list of talkgroups I’ve been receiving unsolicited to the cBridge maintainer, and he fixed that when he got home tonight. So now I’m sitting down and testing again.
Just a couple of minutes ago, I heard a ham call out on the 8802 talkgroup via the radio connected to the known good repeater (40+ miles away), but the HT listening to the benchtop repeater had no audio output at all. Everything else looked normal, the pi-star dashboard showed the contact, that TX was occurring, etc. The AnyTone 878 showed the contact information, talkgroup, etc, and updated the last call info after he finished talking.
Here’s the output from IPSC_Bridge:
INFO 2018-11-23 23:54:31,694 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3121792 (3121792)
INFO 2018-11-23 23:54:34,392 Voice Transmission End 2.70 seconds loss rate: 93.33% (3/45)
INFO 2018-11-23 23:56:06,731 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3121792 (3121792)
INFO 2018-11-23 23:56:11,592 Voice Transmission End 4.86 seconds loss rate: 96.30% (3/81)
INFO 2018-11-23 23:57:41,114 Voice Transmission Start on TS 1 and TG 8802 (8802) from 3111697 (3111697)
INFO 2018-11-23 23:57:45,252 Voice Transmission End 4.14 seconds loss rate: 95.65% (3/69)
Here’s the output from HB_Bridge:
INFO 2018-11-23 23:54:31,692 (MASTER-1) Begin AMBE encode STREAM ID: 3929710726 SUB: 3121792 (3121792) REPEATER: 13100030 (13100030) TGID 8802 (8802), TS 1
INFO 2018-11-23 23:56:06,732 (MASTER-1) Begin AMBE encode STREAM ID: 725990770 SUB: 3121792 (3121792) REPEATER: 13100030 (13100030) TGID 8802 (8802), TS 1
INFO 2018-11-23 23:57:41,112 (MASTER-1) Begin AMBE encode STREAM ID: 754258576 SUB: 3111697 (3111697) REPEATER: 13100030 (13100030) TGID 8802 (8802), TS 1
Now that loss rate from IPSC_Bridge worried me when I first discovered it, but since I was actually passing audio both ways earlier today when it was happening, I figured it wasn’t worth worrying about, probably just mis-reporting. Notice how it’s always 3 out of however many. Always. But now I wonder if it’s indicative of a problem I should track down.
Any ideas what I should check next?
In terms of setting up confbridge, which is preferred to work with, the one in dmrlink or the one in hblink? Ultimately, I want one of those to be the primary decision maker in the “center” of it all. With the link to BM being the most number of talkgroups, I’m leaning towards the hblink one as the one to use.
On Nov 23, 2018, at 7:14 AM, Jim Gifford - KD4PPG <jim@...
I've reached the point where I need someone with experience with these tools to point me in the right direction. I think I am getting overwhelmed with too much "there's more than one way to do it" combined with not knowing the limitations of the various branches of dmrlink and hblink (IPSC_Bridge and HB_Bridge specifically).
I have the need to connect 2 repeaters up to 2 different networks simultaneously. One repeater is Mototrbo/IPSC and the other is MMDVM/Pi-Star. One of the networks is a cBridge, and the other is Brandmeister.
On the IPSC repeater, the requirement is to have TS1 TG8802 and TS2 TG3151 by default, with TG8802 sourced from the cBridge, and TG3151 sourced from either the cBridge or Brandmeister. I can get it from either source, but TG8802 is only from the cBridge due to policy. The part that makes it difficult for me to know how to implement it is that the repeater owner wants TS1 to share with "any possible" BM TG, with a PTT setup with 15 minute timeout to revert to TG8802.
On the MMDVM repeater, the requirement is to have TS1 TG8802 and TS2 TG3151 by default. Again, TG8802 sourced from the cBridge, and TG3151 from either. The repeater owner on this one is me, and I'd rather have my PTT groups on TS2, and I don't necessarily care if it is "any possible" BM TG or simply a predefined subset.
Eventually, we might add additional DMR repeaters into the mix, and have different requirements for them.
I've started with a pristine install of Ubuntu 18.04 LTS, updated it, added Steve's DVSwitch-System-Builder script, and followed its directions.
Any suggestions for the best way to implement the system as described, or as closely as possible?
Thanks in advance,