Block specific Inbound Callers

[PFCCWA]

Hello,
Does anybody use a routing method whereby specific inbound callers are blocked?
The obvious function is a segmentation which determines the ANI of caller, then directs them to an annoucement.
This requires continuous additions if we have multiple ANIs to block.

Is there a more efficient way? maybe have a list checked?

Thanks.

[Kubig]

Yes,it is standard blacklist function. My way was in create new substrategy in which I have checked ANI number against blacklist database,and all caller with blacklist result = 1 were abandoned.

[smile]

one can suggest using list object instead of external db. the pros - it's more simple to develop and simple to make changes via Administrator. The cons - it works fine only if you have small list, because urs load all list object into memory during startup...
I agree with Kubig, substrategy with result is preferable.

[terry]

Also there is very old URS function created originally for similar things - ListLookup.
When List objects were introduced ListLookupCfg function was added basically to provide the same functionality based on List objects.
Original ListLookup work with databases (through tablaaccess objects), it also allows cashing of information from database with periodic aupdates (if it is not too big) to avoid acessing database for every call.