Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: mhumphries on April 24, 2018, 12:15:34 PM
-
so here is my current setup
ARS Digits Dialed vid7.31 14.0.3.19
0 1 2 3
Digits Dialed ....Number of Digits to Follow.... Termination Type.... Termination Number
1020................4............................ ....Route................12
8 ................7................................ Route................12
818XX...............7............................ ....Route................12
81NXX...............7............................ ....Route................12
8911............... 0................................Route........... .....10
8NXX................7............................ ....Route................12
9...................7............................ ....Route................20
9011................Unknown...................... ....Route................19
911.................0............................ ....Route................10
91NXX................7........................... ....Route................19
ARS Routes
Route Number COR Group Number Digit Modification Number Route Type
10....................4.........................8 05..............Emergency
12....................4.........................8 05
1
19....................1.........................1 9
20....................1.........................2 0
Class of Restriction Groups vid7.1
0 1
Number Classes Of Restriction For Group
1
4....................4
i would like to restrict international calling to assigned users only
currently all users have a CoR of 1
i am thinking i need to setup something like CoR groups, creating 2 new CoR and blocking the default.
1......................1-64 #block all by default
20....................1-19,22-64 # no international calling
21....................1-20,22-64 #interntional calling
then modify the Digits Dialed like so, assigning the 9011 to its own termination number
ARS Digits Dialed vid7.31 14.0.3.19
0 1 2 3
Digits Dialed ....Number of Digits to Follow.... Termination Type.... Termination Number
1020................4............................ ....Route................12
8 ................7................................ Route................12
818XX...............7............................ ....Route................12
81NXX...............7............................ ....Route................12
8911............... 0................................Route........... .....10
8NXX................7............................ ....Route................12
9...................7............................ ....Route................20
9011................Unknown...................... ....Route................21
911.................0............................ ....Route................10
91NXX................7........................... ....Route................19
then modify the ARS Routes like so, giving the 9011 its own ARS route
10....................4.........................8 05..............Emergency
12....................4.........................8 05
19....................19......................... 19
20....................19......................... 20
21....................20......................... 19
then assign the proper CoR to all phones in the system.
is that about right?
what happens to the Emergency route? do i need to address that also? it currently works but i think that it works because everyone is a one. should the core read more like this 1-3,5-19,22-64?
am i missing some over pitfall?
-
Have you seen this link?
http://www.mitelforums.com/articles/mitel_ars_programming.php
Ralph
-
Have you seen this link?
http://www.mitelforums.com/articles/mitel_ars_programming.php
Ralph
i have seen this and that is where i based this post on but since i am not 100% sure i thought i would reach out to guys that are much smarter then i am and ask if you all thought this was a solid setup. ??
-
The important bit to remember is that routes reference COR Groups, while devices and trunks belong to COR Classes, which can then be assigned to a group. If a class is included in a COR group, it is blocked from any routes using that group. So, for your example of COR Group 19, any COR classes assigned (and, by extension, the devices or trunks assigned those COR classes) to that group are blocked.
-
Here is a nice planning document I was given during the training course.
It lays out the connections on one page