Some of our customers are getting slammed by robo calls that have access to hundreds of caller-ID numbers to choose from. As soon as we block one number another one appears.
Sometimes they have the same Caller Name, I would like to be able block calls based on the caller-name as well as the caller-ID.
I always liked the way that FreePBX did inbound routes, now we just identify by DNIS, it could be expanded to:
DNIS
Caller-ID
Caller-Name
You could have multiple inbound routes for the same DNIS based on who is calling.
With the new DB driven back end the overhead shouldn't be that great.
-Matt
I guess, this will be white
I guess, this will be white/black lists, similar to what we already do for user extensions - not just single names or numbers, right?
So theoretically you could
So theoretically you could have an inbound route that matches and DNIS, any Caller-ID and a particular Caller name......send them to Lenny
On the system level I can
On the system level I can only see a blacklist, on the tenant level - every option. This also brings up a question of keeping the stats of all of the above. Also, what about a rule based automated black list management?
would it be possible to
would it be possible to implement a external hook to do this ? Like in form of a API Rest Call . Then the service could provide the block or no block response and anyone could go crazy in implementing its own logic to determine if to answer the call. What would be great would also be like being able to push a prefix in the caller id so it could get a spam info to the phone.
For now I created a fake user and changed the stored procedure which returns the blocked number to queries for all blocked nbrs for the user as well as the fake user. What that gets you is a system or tenant wide blacklist. I also created a small nodeJs scirpt to maintain the nbrs. What would be great now would be a way from connect to make a call to add a caller to the list.
Has there been an update to
Has there been an update to handle Tenant wide black list or Caller-Name blocking ? I have currently a System wide blocking via some modified mysql stored procedures which allow the nbr to be blocked system or user based.
This will create some overhead, but may be worth implementing. I will discuss this with the team