We have 12 nodes in our network. I would be nice to see which one was keyed or trigger first that set off the other nodes. A great tool to help us monitor traffic and see which one is causing the kerchunking... Help any ideas.
Thank You
Sal N6SPD
28365
Are you not using Allmon3? Not really clear what you're asking here...
ASl3, Allmon3, Allscan, Supermon 7.4 Using all 4.
I would like to know the originating node or first node that the signal came from.
Keeping an eye on 12 nodes, it would be nice to see the traffic flow from trigger site.
There is no stat in asterisk for that to be able to retrieve it in the AMI for any of those programs.
However, there is a stat for the last node to TX.
Not helping this.
Look for the post on feature requests.
The current code does not provide any data over the connections to get this information. Hopefully, somebody smart will finish implementing this feature into app_rpt, and then dashboard utilities such as Allmon/Supermon/etc will be able to add code to implement displaying that information.
Supermon 7.4 does display where COS is received. . which would indicate that your other sites received a signal. It also tells you which is in PTT transmit and who is transmitting if linked into the site. Over RF it would indicate which site was used. better way is with a voter system to track the signal if the person is on the move. before mason says anything YES it was Done when we had the 145.190 Fara system in Ohio, Michigan, Kentucky and Indiana we did track a guy from system to system and what route he took. It can be done and has been done
Lol. You're misunderstanding, there is difference between just "looking at Supermon" what OP is asking. Supermon does the same thing Allmon3 does, and has the same data available to it. Supermon is not "special" in that regard. All Supermon does is tell you whether the key up came from the local RXchannel or an adjacent linked node. If the traffic came from a node that is linked to a node that is linked directly to you, well, Supermon just shows you that the traffic came from the node linked directly to you because there is no data that goes deeper than that 1-hop level.
OP wants to see "keyed" status from more than 1-hop away, which is not currently possible. Nowhere in the IAX data stream is that data sent.
I run a multi-site VOTER system, but the capabilities of that system do not have any relevance here. This thread is about getting keyed status from a non-local node that is more than 1-hop away from the local node.
I'm not saying you can't track down the source of a signal with the data we currently have available. I'm simply saying that the "keyed" status data in the IAX stream has not yet been implemented.
Sal, I might suggest, if you are willing to work for it, that you use a 'on event' program at each of those 12 nodes to log COS activity (not tx)
That is the only remedy I see in the short.
You might even be able to 'pool' a http gui to watch it by tailing the individual logs..