Hello,
best practice puts signaling into another class than voip "payload" as you named it.
The reason is that the qos requirements are different. Signaling needs guaranteed bandwidth, voip needs low delay and guaranteed bandwidth.
TFTP can be placed into signaling class or in a separate class.
An example config could look like this:
ip cef
class-map match-any VoIP
match ip dscp ef cs5
match protocol rtp audio
class-map match-any VoIPsignal
match ip dscp cs3
class-map match-all TFTP
match protocol tftp
policy-map VoIPprio
class VoIP
priority percent 10
class VoIPsignal
bandwidth remaining percent 5
class TFTP
bandwidth remaining percent 5
class class-default
fair-queue
random-detect
interface Serial0
ip address ...
service-policy output VoIPprio
You would have to adjust the bandwith ratios for your needs and the interface naming to your environment.
The policy will give 10% of the link to voip traffic with lowest possible delay, 5% of the rest for voip signaling, 5% to TFTP and the rest for the other data present.
Hope this helps
