-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chan_simpleusb, chan_usbradio: Use tune sections from main config file. #281
Conversation
The |
Good catch! I missed those since they were not using the CONFIG_TUNE macro like the other ones. I'll update that and repush. I'm also going to change from rewriting the entire file to using the ast_config APIs. |
1058074
to
b759043
Compare
Getting error on asterisk start: ERROR[4118856]: chan_simpleusb.c:891 hidthread: Channel 25334: Device string 1-1.3:1 was not found.
1-1.3:1.0 --> 0d8c:0013 C-Media Electronics Inc. Add this to simpleusb.conf under devicenum=1 devstr=1-1.3:1.0 rxmixerset=750 txmixaset=450 txmixbset=0 *CLI> Active radio interface is [25334] Device String is 1-1.3 Card is -1 Rx Level currently set to 750 Tx A Level currently set to 450 Tx B Level currently set to 0 |
Not sure how to interpret this... I remember Danny saying that warning was showing up before, so is all good or not? |
It's not good, nor is the Bottom line is the URI is not recognized by app_rpt. |
@InterLinked1 Maybe this will help. The string comparison in simpleusb.c line 882 is not matching. The actual device string is That string has been entered into simpleusb.conf. But chan_simpleusb seems to be dropping the ERROR[5895]: chan_simpleusb.c:891 hidthread: Channel 25334: Device string 1-1.3:1 was not found. |
d41854a
to
bb24ae8
Compare
Was this working before and is not working now (a regression) or was it not working before and still not working now? I pushed a slight change; could you do |
Simpleusb used to load fine. It has not worked since the tune settings have moved. Debug and reload: Device string is still |
Thanks, that helps!
But are there any debug messages output, or none? I can't look at this right now but I can log into your box to debug more. Is this 2509, or Murdoch? |
Yes, 2509. I guess you didn't compile it... chan_simpleusb.c: In function ‘load_tune_config’: chan_simpleusb.c:797:1: error: version control conflict marker in file 797 | <<<<<<< HEAD | ^~~~~~~ chan_simpleusb.c:800:1: error: version control conflict marker in file 800 | >>>>>>> bb24ae8b5b892a4984f370a109bdd321a8d4eb80 | ^~~~~~~ chan_simpleusb.c:766:6: warning: variable ‘configured’ set but not used [-Wunused-but-set-variable] 766 | int configured = 0; | ^~~~~~~~~~ chan_simpleusb.c:765:6: warning: variable ‘opened’ set but not used [-Wunused-but-set-variable] 765 | int opened = 0; | ^~~~~~ chan_simpleusb.c:809:1: warning: control reaches end of non-void function [-Wreturn-type] 809 | } | ^ make[1]: *** [/usr/src/asterisk-20.5.2/Makefile.rules:150: chan_simpleusb.o] Error 1 make: *** [Makefile:396: channels] Error 2 |
Instead of having separate tune files for each node, look for a section for the node in the main config file. Closes #276
bb24ae8
to
2a0ad07
Compare
Looks like those creeped in due to some Git weirdness. Config issues have been resolved and changes repushed. Comments welcome. |
The device string is correct now thanks to @InterLinked1. I did some basic testing including |
The repeater used for testing USB was found stuck in transmit. The node (2509 and 25334) was configured with chan_voter and chan_simpleusb. The voter node (2509) was not keyed. The USB node did not have a URI attached so unknown how repeater was keyed. Will monitor. |
Instead of having separate tune files for each node, look for a section for the node in the main config file.
Closes #276