# Two nodes on one server, audio issues **URL:** \ **Category:** AllStarLink\ **Created:** [July 8, 2024, 7:12am UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335 "2024-07-08T07:12:42Z")\ **Posts on this page:** 13\ **Page:** 2
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [July 11, 2024, 1:33pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/21 "2024-07-11T13:33:37Z")
To be most precise, the problem is possibly power load issues on the USB ports. The Pi is a low-power device and cannot support significant power draw out of the USB ports. Try putting your USB fobs on a **powered** USB hub and see if the problem goes away. ---
**Author:** ![N2DYI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n2dyi/32/1712_2.png) [@N2DYI](https://community.allstarlink.org/u/N2DYI)\ **Post date:** [July 11, 2024, 3:11pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/22 "2024-07-11T15:11:54Z")
I can’t find threads when I’m looking for them (of course) but I don’t believe it’s directly related to power, at least not in this case. It’s something to do with a weird way the rPi4 addresses USB devices. Supposedly, this was corrected in rev 1.5 boards, but in my testing, it doesn’t seem to be the case. I have even used bus-powered hubs to get around this problem. Yes, I would absolutely recommend using a powered hub. ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [July 11, 2024, 5:01pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/23 "2024-07-11T17:01:10Z")
Hi N8EI and KE4DYI, I tried moving from black to blue USB ports, same issue. I tried a USB hub (unpowered), same issue. There are no usb power warnings in the kernel output (dmesg). Generally you will see notices about this sort of thing, or, you’ll see USB devices disappear and reappear. Or bus power warnings. I see nothing during PTT. I’m not saying this absolves the USB but it doesn’t place blame with them either. I’ll have to look around for a powered hub and give that a try, but without any indication of power issues, I find it unlikely to be a solution. I did notice that in extensions.conf, there are references to `${NODE}`. This variable is of course set to the first node I set up (617080). The second node (617081) is absent in this file. I’ve only used the automated setup script (asl-menu) to add the second node. Do I need to tweak or add anything here for the second node? I feel like I did modify this with my older ASL install (from a few days ago) without effect but I figure it’s worth asking. Can I send y’all my configs? As attachments, termbin posts, or inline? What do you prefer? Thanks, –E de W6EL ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [July 12, 2024, 1:56am UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/24 "2024-07-12T01:56:29Z")
> [@W6EL](#): > > When I added the second radio, the 900 MHz one, I followed this guide, which seems to be the only guide of its kind on the internet: [Two Nodes on One Server - AllStarLink Wiki](https://wiki.allstarlink.org/wiki/Two_Nodes_on_One_Server) Where the WiKi talks about extensions.conf, that is outdated. ASL3 needs no changes to extensions.conf for normal node operation. Try putting that back and see what happens. If you want to zip up your rpt.conf and simpleusb.conf, remove passwords and post them, we could take a look. ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [July 12, 2024, 2:27am UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/25 "2024-07-12T02:27:18Z")
Unfortunately, it will not allow me to upload anything that isn’t a picture/pdf/mp3 format. Here are the files on termbin: simpleusb.conf: [https://termbin.com/5p6b](https://termbin.com/5p6b) usbradio.conf: [https://termbin.com/yc1o](https://termbin.com/yc1o) rpt.conf: [https://termbin.com/1czk](https://termbin.com/1czk) On this clean ASL3 install, I did not alter extensions.conf. The 41751 node is mentioned in rpt.conf so that it can make a local connection on the LAN. When the problem initially happened, I tried switching one node over to usbradio and keeping the other on simpleusb, on the off chance that there was some kind of collision happening. This didn’t solve anything, but I got the usbradio.conf so nicely dialed in that I have decided to stay with it :-). Thanks for any advice you have, –E de W6EL ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [July 17, 2024, 5:25pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/26 "2024-07-17T17:25:32Z")
Well, I gave up and got another Pi 4B. With one Pi per node everything is working. The nodes can transmit at the same time without any audio dropping. I strongly suspect there is a bug within app\_rpt, but I just don’t know enough about how that code works to make any meaningful diagnostics of it. I am fairly certain that the behavior I witnessed cannot be said to be configuration based, as I don’t think there are any known configurations that exhibit this particular issue. Note that I did try upgrading asterisks (apt upgrade), did not notice any difference with this issue. Honestly I can’t complain, with the “investment” of another Pi, everything is working quite well. I’ll give the two-nodes-one-Pi thing a shot with the next significant release. ASL 3 is a mighty effort with really amazing results. Keep it up! Thanks all for your time, –E de W6EL ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [July 17, 2024, 6:01pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/27 "2024-07-17T18:01:37Z")
> [@W6EL](#): > > Unfortunately, it will not allow me to upload anything that isn’t a picture/pdf/mp3 format. Yes, GitHub doesn’t like “.conf” files. My solution is to add a “.txt” extension to the file before uploading (e.g. “rpt.conf.txt”). I suspect you can do something similar with ".zip"s. ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [July 17, 2024, 6:19pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/28 "2024-07-17T18:19:18Z")
This is what this forum allows for uploading (see the screenshot of the “attach file” dialog). –E de W6EL ![uploadtypes](https://community.allstarlink.org/uploads/default/original/2X/7/74adb74a394525970195dfa918a0c0975fa82276.png) ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [July 17, 2024, 6:21pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/29 "2024-07-17T18:21:03Z")
Here’s what happens when you try a zip file or other non-supported file type. ![allowed_types](https://community.allstarlink.org/uploads/default/original/2X/1/1ca253619e42f073f0a0f156f0436bb18de5ae84.png) ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [July 17, 2024, 6:23pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/30 "2024-07-17T18:23:57Z")
We run a discourse forum for wfview. If you log in and go to: Admin → Settings → Files → authorized extensions then you can add .conf and .txt to the list. Pretty harmless addition. ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [July 17, 2024, 6:52pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/31 "2024-07-17T18:52:38Z")
Attached is a PDF “test” file. To create this “.pdf” I started off with two files (1.conf, 2.conf), created a zip archive of the two files, and then renamed the “.zip” to have a “.pdf” extension. In reality, this is NOT a “.pdf” file. When we (or anyone) downloads the file we would just change the name back to “.zip”. [test.zip-renamed-to.pdf](https://community.allstarlink.org/uploads/short-url/lQzw7dYKmjzRxKBQxk23rnrOFu.pdf) (382 Bytes) ---
**Author:** ![W6EL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w6el/32/3070_2.png) [@W6EL](https://community.allstarlink.org/u/W6EL)\ **Post date:** [July 17, 2024, 6:56pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/32 "2024-07-17T18:56:53Z")
Yeah, it’s better to not name files with deceptive or incorrect extensions. The forum engine can easily be adjusted (per the earlier post) to allow config files directly without even needing to zip them. –E de W6EL ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [July 17, 2024, 7:26pm UTC](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335/33 "2024-07-17T19:26:40Z")
> [@W6EL](#): > > Yeah, it’s better to not name files with deceptive or incorrect extensions. I agree. I was just offering a way to share content until the web site(s) can be updated. [Previous page](https://community.allstarlink.org/t/two-nodes-on-one-server-audio-issues/21335.md?page=1)