My initial reaction to this post was "that would not be hard to do". But to
@Frederick Marcoux point, this is probably more efficiently handled at the carrier.
I don't know how many phone numbers we are talking about, but I assume we are talking about many thousands of numbers. Asking your 3CX server to evaluate every inbound call against a list of tens of thousands of phone numbers might have performance impacts.
However, we have a tool (
3CX Do Not Call) that compares every outbound phone call against a very large list of phone numbers (we have customers with over 6 million phone numbers in their list) and we can evaluate and reject calls before the carrier can set up the call and start ringing. So, this should be possible.
We had a similar conversation in the forums a couple years ago about creating a shared list of IP addresses that should be blocked. In that conversation we talked about how every 3CX partner could submit IP addresses to the shared list, and based on the number of submissions, rank how likely the IP should be blocked. We would also probably need a the ability to whitelist certain IPs that were erroneously added to the list. And perhaps provide a mechanism for requesting the removal of an IP from the shared list. We could do the same for phone numbers.
We have to recognize, however, that someone would have to be the caretaker of the master list. That presumably means maintaining a website for accepting submissions, and a webservice to provide updates to subscribers. There is a cost to maintaining this infrastructure, but that could easily be covered by a modest paid subscription.
Perhaps there are already services that provide this functionality? If so, then all that would be needed is a local service running on your 3CX server that maintains the list. If there is sufficient interest, we have the expertise needed to build and manage all the pieces for a solution. If you are interested, email me and we will see whether their is enough demand.
