Configuration Cisco CME COR List
May 12, 2013 Leave a comment
Introduction :
This post summarize the configuration of COR Lists ( Class Of Restriction).
COR Lists define restrictions that you can apply on ephones-dn and dial-peer. These restrictions allow to limit the access for routes reserved for only ephone_dn permitted.
The principle is based on tags that you set on ephones-dn and dial-peers.
To explain a basic configuration we are going to configure the following topology :
The COR configuration scenario is the following :
- The ephone-dn 3000 can call only numbers as 1XXX
- The ephone-dn 4000 can call only numbers as 2XXX
CME Configuration :
Tags definition :
For our scenario, we need two tags RED and PURPLE.
The following configuration allows to define the name of these tags :
dial-peer cor custom name red name purpled
Incoming and Outgoing COR Lists :
We need to configure Incoming and Outgoing COR Lists which will be applied to ephones-dn and dial-peers.
- Incoming COR Lists will be used to tag an incoming call with tags defined as member.
- Outgoing COR Lists will be used to check if tags are present in a call which go out.
dial-peer cor list PURPLE-OUT member purple ! dial-peer cor list PURPLE-IN member purple ! dial-peer cor list RED-IN member red ! dial-peer cor list RED-OUT member red
COR List Application :
According to our scenario, we place INCOMING COR LIST on ephones-dn and OUTGOING COR LIST on dial-peers voip
!
ephone-dn 1 number 3000 name bob corlist incoming RED-IN ! ephone-dn 2 number 4000 name alice corlist incoming PURPLE-IN ! dial-peer voice 2 voip corlist outgoing RED-OUT description **Outgoing Call to SIP Trunk dest 1...** destination-pattern 1... session protocol sipv2 session target sip-server ! dial-peer voice 3 voip corlist outgoing PURPLE-OUT description **Outgoing Call to SIP Trunk dest 2...** destination-pattern 2... session protocol sipv2 session target sip-server !