[cisco-voip] COR sanity/best practice check..

[Lelio Fulgenzi]

Yes, I only found the matrix after a few days of reading. Wish I had found it earlier. The important thing to remember is superset. Incorrectly, I drew an intersection of two circles while reading. :(

Then I started trying to figure thing out with the PSTN dial peers having a COR with more than one group in it. That too confused things. Think of the COR of an outbound dial peer as a partition, i.e. one group only, and the CORs of the phones as a CSS , containing multiple groups. 

Sent from my iPod

On Nov 1, 2010, at 1:26 PM, Ed Leatherman <ealeatherman at gmail.com> wrote:

> Thanks Lelio. I was reading the IOS dial-peer configuration guide..
> the one you are referring to is much better at clearing up my
> questions about cor.
> 
> On Mon, Nov 1, 2010 at 12:36 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>> I would take the same approach in thus scenario Ed.
>> 
>> Some notes:
>> 
>> - there is a matrix that explains what happens when one leg of the call has a dial peer with a COR on it and the other does not. Just google "COR site:cisco.com" and it should come up
>> 
>> - consider the fact that inbound calls from the PSTN can be transferred and/or forwarded (sometimes intentionally, sometimes not) back out the PSTN, without CORs. Be careful. Especially with two stage dialing and autoattendants on CUE.
>> 
>> 
>> Sent from my iPod
>> 
>> On Nov 1, 2010, at 12:06 PM, Ed Leatherman <ealeatherman at gmail.com> wrote:
>> 
>>> This is (probably) a very basic CME question but I am curious if I'm
>>> pursuing it in the right manner or if there is a smarter way.
>>> 
>>> I have a CME (4.1) install at a branch office. It's 1 department and
>>> no call restriction really is needed, so no COR or anything going on.
>>> normal POTS lines to PSTN with a CUE AA.
>>> 
>>> Now they are moving in a 2nd department that is to be using a
>>> different set of PSTN lines, so that the 2 groups don't impact each
>>> others PSTN calling capacity inbound or outbound. They want to be
>>> logically separated with regards to voice/data.
>>> 
>>> I'm guessing COR is the way to go here but i've not set it up before.
>>> My initial thoughts are to set up a COR for the existing department
>>> and configure their existing ephone-dn's and dialpeers for that, and
>>> then a second COR for the new group, and just make a duplicate
>>> dialplan basically for that group. I suspect I might need some nuances
>>> in there so that they can call each other and CUE internally also. Am
>>> I headed down the right path here?
>>> 
>>> If an outbound dial-peer has no cor-lists setup for it, can any
>>> ephone-dn or inbound dial-peer regardless of COR? or must all
>>> dial-peers have a COR lists configured once I start this? I'm thinking
>>> for 911 and voip dial-peers I want anyone to have the capability to
>>> call, maybe I don't have to add any additional complexity for these.
>>> 
>>> Thanks in advance!
>>> 
>>> 
>>> 
>>> --
>>> Ed Leatherman
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> 
> 
> 
> 
> -- 
> Ed Leatherman