© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Configuring PSTN Interfaces and Voice Dial Peers Class of Restriction

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Outline Overview What is Class of Restriction Steps to Configure Class of Restriction Case Study Summary

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Features of COR COR provides a way to deny certain calls based upon the incoming and outgoing settings on dial peers and ephone- dns. Each dial peer and ephone-dn can have one incoming COR and one outgoing COR. COR can be used to control access to dialable destinations that are internal to the enterprise or external to the enterprise. The incoming COR list indicates the capacity of the dial peer to initiate certain classes of calls. The outgoing COR list indicates the capacity required for an incoming dial peer to deliver a call via this outgoing dial peer.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Incoming and Outgoing CORs Incoming COROutgoing COR The incoming COR is like having one or more keys. The lack of an incoming COR is like having a master key that can unlock all locks. The outgoing COR is like a lock or locks. The lack of an outgoing COR is like having no lock. or

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Results of Incoming and Outgoing CORs COR List on Incoming Dial Peer or Ephone-dn COR List on Outgoing Dial Peer or Ephone-dn ResultReason No COR Call succeedsCOR is not applied No COR Outgoing COR applied Call succeeds The no (null) incoming COR condition has highest COR priority Incoming COR applied No CORCall succeeds Incoming COR list is a superset of the no (null) outgoing COR list Incoming COR applied is a superset of outgoing COR Outgoing COR applied Call succeeds Incoming COR list is a superset of outgoing COR list Incoming COR applied not a superset of outgoing COR Outgoing COR applied Call cannot be completed Tncoming COR list is not a superset of outgoing COR list

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Configuration COR Step 1 – Configure the class of restriction names. Step 2 – Configure the class of restriction lists and members. Step 3 – Assign the COR list to the dial peers. Step 4 - Assign the COR to the ephone-dns.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v dial-peer cor custom CMERouter(config)# Enters COR configuration mode where classes of restrictions are specified name class-name CMERouter(config-dp-cor)# Used to specify a class of restriction Configuring COR Names Step 1 – Configure the class of restriction names.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v dial-peer cor list list-name CMERouter(config)# Provides a name for a list of restrictions member class-name CMERouter(config-dp-corlist)# Adds a COR class to this list of restrictions Configuring COR Lists and Members Step 2 – Configure the class of restriction lists and members.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v dial-peer voice number {pots | voip} CMERouter(config)# Defines a dial peer and enters dial-peer configuration mode corlist {incoming | outgoing} list-name CMERouter(config-dial-peer)# Specifies a COR list to be used when the dial peer is either the incoming or outgoing dial peer Assigning COR List to Dial Peers Step 3 – Assign the COR list to the dial peers.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v ephone-dn tag CMERouter(config)# Defines an ephone-dn and enters ephone-dn mode cor {incoming | outgoing} list-name CMERouter(config-ephone-dn)# Specifies a COR list to be used when the ephone-dn is used as either the incoming or outgoing part of a call Assigning COR List to Ephone-dns Step 4 – Assign the COR list to the Ephone-dns.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Example: COR Ephone-dn 1 Employee Ext 1000 Ephone-dn 2 Executive Ext 2000 dial-peer cor custom name 1xxx name 2xxx dial-peer cor list Executive member 1xxx member 2xxx dial-peer cor list Employee member 1xxx ephone-dn 1 number 1000 cor incoming Employee ephone-dn 2 number 2000 cor outgoing Executive The executive can call the employee but the employee cannot call the executive. The incoming COR employee is not a superset of the executive, so the call will not succeed.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v COR Case Study: XYZ Company The XYZ company wishes to prevent toll fraud by restricting the destinations on the PSTN that IP Phones and analog phones attached to the FXS port can call. XYZ wants no internal restrictions; anyone internal should be able to call anyone else internal. All phones must be able to call 911. Within XYZ, there are lobby phones, employee phones, sales phones, and executive phones. The lobby phone should be able to call only 911 on the PSTN. The employee phones should be able to call 911 and make local calls on the PSTN. The sales phones should be able to call 911 and make local calls and domestic long distance on the PSTN. The executives should be able to call 911 and make local calls, domestic long distance calls, and international calls on the PSTN. No one should be able to call 900 numbers.

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v COR Case Study: XYZ Company (Cont.) dial-peer cor custom name 911 name local name long_distance name international name 900 Step 1 - Define the classes of restriction. 911 local long_distance international 900

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v COR Case Study: XYZ Company (Cont.) dial-peer cor list call911 member 911 dial-peer cor list callLocal member local dial-peer cor list callLD member long_distance dial-peer cor list callInt member international dial-peer cor list call900 member 900 Step 2 – Define the COR lists and members. dial-peer cor list Lobby member 911 dial-peer cor list Employee member 911 member local dial-peer cor list Sales member 911 member local member long_distance dial-peer cor list Executive member 911 member local member long_distance member international

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v COR Case Study: XYZ Company (Cont.) dial-peer voice 1 pots destination-pattern 911 port 1/0/0 corlist outgoing call911 dial-peer voice 2 pots destination-pattern 1[2-9]..[2-9] port 1/0/0 corlist outgoing callLD dial-peer voice 3 pots destination-pattern [2-9] port 1/0/0 corlist outgoing callLocal dial-peer voice 5 pots destination-pattern 1011T port 1/0/0 corlist outgoing callInt dial-peer voice 6 pots destination-pattern port 1/0/0 corlist outgoing call900 Step 3 – Assign the COR to the PSTN dial peers. Dial peer 1 – COR out call 911 Dial peer 2 – COR out call LD Dial peer 3 – COR out call Local Dial peer 4 – COR out call Int Dial peer 5 – COR out call 900

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v COR Case Study: XYZ Company (Cont.) ephone-dn 1 number 1001 cor incoming Lobby ephone-dn 2 number 1002 cor incoming Employee ephone-dn 3 number 1003 cor incoming Sales ephone-dn 4 number 1004 cor incoming Executive Step 4 – Assign the COR to the ephone-dns. Ephone-dn 1 COR in Lobby Ext 1001 Ephone-dn 2 COR in Employee Ext 1002 Ephone-dn 3 COR in Sales Ext 1003 Ephone-dn 4 COR in Executive Ext 1004

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v COR Case Study: XYZ Company (Cont.) Results: The lobby ephone-dn can call only 911 on the PSTN. The employee ephone-dn can call 911 and local calls on the PSTN. The sales ephone-dn can call 911 and make local and domestic long distance calls on the PSTN. The executive ephone-dn can call 911 and make local calls, domestic long distance calls, and international calls on the PSTN. No one can call 900 numbers. Ephone-dn 1 COR in Lobby Ext 1001 Ephone-dn 2 COR in Employee Ext 1002 Ephone-dn 3 COR in Sales Ext 1003 Ephone-dn 4 COR in Executive Ext 1004

© 2005 Cisco Systems, Inc. All rights reserved. IPTX v Summary A dial peer is an addressable endpoint. Cisco voice-enabled routers support POTS dial peers and VoIP dial peers. Basic POTS dial-peer configuration consists of defining the dial peer with a tag number and POTS designation, defining the destination pattern, and defining the voice port to which the device is connected. Basic VoIP dial-peer configuration consists of defining the dial peer with a tag number and VoIP designation, defining the destination pattern, and defining the remote voice-enabled router through the session target command. The destination-pattern on a dial peer can utilize wildcards to simplify configuration. The default dial peer is used when no match in the configured dial peers is found. Class of restrictions can be used to control the allowable destinations for either an incoming or outgoing call.