<html>

<head>

<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">

<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>

</head>

<body dir="ltr">

<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr">

<p>Is there a similar process for Macs?</p>

<p><br>

</p>

<p><br>

</p>

<p><br>

</p>

<div id="Signature">

<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">

<p></p>

<div>---</div>

<div>Lelio Fulgenzi, B.A.</div>

<div>Senior Analyst, Network Infrastructure</div>

<div>Computing and Communications Services (CCS)</div>

<div>University of Guelph</div>

<div><br>

</div>

<div>519-824-4120 Ext 56354</div>

<div>lelio@uoguelph.ca</div>

<div>www.uoguelph.ca/ccs</div>

<div>Room 037, Animal Science and Nutrition Building</div>

<div>Guelph, Ontario, N1G 2W1</div>

<p></p>

</div>

</div>

<br>

<br>

<div style="color: rgb(0, 0, 0);">

<hr tabindex="-1" style="display:inline-block; width:98%">

<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Anthony Holloway <avholloway+cisco-voip@gmail.com><br>

<b>Sent:</b> Tuesday, January 10, 2017 2:01 PM<br>

<b>To:</b> Ben Amick; Dana Tong; Tom Sparks; cisco-voip@puck.nether.net<br>

<b>Subject:</b> Re: [cisco-voip] Jabber/CIPC and QoS</font>

<div> </div>

</div>

<div>

<div dir="ltr">

<div>Setting the port ranges gives you two benefits:<br>

</div>

<div><br>

</div>

<div>1) You get to know exactly, and somewhat succinctly which ports will be used by Jabber for RTP (cause you already know what it is for signaling 5060).  This one isn't all that great, but if you're going to write an ACL, then it's nice to write 3000 39999,

 versus 16384 32768.  Preference I guess.</div>

<div><br>

</div>

<div>2) This one is the real winner.  You get to separate your voice from your video traffic, into two different port ranges, allowing you to mark audio at EF and video at AF42, or something else.  This way you can have video deteriorate by audio survive. 

 The Sync no longer relies on same classification/marking, that's what RTCP is doing for you nowadays.</div>

<div><br>

</div>

<div>At the end of the day, the Group Policy allows you to deny programs from hijacking your markings as they leave the PC.  Therefore, the switch would only ever receive trusted DSCP markings.</div>

<div><br>

</div>

<div>"For later operating systems such as Microsoft Windows 7, Microsoft implements a security feature that prevents applications from setting DSCP values on IP packet headers. For this reason, you should use an alternate method for marking DSCP values, such

 as Microsoft Group Policy."</div>

<div>Source: <a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_010001.html">

Jabber On-Prem Deployment Guide</a></div>

<div><br>

</div>

<div><br>

</div>

</div>

<br>

<div class="gmail_quote">

<div dir="ltr">On Tue, Jan 10, 2017 at 10:18 AM Ben Amick <<a href="mailto:bamick@humanarc.com">bamick@humanarc.com</a>> wrote:<br>

</div>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">

<div bgcolor="white" lang="EN-US" class="gmail_msg">

<div class="m_261435386047953373WordSection1 gmail_msg">

<p class="MsoNormal gmail_msg"><span class="gmail_msg" style="font-family:"Calibri",sans-serif; color:#1f497d">Dana,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span class="gmail_msg" style="font-family:"Calibri",sans-serif; color:#1f497d">So if I understand you right, you used the SIP profile to set the ranges, GPO to mark the DSCPs, and the switches to trust DSCP.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span class="gmail_msg" style="font-family:"Calibri",sans-serif; color:#1f497d"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span class="gmail_msg" style="font-family:"Calibri",sans-serif; color:#1f497d">I assume this means you used access lists to only accept the marking if from that port range? If not, why did you set the port ranges and how are

 you mitigating the risk of other programs hijacking your QoS?<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span class="gmail_msg" style="font-family:"Garamond",serif; color:#1f497d"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg" style="text-autospace:none"><b class="gmail_msg"><span class="gmail_msg" style="font-size:10.0pt; font-family:"Garamond",serif; color:#3b3838">Ben Amick<u class="gmail_msg"></u><u class="gmail_msg"></u></span></b></p>

<p class="MsoNormal gmail_msg" style="text-autospace:none"><span class="gmail_msg" style="font-size:9.0pt; font-family:"Garamond",serif; color:#3b3838">Telecom Analyst</span><span class="gmail_msg" style="font-size:9.0pt; font-family:"Garamond",serif; color:#666666"><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

</div>

<p class="MsoNormal gmail_msg"><span class="gmail_msg" style="font-family:"Garamond",serif; color:#1f497d"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<div class="gmail_msg" style="border:none; border-top:solid #e1e1e1 1.0pt; padding:3.0pt 0in 0in 0in">

<p class="MsoNormal gmail_msg"><b class="gmail_msg"><span class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif">From:</span></b><span class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank">cisco-voip-bounces@puck.nether.net</a>]

<b class="gmail_msg">On Behalf Of </b>Dana Tong<br class="gmail_msg">

<b class="gmail_msg">Sent:</b> Monday, January 09, 2017 11:29 PM<br class="gmail_msg">

<b class="gmail_msg">To:</b> Tom Sparks <<a href="mailto:tsparks@taosconsulting.com" class="gmail_msg" target="_blank">tsparks@taosconsulting.com</a>>;

<a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank">cisco-voip@puck.nether.net</a></span></p>

</div>

</div>

</div>

</div>

<div bgcolor="white" lang="EN-US" class="gmail_msg">

<div class="m_261435386047953373WordSection1 gmail_msg">

<div class="gmail_msg">

<div class="gmail_msg" style="border:none; border-top:solid #e1e1e1 1.0pt; padding:3.0pt 0in 0in 0in">

<p class="MsoNormal gmail_msg"><span class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><br class="gmail_msg">

<b class="gmail_msg">Subject:</b> Re: [cisco-voip] Jabber/CIPC and QoS<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

</div>

</div>

</div>

</div>

<div bgcolor="white" lang="EN-US" class="gmail_msg">

<div class="m_261435386047953373WordSection1 gmail_msg">

<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif">FYI,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif">I’ve been working with a customer recently where we have utilised both the SIP Profile on CUCM to specify port ranges for voice /video

 and AD Group Policy to mark the traffic. <u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif">There are a few caveats to getting this working. It requires both a Windows registry value turned on, and some settings in the Windows

 QoS policy.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif">They had a mix of different switches. They configured the switches to “Trust DSCP”.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Hope this helps.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><br class="gmail_msg">

Cheers<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Dana<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-size:11.0pt; font-family:"Calibri",sans-serif"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<div class="gmail_msg" style="border:none; border-top:solid #b5c4df 1.0pt; padding:3.0pt 0in 0in 0in">

<p class="MsoNormal gmail_msg"><b class="gmail_msg"><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif; color:black">From:

</span></b><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif; color:black">cisco-voip <</span><a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif">cisco-voip-bounces@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif; color:black">>

 on behalf of Tom Sparks <</span><a href="mailto:tsparks@taosconsulting.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif">tsparks@taosconsulting.com</span></a><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif; color:black">><br class="gmail_msg">

<b class="gmail_msg">Date: </b>Thursday, 5 January 2017 at 11:31 am<br class="gmail_msg">

<b class="gmail_msg">To: </b>"</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif; color:black">"

 <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg" style="font-family:"Calibri",sans-serif; color:black">><br class="gmail_msg">

<b class="gmail_msg">Subject: </b>Re: [cisco-voip] Jabber/CIPC and QoS<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

</div>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

</div>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg">I believe that medianet plugin was discontinued by Cisco.   But if anyone gets it working, please let me know.  

<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

</div>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg">Here's a seemingly good blog on the whole topic also  <u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

</div>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

</div>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><a href="http://cp.mcafee.com/d/avndzhJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJ4SYqejt-KyUyOCUMqekjtPpesRG9pAEeNSAUJSCT7PZwxNyIk5E_iDbUDt5_bFVstwzF0xYiWau6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrijV4" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://infrastructureland.wordpress.com/2015/02/07/jabber-12/</span></a><span lang="EN-GB" class="gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg"><br clear="all" class="gmail_msg">

<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<div class="gmail_msg">

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg">Tom Sparks <u class="gmail_msg">

</u><u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg">Taos Consulting 

<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg">Sr. Voice | Video Engineer<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

</div>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><a href="mailto:tsparks@taosconsulting.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">tsparks@taosconsulting.com</span></a><span lang="EN-GB" class="gmail_msg"><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

</div>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span class="m_261435386047953373gc-cs-link gmail_msg"><span lang="EN-GB" class="gmail_msg"><a href="tel:(415)%20515-2391" value="+14155152391" class="gmail_msg" target="_blank">+1 415.515.2391</a></span></span><span lang="EN-GB" class="gmail_msg"><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

</div>

</div>

</div>

</div>

</div>

</div>

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>

<div class="gmail_msg">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg">On Wed, Jan 4, 2017 at 9:00 AM, <</span><a href="mailto:cisco-voip-request@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-request@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">>

 wrote:<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>

<blockquote class="gmail_msg" style="border:none; border-left:solid #cccccc 1.0pt; padding:0in 0in 0in 6.0pt; margin-left:4.8pt; margin-top:5.0pt; margin-right:0in; margin-bottom:5.0pt">

<p class="MsoNormal gmail_msg"><span lang="EN-GB" class="gmail_msg">Send cisco-voip mailing list submissions to<br class="gmail_msg">

        </span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

<br class="gmail_msg">

To subscribe or unsubscribe via the World Wide Web, visit<br class="gmail_msg">

        </span><a href="http://cp.mcafee.com/d/k-Kr4zqb3P5QQT67PtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqpJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdFYMc" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

or, via email, send a message with subject or body 'help' to<br class="gmail_msg">

        </span><a href="mailto:cisco-voip-request@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-request@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

<br class="gmail_msg">

You can reach the person managing the list at<br class="gmail_msg">

        </span><a href="mailto:cisco-voip-owner@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-owner@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

<br class="gmail_msg">

When replying, please edit your Subject line so it is more specific<br class="gmail_msg">

than "Re: Contents of cisco-voip digest..."<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Today's Topics:<br class="gmail_msg">

<br class="gmail_msg">

   1. Re: CUCM Patch Insight (NateCCIE)<br class="gmail_msg">

   2. Jabber/CIPC and QoS (Ben Amick)<br class="gmail_msg">

   3. Re: Jabber/CIPC and QoS (Lelio Fulgenzi)<br class="gmail_msg">

   4. Re: Jabber/CIPC and QoS (Ben Amick)<br class="gmail_msg">

   5. Re: Jabber/CIPC and QoS (Hodgeman, Samuel)<br class="gmail_msg">

   6. Re: Jabber/CIPC and QoS (NateCCIE)<br class="gmail_msg">

   7. Re: Jabber/CIPC and QoS (Ryan Huff)<br class="gmail_msg">

   8. LiveData enhancements in UCCX 11.0 and 11.5<br class="gmail_msg">

      (Abhiram Kramadhati (akramadh))<br class="gmail_msg">

   9. Re: Jabber/CIPC and QoS (Ben Amick)<br class="gmail_msg">

  10. Re: Jabber/CIPC and QoS (Ryan Huff)<br class="gmail_msg">

  11. Re: Jabber/CIPC and QoS (Ben Amick)<br class="gmail_msg">

  12. Re: Jabber/CIPC and QoS (Ryan Huff)<br class="gmail_msg">

  13. Re: Jabber/CIPC and QoS (Evgeny Izetov)<br class="gmail_msg">

  14. 7921g-w-k9 -> 7921g-a-k9 (Tim Warnock)<br class="gmail_msg">

  15. Re: Jabber/CIPC and QoS (Ben Amick)<br class="gmail_msg">

  16. Re: Jabber/CIPC and QoS (Lelio Fulgenzi)<br class="gmail_msg">

  17. Re: Jabber/CIPC and QoS (Ryan Huff)<br class="gmail_msg">

  18. Re: 7921g-w-k9 -> 7921g-a-k9 (Ben Amick)<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

----------------------------------------------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 1<br class="gmail_msg">

Date: Tue, 3 Jan 2017 10:33:39 -0700<br class="gmail_msg">

From: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: "'Jeffrey McHugh'" <</span><a href="mailto:jmchugh@fidelus.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">jmchugh@fidelus.com</span></a><span lang="EN-GB" class="gmail_msg">>, "'Tim Franklin'"<br class="gmail_msg">

        <</span><a href="mailto:tim@tripplehelix.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">tim@tripplehelix.net</span></a><span lang="EN-GB" class="gmail_msg">>, <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] CUCM Patch Insight<br class="gmail_msg">

Message-ID: <062901d265e7$8652f4c0$92f8de40$@</span><a href="http://cp.mcafee.com/d/2DRPoQcCQm7CbFFKcfCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CSjrNEVdTWWbybarz1EVhdTdw0O8DOVKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6UKdGDJ2D" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">gmail.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="utf-8"<br class="gmail_msg">

<br class="gmail_msg">

I would wait for SU2 at this point.  It will be soon.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

From: cisco-voip [mailto:</span><a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-bounces@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">] On Behalf Of Jeffrey

 McHugh<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 8:53 AM<br class="gmail_msg">

To: Tim Franklin <</span><a href="mailto:tim@tripplehelix.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">tim@tripplehelix.net</span></a><span lang="EN-GB" class="gmail_msg">>;

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

Subject: Re: [cisco-voip] CUCM Patch Insight<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Just did an SU1 upgrade, no issues reported but look into bug CSCux90747 depending on your esxi versions<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

I would expect SU2 soon as its named in the Expressway 8.9 release notes for some MRA feature preview<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

From: cisco-voip [mailto:</span><a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-bounces@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">] On Behalf Of Tim Franklin<br class="gmail_msg">

Sent: Tuesday, January 3, 2017 10:44 AM<br class="gmail_msg">

To: </span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"> <mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: [cisco-voip] CUCM Patch Insight<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Just curious if anyone on this list has any feedback as to the stability of CUCM 11.5(1)SU1. I'm planning my upgrades out and I'm a bit leery to deploy it given that it's been out since November. While that speaks to no large defects to cause a deferral notice

 I'm also wondering if another SU is on the horizon?<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Thanks<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Jeffrey McHugh | Sr. Collaboration Consulting Engineer | VCP-DCV, CCNP Collaboration<br class="gmail_msg">

<br class="gmail_msg">

 <</span><a href="http://cp.mcafee.com/d/avndygQcz9J5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJwSYqejt-KyUyOCUMqekjtPo09Si7DJQVv3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdUnpJeONP" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.fidelus.com/</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

Fidelus Technologies, LLC<br class="gmail_msg">

Named  <</span><a href="http://cp.mcafee.com/d/FZsS86Qm7CbFFKcfCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CTPrNEVdTWWbybarz1EVhdTdw0Dp8uuTjBYtAxVXt2Y_Ijxk-F6nQbMRnQ2V3WjbJMAXbQ2WWHs9mSsGMEnmzkP93UBVgbP9-nrFK6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrYUwulxMg" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.fidelus.com/fidelus-technologies-named-best-unified-communications-provider-in-the-usa/</span></a><span lang="EN-GB" class="gmail_msg">>

 Best UC Provider in the USA<br class="gmail_msg">

<br class="gmail_msg">

240 West 35th Street, 6th Floor, New York, NY 10001<br class="gmail_msg">

<br class="gmail_msg">

</span><a href="tel:%2B1-212-616-7801" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">+1-212-616-7801</span></a><span lang="EN-GB" class="gmail_msg"> office |

</span><a href="tel:%2B1-212-616-7850" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">+1-212-616-7850</span></a><span lang="EN-GB" class="gmail_msg"> fax |  <</span><a href="http://cp.mcafee.com/d/2DRPoQd3hJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJMSYqejt-KyUyOCUMqekjtPo09Si7DJQVv3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdzS9S" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.fidelus.com/</span></a><span lang="EN-GB" class="gmail_msg">>

</span><a href="http://cp.mcafee.com/d/2DRPow76Qm7CbFFKcfCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CNNJUQsCXZt5N5BdNwQsECXCM0jIAffrFOVKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6PNUF0vqu" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">www.fidelus.com</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

<br class="gmail_msg">

 <</span><a href="http://cp.mcafee.com/d/2DRPow739J5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJUSYqejt-KyUyOCUMqekjtPo08-k2LEixO-bHr0JzIAffrEnDZysaDR8O-CbhGwTqt3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdFG6u" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.linkedin.com/company/fidelus-technologies/products</span></a><span lang="EN-GB" class="gmail_msg">> 

 <</span><a href="http://cp.mcafee.com/d/FZsScyhJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FIQsCTzhOrLRQn4mkT63hOyrKr01jciDfUYLwL93PSW1ci4ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdJHdfWBYi" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.twitter.com/FidelusUCC</span></a><span lang="EN-GB" class="gmail_msg">> 

 <</span><a href="http://cp.mcafee.com/d/1jWVIq6xAe6jqb3P5QQT67PtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqdPrNEVdTWWbybarz1EVhdTdw0DtJV2JiLbUbOgYZKwj4x8TqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3vxTfwBrD" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.facebook.com/FidelusUCC</span></a><span lang="EN-GB" class="gmail_msg">> 

 <</span><a href="http://cp.mcafee.com/d/2DRPowrhouoKCCUM-rKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrp7cKc3DD-LPbZT7TxTnKnjjosVYQsLThhLR4kRHFGTusVkffGhBrwqrhhdL6zATvHEK8IFKc6zB4TsS02blrCSg_BY5V8uuTg4NSk9g8CXiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUr351jzPT" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.youtube.com/FidelusTraining</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/1jWVIe6x8i6jqb3P5QQT67PtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqapJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3smAJYhfbiFqFsPmiSreuS9G_2tcjKyeKztD20XXueLrdDfr4RvxcLuZQu1NKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6PREboVEC" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

A non-text attachment was scrubbed...<br class="gmail_msg">

Name: image001.png<br class="gmail_msg">

Type: image/png<br class="gmail_msg">

Size: 1989 bytes<br class="gmail_msg">

Desc: not available<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/FZsS82hJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJ5ASYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKPx0tZL7nJCPDJyqLMCnLuX_bg8CXiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrJ5z6" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0005.png</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

A non-text attachment was scrubbed...<br class="gmail_msg">

Name: image002.png<br class="gmail_msg">

Type: image/png<br class="gmail_msg">

Size: 1500 bytes<br class="gmail_msg">

Desc: not available<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/k-Kr4x0e3xASyMYNtddNxYTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSyMrud79K_nhshpjsod7a9KVIDeqR4INpKNnwqj-f0T5Fbv4jOQGmGncRAJCPDJyqLMDj4XEzHETpMwe-TzHSPpPSNdnUjbTLtPBE4jtFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdJPaTf-pN" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0006.png</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

A non-text attachment was scrubbed...<br class="gmail_msg">

Name: image003.png<br class="gmail_msg">

Type: image/png<br class="gmail_msg">

Size: 1526 bytes<br class="gmail_msg">

Desc: not available<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/avndy1J5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJ5YSYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKPx0tZL7nJCPDJyqLMCnLuUXBE4jtFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdHfqj0Jdb" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0007.png</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

A non-text attachment was scrubbed...<br class="gmail_msg">

Name: image004.png<br class="gmail_msg">

Type: image/png<br class="gmail_msg">

Size: 1450 bytes<br class="gmail_msg">

Desc: not available<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/5fHCNAqdEIfcnjjsovdTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndIzCn61PP_nVB-XzXMXHTbFFIes-qenXEETWyaqRQRrLesG7DR8OJMddEK6TzhOrLRQn4mkT63hOyrKr9PCJhbcmrIlU6A_zMdNqiTN4YJaBGBPdpbpIVXoCHY9QNeW8WWdSs83LJUWZISsZIjl-4OZXTuVq14TqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3sYDBnprqKTZu" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0008.png</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

A non-text attachment was scrubbed...<br class="gmail_msg">

Name: image005.png<br class="gmail_msg">

Type: image/png<br class="gmail_msg">

Size: 1632 bytes<br class="gmail_msg">

Desc: not available<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/FZsSd6Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQhNJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3smAJYhfbiFqFsPmiSreuS9G_2tcjKyeKztD20XXueLrdDfr4RvxcLuZPhPOQ29KQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6UmZUv97LE4AQ" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0009.png</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 2<br class="gmail_msg">

Date: Tue, 3 Jan 2017 21:25:20 +0000<br class="gmail_msg">

From: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:820C24BFE55F434C97807C60D4647ACE0F9D3DBB@E2k10-MB-HT1.humanarc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">820C24BFE55F434C97807C60D4647ACE0F9D3DBB@E2k10-MB-HT1.humanarc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="us-ascii"<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/FZsS92gQ96Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQnzrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6Xec86zDn6k7ISsZIjl-4OZXThU76XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrhqni1KHj" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/4d9a63d8/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 3<br class="gmail_msg">

Date: Tue, 3 Jan 2017 21:35:41 +0000<br class="gmail_msg">

From: Lelio Fulgenzi <</span><a href="mailto:lelio@uoguelph.ca" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">lelio@uoguelph.ca</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>, Cisco VoIP Group<br class="gmail_msg">

        <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:YTOPR01MB0251F94A8E59508021DD7D21AC6E0@YTOPR01MB0251.CANPRD01.PROD.OUTLOOK.COM" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">YTOPR01MB0251F94A8E59508021DD7D21AC6E0@YTOPR01MB0251.CANPRD01.PROD.OUTLOOK.COM</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

Content-Type: text/plain; charset="iso-8859-1"<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

good question Ben. i look forward to reading this thread.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

i've been meaning to read up on mediaNet, and it seems it's more required than not, especially for QoS.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

are you suggesting (with option 3) that there is software you can install on desktops? what about mobile devices?<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

QoS, both wired and wireless, will definitely be an interesting challenge.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

---<br class="gmail_msg">

Lelio Fulgenzi, B.A.<br class="gmail_msg">

Senior Analyst, Network Infrastructure<br class="gmail_msg">

Computing and Communications Services (CCS)<br class="gmail_msg">

University of Guelph<br class="gmail_msg">

<br class="gmail_msg">

</span><a href="tel:519-824-4120%20Ext%2056354" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">519-824-4120 Ext 56354</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

</span><a href="mailto:lelio@uoguelph.ca" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">lelio@uoguelph.ca</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/avndy0s73gArhouoKCCUMUrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrp7cKc3DD-LPbZT7TxTnKnjjosVYQsLThhLR4kRHFGTusVkffGhBrwqrhd79JUQsCXZt5N5BdNwQsECXCM0jtibvDH4-JKmJgTqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3rccsL59Vmz-x" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">www.uoguelph.ca/ccs</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

Room 037, Animal Science and Nutrition Building<br class="gmail_msg">

Guelph, Ontario, N1G 2W1<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

________________________________<br class="gmail_msg">

From: cisco-voip <</span><a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-bounces@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">> on behalf of Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Sent: Tuesday, January 3, 2017 4:25 PM<br class="gmail_msg">

To: Cisco VoIP Group<br class="gmail_msg">

Subject: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/1jWVIq4zqb3P5QQT673tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqtPrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6XenRBxB5-SreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdKt1CZLGM" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/0a34315c/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 4<br class="gmail_msg">

Date: Tue, 3 Jan 2017 22:02:42 +0000<br class="gmail_msg">

From: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Lelio Fulgenzi <</span><a href="mailto:lelio@uoguelph.ca" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">lelio@uoguelph.ca</span></a><span lang="EN-GB" class="gmail_msg">>, Cisco VoIP Group<br class="gmail_msg">

        <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:820C24BFE55F434C97807C60D4647ACE0F9D3E0F@E2k10-MB-HT1.humanarc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">820C24BFE55F434C97807C60D4647ACE0F9D3E0F@E2k10-MB-HT1.humanarc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="us-ascii"<br class="gmail_msg">

<br class="gmail_msg">

>From what I understand, it's not so much as "software" as it is a plugin for jabber that enables Jabber to send the medianet signaling. I don't believe it's a function of iOS/android Jabber though, but I could be mistaken<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

From: Lelio Fulgenzi [mailto:</span><a href="mailto:lelio@uoguelph.ca" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">lelio@uoguelph.ca</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 4:36 PM<br class="gmail_msg">

To: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>; Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

good question Ben. i look forward to reading this thread.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

i've been meaning to read up on mediaNet, and it seems it's more required than not, especially for QoS.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

are you suggesting (with option 3) that there is software you can install on desktops? what about mobile devices?<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

QoS, both wired and wireless, will definitely be an interesting challenge.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

---<br class="gmail_msg">

Lelio Fulgenzi, B.A.<br class="gmail_msg">

Senior Analyst, Network Infrastructure<br class="gmail_msg">

Computing and Communications Services (CCS)<br class="gmail_msg">

University of Guelph<br class="gmail_msg">

<br class="gmail_msg">

</span><a href="tel:519-824-4120%20Ext%2056354" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">519-824-4120 Ext 56354</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

</span><a href="mailto:lelio@uoguelph.ca" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">lelio@uoguelph.ca</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:lelio@uoguelph.ca" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">lelio@uoguelph.ca</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/2DRPoQ91MwrhouoKCCUMUrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrp7cKc3DD-LPbZT7TxTnKnjjosVYQsLThhLR4kRHFGTusVkffGhBrwqrjhdL6zATvHEK8IFKc6zB4TsS02rGhrYZoDRJORG6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrwtT4" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">www.uoguelph.ca/ccs</span></a><span lang="EN-GB" class="gmail_msg"><</span><a href="http://cp.mcafee.com/d/1jWVIpdEIfcnjjsosdTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndIzCn61PP_nVB-XzXMXHTbFFIes-qenXEETWyaqRQRrLesG7DR8OJMddFFCTzhOrLRQn4mkT63hOyrKr01dR8J-uIjWSVqR3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdURoXVnvH" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.uoguelph.ca/ccs</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Room 037, Animal Science and Nutrition Building<br class="gmail_msg">

Guelph, Ontario, N1G 2W1<br class="gmail_msg">

<br class="gmail_msg">

________________________________<br class="gmail_msg">

From: cisco-voip <</span><a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-bounces@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-bounces@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">>>

 on behalf of Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Sent: Tuesday, January 3, 2017 4:25 PM<br class="gmail_msg">

To: Cisco VoIP Group<br class="gmail_msg">

Subject: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/FZsS72hJ5xVyWqrz3xKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJdASYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKPxEVvd7a91OO6reuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdLoauYdUu" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/9591b6cd/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 5<br class="gmail_msg">

Date: Tue, 3 Jan 2017 22:13:15 +0000<br class="gmail_msg">

From: "Hodgeman, Samuel" <</span><a href="mailto:shodgeman@xo.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">shodgeman@xo.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>, Cisco VoIP Group<br class="gmail_msg">

        <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:94004f6f0f8646e7a51539636329908b@TXPLANEXCH101.corp.inthosts.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">94004f6f0f8646e7a51539636329908b@TXPLANEXCH101.corp.inthosts.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="us-ascii"<br class="gmail_msg">

<br class="gmail_msg">

For option 1, using Windows... this can be implemented with Group Policies, taking it out of the hands of end users, and can be associated with specific application executable and/or specific IP address source/destination.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

-          Sam H<br class="gmail_msg">

<br class="gmail_msg">

From: cisco-voip [mailto:</span><a href="mailto:cisco-voip-bounces@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip-bounces@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">] On Behalf Of Ben Amick<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 3:25 PM<br class="gmail_msg">

To: Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/2DRPoA92gQ76Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQS3rNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6Xec-We79CzCSreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdKKKK" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/3ef7729c/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 6<br class="gmail_msg">

Date: Tue, 3 Jan 2017 17:53:14 -0700<br class="gmail_msg">

From: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID: <</span><a href="mailto:05C8F1E2-B3DA-435C-BAB4-3C8278A0A726@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">05C8F1E2-B3DA-435C-BAB4-3C8278A0A726@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="utf-8"<br class="gmail_msg">

<br class="gmail_msg">

Or take the most approach of do nothing.<br class="gmail_msg">

<br class="gmail_msg">

My personal favorite is to use codecs where QoS matters less, like iLBC, OPUS, etc.<br class="gmail_msg">

<br class="gmail_msg">

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 class="gmail_msg">

<br class="gmail_msg">

Sent from my iPhone<br class="gmail_msg">

<br class="gmail_msg">

> On Jan 3, 2017, at 2:25 PM, Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">> wrote:<br class="gmail_msg">

><br class="gmail_msg">

> 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.<br class="gmail_msg">

><br class="gmail_msg">

> 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.<br class="gmail_msg">

> 1.      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.<br class="gmail_msg">

> 2.      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<br class="gmail_msg">

> 3.      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?)?<br class="gmail_msg">

><br class="gmail_msg">

> 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)?<br class="gmail_msg">

><br class="gmail_msg">

> Ben Amick<br class="gmail_msg">

> Telecom Analyst<br class="gmail_msg">

><br class="gmail_msg">

><br class="gmail_msg">

> 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<br class="gmail_msg">

> _______________________________________________<br class="gmail_msg">

> cisco-voip mailing list<br class="gmail_msg">

> </span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

> </span><a href="http://cp.mcafee.com/d/k-Kr41ASyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSC-rud79K_nhshpjsod7a9KVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oTqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3oNSWLrXW" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/k-Kr3zqb3P5QQT673tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqrxJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3smAJYhfbiFqFsPmiSreuS9G_2tcjKyeKztDbEqyWXXKreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdUbpOd1FA" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/0da1ffef/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 7<br class="gmail_msg">

Date: Wed, 4 Jan 2017 01:39:30 +0000<br class="gmail_msg">

From: Ryan Huff <</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>, Cisco VoIP Group<br class="gmail_msg">

        <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:BLUPR18MB0482767CF5DE727DDEE526FEC5610@BLUPR18MB0482.namprd18.prod.outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">BLUPR18MB0482767CF5DE727DDEE526FEC5610@BLUPR18MB0482.namprd18.prod.outlook.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

Content-Type: text/plain; charset="us-ascii"<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 7:53 PM, NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>>

 wrote:<br class="gmail_msg">

<br class="gmail_msg">

Or take the most approach of do nothing.<br class="gmail_msg">

<br class="gmail_msg">

My personal favorite is to use codecs where QoS matters less, like iLBC, OPUS, etc.<br class="gmail_msg">

<br class="gmail_msg">

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 class="gmail_msg">

<br class="gmail_msg">

Sent from my iPhone<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/k-Kr3xESyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSCedL6zATvHEK8IFKc6zB4TsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddIzArLf6MnWhEwdbtFkJkKpH9oQKCy02d84fzwA6xoid46Mgd403R63rbxK3usreMyXzZC" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/2DRPoA92gO96Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQTzrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUr1zcmvasqGTf" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/1jWVIi3xASyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSCqejrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6X6eCzAwqevd7ap3dDfr4RvxcLuZQu1NKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6YTzlm_uR" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/f9b9e92b/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 8<br class="gmail_msg">

Date: Wed, 4 Jan 2017 01:48:30 +0000<br class="gmail_msg">

From: "Abhiram Kramadhati (akramadh)" <</span><a href="mailto:akramadh@cisco.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">akramadh@cisco.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: [cisco-voip] LiveData enhancements in UCCX 11.0 and 11.5<br class="gmail_msg">

Message-ID: <</span><a href="mailto:5C88B902-AED4-4603-8707-A2BAE18A1181@cisco.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">5C88B902-AED4-4603-8707-A2BAE18A1181@cisco.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="utf-8"<br class="gmail_msg">

<br class="gmail_msg">

Hi all,<br class="gmail_msg">

<br class="gmail_msg">

Happy 2017!<br class="gmail_msg">

<br class="gmail_msg">

We just published a Field Notice about LiveData stabilization enhancements done in 11.0(1)SU1 and 11.5(1)ES1.<br class="gmail_msg">

</span><a href="http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64240.html" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64240.html</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

<br class="gmail_msg">

So, if you are on 11.0 or 11.5, our recommendation is to move to the above-mentioned releases. You could be running on 11.0/11.5 with no LD issues ? this is just a proactive measure.<br class="gmail_msg">

<br class="gmail_msg">

[</span><a href="http://www.cisco.com/c/dam/assets/email-signature-tool/logo_07.png?ct=1421802598153" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.cisco.com/c/dam/assets/email-signature-tool/logo_07.png?ct=1421802598153</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

<br class="gmail_msg">

Abhiram Kramadhati<br class="gmail_msg">

Technical Solutions Manager<br class="gmail_msg">

Customer Solutions Success team, CCBU<br class="gmail_msg">

</span><a href="mailto:akramadh@cisco.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">akramadh@cisco.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:akramadh@cisco.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">akramadh@cisco.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Phone: </span><a href="tel:%2B61%202%208446%206257" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">+61 2 8446 6257</span></a><span lang="EN-GB" class="gmail_msg"><br class="gmail_msg">

<br class="gmail_msg">

CCIE Collaboration  - 40065<br class="gmail_msg">

<br class="gmail_msg">

Cisco Systems Australia Pty Limited<br class="gmail_msg">

The Forum<br class="gmail_msg">

201 Pacific Highway<br class="gmail_msg">

2065<br class="gmail_msg">

St Leonards<br class="gmail_msg">

Australia<br class="gmail_msg">

Cisco.com<</span><a href="http://www.cisco.com/web/AU/" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.cisco.com/web/AU/</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

[</span><a href="http://www.cisco.com/assets/social_media_icons/linkedin-16x16.png" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.cisco.com/assets/social_media_icons/linkedin-16x16.png</span></a><span lang="EN-GB" class="gmail_msg">]<</span><a href="http://wwwin.cisco.com/marketing/corporate/brand/intelbrand/brandstrat/signature/Insert%20your%20LinkedIn%20link" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://wwwin.cisco.com/marketing/corporate/brand/intelbrand/brandstrat/signature/Insert%20your%20LinkedIn%20link</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

[</span><a href="http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif%5dThink" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think</span></a><span lang="EN-GB" class="gmail_msg">

 before you print.<br class="gmail_msg">

<br class="gmail_msg">

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient),

 please contact the sender by reply email and delete all copies of this message.<br class="gmail_msg">

Please click here<</span><a href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</span></a><span lang="EN-GB" class="gmail_msg">>

 for Company Registration Information.<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/5fHCN8e4wUSyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSPsSYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKNzF1zmkmncSsZIjl-4OZXThU76XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrS1LI" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/fb4a3136/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 9<br class="gmail_msg">

Date: Wed, 4 Jan 2017 02:15:06 +0000<br class="gmail_msg">

From: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Ryan Huff <</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">>, NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:820C24BFE55F434C97807C60D4647ACE0F9DE054@E2k10-MB-HT1.humanarc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">820C24BFE55F434C97807C60D4647ACE0F9DE054@E2k10-MB-HT1.humanarc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="us-ascii"<br class="gmail_msg">

<br class="gmail_msg">

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

 *cough*developers*cough* 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<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

From: Ryan Huff [mailto:</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 8:40 PM<br class="gmail_msg">

To: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>; Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 7:53 PM, NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>>

 wrote:<br class="gmail_msg">

Or take the most approach of do nothing.<br class="gmail_msg">

<br class="gmail_msg">

My personal favorite is to use codecs where QoS matters less, like iLBC, OPUS, etc.<br class="gmail_msg">

<br class="gmail_msg">

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 class="gmail_msg">

<br class="gmail_msg">

Sent from my iPhone<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/avndy0OcCQm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CSkjrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrnghujSVnQnp7" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><</span><a href="http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/1jWVIi41Ae6zqb3P5QQT673tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jrapJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdyMRDJKUO" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><</span><a href="http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/FZsScxMw91NJ5xVyWqrz3xKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJBASYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKNwVwxHXa3SreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdAi0c" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/74ba53d8/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 10<br class="gmail_msg">

Date: Wed, 4 Jan 2017 02:18:06 +0000<br class="gmail_msg">

From: Ryan Huff <</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>, Cisco VoIP Group<br class="gmail_msg">

        <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:BLUPR18MB04820158AE92067D655F5A57C5610@BLUPR18MB0482.namprd18.prod.outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">BLUPR18MB04820158AE92067D655F5A57C5610@BLUPR18MB0482.namprd18.prod.outlook.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

Content-Type: text/plain; charset="us-ascii"<br class="gmail_msg">

<br class="gmail_msg">

Ben,<br class="gmail_msg">

<br class="gmail_msg">

By flat network; I am to assume that there is no layer 2 partition between rtp/signaling and general data traffic?<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

<br class="gmail_msg">

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

 *cough*developers*cough* 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<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

From: Ryan Huff [mailto:</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 8:40 PM<br class="gmail_msg">

To: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Cc: Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>>; Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 7:53 PM, NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>>

 wrote:<br class="gmail_msg">

Or take the most approach of do nothing.<br class="gmail_msg">

<br class="gmail_msg">

My personal favorite is to use codecs where QoS matters less, like iLBC, OPUS, etc.<br class="gmail_msg">

<br class="gmail_msg">

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 class="gmail_msg">

<br class="gmail_msg">

Sent from my iPhone<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/2DRPoO96Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CSm3rNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrO7xxj0KX" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><</span><a href="http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/FZsS720QcCQm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CSnPrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrWVos" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><</span><a href="http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/2DRPoQd1MOrhouoKCCUMUrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrp7cKc3DD-LPbZT7TxTnKnjjosVYQsLThhLR4kRHFGTusVkffGhBrwqrpsdL6zATvHEK8IFKc6zB4TsSjDdqymoIToHMd9_7wryQBLy9VqlblbCqOmPpPSNdnUjFytQhRQrIoMVW6EA4sSsZIjl-4OZXThU76XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrwRCj" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/46eda1b1/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 11<br class="gmail_msg">

Date: Wed, 4 Jan 2017 02:30:35 +0000<br class="gmail_msg">

From: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Ryan Huff <</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>, Cisco VoIP Group<br class="gmail_msg">

        <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:820C24BFE55F434C97807C60D4647ACE0F9DE08E@E2k10-MB-HT1.humanarc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">820C24BFE55F434C97807C60D4647ACE0F9DE08E@E2k10-MB-HT1.humanarc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Content-Type: text/plain; charset="us-ascii"<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

From: Ryan Huff [mailto:</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 9:18 PM<br class="gmail_msg">

To: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>; Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

Ben,<br class="gmail_msg">

<br class="gmail_msg">

By flat network; I am to assume that there is no layer 2 partition between rtp/signaling and general data traffic?<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

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

 *cough*developers*cough* 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<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

From: Ryan Huff [mailto:</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 8:40 PM<br class="gmail_msg">

To: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Cc: Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>>; Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 7:53 PM, NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>>

 wrote:<br class="gmail_msg">

Or take the most approach of do nothing.<br class="gmail_msg">

<br class="gmail_msg">

My personal favorite is to use codecs where QoS matters less, like iLBC, OPUS, etc.<br class="gmail_msg">

<br class="gmail_msg">

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 class="gmail_msg">

<br class="gmail_msg">

Sent from my iPhone<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

1.      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.<br class="gmail_msg">

<br class="gmail_msg">

2.      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<br class="gmail_msg">

<br class="gmail_msg">

3.      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?)?<br class="gmail_msg">

<br class="gmail_msg">

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)?<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/k-Kr3x8pdEIfcnjjsosdTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndIzCn61PP_nVB-XzXMXHTbFFIes-qenXEETWyaqRQRrLesG7DR8OJMddIzzrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrLukq" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><</span><a href="http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

_______________________________________________<br class="gmail_msg">

cisco-voip mailing list<br class="gmail_msg">

</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

</span><a href="http://cp.mcafee.com/d/2DRPos96Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CSnzrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrc7P7ZXRwrp2x" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><span lang="EN-GB" class="gmail_msg"><</span><a href="http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

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<br class="gmail_msg">

-------------- next part --------------<br class="gmail_msg">

An HTML attachment was scrubbed...<br class="gmail_msg">

URL: <</span><a href="http://cp.mcafee.com/d/k-Kr41Ae6zqb3P5QQT673tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jr9EVdL6zATvHEK8IFKc6zB4TsSjDdqymoIToHMd9_7wryQBLy9VqlblbCqOmPpPSNdnUjFytQhRQrIo-UNHZZLCPDJyqLMCnLuWf0UTqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3ukEBEnnp" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/564a50a0/attachment-0001.html</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

------------------------------<br class="gmail_msg">

<br class="gmail_msg">

Message: 12<br class="gmail_msg">

Date: Wed, 4 Jan 2017 02:49:49 +0000<br class="gmail_msg">

From: Ryan Huff <</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

To: Ben Amick <</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Cc: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>, Cisco VoIP Group<br class="gmail_msg">

        <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

Message-ID:<br class="gmail_msg">

        <</span><a href="mailto:BLUPR18MB048225F237E9FCEFAF1C726FC5610@BLUPR18MB0482.namprd18.prod.outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">BLUPR18MB048225F237E9FCEFAF1C726FC5610@BLUPR18MB0482.namprd18.prod.outlook.com</span></a><span lang="EN-GB" class="gmail_msg">><br class="gmail_msg">

<br class="gmail_msg">

Content-Type: text/plain; charset="windows-1252"<br class="gmail_msg">

<br class="gmail_msg">

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).<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

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 class="gmail_msg">

<br class="gmail_msg">

-Ryan<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

<br class="gmail_msg">

Sent from my iPhone<br class="gmail_msg">

On Jan 3, 2017, at 9:30 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

From: Ryan Huff [mailto:</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 9:18 PM<br class="gmail_msg">

To: Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Cc: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>>;

 Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

Ben,<br class="gmail_msg">

<br class="gmail_msg">

By flat network; I am to assume that there is no layer 2 partition between rtp/signaling and general data traffic?<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>> wrote:<br class="gmail_msg">

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

 *cough*developers*cough* 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<br class="gmail_msg">

<br class="gmail_msg">

Ben Amick<br class="gmail_msg">

Telecom Analyst<br class="gmail_msg">

<br class="gmail_msg">

From: Ryan Huff [mailto:</span><a href="mailto:ryanhuff@outlook.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">ryanhuff@outlook.com</span></a><span lang="EN-GB" class="gmail_msg">]<br class="gmail_msg">

Sent: Tuesday, January 03, 2017 8:40 PM<br class="gmail_msg">

To: NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Cc: Ben Amick <bamick@HumanArc.com<mailto:</span><a href="mailto:bamick@HumanArc.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">bamick@HumanArc.com</span></a><span lang="EN-GB" class="gmail_msg">>>; Cisco VoIP Group <</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg"><mailto:</span><a href="mailto:cisco-voip@puck.nether.net" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">cisco-voip@puck.nether.net</span></a><span lang="EN-GB" class="gmail_msg">>><br class="gmail_msg">

Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br class="gmail_msg">

<br class="gmail_msg">

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.<br class="gmail_msg">

<br class="gmail_msg">

Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.<br class="gmail_msg">

<br class="gmail_msg">

On Jan 3, 2017, at 7:53 PM, NateCCIE <</span><a href="mailto:nateccie@gmail.com" class="gmail_msg" target="_blank"><span lang="EN-GB" class="gmail_msg">nateccie@gmail.com</span></a><span lang="EN-GB" class="gmail_msg"></span></p>

</blockquote>

</div>

</div>

</div>

</div>

</div>

</div>

</blockquote>

</div>

</div>

</div>

</div>

</body>

</html>