<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">There is the dscp-profile command under voice services voip -> sip</div><div dir="ltr"><br></div><div dir="ltr">Never used it but if it’s going to be somewhere I’d expect it to be there.</div><div dir="ltr"><br><blockquote type="cite">On Apr 23, 2020, at 14:55, Anthony Holloway <avholloway+cisco-voip@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">Well Scuba Jason,<div><br></div><div>IOS has always marked control traffic as AF31, as well as SCCP control traffic for registered media resources.</div><div><br></div><div>The two things I have seen recommended and done are:</div><div><br></div><div>1. Change the settings per dial-peer / sccp config (technically this is ip precedence 3, which aligns loosely with cs3, as they share the first 3 bits)</div><div>2. Use a match-any for cs3 and af31 in your class maps</div><div><br></div><div>From the QoS SRND: <br></div><div><br></div><div>"The QoS Baseline recommends marking Call-Signaling to CS3. However, currently most Cisco IP Telephony products mark Call-Signaling to AF31. A marking migration from AF31 to CS3 is under way within Cisco, but in the interim it is recommended that both AF31 and CS3 be reserved for Call-Signaling and that Locally-Defined Mission-Critical Data applications be marked to a temporary placeholder non-standard DSCP, such as 25. Upon completion of the migration, the QoS Baseline marking recommendations of CS3 for Call-Signaling and AF31 for Locally-Defined Mission-Critical Data applications should be used. These marking recommendations are more in line with RFC 2474 and RFC 2597."</div><div><br></div><div><a href="https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND/QoS-SRND-Book/QoSIntro.html">Source</a></div><div><br></div><div>Though, this "transition period" seems to have gone on indefinitely.</div><div><br></div><div>FWIW, I have never seen a global command to switch it, and <a href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/vcr2/vcr2-cr-book/vcr-i1.html#wp3986668457">the documentation</a> doesn't tell us that there is one for dial-peer signaling. The sccp command is global.</div><div><br></div><div>Stay buoyant!</div><div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 23, 2020 at 1:55 PM Jason Aarons <<a href="mailto:scubajasona@gmail.com">scubajasona@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>CallManager marks control traffic as CS3, but just see that IOS-XE on 4431 16.09.05 marks control as AF31 by default. <br></div><div><br></div><div>Is there a global IOS command to change IOS-XE to use CS3 ? Rather then on a per dial-peer level?</div><div><br></div><div>All my class maps to protect control are based on CS3.</div><div><br></div><div>Hope all is well here. Work changed emails couple times and that created challenges! I still read every week, but changed emails so I can actually reply again!</div><div><br></div><div>-jason<br></div></div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
<span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span>cisco-voip@puck.nether.net</span><br><span>https://puck.nether.net/mailman/listinfo/cisco-voip</span><br></div></blockquote></body></html>