Cisco Cisco IP Contact Center Release 4.6.1 Design Guide

Using the public (visible) network as an example, the class map below identifies two marking levels, 
AF31 for high-priority traffic (which actually includes medium-priority public network traffic because 
it is marked the same as the high-priority traffic by default) and AF11 for low-priority traffic:

class-map match-all Unified ICM_Public_High

    match ip dscp af31

class-map match-all ICM_Public_Low

    match ip dscp af11

If the link is dedicated to Unified ICM Public traffic only, the policy map puts ICM_Public_High traffic 
into the priority queue with the minimum and maximum bandwidth guarantee of 500 kbps, and it puts 
ICM_Public_Low traffic into the normal queue with a minimum bandwidth of 250 kbps:

policy-map ICM_Public_Queuing

    class ICM_Public_High

        priority 500

    class ICM_Public_Low

        bandwidth 250

You can also use the commands priority percent and bandwidth percent to assign bandwidth on a 
percentage basis, and 90% of the link bandwidth should be assigned to the priority queue.

If it is a shared link, then you should use the sizing tools introduced in the section on Bandwidth 
Provisioning, to calculate the bandwidth requirement at each priority level and add it to the allocation 
for non-ICM traffic in the same queue. For example, if the link is shared with Unified CM ICCS traffic 
and RTP traffic and they respectively require 600 kbps and 400 kbps, and if the link also carries the 
private traffic in case of failover and the high priority and low priority private ICM traffic respectively 
require 200 kbps and 100 kbps, the configuration would be:

policy-map Converged_Link_Queuing

    class RTP

  priority 400

    class ICCS

        bandwidth 600

    class ICM_Public_High

        bandwidth 500

    class ICM_Public_Low

        bandwidth 250

    class ICM_Private_High

        bandwidth 200

    class ICM_Private_Low

        bandwidth 100

You can also use the commands priority percent and bandwidth percent to assign bandwidth on a 
percentage basis. If the link is dedicated to Unified ICM traffic only, 90% of the link bandwidth should 
be assigned to the priority queue. If it is a shared link, then you should use the sizing tools introduced 
in the section on 

, to calculate the bandwidth requirement at each 

priority level and add it to the allocation for non-ICM traffic in the same queue.

Finally, the queuing policy is applied to the outgoing interface:

interface mod/port 

    service-policy output ICM_Public_Queuing

As discussed earlier, rather than marking traffic in the Unified ICM, another option is to mark traffic at 
the network edge. First, define access lists to recognize Unified ICM traffic flows:

access-list 100 permit tcp host Public_High_IP any

access-list 100 permit tcp any host Public_High_IP