As Dennis alluded to you should separate the classification and marking duties from the prioritization and queuing/policing effort. For one thing, doing this on Catalyst switching platforms offloads effort to the ASIC instead of doing it in router CPU.
Physical phones are capable of marking their traffic in accordance with the settings on CUCM; by default this is EF for RTP traffic, CS3 for SIP/SCCP signaling, and CS3 for TFTP config. I always change the TFTP traffic to get it out of call signaling and recommend either AF11 or BE depending on how many queues your QoS design/model is following. If you are using software phones, such as IP Communicator or Jabber the reality is that their DSCP markings likely won't make it to the switch. For those use cases you can: a) fix Windows/OS to get DSCP markings through & do a conditional trust model where the PC is allowed to send DSCP-marked traffic up to a policed threshold; b) force soft phones to use a Trusted Relay Point (i.e. software MTP on the local router) to proxy and mark the packets from a more trusted device in the network; or, c) classify manually.
So, in a typical design you would see the access layer switch either trust, conditionally trust, or classify and mark at ingress, uplink ports to distribution/core trust and prioritize merely at the layer two/ASIC (aka wrr-queue priority commands), and the WAN router perform prioritization and LLQ/CBWFQ.
Enterprise QoS Solution Reference Network Design Guide Version 3.3
Medianet Campus QoS Design 4.0
Network management traffic is typically CS6 and most - but not all - router processes tag packets with this by default. Adapting your example:
class-map match-any VOIP-MEDIA
match dscp ef
class-map match-any VOIP-SIGNAL
match dscp cs3
match dscp af31 ! This is a deprecated marking for VoIP. You should reconfigure your gear to stop using this.
class-map match-any VOIP-VIDEO
match af41 ! Doesn't account for immersive video but I'm guessing you don't have this.
class-map match-any MANAGEMENT
match CS6
match protocol ssh ! Notice: Invokes NBAR.
policy-map AVPN-POLICY-MAP
class VOIP-MEDIA
priority 320 ! See http://www.bandcalc.com for value to put here; ensuring you choose Link radio button, correct codec, and if you are using RTCP
class VOIP-SIGNAL
bandwidth remaining percent 5 ! Commonly bumped up to 10% if heavy SIP usage.
class VOIP-VIDEO
bandwidth remaining percent 50
class MANAGEMENT
bandwidth remaining percent 3
class class-default
fair-queue
Disclaimer: I spent about 90 seconds on this; consider this a micro-level example and not a macro-level design recommendation.
PS- Don't use the word COS in the context of a layer three class/policy-map. COS is a term used with IEEE 802.1p, which in turn only exists on 802.1q trunks (e.g. phone to switch, switch uplinks, etc).
