Blocking incoming calls/numbers

[southeasternMI]

ShoreTel needs to look into a feature in the trunk groups, so certain numbers can be block from calling in at the trunk level and or the extension level.

[Forum]

there is a SDK that does just that. It will block all calls from a particular number. It's designed for faxes (to block spam faxes), but it will work other ways as well. It operates at the TRUNK level.

Sorry though, I don't have access to it, but I know somebody who does

[blanning]

Not only should you be able to block calls form a certain number, but you should be able to have different ring tones based on the incoming trunk (not number but trunk). This is vital for call centers where they answer for multiple businesses.

[Palitto Consulting]

Have you tried personalized call handling rules in ST9. I have heard that this works for the distinct rings. Since we do not have DNIS here, I haven't been able to test yet.

[Rob Bush]

Just editing my post because after reviewing I see that I was in error with my information. Sorry about that everyone... Thanks Bobby for pointing it out. Rather than leave it in here and mis-guide someone else, I'd prefer to edit so others don't make the same mistake if they don't read Bobby's post below.

<original post>
You could just route a DNIS number to an AutoAttendant that either plays a nice message that indicates you don't want them to call, or just record silence. Either way, don't give them any menu options and just tell it to hang up the call. The nice thing is that this can be done with any version of Shoretel.

One caveat about the Personal Call Handling rules in ST9. #1 You can't "BLOCK" a call. You can send it to voice mail, you can send it to an AA that is specific for phone spam, but you can't block a call. #2 It doesn't work for inbound workgroup calls.

To implement inbound DNIS routing... Go to your Trunks and select a PRI Trunk group. Click on the 'Edit DNIS Map', enter in the inbound phone number, and select a destination AA you have setup for phone spam and hit the Save button and, BOOM, no more phone spam.
<end of original post>

[Bobby_Digital]

Mmmm...DNIS would be for a called number, not calling number...So, you would block all calls to a certain number, not from a certain number.

DNIS- Dialed Number Identification Service

[Palitto Consulting]

Personalized Call Handling rules work both off of DNIS or caller ID, depending on the options you choose. They do not work with calls coming from a workgroup.

[blanning]

Have you tried personalized call handling rules in ST9. I have heard that this works for the distinct rings. Since we do not have DNIS here, I haven't been able to test yet.

This works great if you have a PRI or SIP trunks and can use DNIS, but there is no way to handle the situation based on trunk, or trunk group. This is a problem for those who are stuck with copper lines.

[Bobby_Digital]

Just editing my post because after reviewing I see that I was in error with my information. Sorry about that everyone... Thanks Bobby for pointing it out. Rather than leave it in here and mis-guide someone else, I'd prefer to edit so others don't make the same mistake if they don't read Bobby's post below.

Well, its good info on DNIS mapping, which is a pretty cool thing, especially in a Call Center environment with multiple customers calling different DIDs!

[Bobby_Digital]

So, here in Germany, we use a Patton Smart Node in between the Telco and Shoretel E1 or BRI switches.

Its a really cool product, and it can perform this function, you can make a rule that says if the inbound caller ID matches (xxx)xxx-xxxx, send to wherever you want to send it.

Thats if you want to spend the money

[davidbec]

Am I correct in saying that based on what Bobby Digital said post #6, you will not be able to block unwanted callers because they are calling the same number as the wanted callers? Using DNIS?

ie. Normally you have one or two numbers that the public (you want) calls to reach a company and the unwanted are calling those same numbers.