It seems odd, admittedly. Basically the recommended standard(IETF or whatever) marking is EF (46 in decimal).
The maps on the Cisco kit are basically worked out in binary... i.e. there are 64 possible DSCP values, and 8 (0-7) COS values. So 0 cos = 0 dscp, 1 cos = 8 dscp, 2cos = 16 dscp and so on. Modifying the COS-DSCP map is basically the quickest and easiest way to bring the 'default' setup to a 'standard' setup.
In reality, there's no reason why you can't use 48 for voice. Or 13, or 58 for that matter. As long as your queueing configuration is appropriate (i.e. puts these marked packets into the PQ) it doesn't matter.
Where it does matter is when you interface to other networks - i.e. a managed WAN or another network using the standard EF marking for voice. If you use something odd, you'll either have to make sure everyone you interface with does as well, or use a dscp mutation map on the interfaces linked to them.
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
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.