Advanced Dial Plans

Here you will find answers to CVoice – Advanced Dial Plan Questions

Question 1

Which mechanism do you use to implement calling privileges on Cisco Unified Communications Manager Express?

A. CoS
B. QoS
C. CAC
D. COR
E. SRST

Answer: D

Explanation

Calling privileges define the destination a user is allowed to dial and they are implemented on Cisco IOS gateway using Class of Restriction.

Class of Restriction (COR) is the feature that determines which numbers might not be dialed on the system. COR is required only when you want to restrict the ability of some phones to make certain types of calls but allow other phones to place those calls. COR functionality provides the ability to deny certain call attempts on the basis of the incoming and outgoing CORs that are provisioned on the dial-peers. This functionality provides flexibility in network design, allows users to block calls (for example, calls to 900 numbers), and applies different restrictions to call attempts from different originators.

(Reference: http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml)

Question 2

Using Cisco Unified Communications Manager Express, what four steps are necessary to implement COR? (Choose four)

A. Configure SRST.
B. Define COR labels.
C. Configure COR lists.
D. Assign COR list to ephone-DN.
E. Configure COR lists on voice ports.
F. Configure dial peers and assign COR lists.

Answer: B C D F

Explanation

Four steps to configure COR on Cisco IOS gateway using Cisco Unified Communications Manager Express:

1) Define COR labels.
2) Configure COR lists.
3) Configure dial peers and assign COR lists.
4) Assign COR lists to ephone-dn.

For example, we will define three calling privilege classes:

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.

Step 1: Define the four COR labels to be used as COR list members with the command dial-peer cor custom.

Router(config)#dial-peer cor custom
Router(config-dp-cor)#name 911
Router(config-dp-cor)#name local
Router(config-dp-cor)#name ld
Router(config-dp-cor)#name intl

Description

• 911: Allows calls to emergency 911
• local: Allows local calls only
• ld: Allows long distance calls
• intl: Allows international calls

Step 2: Define the COR lists that will be assigned as “outgoing” to the PSTN dial peers with the command dial-peer cor list.

Router(config-dp-corlist)#dial-peer cor list 911call
Router(config-dp-corlist)#member 911
Router(config-dp-corlist)#dial-peer cor list localcall
Router(config-dp-corlist)#member local
Router(config-dp-corlist)#dial-peer cor list ldcall
Router(config-dp-corlist)#member ld
Router(config-dp-corlist)#dial-peer cor list intlcall
Router(config-dp-corlist)#member intl

Define the COR lists that will be assigned as “incoming” from the local dial peers with the command dial-peer cor list .

Router(config)#dial-peer cor list local
Router(config-dp-corlist)#member 911
Router(config-dp-corlist)#member local

Router(config)#dial-peer cor list ld
Router(config-dp-corlist)#member 911
Router(config-dp-corlist)#member local
Router(config-dp-corlist)#member ld

Router(config)#dial-peer cor list intl
Router(config-dp-corlist)#member 911
Router(config-dp-corlist)#member local
Router(config-dp-corlist)#member ld
Router(config-dp-corlist)#member intl

Step 4: Assign Outbound COR Lists to PSTN Dial Peers

• Dial peer 911 has the outgoing 911call COR list
• Dial peer 9911 has the outgoing 911call COR list.
• Dial peer 9 has the outgoing localcall COR list.
• Dial peer 91 has the outgoing ldcall COR list.
• Dial peer 9011 has the outgoing intlcall COR list.

Router(config)#dial-peer voice 911 pots
Router(config-dial-peer)#destination-pattern 911
Router(config-dial-peer)#forward-digits all
Router(config-dial-peer)#corlist outgoing 911call
Router(config-dial-peer)#port 0/0/0:23

Router(config)#dial-peer voice 9911 pots
Router(config-dial-peer)#destination-pattern 9911
Router(config-dial-peer)#forward-digits 3
Router(config-dial-peer)#corlist outgoing 911call
Router(config-dial-peer)#port 0/0/0:23

Router(config)#dial-peer voice 9 pots
Router(config-dial-peer)#destination-pattern 9[2-9]……
Router(config-dial-peer)#corlist outgoing localcall
Router(config-dial-peer)#port 0/0/0:23

Router(config)#dial-peer voice 91 pots
Router(config-dial-peer)#destination-pattern 91[2-9]..[2-9]……
Router(config-dial-peer)#prefix 1
Router(config-dial-peer)#corlist outgoing ldcall
Router(config-dial-peer)#port 0/0/0:23

Router(config)#dial-peer voice 9011 pots
Router(config-dial-peer)#destination-pattern 9011T
Router(config-dial-peer)#prefix 011
Router(config-dial-peer)#corlist outgoing intlcall
Router(config-dial-peer)#port 0/0/0:23

Reference: CVoice Student Guide v6.0 (Page 4-165)

Question 3

Refer to the exhibit. Which dial peer configuration will block phone A from making long distance calls?

Partial configuration on Gateway-A: dial-peer cor custom name Emergency name Local name LD name Intl dial-peer cor list Em01 member Emergency dial-peer cor list Local01 member Local dial-peer cor list LD01 member LD dial-peer cor list Intl01 member Intl dial-peer cor list LocalLst member Emergency member Local dial-peer cor list LDLst member Emergency member Local member LD dial-peer cor list IntlLst member Emergency member Local member LD member Intl

A.
dial-peer voice 1374 pots
destination-pattern 1374
port1/0/0
dial-peer voice 100 voip
corlist incoming Intl01
destination-pattern 9011T
session target ipv4:192.168.101.254

B.
dial-peer voice 1374 pots
destination-pattern 1374
port1/0/0
dial-peer voice 100 voip
corlist outgoing Intl01
destination-pattern 9011T
session target ipv4:192.168.101.254

C.
dial-peer voice 1374 pots
corlist incoming LDLst
destination-pattern 1374
port1/0/0
dial-peer voice 100 voip
destination-pattern 9011T
session target ipv4:192.168.101.254

D.
dial-peer voice 1374 pots
corlist outgoing LDLst
destination-pattern 1374
port1/0/0
dial-peer voice 100 voip
destination-pattern 9011T
session target ipv4:192.168.101.254

E.
dial-peer voice 1374 pots
corlist incoming LocalLst
destination-pattern 1374
port1/0/0
dial-peer voice 100 voip
corlist outgoing Intl01
destination-pattern 9011T
session target ipv4:192.168.101.254

F.
dial-peer voice 1374 pots
corlist outgoing LDLst
destination-pattern 1374
port1/0/0
dial-peer voice 100 voip
corlist outgoing Intl01
destination-pattern 9011T
session target ipv4:192.168.101.254

Answer: E

Explanation

To block phone A from making long distance calls, phone A must belong to an “incoming” dial-peer which is not a member of the LD (Long Distance). In three incoming dial-peer (the three last dial-peers), there is only one dial-peer satisfies with this condition, that is the LocalLst dial-peer so the answer should be E.

One tip to quickly recognizes which dial-peer is for “outgoing” dial-peer is that this type of dial-peer usually have only one member. In this question, the outgoing dial-peers are Em01, Local01, LD01, Intl01. Dial-peers which have more than one member are often “incoming” dial-peers.

You can read http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml for another example. [/protect]

Question 4

Where would you assign COR lists in Cisco Unified Communications Manager Express?

A. ephone
B. ephone-dn
C. voice register dn
D. voice register pool

Answer: B

Explanation

For Cisco Unified Communications Manager Express, the COR list is directly assigned to the appropriate Ethernet phone-dn (ephone-directory number)