Re: HBLink: Adhoc clients with routing rules, conferences etc
Cort N0MJS <n0mjs@...>
I don’t see it going beyond the ACL logic from the bridging apps: An (allow | deny) a list of subscriber IDs (list meaning multiple entries, including ranges) and the same for destination TGIDs… with the allow/drop action on ingress.
Those are basic sanity and security filters… really beyond that and we’re starting to talk more about selective call routing… which belongs elsewhere.
0x49 DE N0MJS