Topics

No Audio Bridge yet the network looks good

Joshua Nulton
 

My Allstar node (42177) is in the cloud, it is online and I can ssh in and link to other nodes no issues. I installed the DVswitch packages and followed the steps outlined by both KV4S and WB4ULK (both excellent tutorials). Once to the end the DMR hotspot was showing up on Brandmeister's page as registered, the first "test" static talk group of 5446 showed as connected and was working with hoseline. I used the Allstar CLI and issued rpt fun 42177 *32000 and it connected, I heard it connect via the web transceiver as well. I take my DMR radio connect to talkgroup 5446 and key up.... no audio comes across through the Allstar web transceiver. Other people talk on Allstar node 2000 and nothing comes in on the DMR talkgroup I am sitting on.

The only thing that I can think of that I might have done wrong is not knowing what audio settings to use. Typically issues like this more often than not end up being a typo, but I have scoured this for hours and can't figure it out. Could someone please take a look at my config files and tell me what I am doing wrong?

I appreciate the time,
Jae  KG5EBI

Steve N4IRS
 

Jae,
Thanks for including the config files. What we need to see is the startup of Analog_Bridge and MMDVM_Bridge. I usually suggest you log one transmission from ASL to DMR and one transmission from DMR to ASL.

Steve N4IRS


On 6/23/19 5:46 PM, Joshua Nulton wrote:
My Allstar node (42177) is in the cloud, it is online and I can ssh in and link to other nodes no issues. I installed the DVswitch packages and followed the steps outlined by both KV4S and WB4ULK (both excellent tutorials). Once to the end the DMR hotspot was showing up on Brandmeister's page as registered, the first "test" static talk group of 5446 showed as connected and was working with hoseline. I used the Allstar CLI and issued rpt fun 42177 *32000 and it connected, I heard it connect via the web transceiver as well. I take my DMR radio connect to talkgroup 5446 and key up.... no audio comes across through the Allstar web transceiver. Other people talk on Allstar node 2000 and nothing comes in on the DMR talkgroup I am sitting on.

The only thing that I can think of that I might have done wrong is not knowing what audio settings to use. Typically issues like this more often than not end up being a typo, but I have scoured this for hours and can't figure it out. Could someone please take a look at my config files and tell me what I am doing wrong?

I appreciate the time,
Jae  KG5EBI

Joshua Nulton
 

Truly an honor Steve, thank you for the help and all that you have done here and prior to the digital work.

Attached are the startup logs. I don't know how to gather the transmission logs, would love to learn so that I can add it to my list of shortcuts. Further, I do not have an Allstar node onsite locally at this moment, just the DMR, will that hinder me getting this linked?

Steve N4IRS
 

Jae,
To capture the transmission keep Analog_Bridge and MMDVM_Bridge running. Send one transmission to ASL and one transmission on the DMR TG. Then stop the programs and grab the logs.
Do you know if the md380-emu is running?
Try systemctl status md380-emu
try ps ax | grep emu

Steve

On 6/23/19 6:33 PM, Joshua Nulton wrote:
Truly an honor Steve, thank you for the help and all that you have done here and prior to the digital work.

Attached are the startup logs. I don't know how to gather the transmission logs, would love to learn so that I can add it to my list of shortcuts. Further, I do not have an Allstar node onsite locally at this moment, just the DMR, will that hinder me getting this linked?

Joshua Nulton
 
Edited

Yes md380-emu is running.

root@KG5EBI-42177:~# systemctl status md380-emu
● md380-emu.service - MD-380 Emulator Service
   Loaded: loaded (/lib/systemd/system/md380-emu.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-06-23 16:17:42 CDT; 1h 22min ago
 

Steve N4IRS
 

It looks like Analog_Bridge is restarting. Do this:
stop Analog_Bridge with systemctl stop analog_bridge
cd /opt/Analog_Bridge
./Analog_Bridge Analog_Bridge.ini

Does AB stay running?

On 6/23/19 6:55 PM, Joshua Nulton wrote:
Yes md380-emu is running.

root@KG5EBI-42177:~# systemctl status md380-emu
● md380-emu.service - MD-380 Emulator Service
   Loaded: loaded (/lib/systemd/system/md380-emu.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-06-23 16:17:42 CDT; 1h 22min ago
 Main PID: 692 (md380-emu)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/md380-emu.service
           └─692 /usr/bin/qemu-arm-static /opt/md380-emu/md380-emu -S 2470
 
Jun 23 16:17:42 KG5EBI-42177 systemd[1]: Started MD-380 Emulator Service.
root@KG5EBI-42177:~# ps ax | grep emu
  692 ?        Ssl    0:06 /usr/bin/qemu-arm-static /opt/md380-emu/md380-emu -S 2470
 2243 pts/0    S+     0:00 grep emu



Joshua Nulton
 

I don't know how to tell, I mean it appears to stay running, after it displays:
I: 2019-06-23 23:23:38.950 Open UDP listener on 127.0.0.1:34001
I: 2019-06-23 23:23:38.950 Starting USRP --> HB_Bridge thread

I would need to CTRL+C to break the program, so I assume it is running without error.

Steve N4IRS
 

OK,
While it's running, send one transmission through ASl and one transmission from DMR. Post the output.

On 6/23/19 7:25 PM, Joshua Nulton wrote:
I don't know how to tell, I mean it appears to stay running, after it displays:
I: 2019-06-23 23:23:38.950 Open UDP listener on 127.0.0.1:34001
I: 2019-06-23 23:23:38.950 Starting USRP --> HB_Bridge thread

I would need to CTRL+C to break the program, so I assume it is running without error.

Joshua Nulton
 

I can do the DMR to ASL easily,  and did. But I do not have a local ASL node available (thus the reason for all this). I disconnected and connected to another node via the CLI in hopes that might trigger something.

Steve N4IRS
 

OK, I see this from the MB log:
M: 2019-06-23 21:17:52.512 DMR, Logged into the master successfully
M: 2019-06-23 21:20:28.401 DMR Slot 2, received network voice header from KG5EBI to TG 5446
M: 2019-06-23 21:20:29.109 DMR Talker Alias (Data Format 1, Received 6/22 char): 'KG5EBI'
M: 2019-06-23 21:20:29.827 DMR Talker Alias (Data Format 1, Received 13/22 char): 'KG5EBI DMR ID'
M: 2019-06-23 21:20:30.545 DMR Talker Alias (Data Format 1, Received 20/22 char): 'KG5EBI DMR ID: 11483'
M: 2019-06-23 21:20:31.268 DMR Talker Alias (Data Format 1, Received 22/22 char): 'KG5EBI DMR ID: 1148310'
M: 2019-06-23 21:20:41.498 DMR Slot 2, received network end of voice transmission, 13.1 seconds, 1% packet loss, BER: 0.0%
M: 2019-06-23 21:21:22.316 DMR Slot 2, received network voice header from KG5EBI to TG 5446
M: 2019-06-23 21:21:23.060 DMR Talker Alias (Data Format 1, Received 6/22 char): 'KG5EBI'
M: 2019-06-23 21:21:23.749 DMR Talker Alias (Data Format 1, Received 13/22 char): 'KG5EBI DMR ID'
M: 2019-06-23 21:21:24.470 DMR Talker Alias (Data Format 1, Received 20/22 char): 'KG5EBI DMR ID: 11483'
M: 2019-06-23 21:21:25.189 DMR Talker Alias (Data Format 1, Received 22/22 char): 'KG5EBI DMR ID: 1148310'
M: 2019-06-23 21:21:25.667 DMR Slot 2, received network end of voice transmission, 3.4 seconds, 0% packet loss, BER: 0.0%
M: 2019-06-23 22:14:32.592 Closing the MMDVM
I: 2019-06-23 22:14:32.844 Stopped the DMR Id lookup reload thread
M: 2019-06-23 22:14:32.844 DMR, Closing DMR Network
I: 2019-06-23 22:14:32.844 MMDVM_Bridge-20180423 exited on receipt of SIGTERM

What I don't see is the same time frame from the Analog_Bridge log.

What I need you to do is to stop both Analog_Bridge and MMDVM_Bridge. Open a ssh session to the host and run Analog_Bridge in the foreground.
Open a second ssh session and run MMDVM_Bridge in the foreground.

Capture the output from each. NOT the logs, capture the output. 

On 6/23/19 7:36 PM, Joshua Nulton wrote:
I can do the DMR to ASL easily,  and did. But I do not have a local ASL node available (thus the reason for all this). I disconnected and connected to another node via the CLI in hopes that might trigger something.

Joshua Nulton
 

I appreciate the help Steve and am grateful for the time, that said I really don't want to waste yours. Respectfully this has escalated beyond my abilities. I will wait a few months for a more in depth tutorial to try following along with. Thank you very much for your time today and the multiple responses, it is appreciated.

Please keep up the great work,
Jae KG5EBI

Joshua Nulton
 

The really interesting thing is when I do the test tone with 

*CLI> rpt cmd 1999 cop 4 1999

I see the Analog_Bridge lights up and the PTT hangs until I send the command a second time.
M: 2019-06-23 23:46:28.355 PTT on
M: 2019-06-23 23:48:18.174 PTT off (keyed for 109819 ms)
M: 2019-06-23 23:48:37.755 PTT on
M: 2019-06-23 23:48:43.414 PTT off (keyed for 5659 ms)

Probably unrelated but still odd that the tone seems to send continually until I send the command again.

Steve N4IRS
 

That is what it is supposed to do.

On 6/23/19 7:55 PM, Joshua Nulton wrote:
The really interesting thing is when I do the test tone with 

*CLI> rpt cmd 1999 cop 4 1999

I see the Analog_Bridge lights up and the PTT hangs until I send the command a second time.
M: 2019-06-23 23:46:28.355 PTT on
M: 2019-06-23 23:48:18.174 PTT off (keyed for 109819 ms)
M: 2019-06-23 23:48:37.755 PTT on
M: 2019-06-23 23:48:43.414 PTT off (keyed for 5659 ms)

Probably unrelated but still odd that the tone seems to send continually until I send the command again.

Steve N4IRS
 

You are close. You can try this: stop both Analog_Bridge and MMDVM_Bridge. delete the log files. Start Analog_Bridge and MMDVM_Bridge. Send one transmission from DMR. Post both logs.
Also I wrote a howto a while ago which includes testing along the way. <https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit?usp=sharing>


On 6/23/19 7:52 PM, Joshua Nulton wrote:
I appreciate the help Steve and am grateful for the time, that said I really don't want to waste yours. Respectfully this has escalated beyond my abilities. I will wait a few months for a more in depth tutorial to try following along with. Thank you very much for your time today and the multiple responses, it is appreciated.

Please keep up the great work,
Jae KG5EBI

Joshua Nulton
 

Ok gonna try to push through.... I have been following your document for a couple hours, that was where I found the test code command...Opening all the shells now.

Joshua Nulton
 

ok When on the DMR HT and I key up the MMDVM console is showing the transmission.

M: 2019-06-24 00:10:58.607 DMR, Logged into the master successfully
M: 2019-06-24 00:11:06.334 DMR Slot 2, received network voice header from KG5EBI to TG 5446
M: 2019-06-24 00:11:07.086 DMR Talker Alias (Data Format 1, Received 6/22 char): 'KG5EBI'
M: 2019-06-24 00:11:07.825 DMR Talker Alias (Data Format 1, Received 13/22 char): 'KG5EBI DMR ID'
M: 2019-06-24 00:11:08.543 DMR Talker Alias (Data Format 1, Received 20/22 char): 'KG5EBI DMR ID: 11483'
M: 2019-06-24 00:11:09.251 DMR Talker Alias (Data Format 1, Received 22/22 char): 'KG5EBI DMR ID: 1148310'
M: 2019-06-24 00:11:14.427 DMR Slot 2, received network end of voice transmission, 8.0 seconds, 2% packet loss, BER: 0.0%

But the Analog_Bridge shows no change at all.
I: 2019-06-24 00:09:41.629 Starting Analog_Bridge --> USRP thread
I: 2019-06-24 00:09:41.629 Open UDP listener on 127.0.0.1:34001
I: 2019-06-24 00:09:41.629 Starting USRP --> HB_Bridge thread

Mike Zingman - N4IRR
 


AB says:
Analog_Bridge --> USRP thread
I: 2019-06-23 22:28:00.744 Open UDP listener on 127.0.0.1:34001
I: 2019-06-23 22:28:00.744 Starting USRP --> HB_Bridge thread

MB says:
M: 2019-06-23 22:24:02.259 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1

MB transmit should match AB receive

On Sun, Jun 23, 2019 at 8:13 PM Joshua Nulton <kg5ebi@...> wrote:
ok When on the DMR HT and I key up the MMDVM console is showing the transmission.

M: 2019-06-24 00:10:58.607 DMR, Logged into the master successfully
M: 2019-06-24 00:11:06.334 DMR Slot 2, received network voice header from KG5EBI to TG 5446
M: 2019-06-24 00:11:07.086 DMR Talker Alias (Data Format 1, Received 6/22 char): 'KG5EBI'
M: 2019-06-24 00:11:07.825 DMR Talker Alias (Data Format 1, Received 13/22 char): 'KG5EBI DMR ID'
M: 2019-06-24 00:11:08.543 DMR Talker Alias (Data Format 1, Received 20/22 char): 'KG5EBI DMR ID: 11483'
M: 2019-06-24 00:11:09.251 DMR Talker Alias (Data Format 1, Received 22/22 char): 'KG5EBI DMR ID: 1148310'
M: 2019-06-24 00:11:14.427 DMR Slot 2, received network end of voice transmission, 8.0 seconds, 2% packet loss, BER: 0.0%

But the Analog_Bridge shows no change at all.
I: 2019-06-24 00:09:41.629 Starting Analog_Bridge --> USRP thread
I: 2019-06-24 00:09:41.629 Open UDP listener on 127.0.0.1:34001
I: 2019-06-24 00:09:41.629 Starting USRP --> HB_Bridge thread

Joshua Nulton
 

Meaning I did not put the ports in correctly?

Steve N4IRS
 

Yes, I forgot to ask to see your DVSwitch.ini

On 6/23/19 8:20 PM, Joshua Nulton wrote:
Meaning I did not put the ports in correctly?

Joshua Nulton
 

So this is what I should see on the Analog_Bridge Console through the duration that I am keyed up?

W: 2019-06-24 00:25:38.922 Received USRP packet without proper header
W: 2019-06-24 00:25:38.994 Received USRP packet without proper header
W: 2019-06-24 00:25:39.040 Received USRP packet without proper header
W: 2019-06-24 00:25:39.101 Received USRP packet without proper header
W: 2019-06-24 00:25:39.163 Received USRP packet without proper header
W: 2019-06-24 00:25:39.219 Received USRP packet without proper header