The 6608 and 6624 cards are not configurable for Quality of Service (QoS). Therefore, you need to understand the default tagging behaviour of these cards and, if necessary, take action on the Catalyst switch to conform to the QoS policy being implemented network wide.
The 6608 and 6624 internal port is treated as trust-cos to the Catalyst 6000. So the default COS-to-DSCP mapping of the cards will determine the DSCP values with which the IP packets are marked unless they are changed in the switch.
The 6608 and 6624 will tag packets as follows:
COS = 5 for rtp traffic
COS = 3 for signalling traffic
By default on the Catalyst 6000, these COS values map in IP packets to DSCP 24 (COS = 3) and 40 (COS = 5) as shown in the table below.
Generally, the recommended DSCP values to use in a VoIP network differ slightly. They are:
It may be necessary to change the default COS-DSCP mapping on the Catalyst 6000 so that the DSCP markings in packets generated by the 6608 and 6624 cards conform to the network policy. For example, if other devices in the network are marking packets with the recommended values.
Hopefully someone can answer this. I have an existing cube with one provider configured and working just fine. I have been tasked with creating another cube at another site coming back to our CUCM 11.0. This is done and configured. ...
Hello,my provider has changed their service and no longer support the DNS configuration setting "A-Record".So my CISCO IP Phone doesn't work anymore. On the display the message is: "Checking DNS".Do you know what I have to change to bring it back to work?...
Hello, we are unable to call numbers in US because our telco is saying we are sending 11 digits to them (instead of 10). My senior staff is away so I am trying to figure this out. We are using e164 dial plan----and using mask with +1XXXXXXXXXX numbe...
I was alerted an issue the other day from a UCCX Subscriber node of the NonVoice Subsystem in partial service. When I checked the CCX Engine service and sub service, it showed fully up and had been up for several weeks since it was last rebooted. Not...