COR Blocking in CME

Unanswered Question
Nov 16th, 2007

Hello all

I'm messing around with COR for a customer and I'm having the following issue. I want to use COR to block 1900 calls but I'm noticing that it's behaving not the way I thought it should. I have the following setup and here is what is happening.

When dialing 91900XXXXXXX from ephone-dn 1 I'm noticing I'm getting my first match on Dial-peer 10 and the call is regected because this peer member is not in ephone-dn 1 corlist "BUT" i'm also getting a match on Dial-peer 8 which is less exact and the call is proceeding. Therefore if there is an overlap you COR doesn't work properly.

Yes I know I can use "after hours block 1 1900 7-24" under telephony services but this will block it for everyone. I want it to be flexible so that I can use COR to allow users to call 1900 if they needed to.

Thoughts?

dial-peer cor custom

name internal

name local

name domestic

name international

name 900

!

!

dial-peer cor list call-internal

member internal

!

dial-peer cor list call-local

member local

!

dial-peer cor list call-domestic

member domestic

!

dial-peer cor list call-international

member international

!

dial-peer cor list call-900

member 900

!

dial-peer cor list user-internal

member internal

!

dial-peer cor list user-local

member internal

member local

!

dial-peer cor list user-ld

member internal

member local

member domestic

member international

!

!

!

dial-peer voice 2 pots

description **Emergency Services 911**

destination-pattern 9911

port 0/1/0:23

forward-digits 3

!

dial-peer voice 3 pots

corlist outgoing call-local

description **For local 7 Digit calls**

destination-pattern 9[2-9]......

port 0/1/0:23

forward-digits 7

!

dial-peer voice 9 pots

corlist outgoing call-international

description **International LD calls**

destination-pattern 9011T

port 0/1/0:23

prefix 011

!

dial-peer voice 10 pots

corlist outgoing call-900

description **Toll Charge Calls**

destination-pattern 91900.......

port 0/1/0:23

forward-digits 11

!

dial-peer voice 11 pots

corlist outgoing call-900

description **Toll Charge Calls**

destination-pattern 91976.......

port 0/1/0:23

forward-digits 11

!

dial-peer voice 8 pots

corlist outgoing call-domestic

description **Domestic LD calls**

destination-pattern 91[2-9]………

port 0/1/0:23

forward-digits 11

!

!

!

gatekeeper

shutdown

!

!

telephony-service

no auto-reg-ephone

load 7960-7940 P00308000400

load 7941 SCCP41.8-2-2SR1S

load 7961 SCCP41.8-2-2SR1S

load 7971 SCCP70.8-2-2SR1S

load 7970 SCCP70.8-2-2SR1S

load 7906 SCCP11.8-2-2SR1S

load 7911 SCCP11.8-2-2SR1S

max-ephones 36

max-dn 108

ip source-address 10.X.X.X port 2000

system message

time-zone 6

voicemail 2499

max-conferences 8 gain -6

call-forward pattern .T

call-forward system redirecting-expanded

moh music-on-hold.au

web admin system name cmeadmin secret

dn-webedit

time-webedit

transfer-system full-consult dss

transfer-pattern 9.T

secondary-dialtone 9

create cnf-files version-stamp Jan 01 2002 00:00:00

!

!

ephone-dn 1 dual-line

number 2400 secondary 7807922400

label 2400

description Remote Site 1

name Remote Site 1

call-forward busy 2499

call-forward noan 2499 timeout 15

corlist incoming user-ld

corlist outgoing call-internal

!

!

ephone-dn 2 dual-line

number 2401 secondary 7807922401

label 2401

description Remote Site 2

name Remote Site 2

call-forward busy 2499

call-forward noan 2499 timeout 15

corlist incoming user-local

corlist outgoing call-internal

!

!

ephone 1

mac-address 001D.4561.5B98

username "user1" password 2400

type 7941

button 1:1

!

!

!

ephone 2

mac-address 001D.4543.A8FD

username "user2" password 2401

type 7941

button 1:2


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
vmilanov Fri, 11/16/2007 - 11:56

Hi Ryan,


First CME does not match peer on the 'most specific' basis, but rather it searches the list of configured dial-peers in the order they appeared in the configuration. So, when the dial-peer was rejected, the CME hunts for the next match.


Second thing, a cor list applied as 'incoming' to a phone-dn restricts where to this ephone-dn can dial-out. It has the same function as the Line CSS has in CCM. And a cor-list applied as 'outgoing' restricts which members can dial-in, and it behaves like the partitions in a CCM environment.


In your configuration the incoming cor-list of ephone-dn 1 has all the members but the '900' member, so this dn can dial out trough all the dial-peer except the dial-peer 10.


Respectively, ephone-dn can be reached by all the dial-peers that are members of the 'internal': in your case by all the dial-peers, because the pots ones do net have cor-list at all, so they have unrestricted access, and the ephone-dn 2 has a 'internal' membership via it's outgoing cor-list.


HTH.



Regards,

Vasil

ryan_oconnell Fri, 11/16/2007 - 12:18

Ok,


Thanks for clarifing point one, about how dial-peer are matched in order vs most exact.


And your points on the Direction of COR and how it's applied I do understand. Or at least I think I do.


But my question is not answered.


At the end of the day, if I wanted to have a user that can dial 1900 as well as everything else but still restrict 1900 from the rest of the users how do I accomplish this?


In my example I'm trying to allow Ehpone 1 to dial "Domestic" but not 1900 numbers.


Thanks Ryan



Ryan

vmilanov Sun, 11/18/2007 - 13:37

Hi Ryan,


I saw Paolo's reply and I find it very useful. I'll rate him.


So having in mind what he advised, and to have an easy to read and clean configuration, I would do the following:


-- copy all dial-peers config to a text file

-- delete all dial-peers from the config

-- re-order the dial-peers in the text file from the most restrictive to less restrictive ones, and then by most specific to less specific destination patterns.

-- add the 'hunstop' command to each one, except those used for local and emergency dialing.

-- re-assign the dial-peer numbers from top to bottom.

-- paste back the new dial-peers config to IOS.


With your config it would look this way:


dial-peer voice 1 pots

corlist outgoing call-900

description **Toll Charge Calls**

huntstop

destination-pattern 91900.......

port 0/1/0:23

forward-digits 11

!

dial-peer voice 2 pots

corlist outgoing call-900

description **Toll Charge Calls**

huntstop

destination-pattern 91976.......

port 0/1/0:23

forward-digits 11

!

dial-peer voice 3 pots

corlist outgoing call-international

description **International LD calls**

huntstop

destination-pattern 9011T

port 0/1/0:23

prefix 011

!

dial-peer voice 4 pots

corlist outgoing call-domestic

description **Domestic LD calls**

huntstop

destination-pattern 91[2-9]………

port 0/1/0:23

forward-digits 11

!

dial-peer voice 5 pots

corlist outgoing call-local

description **For local 7 Digit calls**

destination-pattern 9[2-9]......

port 0/1/0:23

forward-digits 7

!

dial-peer voice 6 pots

description **Emergency Services 911**

destination-pattern 9911

port 0/1/0:23

forward-digits 3




Regards,

Vasil


ryan_oconnell Sun, 11/18/2007 - 17:29

I did give his suggestion a try on Friday, just how you outlined and it did not work.

Actions

This Discussion