It depends on the type of trunking you are using, more than anything. If you are trying to block a range of numbers like 212555XXXX, this will block everything in the 212555 range. If you want to just block individual numbers build your ICRs to have the same incoming number but different CLI (each one is different so no duplicates) and send them to busy or VM that states number OOS.
Hmm, maybe the duplicate error was just a result of not running validation after saving the copy that I edited. It sounds like it works as I thought it did.
I just monitor traced a spam call where the originator spoofed the incoming number instead of the ICLID.
The incoming number was not in the owned range either.
It passed using the default route.
Then the spammers made a ga-jillion calls all at once.
ICLID had no number or name over PRI
They spammed a range so had to add a route to kill the range.
spamity spammers should get the spam spammed out of them.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.