|
|
|
|
Joined: Nov 2013
Posts: 1
Member
|
|
Member
Joined: Nov 2013
Posts: 1 |
I have done the above but when I select "Collected Digits" for the number I want to block I no longer can enter a Ring-In Destination. It rings to the Primary Attendent. My doc says, "If the collected digits plus the base digits do not make up a valid ring-in destination, the call is routed to the primary attendant."
I'm running DB Studio 3.2 with an Inter-tel/Mitel 5200 version 3.2.4.59
Am I missing something?
Thanks in advance.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Jul 2013
Posts: 81
Member
|
|
Member
Joined: Jul 2013
Posts: 81 |
Nothing new to add to this, just how I listed the steps out for myself:
Make an existing DID ring to a new call routing table.
Set that new call routing tables’ Call Routing Key as Outside-Party Number.
Make its first entry the number you want blocked, and set it's destination as a hangup CRA.
Make 2 new, separate patterns “+†and “E†and set the destination to wherever you want the 'good' calls to go.
The good calls go where you want, the blocked number gets hung up on.
|
|
|
|
|
Joined: Jan 2006
Posts: 179
Member
|
|
Member
Joined: Jan 2006
Posts: 179 |
DnR, I do this the opposite way. Whenever I install a system with PRI, the CO trunk group points to a CRT using Caller ID to route, with E and + pointing to a second CRT routing based on DID.
That way I can intercept any calls from the harassing caller and dead-end them regardless of which number they call and after checking my CID list, I then route based on DID normally.
Just a thought.
Mitel, Samsung, CTP+ and A+ Certified.
|
|
|
|
Forums84
Topics94,428
Posts639,501
Members49,821
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
