Channel SimpleUSB does not exist

AllStarLink
1

Hi,

I have been struggling to get a new cm108 & baofeng UV82 node to connect to any other node. It is on a Debian virtual machine using virtualbox.

I installed Debian multiple times in search of a resolution. After fresh install, I am able to connect to other nodes but as soon as the fob is plugged in (and system restarted) connection doesn't get established and I continuosly get the following in asterisk CLI;

WARNING[1861]: app_rpt/rpt_manager.c:340 rpt_manager_do_xstat: Channel SimpleUSB/638384 does not exist, cannot access variables

I have multiple such nodes and they work flawlessly. The fob connections on this one were made by a friend which i verified via pictures/videos. All else is the same however I also think that it might not be the issue.

Node shows up as online (638384), IP matches, I am able to connect to its CLI remotely. rpt_extnodes is up to date. Port 4569 UDP is open on router. simpleusb.conf is as follows;

[638384](node-main)
carrierfrom = usb
ctcssfrom = no

;;;;; ASL3 Tune settings ;;;;;
devstr = 
rxmixerset = 750
txmixaset = 350
txmixbset = 350

This is the same as my other nodes. The fob acts as expected (i.e. blinking light) and shows up in lsusb.

Any guidance as to what I might be doing wrong or where I should check for logs etc. related to this?

Thanks,
Adam

2

Have to attached the USB device to the VirtualBox VM?Does asl-find-sound display a sound adapter?

3

Yes, it does. I have had local rf tx of node connection status as well as echo. However at times it does state that SimpleUsb is not working and I need to restart asterisk.

4

i see devstr = is blank. your devstr = should read something like this.
devstr = 1-1.3:1.0

that's your issue as far as i can see.

5

If devstr= is blank, the channel driver should simply be using the first acceptable device it enumerates. Is there anything in /var/log/asterisk/messages.log that explains the error?

6

Hi @N8EI Thank you for the response. The issue was identified as electronic. Some soldering was off on the CM108 which was causing the fob to drop most probably.

It is now acting as expected with an occasional disconnection but an auto connect script is keeping everything intact.

@w5mgm Thanks for the response. As N8EI mentioned, devstr= is good, as, at times when port is changed or for some weird random reason, device is with a different identifier then blank devstr automatically picks up the C-Media fob.

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.