Skip to content

Implement a method for AMI/app_rpt to return a connected node graph data structure #147

@davidgsd

Description

@davidgsd

A common issue with AllStar is that users sometimes make multiple connections at a time and thus bridge large numbers of nodes together. Admins of repeaters/hubs then have no easy way to know which nodes made those connections or which indirectly connected nodes are keying up. The ASL Stats API is not very helpful because nodes are not required to do stats reporting, and the stats API does not have any easy way to get the data structure that the bubble chart graphics are generated from.

AMI does provide the rptStat Conn LinkedNodes list, and it would be interesting to know how it assembles that information, when it may have never received any IAX data from some of the nodes. Apparently, when an IAX connection is made there is some exchange of that information (indirectly connected node #s). And presumably therefore, there should be a way to get that data from Asterisk in a more structured way (node graph data structure rather than just a CSV list). This would be a very useful and important enhancement, as without it repeater/hub admins have no easy way to prevent major issues anytime any user accidentally or intentionally bridges large numbers of nodes. Ideally there could be an API that returned a structure showing all directly and indirectly connected nodes and the last time that each of those nodes keyed up.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfor_app_rptEventually Move to app_rpt

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions