Implementing Calling Privileges on Cisco IOS Gateways (Configuring Advanced Dial Plans) (Cisco Voice over IP (CVOICE)) Part 2

COR Example

Figure 7-33 illustrates the concept of COR on Cisco IOS gateways.

Figure 7-33 COR Example

A typical application of COR is to define a COR name for the number that an outgoing dial peer serves, then define a list that contains only that COR name, and assign that list as corlist outgoing for this outgoing dial peer. For example, the dial peer with destination pattern 9011T can have a corlist outgoing that contains COR INTL, as shown in Figure 7-33.

In this example, four CORs are defined:

■ 911

■ Local

■ LD

■ INTL

The four CORs are used to create three incoming corlists that will be assigned to phones and users:

■ Local: This corlist contains the CORs 911 and Local. This list will allow users to place emergency calls and local PSTN calls.

■ LD: This corlist contains the CORs 911, Local, and LD. This corlist will allow users to place emergency calls, local calls, and long distance PSTN calls.

■ INTL: This corlist contains the CORs 911, Local, LD, and INTL. This corlist will allow users to place any PSTN call.

A corlist will be assigned to an outgoing POTS dial peer used to route international calls to the international long distance service provider:

■ INTLCall: This corlist contains the COR INTL and will be used for outbound INTL PSTN calls.

When a call is routed using the incoming corlist INTL and is matched against the outgoing corlist INTLCall, the call succeeds because COR INTL is included in the corlist INTL.

When a call is routed using the incoming corlist Local and is matched against the outgoing corlist INTLCall, the call is blocked because COR INTL is not included in the corlist Local.

Understanding COR for SRST and CME

When you use COR with SRST and Cisco Unified CME, a corlist cannot be simply bound to all dial peers, because one call leg will be represented by dynamic dial peers derived from ephones.

For Cisco Unified CME, the corlist is directly assigned to the appropriate ephone-dn and will then be included in the dynamic ephone dial peer. Both inbound and outbound corlists can be applied. An inbound corlist on an ephone restricts the destination to which a user can dial, whereas an outbound corlist defines who can call a user.

For standard SRST, ephones are not statically configured on the Cisco IOS gateway. Instead, the gateway pulls the configuration from the phone and dynamically creates corresponding ephones. To assign a corlist in SRST mode, a corlist is matched to a range of directory numbers in global SRST configuration mode.

Note COR is not limited to Cisco Unified CME or SRST. COR can be applied to any inbound and outbound dial peer on a Cisco IOS gateway.

This Cisco Unified CME configuration assigns the incoming corlist INTL to ephone 1:

Figure 7-34 shows a sample configuration for Cisco Unified CME and SRST.

This SRST configuration assigns the incoming corlist INTL to all phones with the DN 2000 through 2010:

 

 

 

 

Figure 7-34 COR and SRST and Cisco Unified CME Example

Note The number that precedes the directory number range in the SRST configuration is the corlist tag. Up to 20 tags can be configured (that is, up to 20 different corlists can be used for SRST ephones).

Configuring COR for Cisco Unified Communications Manager Express

In the following example, you are required to configure COR for Cisco Unified CME according to the following network requirements.

For this example, three calling privilege classes are required:

■ Local: This class should allow emergency and local calls.

■ Long Distance: This class should allow emergency, local, and long distance calls.

■ International: This class should allow emergency, local, long distance, and international calls.

Note No standard naming conventions exist for the privilege classes. Ensure that you choose a descriptive name.

You can use the following steps to configure COR for Cisco Unified CME:

Step 1. Define the four individual "tags" (CORs) to be used as corlist members with the command dial-peer cor custom.

Step 2. Define the corlists that will be assigned "outgoing" to the PSTN dial peers with the command dial-peer cor list corlist-name.

Step 3. Define the corlists that will be assigned "incoming" from the local dial peers with the command dial-peer cor list corlist-name.

Step 4. Associate corlists with existing VoIP or POTS PSTN dial-peers by using the command corlist {incoming | outgoing} corlist-name within the dial-peer configuration.

Step 5. Assign the corlists for user privileges to the corresponding ephone-dns.

The topology shown in Figure 7-35 will be used throughout the configuration steps in this scenario. Notice that the Chicago site is handled by a Cisco Unified CME router.

Figure 7-35 COR Cisco UCME Scenario Topology

Step 1: Define COR Labels

The first step is to define the individual CORs. Four COR labels will be defined:

■ 911: Allows calls to emergency 911

■ Local: Allows local calls only

■ LD: Allows long distance calls

■ INTL: Allows international calls

You can use the following procedure to configure these four CORs.

Step 1. Use the dial-peer cor custom command to enter COR configuration mode. Router(config)#dial-peer cor custom

Step 2. Use the name command in COR configuration mode to create the named CORs.

Step 2: Configure Outbound Corlists

After you define the CORs, you can configure the incoming and outgoing corlists. Four outgoing corlists will be defined:

■ 911call: Allows calls to emergency 911

■ Localcall: Allows local calls only

■ Ldcall: Allows long distance calls

■ Intlcall: Allows international calls

The following configuration defines the corlists used for the outbound PSTN dial peers. Note that each corlist contains a single COR member.

Step 1. Define a corlist name for 911 calls.

Step 2. Add members to dial-peer corlists. The member needs to reference a previously configured COR tag.

Step 3. Repeat Steps 1 and 2 for the other outgoing corlists.