Configuring Call Blocking

Table Of Contents

Configuring Call Blocking

Contents

Information About Call Blocking

Call Blocking Based on Date and Time (After-Hours Toll Bar)

Call Blocking Override

Class of Restriction

How to Configure Call Blocking

SCCP: Applying Class of Restriction to a Directory Number

SIP: Applying Class of Restriction to Directory Number

Verifying Class of Restriction

Configuring Call Blocking Based on Date and Time

Configuring Call Blocking Exemption for a Dial Peer

SCCP: Configuring Call Blocking Exemption for an Individual Phone

SIP: Configuring Call Blocking Exemption for an Individual Phone or Directory Number

Verifying Call Blocking Based on Date and Time

Configuration Examples for Call Blocking

Call Blocking: Example

Class of Restriction: Example

Where to Go Next

Additional References

Related Documents

Technical Assistance

Feature Information for Call Blocking

Configuring Call Blocking

Last Updated: July 26, 2007

This chapter describes Call Blocking features in Cisco Unified Communications Manager Express (Cisco Unified CME).

Finding Feature Information in This Module

Your Cisco Unified CME version may not support all of the features documented in this module. For a list of the versions in which each feature is supported, see the "Feature Information for Call Blocking" section.

Contents

• Information About Call Blocking

• How to Configure Call Blocking

• Configuration Examples for Call Blocking

• Where to Go Next

• Additional References

• Feature Information for Call Blocking

Information About Call Blocking

To configure call blocking features, you should understand the following concepts:

• Call Blocking Based on Date and Time (After-Hours Toll Bar)

• Call Blocking Override

• Class of Restriction

Call Blocking Based on Date and Time (After-Hours Toll Bar)

Call blocking to prevent unauthorized use of phones is implemented by matching dialed numbers against a pattern of specified digits and matching the time against the time of day and day of week or date that has been specified for call blocking. Up to 32 patterns of digits can be specified. Call blocking is supported on IP phones only and not on analog foreign exchange station (FXS) phones.

When a user attempts to place a call to digits that match a pattern that has been specified for call blocking during a time period that has been defined for call blocking, a fast busy signal is played for approximately 10 seconds. The call is then terminated and the line is placed back in on-hook status.

Call blocking applies to all IP phones in Cisco Unified CME, although individual IP phones can be exempted from all call blocking.

In Cisco CME 3.4 and later versions, the same time-based call-blocking mechanism that is provided for SCCP phones is expanded to SIP endpoints. Call blocking to prevent unauthorized use of Cisco Unified IP phones is implemented by matching a pattern of specified digits during a particular time of the day and day of the week or date.You can specify up to 32 patterns of digits for blocking.

Prior to Cisco CME 3.4, call blocking is supported on IP phones and on analog phones connected to SCCP-controlled analog telephone adaptors (Cisco ATA) or SCCP-controlled foreign exchange station (FXS) ports. This feature supports incoming SIP and analog FXS calls. In Cisco CME 3.4 and later, call-blocking configuration applies to all SCCP, H.323, SIP and POTS calls that go through the Cisco Unified CME router.

The Cisco Unified CME session application accesses the current after-hours configuration and applies it to calls originated by SIP phones that are registered to the Cisco Unified CME router. The after-hours commands are the same as for SCCP phones in Cisco Unified CME.

When a user attempts to place a call to digits that match a pattern that has been specified for call blocking during a time period that has been defined for call blocking, the call is immediately terminated and the caller will hear a fast busy signal.

For configuration information, see the "Configuring Call Blocking Based on Date and Time" section.

Call Blocking Override

The after-hours configuration applies globally to all dial peers in Cisco Unified CME. You can disable the feature on phones using one of three mechanisms:

•directory number—To configure an exception for an individual directory number.

•phone-level—To configure an exception for all directory numbers associated to a Cisco Unified IP phone regardless of any configuration for an individual directory number.

•dial peer—To configure an exception for a particular dial peer.

Individual phone users can be allowed to override call blocking associated with designated time periods by entering personal identification numbers (PINs) that have been assigned to their phones. For IP phones that support soft keys, such as the Cisco Unified IP Phone 7940G and the Cisco Unified IP Phone 7960G, the call-blocking override feature allows individual phone users to override the call blocking that has been defined for designated time periods. The system administrator must first assign a personal identification number (PIN) to any phone that will be allowed to override call blocking.

Logging in to a phone with a PIN only allows the user to override call blocking that is associated with particular time periods. Blocking patterns that are in effect 7 days a week, 24 hours a day, and they cannot be overridden by using a PIN.

When PINs are configured for call-blocking override, they are cleared at a specific time of day or after phones have been idle for a specific amount of time. The time of day and amount of time can be set by the system administrator, or the defaults can be accepted.

For configuration information, see the following sections:

• "Configuring Call Blocking Exemption for a Dial Peer" section.

• "SCCP: Configuring Call Blocking Exemption for an Individual Phone" section.

• "SIP: Configuring Call Blocking Exemption for an Individual Phone or Directory Number" section.

Class of Restriction

Class of restriction (COR) is the capability to deny certain call attempts based on the incoming and outgoing class of restrictions provisioned on the dial peers. COR specifies which incoming dial peer can use which outgoing dial peer to make a call. Each dial peer can be provisioned with an incoming and an outgoing COR list.

COR functionality provides flexibility in network design by allowing users to block calls (for example, calls to 900 numbers) and allowing different restrictions to call attempts from different originators.

For configuration information, see the "SCCP: Applying Class of Restriction to a Directory Number" section.

How to Configure Call Blocking

This section contains the following tasks:

• SCCP: Applying Class of Restriction to a Directory Number

• SIP: Applying Class of Restriction to Directory Number

• Verifying Class of Restriction

• Configuring Call Blocking Based on Date and Time

• Configuring Call Blocking Exemption for a Dial Peer

• SCCP: Configuring Call Blocking Exemption for an Individual Phone

• SIP: Configuring Call Blocking Exemption for an Individual Phone or Directory Number

• Verifying Call Blocking Based on Date and Time

SCCP: Applying Class of Restriction to a Directory Number

To apply a class of restriction to a directory number, perform the following steps.

Prerequisites

•COR lists must be created in dial peers. For information, see the " Class of Restrictions" section in the " Dial Peer Configuration on Voice Gateway Routers" document in the Cisco IOS Voice Configuration Library.

•Directory number to which COR is to be applied must be configured in Cisco Unified CME. For configuration information, see "SCCP: Creating Directory Numbers" on page 177.

SUMMARY STEPS

1. enable

2. configure terminal

3. ephone-dn dn-tag

4. corlist {incoming | outgoing} cor-list-name

5. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

ephone-dn dn-tag
Example:

Router(config)# ephone-dn 12

Enters ephone-dn configuration mode.

Step 4

corlist {incoming | outgoing} cor-list-name
Example:

Router(config-ephone-dn)# corlist outgoing localcor

Configures a COR on the dial peers associated with an ephone-dn.

Step 5

end
Example:

Router(config-ephone-dn)# end

Returns to privileged EXEC mode.

SIP: Applying Class of Restriction to Directory Number

To apply a class of restriction to virtual dial peers for directory numbers associated with a SIP IP phone connected to Cisco Unified CME, perform the following steps.

Prerequisites

•Cisco unified CME 3.4 or a later version.

•COR lists must be created in dial peers. For information, see the " Class of Restrictions" section in the " Dial Peer Configuration on Voice Gateway Routers" document in the Cisco IOS Voice Configuration Library.

•Individual phones to which COR is to be applied must be configured in Cisco Unified CME. For configuration information, see "SIP: Creating Directory Numbers" on page 181.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice register pool pool-tag

4. cor {incoming | outgoing} cor-list-name {cor-list-number starting-number [- ending-number] | default}

5. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

voice register pool pool-tag
Example:

Router(config)# voice register pool 3

Enters voice register pool configuration mode to set phone-specific parameters for a SIP phone in Cisco Unified CME.

Step 4

cor {incoming | outgoing} cor-list-name {cor-list-number starting-number [- ending-number] | default}
Example:

Router(config-register-pool)# cor incoming call91 1 91011

Configures a class of restriction (COR) for the dynamically created VoIP dial peers associated with directory numbers and specifies which incoming dial peer can use which outgoing dial peer to make a call.

•Each dial peer can be provisioned with an incoming and an outgoing COR list.

Step 5

end
Example:

Router(config-register-pool)# end

Exits configuration mode and enters privileged EXEC mode.

Verifying Class of Restriction

Step 1 Use the show running-config command or the show telephony-service ephone-dn command to verify whether the COR lists have been applied to the appropriate ephone-dns.

Router# show running-config

ephone-dn 23
number 2835
corlist outgoing 5x
Step 2 Use the show dialplan dialpeer command to determine which outbound dial peer is matched for an incoming call, based on the COR criteria and the dialed number specified in the command line. Use the timeout keyword to enable matching variable-length destination patters associated with dial peers. This can increase your chances of finding a match for the dial peer number you specify.

Router# show dialplan dialpeer 300 number 1900111

VoiceOverIpPeer900
information type = voice,
description = `',
tag = 900, destination-pattern = `1900',
answer-address = `', preference=0,
numbering Type = `unknown'
group = 900, Admin state is up, Operation state is up,
incoming called-number = `', connections/maximum = 0/unlimited,
DTMF Relay = disabled,
modem passthrough = system,
huntstop = disabled,
in bound application associated: 'DEFAULT'
out bound application associated: ''
dnis-map =
permission :both
incoming COR list:maximum capability
outgoing COR list:to900
type = voip, session-target = `ipv4:1.8.50.7',
technology prefix:
settle-call = disabled
...
Time elapsed since last clearing of voice call statistics never
Connect Time = 0, Charged Units = 0,
Successful Calls = 0, Failed Calls = 0, Incomplete Calls = 0
Accepted Calls = 0, Refused Calls = 0,
Last Disconnect Cause is "",
Last Disconnect Text is "",
Last Setup Time = 0.
Matched: 19001111 Digits: 4
Target: ipv4:1.8.50.7

Step 3 Use the show dial-peer voice command to display the attributes associated with a particular dial peer.

Router# show dial-peer voice 100

VoiceEncapPeer100
information type = voice,
description = `',
tag = 100, destination-pattern = `',
answer-address = `', preference=0,
numbering Type = `unknown'
group = 100, Admin state is up, Operation state is up,
Outbound state is up,
incoming called-number = `555....', connections/maximum = 0/unlimited,
DTMF Relay = disabled,
huntstop = disabled,
in bound application associated: 'vxml_inb_app'
out bound application associated: ''
dnis-map =
permission :both
incoming COR list:maximum capability
outgoing COR list:minimum requirement
type = pots, prefix = `',
forward-digits default
session-target = `', voice-port = `',
direct-inward-dial = disabled,
digit_strip = enabled,
register E.164 number with GK = TRUE

Connect Time = 0, Charged Units = 0,
Successful Calls = 0, Failed Calls = 0, Incomplete Calls = 0
Accepted Calls = 0, Refused Calls = 0,
Last Disconnect Cause is "",
Last Disconnect Text is "",
Last Setup Time = 0.

Configuring Call Blocking Based on Date and Time

To define dial patterns and time periods during which calls to those dial patterns are blocked, perform the following steps.

Restrictions

•Before Cisco CME 3.3, call blocking is not supported on analog phones connected to Cisco ATAs or FXS ports in H.323 mode.

•Before Cisco CME 3.4, call blocking is not supported on SIP IP phones connected directly in Cisco Unified CME.

SUMMARY STEPS

1. enable

2. configure terminal

3. telephony-service

4. after-hours block pattern tag pattern [7-24]

5. after-hours day day start-time stop-time

6. after-hours date month date start-time stop-time

7. login [timeout [minutes]] [clear time]

8. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

telephony service
Example:

Router(config)# telephony service

Enters telephony service configuration mode.

Step 4

after-hours block pattern pattern-tag pattern [7-24]
Example:

Router(config-telephony)# after-hours block pattern 2 91

Defines pattern to be matched for blocking calls from IP phones.

•pattern-tag—Unique number pattern for call blocking. Define up to 32 call-blocking patterns in separate commands. Range is 1 to 32.

Step 5

after-hours date month date start-time stop-time
Example:

Router(config-telephony)# after-hours date jan 1 0:00 23:59

Defines a recurring period based on date of month during which outgoing calls that match defined block patterns are blocked on IP phones.

•Enter beginning and ending times for call blocking in an HH:MM format using a 24-hour clock. The stop- time must be greater than the start-time. The value 24:00 is not valid. If you enter 00:00as a stop time, it is changed to 23:59. If you enter 00:00 for both start time and stop time, calls are blocked for the entire 24-hour period on the specified date.

Step 6

after-hours day day start-time stop-time
Example:

Router(config-telephony)# after-hours day sun 0:00 23:59

Defines a recurring period based on day of the week during which outgoing calls that match defined block patterns are blocked on IP phones

•Enter beginning and ending times for call blocking, in an HH:MM format using a 24-hour clock. The stop- time must be greater than the start-time. The value 24:00 is not valid. If you enter 00:00 as a stop time, it is changed to 23:59. If you enter 00:00 for both start time and stop time, calls are blocked for the entire 24-hour period on the specified day.

Step 7

login [timeout [minutes]] [clear time]
Example:

Router(config-telephony)# login timeout 120 clear 23:00

Deactivates all user logins at a specific time or after a designated period of idle time on a phone.

•Only for IP phones running SCCP.

•minutes—(Optional) Range: 1 to 1440. Default: 60. Before Cisco Unified CME 4.1, the minimum value for this argument was 5 minutes.

Step 8

end
Example:

Router(config-telephony)# end

Returns to privileged EXEC mode.

Configuring Call Blocking Exemption for a Dial Peer

To allow H.323 and SIP trunk calls to utilize the voice gateway in spite of the the after-hours configuration in Cisco Unified CME, follow the steps in this section.

SUMMARY STEPS

1. enable

2. configure terminal

3. dial-peer voice tag {pots | voatm | vofr | voip}

4. paramspace callsetup after-hours-exempt true

5. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

dial-peer voice tag {pots | voatm | vofr | voip}
Example:

Router(config)# dial peer voice 501 voip

Defines a particular dial peer, specifies the method of voice encapsulation, and enters dial-peer configuration mode.

Step 4

paramspace callsetup after-hours-exempt true
Example:

Router(config-dialpeer)# paramspace callsetup after-hours-exempt true

Exempts a dial peer from call blocking configuration.

Step 5

end
Example:

Router(config-dialpeer)# end
or

Router(config-register-dn)# end

Exits configuration mode and enters privileged EXEC mode.

SCCP: Configuring Call Blocking Exemption for an Individual Phone

To exempt all directory numbers associated with an individual SCCP phone from the call blocking configuration, follow the steps in this section.

Restrictions

Call blocking override is supported only on phones that support soft-key display.

SUMMARY STEPS

1. enable

2. configure terminal

3. ephone phone-tag

4. after-hour exempt

5. pin pin-number

6. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

ephone phone-tag
Example:

Router(config)# ephone 4

Enters ephone configuration mode.

•phone-tag—The unique sequence number for the phone that is to be exempt from call blocking.

Step 4

after-hour exempt
Example:

Router(config-ephone)# after-hour exempt

Specifies that this phone is exempt from call blocking. Phones exempted in this manner are not restricted from any call-blocking patterns and no authentication of the phone user is required.

Step 5

pin pin-number
Example:

Router(config-ephone)# pin 5555

Declares a personal identification number (PIN) that is used to log into an ephone.

•pin-number—Number from four to eight digits in length.

Step 6

end
Example:

Router(config-ephone)# end

Returns to privileged EXEC mode.

SIP: Configuring Call Blocking Exemption for an Individual Phone or Directory Number

To exempt all extensions associated with an individual SIP phone or an individual directory number from the call blocking configuration, follow the steps in this section.

Restrictions

The Login toll-bar override is not supported on SIP IP phones; there is no pin to bypass blocking on IP phones that are connected to Cisco Unified CME and running SIP.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice register pool pool-tag
or
voice register dn dn-tag

4. after-hour exempt

5. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

voice register pool pool-tag
or

voice register dn dn-tag
Example:

Router(config)# voice register pool 1
or

Router(config)# voice register dn 1

Enters voice register pool configuration mode to set parameters for specified SIP phone.

or

Enters voice register dn mode to define a directory number for a SIP phone, intercom line, voice port, or an MWI.

Step 4

after-hour exempt
Example:

Router(config-register-pool)# after-hour exempt
or

Router(config-register-dn)# after-hour exempt

Exempts all numbers on a SIP phone from call blocking.

or

Exempts an individual directory number from call blocking.

Step 5

end
Example:

Router(config-register-dn)# end
or

Router(config-register-dn)# end

Exits configuration mode and enters privileged EXEC mode.

Verifying Call Blocking Based on Date and Time

Step 1 Use the show running-config command to display an entire configuration, including call blocking number patterns and time periods and the phones that are marked as exempt from call blocking.

telephony-service
fxo hook-flash
load 7960-7940 P00305000600
load 7914 S00103020002
max-ephones 100
max-dn 500
ip source-address 10.115.43.121 port 2000
timeouts ringing 10
voicemail 7189
max-conferences 8 gain -6
moh music-on-hold.au
web admin system name sys3 password sys3
dn-webedit
time-webedit
transfer-system full-consult
transfer-pattern .T
secondary-dialtone 9
after-hours block pattern 1 91900 7-24
after-hours block pattern 2 9976 7-24
after-hours block pattern 3 9011 7-24
after-hours block pattern 4 91...976.... 7-24
!
create cnf-files version-stamp 7960 Jul 13 2004 03:39:28

Step 2 Use the show ephone login command to display the login status of all phones.

Router# show ephone login

ephone 1 Pin enabled:TRUE Logged-in:FALSE
ephone 2 Pin enabled:FALSE
ephone 3 Pin enabled:FALSE
Step 3 The show voice register dial-peer command displays all the dial peers created dynamically by SIP phones that have registered, along with configurations for after hours blocking.

Configuration Examples for Call Blocking

This section contains the following examples:

• Call Blocking: Example

• Class of Restriction: Example

Call Blocking: Example

The following example defines several patterns of digits for which outgoing calls are blocked. Patterns 1 and 2, which block calls to external numbers that begin with "1" and "011," are blocked on Monday through Friday before 7 a.m. and after 7 p.m., on Saturday before 7 a.m. and after 1 p.m., and all day Sunday. Pattern 3 blocks calls to 900 numbers 7 days a week, 24 hours a day. The IP phone with tag number 23 and MAC address 00e0.8646.9242 is not restricted from calling any of the blocked patterns.

telephony-service
after-hours block pattern 1 91
after-hours block pattern 2 9011
after-hours block pattern 3 91900 7-24
after-hours day mon 19:00 07:00
after-hours day tue 19:00 07:00
after-hours day wed 19:00 07:00
after-hours day thu 19:00 07:00
after-hours day fri 19:00 07:00
after-hours day sat 13:00 12:00
after-hours day sun 12:00 07:00
!
ephone 23
mac 00e0.8646.9242
button 1:33
after-hour exempt
!
ephone 24
mac 2234.1543.6352
button 1:34

The following example deactivates a phone's login after three hours of idle time and clears all logins at 10 p.m.:

ephone 1
pin 1000
!
telephony-service
login timeout 180 clear 2200
Class of Restriction: Example

The following example shows three dial peers for dialing local destinations, long distance, and 911. COR list user1 can access the dial peers used to call 911 and local destinations. COR list user2 can access all three dial peers. Ephone-dn 1 is assigned COR list user1 to call local destinations and 911, and ephone-dn 2 is assigned COR list user2 to call 911, local destinations, and long distance.

dial-peer cor custom
name local
name longdistance
name 911
!
dial-peer cor list call-local
member local
!
dial-peer cor list call-longdistance
member longdistance
!
dial-peer cor list call-911
member 911
!
dial-peer cor list user1
member 911
member local
!
dial-peer cor list user2
member 911
member local
member longdistance
!
dial-peer voice 1 pots
corlist outgoing call-longdistance
destination-pattern 91..........
port 2/0/0
!
dial-peer voice 2 pots
corlist outgoing call-local
destination-pattern 9[2-9]......
port 2/0/0
!
dial-peer voice 3 pots
corlist outgoing call-911
destination-pattern 9911
port 2/0/0
!
ephone-dn 1
corlist incoming user1
corlist outgoing user1
!
ephone-dn 2
corlist incoming user2
corlist outgoing user2

Where to Go Next

After modifying a configuration for a Cisco Unified IP phone connected to Cisco Unified CME, you must reboot the phone to make the changes take effect. For more information, see "Resetting and Restarting Phones" on page 277.

Soft Key Control

To move or remove the Login soft key on one or more phones, create and apply an ephone template that contains the appropriate softkeys commands.

For more information, see "Customizing Soft Keys" on page 875.

Ephone-dn Templates

The corlist command can be included in an ephone-dn template that is applied to one or more ephone-dns. For more information, see "Creating Templates" on page 927.

Additional References

The following sections provide references related to Cisco Unified CME features.

Related Documents

Related Topic

Document Title

Cisco Unified CME configuration

• Cisco Unified CME Command Reference

• Cisco Unified CME Documentation Roadmap

Cisco IOS commands

• Cisco IOS Voice Command Reference

• Cisco IOS Software Releases 12.4T Command References

Cisco IOS configuration

• Cisco IOS Voice Configuration Library

• Cisco IOS Software Releases 12.4T Configuration Guides

Phone documentation for Cisco Unified CME

• Quick Reference Cards

• User Guides

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register on Cisco.com.

http://www.cisco.com/techsupport

Feature Information for Call Blocking

Table 27 lists the features in this module and enhancements to the features by version.

To determine the correct Cisco IOS release to support a specific Cisco Unified CME version, see the Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_documentation_roadmap09186a0080189132.html.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 27 lists the Cisco Unified CME version that introduced support for a given feature. Unless noted otherwise, subsequent versions of Cisco Unified CME software also support that feature.

Table 27 Feature Information for Call Blocking

Feature Name

Cisco Unified CME
Version

Feature Information

Call Blocking

3.4

Added support for call blocking on SIP IP phones connected directly in Cisco Unified CME.

3.3

Added support for call blocking on analog phones connected to Cisco ATAs or FXS ports in H.323 mode.

3.0

•Call blocking based on date and time was introduced.

•Override of call blocking was introduced.

Class of Restriction

3.4

Added support for COR on SIP IP Phones connected directly in Cisco Unified CME.

2.0

Class of restriction was introduced.

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	ephone-dn dn-tag Example: Router(config)# `ephone-dn 12`	Enters ephone-dn configuration mode.
Step 4	corlist {incoming \| outgoing} cor-list-name Example: Router(config-ephone-dn)# `corlist outgoing localcor`	Configures a COR on the dial peers associated with an ephone-dn.
Step 5	end Example: Router(config-ephone-dn)# end	Returns to privileged EXEC mode.

Related Topic	Document Title
Cisco Unified CME configuration	• Cisco Unified CME Command Reference • Cisco Unified CME Documentation Roadmap
Cisco IOS commands	• Cisco IOS Voice Command Reference • Cisco IOS Software Releases 12.4T Command References
Cisco IOS configuration	• Cisco IOS Voice Configuration Library • Cisco IOS Software Releases 12.4T Configuration Guides
Phone documentation for Cisco Unified CME	• Quick Reference Cards • User Guides

Feature Name	Cisco Unified CME Version	Feature Information
Call Blocking	3.4	Added support for call blocking on SIP IP phones connected directly in Cisco Unified CME.
	3.3	Added support for call blocking on analog phones connected to Cisco ATAs or FXS ports in H.323 mode.
	3.0	•Call blocking based on date and time was introduced. •Override of call blocking was introduced.
Class of Restriction	3.4	Added support for COR on SIP IP Phones connected directly in Cisco Unified CME.
Class of Restriction	2.0	Class of restriction was introduced.