COR setup

[johnp]

After my last response, it had me thinking. How do you all like to setup yours? Being in the US, I set 1 to allow 1NNX, 2 internal, 3 tollfree, 4 local + tollfree, 5 local, tollfree, lata, 6 ...+statewide, 7 ... +continental US, 8 US + ak and hi, 9 US and Canada, 10 ...other 1 plus islands, 11 ... 011, 12 add 1900

[LoopyLou]

Since COR 1 is the default I always make it totally restricted. I would rather get a call from the customer saying the created a new user and they can't call out rather then a call that they have thousands of dollars in toll fraud. So what I do is 1 is internal only ( totally blocked ), 2 local, 3 Canada wide, 4 international. Depending on the customer the international might be subdivided to restrict some areas.

[acejavelin]

Actually, for most of my customers 1-3 CORs is usually all that is needed. Like LoopyLou I keep COR1 as fully restricted on new installs, then depending on the customer requirements, I setup one that is allowed everything except 900 calls which is all 75% of customers need. In a few others I setup a COR to allow local and 800's only, one to allow Local/800/1+LD, and one to allow all but 900 calls. Unless there are specific requirements, this is all that is really needed. When it comes to ARS, I believe in the KISS principle.

[v2win]

We do 7 levels of COR tables and associate them with the same route numbers

1   1-64           Restricted
9                     911 Unrestricted
11 1-10,16-64 Local/Toll Free
12 1-11,16-64
13 1-12,16-64
14 1-13,16-64
15 1-14,16,64 International/Unrestricted

Then the CORs 11-15 go to routes 11-15, 21-25 etc... depending on the number of routes

We also make the Digit Mods equal the route numbers. Its somewhat repetitive programming but it makes it easier to troubleshoot.