since qos is not enabled, the dscp will be preserved when it passes through the switch. cos is sent across a link only if the link is a trunk. Now there is an internal DSCP/COS that is used by the switch when the packet traverses through the backplane of the switch. This DSCP is usually derived on ingress either using the trust state of the ingress port or using ACLs or policy maps that have been used to remark the packet on ingress. This DSCP is used in conjunction with DSCP-COS value and the cos value generated is usually used for outbound queueing on egress ports. All the above works only if QOS is enabled on the switch. So to answer your second question, if the outbound port is a trunk link cos is set to 0, otherwise cos is not sent.
Thanks for your response. One more question regarding this: if that's the case, is the voice packet will be residing in the non-priority queue before transmitted out the switch(you know what i am refering to is 1q4t this kind of switch queue) right?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.