this is how it was explained to me by Matt in another thread:
In short, here's what you do:
1) Make the PDN of the phone a non-DID; you can still have rollovers, FDN/HUNT/LHK, etc...
2) Build the DID number as a CDN
3) Acquire the CDN in Symposium / CCMS and add it to the Master Script; point to its own Primary Script
Assume the DID is x7580
Assume the non-DID you assigned it is 6580
That primary script should say something like this:
IF CLID = 3105551212 THEN (the number you want blocked)
GIVE BUSY (or DISCONNECT, or whatever you want it to do)
ELSE
ROUTE CALL 6580
END IF
That will screen the calls for the CLID of 3105551212 (calling number) and if that is the number that called, then it'll give it busy, or disconnect; whatever you want.
If it's NOT that number calling, it'll route it to the phone.
The only problem is this caller will just probably move to calling another number. We're exploring the possibility of installing a voice firewall on the PBX.
dee, another thing is once the CLID is blocked all the caller has to do is not send the calling information and the call goes through. So unless you allso block UNKNOWN NUMBER even with the firewall they will get through.
If the call is harrassing and threatening in nature, call the police and maybe a night in jail will get him to stop. Telemarketers, not sure of the "Do Not Call" registry will accept entire DID blocks or anything like that.
Securelogix firewall is your answer for this. if you ae talking about a voice firewall in your previous post then i assume you are already engaged in conversations surrounding this product. Keep in mind their product does much more than just block calls it can also re-route, alert, report etc. which opens up alot of different options when you start to apply functions with scenarios.
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.