could you post your solution?

greets norbert

See if this explains it

----------------------------------------------------CUSTOM DIAL PEER---------------------------------

dial-peer cor custom (We create the names here)

Name Unrestricted

Name Local

Name Cellular_Only

Name Local_Only

---------------------------------------------------CLASS OF RESTRICTION LISTS-------------------------

dial-peer cor list Unrestricted

member Unrestricted

dial-peer cor list Local

Member Local

dial-peer cor list Cellular-Only

Member Cellular_Only

dial-peer cor list Local-Only

member Local_Only

---------------------------------------------------ASSIGNED USER LIST (This is what we assign for the user)----------------------------------

dial-peer cor list International

member Unrestricted

member Local

member Cellular_Only

member Local_Only

dial-peer cor list National

member Local

member Cellular_Only

member Local_Only

dial-peer cor list LandLineOnly

member Local_Only

dial-peer cor list Cellular_Only

member Cellular_Only

Hope this helps

Hi Gooding,

I do understand that COR works like Partitions and CORlist like a CSS in CCM.

But in CCM we have Route Patterns assigned under Partitions, so when we apply the CSS, it works by seeing the Route Patterns.

But as we go to CUCME we don't have Route Patterns but destination pattern under dial-peer. And under ephone-dn we have the number assigned to it.

My query is that when one particular DN makes an outgoing call, the call checks the CORlist (CSS) and the CORlist goes to the COR (Partition),where only name is specified. How this will then restrict the Outgoing call?

Let me know if I sound stupid, Would deeply appreciate if some one clears this doubt

Thanks in Advance

Hi Ashish,

COR is often described as a lock and key mechanism. Locks are assigned to dial peers with an outgoing COR list. Keys are assigned to DNs with an incoming COR list.

So, if the member listed in the corlist outgoing of a dial-peer is not listed in the corlist incoming of a DN, then the call will be rejected. That means, that the DN doesn't have a key to open the lock configured to the dial-peer.

Remember that if a DN have no corlist incoming, then that DN will reach every dial-peer (regardless of its corlist outgoing configured). If a dial-peer have no corlist outgoing, it can be reached by any DN (regardless of its corlist incoming configured).

Best regards,

- Adrián.