<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div>I see; while this is by no means a complete solution, it may help. I'm assuming Cisco based soft phones (CIPC, CSF, BOT, TAB ... etc).</div>
<div><br>
</div>
<div>You may try Trusted Relay Points (set in the device level configuration). This does rely and depend on your media resource architecture and design; i.e. you'll need to have media resources that support TRP available.</div>
<div><br>
</div>
<div>Using TRP on the device config for a soft phone will cause CUCM to dynamically insert an MTP in the call flow which will allow for adherence to QOS trust policies and offer a predetermined network path for call flows in an otherwise untrusted network (presumably,
the data network).<br>
<br>
<div>-Ryan</div>
</div>
<div><br>
<div><br>
<br>
Sent from my iPhone</div>
On Jan 3, 2017, at 9:30 PM, Ben Amick <<a href="mailto:bamick@HumanArc.com">bamick@HumanArc.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Garamond",serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Garamond",serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Garamond",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Only for softphones. Currently most of our servers live on the same LAN as end users, so yeah. Hardphones have their own VLAN so its not as bad. In the future it won’t be that way but for the
time being it is.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3B3838">Ben Amick<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#3B3838">Telecom Analyst</span><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#666666"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]
<br>
<b>Sent:</b> Tuesday, January 03, 2017 9:18 PM<br>
<b>To:</b> Ben Amick <<a href="mailto:bamick@HumanArc.com">bamick@HumanArc.com</a>><br>
<b>Cc:</b> NateCCIE <<a href="mailto:nateccie@gmail.com">nateccie@gmail.com</a>>; Cisco VoIP Group <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> Re: [cisco-voip] Jabber/CIPC and QoS<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Ben,<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">By flat network; I am to assume that there is no layer 2 partition between rtp/signaling and general data traffic?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Jan 3, 2017, at 9:15 PM, Ben Amick <<a href="mailto:bamick@HumanArc.com">bamick@HumanArc.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#1F497D">Yeah, I have the luck of having MPLS right now, and I don’t see us going iWAN for a while for various reasons. QoS on the WAN right now even isn’t my issue, it’s QoS on the LAN. Right now we
have a relatively flat network, and certain segments of our troupe *<b>cough*</b>developers<b>*cough</b>* seems to have made our internal traffic ugly, to the point that I may have to do an analysis of it, as we’re having just random periods here and there
where calls just have horrible quality, of the type you normally see fixed by QoS</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3B3838">Ben Amick</span></b><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#3B3838">Telecom Analyst</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]
<br>
<b>Sent:</b> Tuesday, January 03, 2017 8:40 PM<br>
<b>To:</b> NateCCIE <<a href="mailto:nateccie@gmail.com">nateccie@gmail.com</a>><br>
<b>Cc:</b> Ben Amick <<a href="mailto:bamick@HumanArc.com">bamick@HumanArc.com</a>>; Cisco VoIP Group <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> Re: [cisco-voip] Jabber/CIPC and QoS<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">It's a shame really ... MPLS is far superior IMO, for many reasons. Call it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public Internet.<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Jan 3, 2017, at 7:53 PM, NateCCIE <<a href="mailto:nateccie@gmail.com">nateccie@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Or take the most approach of do nothing.<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">My personal favorite is to use codecs where QoS matters less, like iLBC, OPUS, etc. <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">So many business are getting rid of the QoS capable WAN and just doing VPNs, even if they have fancy names that make it sound better than public internet.<br>
<br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Jan 3, 2017, at 2:25 PM, Ben Amick <<a href="mailto:bamick@HumanArc.com">bamick@HumanArc.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt">So, I know this is an age old question that’s debated, but I’ve been wondering if anyone here has a perspective here in regards to QoS for softphones. Obviously, with hardphones, you usually partition a separate
VLAN with AutoQoS/DSCP tags, but that isn’t applicable with softphones. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">I’ve heard of three different options in the past, neither of which seem to be very simple to deploy, but all seem to be Jabber-centric.
</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:12.0pt">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Configuring windows to perform DSCP tagging, and do DSCP QoS on the switches they are connected to, as well as trusting the device. Problems: Requires users to be local admins, openings for abuse and network impact due
to blind PC trust.</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:12.0pt">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Configuring your switches with an access list that recognizes the ports Jabber does outbound to attach DSCP tags to them. Problems: Other programs could theoretically use those ports</span><o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:12.0pt">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:12.0pt">Installing Medianet services on all jabber clients; Configure all switches for medianet tagging. Problem: (I think?) Requires newer switches to use, maybe needs an additional server (I vaguely remember possibly needing
prime collab?)? </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Maybe I’m missing some things, but what approach have you guys taken for softphone/Jabber QoS? And on top of that, what options are there for CIPC (I know there’s the auto qos trust cisco-softphone for cisco
switches, but I don’t believe there’s a solution other than #1 for non-cisco switches)?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Garamond",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3B3838">Ben Amick</span></b><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#3B3838">Telecom Analyst</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
</span><o:p></o:p></p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><o:p></o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
<o:p></o:p></span></p>
</div>
</blockquote>
</div>
<br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
</div>
</blockquote>
</body>
</html>