Currently, when adding blacklist entries from a registered extension via *30, there is no way to enter an expected E164 formatted number such as +19999999999. I recommend defaulting all entries to using CONTAINS, meaning if the entry is 9999999999 it will look for the number containing this sequence.
If a user chooses to blacklist the last caller via *32, then it needs to be smart enough to remove any + in the number.
This has already been suggested… The ability to determine the destination when entering a Blacklist item from a phone, such as “Press one for a fast busy, Press two to send to a voicemail box”, etc.
This too has been suggested… Upload and download of a blacklist CSV file.
Finally, API calls and methods for managing the blacklists.