COR explanation 1

[rfcomm2k]

I have looked at many of the threads relating to COR on Avaya Definity, but they all seem to start with the basic premise that the person asking already knows how to do it.

I am new to Definity, have no opportunity to go to school on it, but am tasked with keeping the system operating. I could of course fail at this, which would be a disappointment to me, the customer, and my employer, so I am trying to avoid that.

I am well trained in other products (Cisco UCM, NEC, Mitel, Siemens, Panasonic), but have never seen Avaya until last February. This is the first time a problem has been raised about COR.

So the problem: Certain phones here are restricted to dial 610 and 215 area codes only. And apparently these phones cannot dial toll free calls (800, 888, 866, 877, etc). I looked up a restricted phone, saw that it is COR 4, whereas my phone is COR 1. I displayed COR 4, and that is where I lost it. 0?, 1? 2?, 15?, 87?, what do these all represent?

Is it the dialed digits AFTER stripping off the access code 9?

Is it ALL the dialed digits including the 9?

Is it something else?

Attached is a screenshot of tab 3 of COR 4.

 

[kyle555]

CORs have a FRL - facility restriction level - 0 thru 7.
Dialed strings in ARS match to route patterns. Choices in route patterns also have a FRL.

If the FRL of the COR of your set is equal to or greater than that of an entry in a route, you may pass.

 

[rfcomm2k]

But what are the entries I see when I display COR 4 tabs 3-12? In my system COR 4 has FRL = 2.

 

[DAVIDPAYNE]

You will normal never need to adjust those on most system. And as long as there are flaged as Y, you should be good.
AS Kyle555 said, you would limit call routing by the FRL and the route pattern.

 

[rfcomm2k]

Thank you both for these answers.

Now, try to explain it to someone who has NEVER worked with COR on Avaya before.

Or, let me put it to you differently. In the NEC system, which I am most familiar with, there is a routing table (AFRS) in which you place an entry consisting of the access code plus the digits dialed as you want them to be analyzed. For example, if the access code is 9, and you must dial a 1+NPA for every call, and you can split your local routing by exchange, then in the AFRS table for my site (area code 610) I would have 9160 pointing to the route table for all area codes beginning with 60. Then, more entries made for 91610xxx (xxx representing each different exchange in area code 610), and these entries would point to the appropriate routing tables for those different exchanges. And thirdly, 912, 913, 914, 915, 9162, 9163, 9164...919 would all be entries in the AFRS table for those area codes.

So, I ask again, so I can understand, what do the entries I show in my sample data represent? Are these dial patterns, or what?

 

[montyzummer]

So in your screen shot they are quite simply the dialling permissions between each COR , if you were to set the highlighted entry "0" to N that would mean that anything in the system that has the COR that you are changing at the time of the screen shot assigned , would not be able to dial anything else that is assigned a COR of "0" in the system.

In you last post you are referring to the Avaya feature called ARS or AAR , ARS (automatic Route Selection , anything off local network....carrier trunks etc) & AAR(Auto alternate route , anything on net so IP/Tie trunks to a separate PBX , messaging etc) , in the ARS and AAR tables is where you designate what route pattern to use when digits that hit those tables utilise , then the route patters contain the physical trunks.

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[joe2938]

https://www.google.com/#q=avaya+world+class+routing

click on this link it will take you teach you world class routing at least it's a start

 

[rfcomm2k]

OK Monty, that is a bit more helpful. But where then would I go to tell the PBX that COR 4, which is what all these phones in question have, would be allowed to call toll free numbers instead of ONLY the local area code.

If I change the cor on my phone from 1 to 4, then I can still dial 215 and 610 calls, but I cannot dial any toll free numbers. And I was told I can enable toll free calls for COR 4.

 

[kyle555]

All the Y/N means is "is this COR allowed calling that other COR. Normally you'd never need it unless you were multi-tenant renting services and didn't want people calling 'internally' across tenants.

Only time I've ever had to use it is for a natural resources company with guys on shift work and you don't want anyone but their boss being able to accidentally fat finger their extension and call them during the day when they're sleeping.

 

[joe2938]

If you read the manuals from the link I attached you will start to understand a little better

 

[montyzummer]

So its the ARS tables that define what to do when dialled , you also have toll lists page 1 of the COR screen , what is that field set to on your COR page 1 , the command "list toll all" will show you what is applied in the toll tables , see below where it says all-toll ,this then populates the unrestricted call list that tallies with the toll table command.

This is conjecture but im guessing COR 4 has the unrestricted call list populated with an entry.... you need to look at the toll list screen and work out the lists that COR can dial , either that or set all-toll to none and open up everything.




ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[montyzummer]

ARS tables that define what to do when dialled , you also have toll lists page 1 of the COR screen , what is that field set to on your COR 4 page 1 , the command "list toll all" will show you what is applied in the toll tables , if it says all-toll ,this then populates the unrestricted call list that tallies with the toll table command.

This is conjecture but im guessing COR 4 has the unrestricted call list populated with an entry.... you need to look at the toll list screen and work out the lists that COR can dial , either that or set all-toll to none and open up everything.

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[rfcomm2k]

Joe, I am reading it now. Trying not to skip ahead too!

One thing confuses me now. I looked at ARS ANA and see 1877 is in the table with min/max digits = 11, route pattern = P1, and type = fnpa. I changed my cor to 4 and dialed an 877 call. It went thru. I dialed several different 877 numbers and all went thru. EXCEPT for 1 specific number. I even dialed an identical number except I changed the last digit of the number. Call went thru.

Where is this restriction occurring?

 

[montyzummer]

run "list trace station xxxx" and post the results of a failed call , but its sounding like toll restriction

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[kyle555]

telco probably

 

[rfcomm2k]

trace uploaded

 

[montyzummer]

So thats self explanatory COR needs a higher FRL than route pattern 14

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[rfcomm2k]

Isn't there just somewhere I can Allow that particular number instead? If I start changing the FRL for COR 4 won't that potentially allow the user to place calls somewhere they should NOT be calling from that particular phone? All I want to do is to allow all COR phones to dial w=exactly what they can right now PLUS 8775659999. Nothing more, nothing less.

 

[kyle555]

so make an exact match in ARS for that number to go to a route that has the FRL of your users.
Say, if 1888 min/max 11 had route 5 with FRL5, you'd add 1877565999 min/max 11 to route 4 with a FRL of 4 as an example.

 

[rfcomm2k]

OK kyle555, in list ARS ANA, 1877 and 1888 are both in there, identical. So OBVIOUSLY there is somewhere else that is blocking 18775659999. Where is THAT being done.

So I typed list ars route-chosen 18775659999 and I got back dialed string 16, route pattern p14.
Then I typed list ars route-chosen 18775659998 and I got back dialed string 1877, route pattern p1.

What did that prove? IDK, because I know very little about this, and all the help I have received so far has done little to help me understand.

If I were to GUESS, 18775659999 is being changed from a toll free call to a local call (hence the dialed string 16), but WHERE IS THAT BEING DONE AND WHY IS IT RESTRICTED? Because ALL phones in COR 4 should be allowed to call 215 and 610 numbers (again, I am assuming the dialed string 16 is referring to calls to 1610xxxxxxx numbers).

Jeez, why is it so hard to get a direct answer here. I do not think it is my lack of knowledge at this point.