Smart questions
Smart answers
Smart people
Join Tek-Tips Forums

Member Login

Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Block Incoming number to all usersHelpful Member!(6) 

Cambece (TechnicalUser) (OP)
1 Sep 06 8:46

I was wondering if there is a way to build an incoming route that would block a number to all of the incoming routes. We have several locations and a total of 600 routes. So short of building individual routes to block the number I was wondering if there is a way I could do this so it applies to all of our routes.

I have tried to leave the incoming number blank and just fill in the caller id and set the destination to a busy short code but that did not work. Any ideas would be appreciated.

kristiandg (Programmer)
1 Sep 06 8:53
Yes, absolutely.

INCOMING CALL ROUTING.  Normally this is used for inbound DID translation, but you can also number-match to treat certain area codes, office codes, specific numbers with different treatment.

You can input the Caller ID and set it specifically to go to something that plays busy signal (perhaps a shortcode with the feature set to CANCEL OR DENY.

Hope this helps...

Kris G.
Helpful Member!(4)  Cambece (TechnicalUser) (OP)
1 Sep 06 8:59
Thank you for the quick reply, instead of leaving the incoming number blank I entered a * and that seems to work.

Thanks again.
kristiandg (Programmer)
1 Sep 06 9:02
You just killed ALL inbound calls most likely.

Kris G.
Cambece (TechnicalUser) (OP)
1 Sep 06 9:15
Nope, tested it out and everything seems to work. Thanks for the concern though.
kristiandg (Programmer)
1 Sep 06 9:37
I'm confused.  How does a * tell it a specific number?  If you're trying to block specific numbers, you need to tell it what numbers you want to block.

Kris G.
kmefford (Vendor)
1 Sep 06 9:50
The * is for all calls when using ananalog lines.  Then you use the "incoming caller id" field to block calls with a certain caller id information.

We have a few routes to block a few people that directs the incoming call to a voicemail pro module I named "discon" that is simply a Start Point--->Disconnect

I also have all incoming calls with no caller id go directly to our auto attendant.

We get a LOT less solicitation calls now. :)
IPGuru (TechnicalUser)
1 Sep 06 9:58
I had completly forgoten about using * as the incomming number along with the CLI field so I think that is worth a *
kristiandg (Programmer)
1 Sep 06 12:05
Indeed.  Here's another.

Kris G.
jamie77 (Programmer)
1 Sep 06 15:15
Would this work on PRI lines in the UK??

Lets say we have 150 DDI's progrmmed to individual users.

Can we block one i/c CLI by adding one route with a * s the i/c DDI and the CLI to be blocked.

When I have needed this before, I have added the CLI to every IC call route so I had each DDI programmed twice.  one for CLI block and one for user.

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

mattKnight (Programmer)
2 Sep 06 5:06


Can we block one i/c CLI by adding one route with a * s the i/c DDI and the CLI to be blocked.

IIRC (and will check) the incoming number (DDI digits) is matched before the CLI is checked so you will need 2 routes per ddi

Take Care

If at first you don't succeed, skydiving is not for you.

jamie77 (Programmer)
2 Sep 06 8:22
That is what I thought.

Thanks anyway

Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!

IPGuru (TechnicalUser)
4 Sep 06 4:59
I havnt tested but if it is working for cambeece it should still work in UK

I would recommend giving it a test on a "tame" system.
if you can do that before I get a chance it will be worth another *
Helpful Member!(2)  aarenot (Vendor)
10 Sep 06 14:36
Here is one for giggles.
route the ICR for the specified CLID to a user that transfers the call to the number you are blocking.   Whenever they try to call, they will be transferred externaly to themselves.   
OK, maybe more fun than practical.   

You do not always get what you pay for, but you never get what you do not pay for.

relder (MIS)
2 Oct 06 17:16
I am searching because I have a similiar situation. An ex of one of the employees is making harrassing inbound calls to random numbers within our DID block and I have been instructed to block these at the switch if possible. So, I created a dummy user and directed via ICR, calls from him to the dummy CallBlock user which unconditionally forwarded them back to one of his own numbers he dials from. If the home number directs to the cell and vice-versa. Actually I created CallBlock1 and CallBlock2 users to do that. Worked great until he figured out he can dial *67 and block his CID, thus negating the ICR rules. Are there any negative possibilities to creating a rule such as this:

ICR: *
Incoming Caller ID:
Destination: CallBlock user port

Would the proper syntax be to leave the Incoming Caller ID blank to match a WITHHELD cid or could you use "" or <NULL>. Or is the whole concept flawed to start with?
aarenot (Vendor)
2 Oct 06 17:58
Check out !, and ? for incoming CLID field in ICR.   The help file below lists this information.  
 I would route the call via ICR to a receptionist.   The receptionist should be bale to recognize the voice at some point, and then put the caller on hold indefinitely.   This will probably discourage the caller most effeftively to waste his time on hold.
     I hope this helps.    

Incoming Caller ID:
Enter a number to match the caller's ICLID provided with the call. This field is matched left-to-right. Number options are:

Full telephone number.

Partial telephone number, for example just the area code.

! : Matches calls where the ICLID was withheld.

? : for number unavailable.

Blank for all.

Note: To match on just the Incoming Caller ID, use a * in the Incoming Number field and leave the Incoming Sub Address blank.

Bearer Capability:

You do not always get what you pay for, but you never get what you do not pay for.

relder (MIS)
4 Oct 06 18:42
Thanks, I had applied the block by creating a CallBlock user with the Incoming Caller ID: blank and saw that it took out the unknowns as well as the withheld ICLID's so I had deleted the ICR entry.

Using Incoming Caller ID: ! just as we wanted. The calling has now ceased, but I am thinking of leaving the rule for a while to test whether we might want to just leave it in place for good.
aarenot (Vendor)
4 Oct 06 20:34
you might want to consider routing it to a person that can screen calls that did not send clid unintentionaly, or send to a aa that does not allow transfer to the emloyee in question.   so you do not lose callers that for some real gliche did not send clid.

glad i could help, thanks for the reply on the resolution, that helps everyone.   

You do not always get what you pay for, but you never get what you do not pay for.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close