UC520 cor list explanation

Answered Question
Mar 31st, 2008
User Badges:

The default install of a UC520 creates two sets of cor lists. One starts with call-xxx and the other starts with user-xxx. Why two lists? Why/when would I want to use the user-xxx over the call-xxx or vice versa?


Thanks,

Diego

Correct Answer by Paolo Bevilacqua about 8 years 12 months ago

COR is a locks and keys mechanism. User-xxx are keys (incoming DP) and call-xxx are locks (outgoing DP). See for a complete explaination;


http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml


hope this helps, please rate post if it does!



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
DIEGO ALONSO Tue, 04/01/2008 - 08:39
User Badges:

I had to read the doc twice because for some reason the inbound/outbound/superset thing is kind of hard to grasp for me. But I think I got it.


Thanks,

Diego

Paolo Bevilacqua Tue, 04/01/2008 - 08:48
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Yes, when explained as the "superset" thing, it becomes hard to understand. So it's easier to think in term of keys and locks:


Incoming DP is your entry door into a building. At entry, you're are given all the keys that are in the incoming list, that in fact can be no keys at all (empty list).


To exit the building, you take an exit door (outgoing DP), and you need to have at least a key that opens one of the locks (listed in outgoing COR). If you are not allowed, you can try (rehunt) another DP with a compatible destination-pattern, a lesser preference and one key/lock match. This is why COR can also be used as a mechanism to route based on calling number (answer-address).


Finally, if either entry or exit door has no list, you're allowed anyway. This concept is crucial for reducing a COR configuration to the minimum necessary.


Thanks for the nice rating and good luck!

Actions

This Discussion