cor-list sample configuration

-
dial-peer cor custom
 name 911696
 name 911697
 name 911777
dial-peer cor list pt-911696
 member 911696
dial-peer cor list pt-911697
 member 911697
dial-peer cor list pt-911777
 member 911777
dial-peer cor list css-dialall
 member 911696
 member 911697
 member 911777
dial-peer cor list css-dialtwo
 member 911697
 member 911777
dial-peer cor list css-dialone
 member 911696

dial-peer voice 911696 voip
 corlist incoming pt-911696
 corlist outgoing pt-911696
 description cor test
 translation-profile outgoing STRIPPREFIX
 destination-pattern *911696
 voice-class h323 1
 session target ras
 tech-prefix 666#91#
 dtmf-relay h245-alphanumeric
 ip qos dscp ef signaling
 no vad
dial-peer voice 911697 voip
 corlist incoming pt-911697
 corlist outgoing pt-911697
 description cor test
 translation-profile outgoing STRIPPREFIX
 destination-pattern *911697
 voice-class h323 1
 session target ras
 tech-prefix 666#91#
 dtmf-relay h245-alphanumeric
 ip qos dscp ef signaling
 no vad
dial-peer voice 911777 voip
 corlist incoming pt-911777
corlist outgoing pt-911777
 description or test
 translation-profile outgoing STRIPPREFIX
 destination-pattern *911777
 voice-class h323 1
 session target ras
 tech-prefix 666#91#
 dtmf-relay h245-alphanumeric
 ip qos dscp ef signaling
 no vad


ephone-dn  24  dual-line
 number 1021 secondary 6491 no-reg both
 label 1021
 description User Name
 name User Name
corlist incoming css-dialtwo
corlist outgoing css-dialtwo


1021 now won't able to reach *911696.
One weird thing about COR, if you exclude CSS from the DNs, calls will start to work. In other words, 'partition' configuration won't come into play till the time DN is configured with the 'CSS'. Hence, you can configure CSS only for those number who you want to restrict.
Also, noticed that in my CME version 4.2, calls were not restricting till the time I restricted the calls for both incoming and outgoing.

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more