Monday, December 28, 2009

CCIE Voice Lab 1.10 – Quality of Service

Quality of Service (QoS) will be the focus CCIE Voice Lab 1.10.

CCIE Voice Lab 1.10 Tasks

1. Ensure that Skinny traffic from New York to Los Angeles is set to DSCP CS3. Any and all markings should be done by the endpoint whenever possible.

2. Limit SCCP traffic in both New York and Los Angeles to 30k per endpoint, and exceed traffic should be remarked to AF11.

3. Configure the frame relay link between New York and Los Angeles as if it is a full T1 (1536kpbs) link. Ensure that MLP FLI is enabled on the link. Lastly, configure the QoS as follows:
a. Voice media traffic should have a 30% priority of link bandwidth;
b. Voice signaling traffic should be given 5% of the link bandwidth;
c. All other traffic should be treated with weighted fair queuing.

4. Configure the frame relay link between New York and Los Angeles as if it is a half- T1 (768 kbps) link, with the following QoS parameters:
a. Voice media traffic should have a 192K of link bandwidth prioritized;
b. Voice signaling traffic should be given 38K of the link bandwidth;
c. All other traffic should be treated with weighted fair queuing.

5. Ensure that the New York VGWY, Los Angeles VGWY, and London CUCME send signaling and media traffic at DSCP CS3 and EF respectively.

CCIE Voice Lab 1.10 Solutions

1. By default, SCCP DSCP values are set at CS3 in the CUCM Enterprise Parameters.




Next, identical QoS policies are configured on both the New York and London switches (3750 and NME-16ES-1G-P, respectively). First, enable QoS globally, then define the policed DSCP remarking:

mls qos
mls qos map policed-dscp 24 to 10



Then, create the appropriate access-list to identify the SCCP traffic, following by the class-map to match the traffic, and finally, the QoS policy.

!
access-list 101 permit tcp any any eq 2000
!
class-map match-all SCCP
match access-group 101
!
!
policy-map MARK-SCCP
class SCCP
set dscp cs3
police 30000 8000 exceed-action policed-dscp-transmit


The final step is to create an inbound service-policy for the switchports that have IP phones.

interface FastEthernet1/0/8
description newyork phones
switchport access vlan 11
switchport voice vlan 12
spanning-tree portfast
service-policy input MARK-SCCP


2. The QoS and Traffic Shaping described in task 3 requires the creation Modular QoS CLI, a Virtual Template, and Frame Relay traffic shaping on both the New York and Los Angeles routers. Note, the configurations are identical on both routers, with the exception of the IP Addressing on both sides of the link. The first step it to create the QoS policy.

class-map match-all SIGNAL
match ip dscp cs3
class-map match-all RTP
match ip dscp ef
!
!
policy-map NY-LA-QOS
class RTP
priority percent 30
class SIGNAL
bandwidth percent 5
class class-default
fair-queue

Next, create the Virtual Templates for both New York and Los Angeles. Below is the New York side of the link.

!
interface Virtual-Template102
bandwidth 1536
ip address 172.16.1.1 255.255.255.252
ip ospf network point-to-point
ppp multilink
ppp multilink interleave
ppp multilink fragment delay 10
service-policy output NY-LA-QOS
!

Then, create the frame relay traffic shaping policy, and associate the Virtual Template with the Frame Relay sub-interface, and associate the frame relay traffic shaping policy.

!
map-class frame-relay FRTS-NY-LA
frame-relay cir 1536000
frame-relay bc 15360
frame-relay be 0
frame-relay mincir 1536000
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
frame-relay traffic-shaping
frame-relay lmi-type cisco
!
interface Serial0/2/0.102 point-to-point
description frame relay link to Los Angeles
ip ospf network point-to-point
frame-relay interface-dlci 102 ppp Virtual-Template102
class FRTS-NY-LA
!


3. The QoS configuration between New York and London is slightly different, since the tasks do not instruct us to configure MLP LFI. For this link, the QoS policy-map is defined, reusing the previously configured class-maps. Then, a frame-relay traffic shaping policy is defined, with the QoS service-policy tied to it. Lastly, the FRTS policy is associated with the frame-relay sub-interfaces between New York and London.

!
policy-map NY-LNDN-QOS
class RTP
priority 192
class SIGNAL
bandwidth 38
class class-default
fair-queue
!
!
map-class frame-relay FRTS-NY-LNDN
frame-relay cir 768000
frame-relay bc 7680
frame-relay be 0
frame-relay mincir 768000
service-policy output NY-LNDN-QOS
!
!
interface Serial0/2/0.103 point-to-point
description frame relay link to London
ip address 172.16.1.5 255.255.255.252
ip ospf network point-to-point
frame-relay interface-dlci 103
class FRTS-NY-LNDN
!

4. By default, the MGCP and H323 gateways send media (RTP) marked as ef and signaling marked as af31.

To verify New York, first issue:

newyork#sh dial-peer voice 100 include DSCP
ip media DSCP = ef, ip media rsvp-pass DSCP = ef
ip media rsvp-fail DSCP = ef, ip signaling DSCP = cs3,
ip video rsvp-none DSCP = af41,ip video rsvp-pass DSCP = af41
ip video rsvp-fail DSCP = af41,

Then, modify the markings for each VOIPdDial-peer. Dial-peer 100 is shown below.

newyork(config)#dial-peer voice 100
newyork(config-dial-peer)#ip qos dscp cs3 signaling

In Los Angeles, verify by issuing a “show mgcp” to view the defaults.

losangeles#sh mgcp
!
MGCP media (RTP) dscp: ef, MGCP signaling dscp: af31


To modify, issue

losangeles(config)#mgcp ip qos dscp ef media
losangeles(config)#mgcp ip qos dscp cs3 signaling


then verify

losangeles#sh mgcp
!
MGCP media (RTP) dscp: ef, MGCP signaling dscp: cs3

CUCME marks voice media traffic at DSCP value EF by default and voice signaling DSCP value CS3 by default. These parameters may be changed under the telephony-service CLI parameters. A “show telephony-service” in London verifies the values.

london#sh telephony-service
CONFIG (Version=7.1)
=====================
Version 7.1
Cisco Unified Communications Manager Express
For on-line documentation please see:
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/tsd_products_support_series_home.html

ip source-address 10.1.32.1 port 2000
ip qos dscp:
ef (the MS 6 bits, 46, in ToS, 0xB8) for media
cs3 (the MS 6 bits, 24, in ToS, 0x60) for signal
af41 (the MS 6 bits, 34, in ToS, 0x88) for video
default (the MS 6 bits, 0, in ToS, 0x0) for serviceservice directed-

Wednesday, December 16, 2009

CCIE Voice Lab 1.9 – Conferencing, Transcoding, and MTP Resources

CCIE Voice Lab 1.9 requires the set up and configuration of Conferencing, Transcoding, and MTP Resources for Ballplayers, LLC.


CCIE Voice Lab 1.9 Tasks

1. For New York users, configure conferencing resources on the New York VGWY first, followed by the PUB, then SUB.

2. For LA users, configure conferencing resources on the LA VGWY first, followed by the PUB, then SUB.

3. Allow a maximum of 8 users in a conference bridge session. Ensure that when the Conference Controller leaves an AdHoc Conference, the call is dropped.

4. For each location, configure a MeetMe conference bridge using an x100 DN, where x= the appropriate dial plan for each location.

5. For both NY and LA, configure local transcoding resources.

6. Configure the London CUCME router to provide local transcoding and both MeetMe and AdHoc conferencing resources for users. Users should have a distinct join and leave tone.

7. Enable MOH for all three locations. Ensure that MOH files are available in G.711ulaw, G.729, and Wideband. Ensure the MOH loops.


CCIE Voice Lab 1.9 Solutions

The tasks in lab 1.9 require configuration in both the CUCM and VGWYs. The IOS commands will be covered first, followed by the CUCM, and lastly the London CUCME configuration.

1. The first step is to configure the DSP services on the New York and Los Angeles. The configurations on both VGWYs are nearly identical, with one exception pertaining to MOH in Los Angeles. That exception will be discussed separately later.

Essentially, you enable dspfarm services, followed by creating dspfarm profiles, and then associating those profiles with SCCP. The NY VGWY configuration is as follows:

newyork#sh run
!
voice-card 0
dspfarm
dsp services dspfarm
!
!
sccp local Loopback0
sccp ccm 10.1.10.21 identifier 2 version 7.0
sccp ccm 10.1.10.20 identifier 1 version 7.0
sccp
!
sccp ccm group 1
associate ccm 1 priority 1
associate ccm 2 priority 2
associate profile 2 register NY-VGWY-TRANS
associate profile 1 register NY-VGWY-CONF
!
dspfarm profile 2 transcode
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g722-64
codec g729br8
codec g729r8
maximum sessions 2
associate application SCCP
!
dspfarm profile 1 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
codec g722-64
maximum sessions 2
associate application SCCP
!

newyork# sh sccp
SCCP Admin State: UP
Gateway Local Interface: Loopback0
IPv4 Address: 1.1.1.1
Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 10.1.10.21, Port Number: 2000
Priority: N/A, Version: 7.0, Identifier: 2
Trustpoint: N/A
Call Manager: 10.1.10.20, Port Number: 2000
Priority: N/A, Version: 7.0, Identifier: 1
Trustpoint: N/A

Transcoding Oper State: ACTIVE - Cause Code: NONE
Active Call Manager: 10.1.10.20, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 2
Reported Max Streams: 4, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: g722r64, Maximum Packetization Period: 30
Supported Codec: g729br8, Maximum Packetization Period: 60
Supported Codec: g729r8, Maximum Packetization Period: 60
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30

Conferencing Oper State: ACTIVE - Cause Code: NONE
Active Call Manager: 10.1.10.20, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 1
Reported Max Streams: 16, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: g729r8, Maximum Packetization Period: 60
Supported Codec: g729br8, Maximum Packetization Period: 60
Supported Codec: g722r64, Maximum Packetization Period: 30
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30



2. Borrowing from the concepts of Gateways > Route Groups > Route Lists, first define the conference bridges and trancoding resources.




Next, define Media Resource Groups (MRG) and assign the conference bridges and trancoding resources accordingly. I’ve created a MRG for each location; New York and Los Angeles.



The MRGs are then added to a Media Resource Groups List (MRGL); one for each location. Watch the ordering, so that HW resources are used prior to SW resources.





Finally, assign the appropriate MRGL to the appropriate Device Pool for each location.




3. Configuring conferencing and transcoding resources for the London CUCME router is nearly identical to as configuring the resources on the NY and LA VGWYs. However, SSCP is associated with CUCME under telephony-service, rather than the UCMs. Rather than revisit the configuration, refer to CUCME-CUE Lab 7 – CUCME Conferencing & Transcoding. I assigned dn 3100 for the MeetMe bridge and 3101 for the AdHoc bridge.

4. There are few tricks for the MOH, specifically for the LA SIP-based location. First, make sure that the “Cisco IP Voice Media Streaming App” is activated under Cisco Unified Serviceability.

Next, make sure that G.711ulaw, G.729, and Wideband are selected under the Service Parameters > Cisco IP Voice Media Streaming App.




The MOH servers are then assigned to the MRGs; see the NY MRG screenshot above. To quickly assign the same MOH file to all phones, go to Device > Device Settings > Common Device Configuration, and create a custom configuration. I’ve chosen “1952 Vincent Black Lightning” from Alt-County band “Reckless Kelly”.




This newly created “MOH Common Device Configuration” can now be assigned to each phone.



When testing MOH up to this point, I noticed the phones based in Los Angeles were not receiving MOH. After some research, I discovered the MOH for SIP phones needs to terminate on an MTP resource on the LA VGWY. Therefore, one additional dspfarm profile is required for the LA VGWY, along with its companion configuration in UCM. This MTP is then assigned to the LA MRG.

losangeles#sh run
!
sccp ccm group 1
associate ccm 1 priority 1
associate ccm 2 priority 2
associate profile 3 register LA-VGWY-MTP
associate profile 1 register LA-VGWY-CONF
associate profile 2 register LA-VGWY-TRANS
!
!
dspfarm profile 3 mtp
codec g711ulaw
maximum sessions software 2
associate application SCCP
!