Showing posts with label Gateway. Show all posts
Showing posts with label Gateway. Show all posts

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-

Friday, October 16, 2009

CCIE Voice Lab 1.5 – Voice Gateways

In CCIE Voice Lab 1.5, tasks will involved configuring the voice gateways in New York, Los Angeles, and London. To conserve DSP resources in my lab, I am only configuring 3 channels per voice gateway.

CCIE Voice Lab 1.5 Tasks

1. Configure the New York voice gateway as an H.323 gateway, and register with CUCM.

2. Configure Los Angeles as an MGCP gateway. However, you cannot use the “ccm-manager config server” command. If the primary CUCM goes down, make sure all endpoints on the MGCP gateway re-register to the backup CUCM.

3. Configure PSTN connectivity for London.

4. Configure the New York voice gateway as a gatekeeper. Register the CUCM servers and London CUCME router to the gatekeeper. The CUCM servers should register with the technology prefix of “1” and the London CUCME router should register with technology prefix “2”.

5. Verify inbound calling from the PSTN.


CCIE Voice Lab 1.5 Solutions

1. First step in adding the New York VGWY to CUCM is to configure the appropriate parameters in the router, including the VWIC module and dial-plan configurations.

newyork#
!
card type t1 0 0
!
network-clock-participate wic 0
!
isdn switch-type primary-ni
!
!
voice class codec 1
codec preference 1 g722-64
codec preference 2 g711ulaw
codec preference 3 g711alaw
codec preference 4 g729r8
!
!
voice class h323 1
h225 timeout tcp establish 3
!
!
controller T1 0/0/0
cablelength long 0db
pri-group timeslots 1-3,24
!
!
!
interface FastEthernet0/0.12
description New York Voice VLAN
encapsulation dot1Q 12
ip address 10.1.12.1 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.1.12.1
!
!
dial-peer voice 1 pots
description inbound PRI dial-peer
incoming called-number .
direct-inward-dial
port 0/0/0:23
!
dial-peer voice 100 voip
description Voip DialPeer to UCMSUB01
preference 1
destination-pattern 2124321...
voice-class codec 1
voice-class h323 1
session target ipv4:10.1.10.21
incoming called-number .
dtmf-relay h245-alphanumeric
!
dial-peer voice 101 voip
description Voip DialPeer to UCMPUB01
preference 2
destination-pattern 2124321...
voice-class codec 1
voice-class h323 1
session target ipv4:10.1.10.20
incoming called-number .
dtmf-relay h245-alphanumeric
!
dial-peer voice 2 pots
destination-pattern 9T
port 0/0/0:23
!


Next, add the voice gateway to CUCM. Do not forget to modify the significant digits that CUCM receives for inbound calls.



2. The instructions for adding Los Angeles as an MGCP voice gateway explicitly tell us NOT to use the the “ccm-manager config server” command. Therefore, we need to manually configure the MGCP information on the router.

losangeles#
!
card type t1 0 1
!
network-clock-participate wic 1
!
isdn switch-type primary-ni
!
!
controller T1 0/1/0
cablelength long 0db
pri-group timeslots 1-3,24 service mgcp
!
!
interface Serial0/1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
!
ccm-manager switchback immediate
ccm-manager redundant-host 10.1.10.20
ccm-manager mgcp
ccm-manager fax protocol cisco
!
mgcp
mgcp call-agent 10.1.10.21 service-type mgcp version 0.1
mgcp fax t38 ecm
mgcp bind control source-interface Vlan22
mgcp bind media source-interface Vlan22
!
mgcp profile default
!
!
!
dial-peer voice 1 pots
service mgcp
incoming called-number .
direct-inward-dial
port 0/1/0:23
!
dial-peer voice 2 pots
service mgcp
destination-pattern 9T
port 0/1/0:23
!


Next, add the router as an MGCP gateway. Again, make sure to modify the significant digits that CUCM receives for inbound calls.







3. Configuring the PSTN and Dial Peers in London is fairly straight forward. Please note, I could not configure my Adtran Atlass 550 to accept the international dial-plan (44-20-7654-3XXX). As a result, I’ve modified the Adtran to accept 20-7654-3XXX. As for the 44 international code for London, I will work around this issue later (TBD).

london#
!
card type t1 0 0
!
network-clock-participate wic 0
!
isdn switch-type primary-ni
!
!
!
controller T1 0/0/0
cablelength short 110
pri-group timeslots 1-3,24
!
!
dial-peer voice 1 pots
description inbound PRI dial-peer
incoming called-number .
direct-inward-dial
port 0/0/0:23
!
dial-peer voice 2 pots
destination-pattern 9T
port 0/0/0:23
!


4. The final gatekeeper configuration requires a little care. First, pay attention to the wording regarding the technology prefix task. Habit may be to add the “#” sign; however the task instructions state only to add a “1” or “2”. Adding the “#” would result in points lost. Also, because the New York VGWY has been added to CUCM with the 10.1.12.1 IP address, you need to use a different IP for gatekeeper.

newyork#
!
gatekeeper
zone local newyork ballplayersllc.com 1.1.1.1
zone local london ballplayersll.com
gw-type-prefix 1* gw ipaddr 10.1.10.21 1720 gw ipaddr 10.1.10.20 1720
gw-type-prefix 2* gw ipaddr 3.3.3.3 1720
no shutdown
!

london#
!
interface Loopback0
ip address 3.3.3.3 255.255.255.0
ip ospf network point-to-point
h323-gateway voip interface
h323-gateway voip id newyork ipaddr 1.1.1.1 1719
h323-gateway voip h323-id london
h323-gateway voip tech-prefix 2
!
gateway
timer receive-rtp 1200
!
Next, add the Gatekeeper and Gatekeeper Controller Trunk to CUCM.







newyork#sh gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
--------------- ----- --------------- ----- --------- ---- -----
3.3.3.3 1720 3.3.3.3 63826 newyork VOIP-GW
H323-ID: london
E164-ID: 3001
E164-ID: 3002
E164-ID: 3003
E164-ID: 3004
E164-ID: 3005
E164-ID: 3333
E164-ID: 2076543001
E164-ID: 2076543002
E164-ID: 2076543003
E164-ID: 2076543004
E164-ID: 2076543005
E164-ID: 2076543333
Voice Capacity Max.= Avail.= Current.= 0
10.1.10.20 41390 10.1.10.20 32833 newyork VOIP-GW
H323-ID: trunk_to_newyork_gkpr_1
Voice Capacity Max.= Avail.= Current.= 0
10.1.10.21 36152 10.1.10.21 32821 newyork VOIP-GW
H323-ID: trunk_to_newyork_gkpr_2
Voice Capacity Max.= Avail.= Current.= 0
Total number of active registrations = 3

newyork#sh gatekeeper gw-type-prefix
GATEWAY TYPE PREFIX TABLE
=========================
Prefix: 1*
Statically-configured gateways (not necessarily currently registered):
10.1.10.21:1720
10.1.10.20:1720
Zone newyork master gateway list:
10.1.10.20:41390 trunk_to_newyork_gkpr_1
10.1.10.21:36152 trunk_to_newyork_gkpr_2

Prefix: 2*
Statically-configured gateways (not necessarily currently registered):
3.3.3.3:1720
Zone newyork master gateway list:
3.3.3.3:1720 london

5. Each location should now be able to receive inbound calls from the PSTN. However, since a dial plan has yet to be configured on CUCM, only London can dial out.