AllStarLink / app_rpt

Refactoring and upgrade of AllStarLink's app_rpt, etc.
4 stars 2 forks source link

When using chan_usrp - rpt_manager_do_xstat: Channel USRP/10.100.21.2:3810:4810 does not exist, #254

Closed KB4MDD closed 6 months ago

KB4MDD commented 7 months ago

I am seeing the following error while using chan_usrp:

[2023-12-12 19:31:24.816] WARNING[663]: app_rpt/rpt_manager.c:304 rpt_manager_do_xstat: Channel USRP/10.100.21.2:3810:4810 does not exist, cannot access variables

core show channels - output

Channel                                                          Location                         State   Application(Data)
DAHDI/pseudo-2045213593                                          s@default:1                      Rsrvd   (None)
DAHDI/pseudo-511676044                                           s@default:1                      Rsrvd   (None)
DAHDI/pseudo-118260524                                           s@default:1                      Rsrvd   (None)
DAHDI/pseudo-1687719277                                          s@default:1                      Rsrvd   (None)
DAHDI/pseudo-1062259241                                          s@default:1                      Rsrvd   (None)
DAHDI/pseudo-38716724                                            s@default:1                      Rsrvd   (None)
DAHDI/pseudo-1932063524                                          s@default:1                      Rsrvd   (None)
usrp/10.100.21.2:3810                                            s@default:1                      Up      Rpt((Repeater Rx))
DAHDI/pseudo-2085628179                                          s@default:1                      Rsrvd   (None)
9 active channels
0 active calls
0 calls processed

This occurs when using allmon3 - apparently it is polling xstat and xstat is failing with the above message.

InterLinked1 commented 6 months ago

What channel is allmon3 actually asking for here?

usrp/10.100.21.2:3810 exists (case insensitively), but there appears to be a :4810 tacked onto the end. It seems that is the rxchanname, which itself seems to come from rxchannel in rpt.conf. Which is "correct", the one with or without the :4810?

Do you mind also posting the output of whatever shows all the RPT channel names?

KB4MDD commented 6 months ago

@tsawyer can you help me with a command that will show the information that @InterLinked1 asked for?

I have not had a chance to look at this and run down the problem.

InterLinked1 commented 6 months ago

@tsawyer can you help me with a command that will show the information that @InterLinked1 asked for?

I have not had a chance to look at this and run down the problem.

I think it's "rpt show" or "rpt dump" something. I don't have a working RPT system so I can't easily confirm off hand but tab complete should bring it up.

I am curious, is there any way to set up a test system with USRP to reproduce this w/o any working equipment?

KB4MDD commented 6 months ago

You can setup a system using chan_usrp without having any hardware. usrp uses UDP - so it will be happy without hardware.

I tried several rpt commands and I could not find one that would show the channel information.

tsawyer commented 6 months ago

I don't have any experience with USRP. Not sure what you'd like me to do?

InterLinked1 commented 6 months ago

I don't have any experience with USRP. Not sure what you'd like me to do?

Never mind, I looked through the code and found it. @KB4MDD try "rpt show channels"

KB4MDD commented 6 months ago
wa4tal*CLI> rpt show channels 59916
RPT channels for node 59916
rxchannel                : usrp/10.100.21.2:3810
txchannel                : usrp/10.100.21.2:3810
monchannel               : DAHDI/pseudo-1133932976
parrotchannel            : DAHDI/pseudo-464123768
pchannel                 : DAHDI/pseudo-814516628
txpchannel               : DAHDI/pseudo-1209733067
dahdirxchannel           : DAHDI/pseudo-814516628
dahditxchannel           : DAHDI/pseudo-1384280824
telechannel              : DAHDI/pseudo-1269191901
btelechannel             : DAHDI/pseudo-164909345
voxchannel               : DAHDI/pseudo-940016395
KB4MDD commented 6 months ago

I am researching the issue now. I enabled AMI debugging. Node 1998 is using chan_usrp.

[2023-12-30 16:19:27.636] <--- Examining AMI action: -->
[2023-12-30 16:19:27.636] ACTION: RptStatus
[2023-12-30 16:19:27.636] COMMAND: XStat
[2023-12-30 16:19:27.636] NODE: 1999
[2023-12-30 16:19:27.636]  ActionID: e0c90bf6-0737-4f51-bdf3-592042197a6c
[2023-12-30 16:19:27.636]
[2023-12-30 16:19:27.636] <--- Examining AMI action: -->
[2023-12-30 16:19:27.636] ACTION: RptStatus
[2023-12-30 16:19:27.636] COMMAND: XStat
[2023-12-30 16:19:27.636] NODE: 1998
[2023-12-30 16:19:27.636]  ActionID: 64522323-3b4a-4561-9577-3368a7ea062d
[2023-12-30 16:19:27.636]
[2023-12-30 16:19:27.636] WARNING[104444]: app_rpt/rpt_manager.c:304 rpt_manager_do_xstat: Channel USRP/127.0.0.1:34001:32001 does not exist, cannot access variables
KB4MDD commented 6 months ago

myrpt->rxchanname has the name as Channel USRP/127.0.0.1:34001:32001

rxchan = ast_channel_get_by_name(rxchanname); fails to find a channel by that name. It is clear that it does not exist as that name.

On my development system, rpt show channels 1998 shows:

RPT channels for node 1998
rxchannel                : usrp/127.0.0.1:34001
txchannel                : usrp/127.0.0.1:34001
monchannel               : DAHDI/pseudo-370293276
parrotchannel            : DAHDI/pseudo-1958804756
pchannel                 : DAHDI/pseudo-1247351427
txpchannel               : DAHDI/pseudo-90465762
dahdirxchannel           : DAHDI/pseudo-1247351427
dahditxchannel           : DAHDI/pseudo-1679735465
telechannel              : DAHDI/pseudo-1071193616
btelechannel             : DAHDI/pseudo-1693803593
voxchannel               : DAHDI/pseudo-163325040
k4mdddevelop*CLI>