The Permit part of Match (Permit) is misleading. You are actually matching extensions by user name, and that is ORed with any IP address match; FreePBX PJSIP extensions never need Match (Permit).
As far as I know, the GUI doesn’t support specifying ACLs, so you would need to use custom configuration. Note that ACLs are not endpoint specific, so will give little benefit over the firewall:
Note that there are known vulnerabilities in 16.30.0 and security fixes for Asterisk 16 will cease entirely some time in October.
As I read ti the section name doesn’t matter, and it can probably go in any custom file for pjsp.conf.
Note that it will apply to INVITE as well as REGISTER, which is probably what you want, as there is no requirement for an extension to REGISTER before it originates a call.
I can’t imagine many people use this. They are more likely to block using the firewall than ACL.
The example clearly shows that it goes in a type=acl section and its effect is global. Your original example was a single deny, which might be meaningful. A single allow is unlikely to be useful.