Implementing Bandwidth Management and Call Admission Control

© 2010 Cisco and/or its affiliates. All rights reserved.

VPN v1.0—6-1

• Call Admission Control Overview • Locations

• RSVP-Enabled Locations
• Automated Alternate Routing • SIP Precondition • H.323 Gatekeeper Call Admission Control

© 2010 Cisco and/or its affiliates. All rights reserved.

VPN v1.0—6-2

All rights reserved.0—6-3 . VPN v1.Call Admission Control Overview © 2010 Cisco and/or its affiliates.

• CAC avoids such problems by limiting the number of voice calls.Any packets of any voice stream are affected (not just packets of the call that exceeds bandwidth limit). • QoS cannot solve the problem of too much prioritized traffic (caused by too many voice calls).0—6-4 . VPN v1. All rights reserved. • Oversubscription results in delayed packets and packet drops: .Results in quality degradation of all voice calls. © 2010 Cisco and/or its affiliates.CAC limits the number of calls between certain parts of the network in order to avoid bandwidth oversubscription: • QoS can be used to give priority to voice over data. .

H. H.RSVP-enabled locations.323 Gatekeeper or SIP CAC • CAC for calls leaving a cluster: . Locations CAC Locations CAC VPN v1.If CAC denies call.0—6-5 . . All rights reserved. © 2010 Cisco and/or its affiliates. . .323 gatekeeper or SIP precondition.Cisco Unified Communications Manager supports the following CAC features: • CAC within a cluster: . call fails.Locations. and no other entries in route list are left to try.If CAC denies call. automated alternate routing (AAR) can be used to reroute call over PSTN.

0—6-6 . All rights reserved.Locations © 2010 Cisco and/or its affiliates. VPN v1.

© 2010 Cisco and/or its affiliates. • Works within a Cisco Unified Communications Manager cluster (including exit points): .729 . gateways.Audio bandwidth is calculated by actual codec plus IP overhead (assuming 20 ms packetization period) • Examples: 80 kb/s for G. • Calls are limited by permitting a certain bandwidth for calls coming in and going out of a location: .Trunks.Bandwidth limitation is independent of destination location.• Each device has one location assigned. • Locations-based CAC is topology-unaware.Calls within a location are unlimited. VPN v1. and others can be put into a location. 24 kb/s for G. allowing some control for calls leaving the cluster.0—6-7 .711. . All rights reserved.

this can cause problems in non hub-and-spoke topologies. Location BR2: 96 Kb/s VPN v1. All rights reserved.0—6-8 . 1x G.Bandwidth is not limited between pairs of locations.729 Location HQ: Unlimited What if no calls to or from BR1 but four calls are attempted from BR2 to HQ? 3x G.729 Location BR1: 48 Kb/s © 2010 Cisco and/or its affiliates.729 IP WAN 1x G.

0—6-9 . location of device pool is ignored. VPN v1. If location is selected here. All rights reserved.Cisco Unified Communications Manager Administration: Device > Phone Location is indirectly applied via device pool (each device pool is configured with a location). © 2010 Cisco and/or its affiliates.

RSVP-Enabled Locations © 2010 Cisco and/or its affiliates.0—6-10 . All rights reserved. VPN v1.

All rights reserved.0—6-11 . Location B RSVP Agent1 to RSVP Agent2: RSVP-RTP Phone2 to RSVP Agent2: RTP VPN v1.SCCP Cisco Unified Communications Manager RSVP RTP RSVP Agent1 SCCP Phone1 IP WAN RSVP Agent2 SCCP Phone2 Location A Phone1 to RSVP Agent1: RTP © 2010 Cisco and/or its affiliates.

• If RSVP is not enabled on any hop in the path. the appropriate link is ignored by CAC algorithm. • Each interface is configured with maximum bandwidth to be reserved by RSVP. • IntServ/DiffServ model is used: 1) RSVP only for CAC (control plane) 2) LLQ for QoS (data plane) • Call is only set up after successful RSVP CAC.0—6-12 .• Based on standard Cisco IOS RSVP. VPN v1. All rights reserved. • IP network between RSVP agents is RSVP-enabled. © 2010 Cisco and/or its affiliates.

50 RSVP Receiver 10.10 N Hop: 10.50.30 Path Dest: 10.60.20 N Hop: 10.60.30 N Hop: 10.60.10.50.30 OK = Bandwidth RSVP-Unaware Router 10.50.30.0—6-13 .60 P Hop: 10. All rights reserved.10 10.40.40 RSVP-Aware Router 10.20.30.50.50.30 Resv Dest: 10.60.30.20 OK P Hop = 10.60.10.60 Path Dest: 10.60.50.60.30.60.30.60.50.20.50.10.20.20.30 P Hop = 10.= RSVP processing occurs RSVP reservedRSVP-Aware on interfaceRSVP-Aware Sender Router Router 10.50 Resv Dest: 10.30.30.30.60.40.60 P Hop: 10.50 Resv Dest: 10.50.50 OK P Hop = 10.10 P Hop = 10.50.20.60 P Hop: 10.30.30.50.20.30.30.50 N Hop: 10.10.60.60.20 10.30.20 Path Dest: 10.60 Resv Dest: 10.60.10.20 Resv Dest: 10.20.20.30.30 Path Dest: 10.60 P Hop: 10.10.50.10.60 P Hop: 10.60.10. VPN v1.30 N Hop: 10.50 OK © 2010 Cisco and/or its affiliates.20.10 Path Dest: 10.20.

VPN v1.0—6-14 . Mandatory RSVP Mid-Call Retry Counter: Defines the ―n‖ tries for mid-call error handling. All rights reserved.Default interlocation RSVP policy: • No Reservation—No RSVP reservations get made between locations. RVSP Retry Timer: Defines how often (in seconds) the RSVP agent will retry the reservation if there is a failure. • Mandatory – Both audio and video (if video call) reservations must succeed for Cisco Unified Communications Manager to ring terminating device. • Mandatory (Video Desired) – A video call can proceed as an audio-only call if a reservation for the audio stream succeeds but a reservation for the video stream does not succeed. © 2010 Cisco and/or its affiliates. • Optional (Video Desired) – A call can proceed as a best-effort. defines whether call becomes best effort or fails (after n retries). Mandatory RSVP Mid-Call Error Handling Option: If a mid-call failure occurs. audio-only call if failure to obtain reservations for both audio and video streams occurs.

VPN v1. All rights reserved.Automated Alternate Routing © 2010 Cisco and/or its affiliates.0—6-15 .

2 © 2010 Cisco and/or its affiliates.0—6-16 . All rights reserved.2 PSTN Branch A WAN CAC Phone A 1 Phone B Headquarters Branch B Cisco Unified Communications Manager CAC blocks 1 a call over the IP WAN. The call is automatically rerouted over the VPN v1.

00 RP: 9.Unified CM* Site1 (+1): international dialing: 9. Phone Nr Mask: 5115552XXX DN**: 3001 Ext. VPN v1. All rights reserved. 2 AAR groups . Mask: 69125XXXX AAR Group Configuration: Prefix US to DE: 901149 Prefix DE to US: 0001 * Unified CM = Cisco Unified Communications Manager © 2010 Cisco and/or its affiliates. Phone Nr. 2 AAR CSS.0—6-17 2 route patterns in different partitions.! AAR Group: DE PSTN DN**: 2001 Ext. Location Configuration: Hub_None: Unlimited BR-LOC: 24 kb/s Site 2 (+49): international dialing: 0.@ AAR Group: US IP WAN RP: 0.011 One active call over IP WAN Second call fails locations-based CAC and should use PSTN.

All rights reserved. © 2010 Cisco and/or its affiliates. Set the AAR Enable service parameter to True to enable AAR.0—6-18 .Cisco Unified Communications Manager Administration: System > Service Parameters > Cisco CallManager By default. VPN v1. Verify or modify the text displayed on the phone when a call is rerouted by AAR. Verify or modify the text displayed on the phone when a call fails due to CAC. AAR is disabled.

Note: In this example. © 2010 Cisco and/or its affiliates. VPN v1. configure the dial prefix that is added to the external phone number mask of the called phone.0—6-19 . All rights reserved. For each other AAR group. a single AAR group could have been used with a prefix of 91 (within the AAR group).Cisco Unified Communications Manager Administration: Call Routing > AAR Groups Enter the name of the AAR group. Specify the dial prefix for both directions (call from this AAR group to the other AAR group and vice versa). Configure the prefix that is added to the external phone number mask of the called phone for AAR calls within the same AAR group.

SIP Precondition © 2010 Cisco and/or its affiliates. All rights reserved. VPN v1.0—6-20 .

Supports RSVP CAC for calls over SIP trunks to • Cisco Unified Communications Manager • Cisco Unified Communications Manager Express • Cisco IOS SIP Gateway © 2010 Cisco and/or its affiliates.Built on the capabilities of Intra-Cluster RSVP .• Based on RFC3312: Integration of Resource Management and SIP . VPN v1.0—6-21 .Cisco Unified Communications Manager currently supports RSVP only • Intercluster (aka E2E [end-to-end]) RSVP . All rights reserved.Allows RSVP to be used with devices outside of the Cisco Unified Communications Manager cluster .RFC allows for several types of precondition signaling .

All rights reserved. SIP Trunk SCCP RTP RSVP Analog or digital Voice VPN v1.0—6-22 . RSVP can be used end-to-end between different domains • In case of Cisco Unified Communications Manager. RSVP agent of the phone is used (not the one of the trunk) • Cisco IOS gateways and Cisco Unified Communications Manager Express also support SIP Precondition IP WAN End-to-end RSVP © 2010 Cisco and/or its affiliates.• For SIP calls going out of the cluster.

1 a=curr:qos e2e none a=des:qos mandatory e2e sendrecv INVITE 183 SESSION PROGRESS PRACK m=audio 20000 RTP/AVP 0 c=IN IP4 192.0.2.2 a=curr:qos e2e none a=des:qos mandatory e2e sendrecv a=conf:qos e2e recv SIP UA1 initiates RSVP reservation in the 1  2 direction SDP 3 200 OK (PRACK) m=audio 10000 RTP/AVP 0 c=IN IP4 192.2. All rights reserved.1 a=curr:qos e2e send a=des:qos mandatory e2e sendrecv Path Resv Path Resv UPDATE 200 OK (UPDATE) 180 RINGING SIP UA2 initiates RSVP reservation in the 2  1 direction SDP 4 m=audio 20000 RTP/AVP 0 c=IN IP4 192.2.0—6-23 .QoS ―precondition‖ SDP 1 SIP UA 1 SIP UA 2 SDP 2 m=audio 10000 RTP/AVP 0 c=IN IP4 192.0.0.2 a=curr:qos e2e sendrecv a=des:qos mandatory e2e sendrecv Precondition complete © 2010 Cisco and/or its affiliates.2. Precondition complete VPN v1.0.

VPN v1.© 2010 Cisco and/or its affiliates.0—6-24 . All rights reserved.

Sign up to vote on this title
UsefulNot useful