Really confused with setting up COR

[aperron]

Hi Everyone-

New to this forum.  I've been working with MiVB for a couple years now, but haven't had to do much with COR and I'm in kind of a bind with a new installation.

This customer is purchasing a MiVB system, 3300 AX controller.  They are a senior living apartment complex that provides analog lines off the PBX to the apartments.


We've been asked for this installation to put in 4 POTS circuits to provide failover in the event the PRI goes down.  Management would like the residents to be able to dial 911, and also 800 numbers (life-alert pendants and such dial an 800 number to report an activation) in the event the PRI goes down.  They would also like the managers and offices in the complex who have IP phones to be able to dial 911, 800 numbers AND any other number.

I'm at a loss on how to configure this.  I can think of ways to restrict the use of a certain trunk facility outright, but not to allow some users to dial 911 and 1800, while others can dial 911, 800 and anything else.

Any help would be greatly appreciated.  I want to make sure this works right, given the safety aspect of what needs to be accomplished.

[v2win]

Ralph actually has a really good how to article on this.

http://www.mitelforums.com/articles/mitel_ars_programming.php

[BlackSunshine]

Rule of thumb for COR....If your in....your Out!!!

[johnp]

Ralph's description is good guidance. My levels are a bit more, they go to Canada, US islands, Mexico before international.  The concept is there to embrace

[VinceWhirlwind]

Rule of thumb for COR....If your in....your Out!!!

So when you look at the form, to understand who might use a route, you have to look for the numbers that aren't listed. And you have info spread across about 5 or 6 different forms so you have to clunk around back and forth to try to figure out what it's doing.
The whole concept couldn't be designed to be more confusing - there's no point having a GUI when it doesn't make things clear.
Personally, I always fill out my own table before doing the programming, that way I can ignore the form while I enter the data and I know it will do what I want it to do.

[x-man]

Ditto with the own table. Once you have grasped the concept it is reasonably easy. However test test and test again once you have programmed just to make sure.  I remember setting up flexible LCR on the Mitel iMAGINATION; just as bad. made sense to programmers and the like but most engineers struggled until the concept dawned.....

[johnp]

I usually set it up like COR Group:
1 blank
2 2
3 2-3
4 2-4
etc
I then make someone with a 2 can only dial 911, 3 local/toll free, 4 plus lata, 5 plus state, 6 plus us (NXX), 7 plus Canada, 8 plus major islands, 9 plus Mexico, 10 plus international, 11 plus 900 976

As long as you understand that it is can't versus can when creating the COR Group setting, it isn't that hard to do.

[VinceWhirlwind]

That becomes a matrix if you are using location-based routing.
For example
NSW---VIC---QLD------User Class
-2------3------7---------Unrestricted
12-----13-----17--------Local, national, mobile
22-----23-----27--------local, national
32-----33-----37--------local only

You then have your route lists as per the digits dialled, eg
call type------Digits--------list:------Routes-----CoR----digmod----absorb----insert----User CoR permitted
emergency----0000+0-----1:--------1,31---------1---------1----------1-------------------all
international--00011+v----11:-----11,21--------11--------11---------1-------------------2-9
mobile--------004+8-------4:--------4,14---------4----------4---------1-------------------2-19
national------002+8-------10:------10,20--------10--------10---------1-------------------2-29
(repeat for 03,07)
local----------02+7---------2:-------2,12----------2---------2----------1--------02--------2,12,22,32
---------------------------------------3,13-----------3---------3----------1--------03-------3,13,23,33
---------------------------------------7,17-----------7---------7----------1--------07-------7,17,27,37
and then add 03+7, 04+7, etc... for all the other 8-digit local numbers to the same "local" routelist.
and then a list for the freecall type numbers, 013+4,01300+6,01800+6. Plus some weird security numbers and so forth that exist out there.
 
You then add another dimension to this entirely if your trunks aren't just redundant, but are located in places where call charges are variable, because then you have to add in least-cost routes depending on the specific national route or the user's CoR (which is linked to their zone), but when this is the case, you may not need location-based routing as well.
 
If you don't write this up as a table, trying to implement it using the controller forms makes your brain explode.