to answer a couple questions....
1. This is affecting calls across the WAN (8 sites)
2. Not a true MPLS, but rather something called VES (Virtual Ethernet Service) it behaves as a mesh network. Everything is controlled through us, not provider
3. We are using a port on the switches for routing into the WAN, only our core site has a true router (the we would like to get away from)
Below is a "boxed" response from the WAN provider and I'm not sure if it's too much or irrelevant to the mitel system
class-map match-any PREMIUM
match ip dscp ef
match ip dscp cs5
exit
class-map match-any CRITICAL
match ip dscp af31
match ip dscp af32
match ip dscp af33
match ip dscp cs3
match ip dscp cs6
exit
class-map match-any BUSINESS
match ip dscp af11
match ip dscp af12
match ip dscp af13
match ip dscp af21
match ip dscp af22
match ip dscp af23
match ip dscp cs2
exit
policy-map QOS-CE-CLASS-A
class PREMIUM
priority percent 35
class CRITICAL
bandwidth percent 25
random-detect dscp-based
class BUSINESS
bandwidth percent 15
random-detect dscp-based
class class-default
fair-queue
random-detect
exit
exit
This would need to be placed on the outbound facing interface.
service-policy output QOS-CE-CLASS-A