<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">The expected behavior, when the Detailed Call by Call CCDR report is run we should see two entries in the first column for the same session id with different sequence number.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Example : 1-10000001-0 / 1-10000001-1 (nodeid-sessionid-sequence no.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">1-10000001-0 ---This is for first leg to agent<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">1-10000001-1 ---This is for second leg to Post call survey RP after agent clicks END on desktop<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">There is one defect CSCvc01391 in this area where the call leg is not written intermittently. The same will be fixed in the upcoming ES/SU on 11.0/11.5. However, there is a patch available
with TAC that can be applied via root. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">So you could review this defect and see if it is relevant to the issue you are seeing.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Regards,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Abhiram Kramadhati<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">Technical Solutions Manager, CCBU<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:Calibri;color:black">CCIE Collaboration # 40065</span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Aaron Banks <amichaelbanks@hotmail.com><br>
<b>Date: </b>Friday, 6 January 2017 at 4:11 AM<br>
<b>To: </b>"cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net>, "claitoncampos@gmail.com" <claitoncampos@gmail.com><br>
<b>Subject: </b>Re: [cisco-voip] Cisco uccx post call survey show duplicate data<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="divtagdefaultwrapper">
<p><span style="font-family:Calibri;color:black">Claiton - I have a similar issue. I get duplicate session IDs (or even multiples) with my SQL query. A callers the IVR (one script), is answered by an agent in a specific queue and then is transferred to another
queue (another script) and answered by a different agent. I assume that it is because a new call leg is created within the same session. I don't know for sure but that is what I believe to be happening. I am interested to hear what others have to say.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:Calibri;color:black"><br>
Aaron<o:p></o:p></span></p>
<div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:Calibri;color:black">
<hr size="2" width="98%" align="center">
</span></div>
<div id="x_divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:Calibri;color:black">From:</span></b><span style="font-size:11.0pt;font-family:Calibri;color:black"> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of cisco-voip-request@puck.nether.net
<cisco-voip-request@puck.nether.net><br>
<b>Sent:</b> January 5, 2017 9:00 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> cisco-voip Digest, Vol 159, Issue 5</span><span style="font-family:Calibri;color:black">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:Calibri;color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri;color:black">Send cisco-voip mailing list submissions to<br>
cisco-voip@puck.nether.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" id="LPlnk708181">
https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></p>
<div style="margin-bottom:15.0pt;overflow:auto" id="LPBorder_GT_14836359846000.5559767726991514">
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="90%" style="width:90.0%;background:white;border-top:dotted #C8C8C8 1.0pt;border-left:none;border-bottom:dotted #C8C8C8 1.0pt;border-right:none">
<tbody>
<tr>
<td valign="top" style="border:none;padding:0cm 0cm 0cm 0cm">
<div id="LPTitle_14836359845980.7963632387804144">
<p class="MsoNormal" style="margin-top:15.0pt;mso-line-height-alt:15.75pt"><span style="font-size:16.0pt;font-family:"Segoe UI","serif";color:#0078D7"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank"><span style="text-decoration:none">cisco-voip
Info Page - puck.nether.net</span></a><o:p></o:p></span></p>
</div>
<div style="margin-top:7.5pt;margin-bottom:12.0pt" id="LPMetadata_14836359845990.4705773596454824">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:10.5pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">puck.nether.net<o:p></o:p></span></p>
</div>
<div id="LPDescription_14836359845990.03694212859258339">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:15.0pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">A list for people interested in using Cisco VoIP equipment in a variety of environments, including service provider,
enterprise and over the public internet.<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri;color:black"><br>
or, via email, send a message with subject or body 'help' to<br>
cisco-voip-request@puck.nether.net<br>
<br>
You can reach the person managing the list at<br>
cisco-voip-owner@puck.nether.net<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cisco-voip digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Cisco uccx post call survey show duplicate data (Claiton Campos)<br>
2. Re: Cisco CER Licensing? (Anthony Holloway)<br>
3. Re: 7921g-w-k9 -> 7921g-a-k9 (Schlotterer, Tommy)<br>
4. Re: Jabber/CIPC and QoS (Evgeny Izetov)<br>
5. Re: 7921g-w-k9 -> 7921g-a-k9 (Ben Amick)<br>
6. Re: Jabber/CIPC and QoS (Tom Sparks)<br>
7. User Address Book (David Zhars)<br>
8. Re: User Address Book (Sean E. Knight)<br>
9. Re: User Address Book (Brian Meade)<br>
10. Re: User Address Book (David Zhars)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 04 Jan 2017 17:46:47 +0000<br>
From: Claiton Campos <claitoncampos@gmail.com><br>
To: "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><br>
Subject: [cisco-voip] Cisco uccx post call survey show duplicate data<br>
Message-ID:<br>
<CAALrejiyAyFwRHSYLfQtHUVWEJwn5i7-vho7gvo37mmx83+YMA@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I have two scripts on my uccx environment, the first is the IVR application<br>
and the second script is the post call survey.<br>
The problem is when agent transfering the call for post call survey script,<br>
the custom report show me duplicated data like show below.<br>
[image: pasted1]<br>
On second script i used session variables to get information on first<br>
script like customer ID and phone number.<br>
Someone have any idea about this problem?<br>
<br>
Regards,<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/0fd3ed36/attachment-0001.html" id="LPlnk452479">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/0fd3ed36/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: pasted1<br>
Type: image/png<br>
Size: 13966 bytes<br>
Desc: not available<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/0fd3ed36/attachment-0001.png" id="LPlnk879810">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/0fd3ed36/attachment-0001.png</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 04 Jan 2017 19:33:40 +0000<br>
From: Anthony Holloway <avholloway+cisco-voip@gmail.com><br>
To: Brian Meade <bmeade90@vt.edu>, Travis Dennis<br>
<tdennis@datasourcepro.com><br>
Cc: Erick Bergquist <erickbee@gmail.com>, Ryan Huff<br>
<ryanhuff@outlook.com>, "cisco-voip@puck.nether.net"<br>
<cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] Cisco CER Licensing?<br>
Message-ID:<br>
<CACRCJOjFJG44=hKU1TV2OLJ0DQtAPyfx1jw8oEQzTnrB9ZyLvw@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Seriously? Default ERL? Everyone go back and check that you're using<br>
Standard Local Route Groups for the Default ERL routing.<br>
<br>
On Tue, Jan 3, 2017 at 7:47 AM Brian Meade <bmeade90@vt.edu> wrote:<br>
<br>
> It doesn't keep the calls from flowing but will send the calls out using<br>
> the Default ERL configuration.<br>
><br>
> You can also now choose which phones are licensed now which is nice.<br>
><br>
> On Sat, Dec 31, 2016 at 1:14 AM, Travis Dennis <tdennis@datasourcepro.com><br>
> wrote:<br>
><br>
> I recently upgraded a site to 10.x and they were out of compliance but CER<br>
> never stopped working. Just the warning banner in CER and in PLM. There<br>
> would be lawsuits a'plenty if 911 calls stopped flowing. Even if it is the<br>
> customer's fault for being out of compliance. No real way to say that a<br>
> particular phone should have been allowed to make a 911 call and this other<br>
> phone shouldn't<br>
><br>
><br>
><br>
><br>
> Regards,<br>
><br>
> Travis L. Dennis<br>
><br>
> Enterprise Solutions Architect<br>
><br>
> DataSource Technical Consulting<br>
><br>
> (770)490-3313 <(770)%20490-3313> Main<br>
><br>
> (925)380-8851 <(925)%20380-8851> Fax<br>
><br>
><br>
> <<a href="http://www.datasourcepro.com/" id="LPlnk969708">http://www.datasourcepro.com/</a>>
<o:p></o:p></span></p>
<div style="margin-bottom:15.0pt;overflow:auto" id="LPBorder_GT_14836360431130.11697125024162547">
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="90%" style="width:90.0%;background:white;border-top:dotted #C8C8C8 1.0pt;border-left:none;border-bottom:dotted #C8C8C8 1.0pt;border-right:none">
<tbody>
<tr>
<td width="250" valign="top" style="width:187.5pt;border:none;padding:15.0pt 15.0pt 15.0pt .75pt">
<div style="margin-top:5.0pt;margin-bottom:5.0pt;display:table" id="LPImageContainer_14836360431080.1493845057903853">
<p class="MsoNormal" style="margin-top:15.0pt;background:white"><a href="http://www.datasourcepro.com/" target="_blank"><span style="text-decoration:none"><img border="0" width="250" height="83" id="LPThumbnailImageID_14836360431090.1573647903739105" src="http://datasourcepro.com/images/flash_01.jpg"></span></a><o:p></o:p></p>
</div>
</td>
<td valign="top" style="border:none;padding:0cm 0cm 0cm 0cm;display:table-cell" id="TextCell_14836360431100.7919110782719939">
<div id="LPTitle_14836360431100.9080303936679907">
<p class="MsoNormal" style="margin-top:15.0pt;mso-line-height-alt:15.75pt"><span style="font-size:16.0pt;font-family:"Segoe UI","serif";color:#0078D7"><a href="http://www.datasourcepro.com/" target="_blank"><span style="text-decoration:none">DataSource IT Consulting
VOIP Managed Services Computer ...</span></a><o:p></o:p></span></p>
</div>
<div style="margin-top:7.5pt;margin-bottom:12.0pt" id="LPMetadata_14836360431110.6226078184515769">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:10.5pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">www.datasourcepro.com<o:p></o:p></span></p>
</div>
<div id="LPDescription_14836360431120.8540991977180206">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:15.0pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">Customer Service: At DataSource, all of our customers are able to reach customer service and technical support 24 hours
a day, 7 days a week including holidays.<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri;color:black"><br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
> *From:* cisco-voip [cisco-voip-bounces@puck.nether.net] on behalf of<br>
> Erick Bergquist [erickbee@gmail.com]<br>
> *Sent:* Saturday, December 31, 2016 12:04 AM<br>
> *To:* Anthony Holloway; Ryan Huff<br>
> *Cc:* cisco-voip@puck.nether.net<br>
> *Subject:* Re: [cisco-voip] Cisco CER Licensing?<br>
><br>
> I believe it only counts registered devices. I've seen it fluctuate by a<br>
> few hundred with organizations with numerous 792x wireless phones day to<br>
> day.<br>
><br>
> I haven't really looked for docs on this yet though.<br>
><br>
> Does CER enforce if it's tracking more phones then licensed? The docs<br>
> aren't really clear and I see it still functioning fine.<br>
><br>
><br>
> On Fri, Dec 30, 2016 at 4:56 PM Ryan Huff <ryanhuff@outlook.com<br>
> <<a href="http://redir.aspx?REF=ADFOb9emI5CqRDm1IK35l9CnSdLQh8GFGsSGjMKhk9um_Zi2QzHUCAFtYWlsdG86cnlhbmh1ZmZAb3V0bG9vay5jb20." id="LPlnk687210">http://redir.aspx?REF=ADFOb9emI5CqRDm1IK35l9CnSdLQh8GFGsSGjMKhk9um_Zi2QzHUCAFtYWlsdG86cnlhbmh1ZmZAb3V0bG9vay5jb20.</a>>><br>
> wrote:<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Anthony, out of curiosity did your situation involve CSF/TCT/BOT devices<br>
> and CER based device discovery?<br>
><br>
><br>
><br>
><br>
><br>
> Sent from my iPhone<br>
><br>
><br>
><br>
><br>
><br>
> On Dec 30, 2016, at 6:43 PM, Anthony Holloway <<br>
> avholloway+cisco-voip@gmail.com<br>
> <<a href="http://redir.aspx?REF=brLhXDP_42HMT8vmU1BIbFX1X21LWAI1GlV3w-tFnhum_Zi2QzHUCAFtYWlsdG86YXZob2xsb3dheStjaXNjby12b2lwQGdtYWlsLmNvbQ.." id="LPlnk595314">http://redir.aspx?REF=brLhXDP_42HMT8vmU1BIbFX1X21LWAI1GlV3w-tFnhum_Zi2QzHUCAFtYWlsdG86YXZob2xsb3dheStjaXNjby12b2lwQGdtYWlsLmNvbQ..</a>>><br>
> wrote:<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> I'm going to love seeing this conversation play out. I just had a weird<br>
> situation where we were over on licensing in CER, we bought more, uploaded<br>
> them to PLM, and then CER was showing an even higher number of licenses<br>
> required. What a bait<br>
><br>
> and switch liar.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Fri, Dec 30, 2016 at 5:05 PM Scott Voll <svoll.voip@gmail.com<br>
> <<a href="http://redir.aspx?REF=UHagl1lji7WUM9LbhPiXCodb2ZNLGcKmzHcd_ZsaPTem_Zi2QzHUCAFtYWlsdG86c3ZvbGwudm9pcEBnbWFpbC5jb20." id="LPlnk929550">http://redir.aspx?REF=UHagl1lji7WUM9LbhPiXCodb2ZNLGcKmzHcd_ZsaPTem_Zi2QzHUCAFtYWlsdG86c3ZvbGwudm9pcEBnbWFpbC5jb20.</a>>><br>
> wrote:<br>
><br>
><br>
><br>
><br>
><br>
><br>
> How does PLM / CER figure out phones that need to be licensed?<br>
><br>
><br>
><br>
><br>
><br>
><br>
> I have 1883 total phones configured.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> almost 500 are IPC clients<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> PLM says I need 1425 licenses.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> I have about 100 phones not registered to CM.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> I can't figure out how PLM comes up with the numbers it does. Can someone<br>
> give me a crash course?<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> TIA<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Scott<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
><br>
><br>
> cisco-voip mailing list<br>
><br>
><br>
> cisco-voip@puck.nether.net<br>
> <<a href="http://redir.aspx?REF=biwTSkHiNFHCEU2y0xToE6DOUzZ6WlPXpch4FSLON82m_Zi2QzHUCAFtYWlsdG86Y2lzY28tdm9pcEBwdWNrLm5ldGhlci5uZXQ." id="LPlnk228109">http://redir.aspx?REF=biwTSkHiNFHCEU2y0xToE6DOUzZ6WlPXpch4FSLON82m_Zi2QzHUCAFtYWlsdG86Y2lzY28tdm9pcEBwdWNrLm5ldGhlci5uZXQ.</a>><br>
><br>
><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" id="LPlnk798249">
https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></p>
<div style="margin-bottom:15.0pt;overflow:auto" id="LPBorder_GT_14836361655860.49252398163833055">
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="90%" style="width:90.0%;background:white;border-top:dotted #C8C8C8 1.0pt;border-left:none;border-bottom:dotted #C8C8C8 1.0pt;border-right:none">
<tbody>
<tr>
<td valign="top" style="border:none;padding:0cm 0cm 0cm 0cm">
<div id="LPTitle_14836361655840.42243400483565985">
<p class="MsoNormal" style="margin-top:15.0pt;mso-line-height-alt:15.75pt"><span style="font-size:16.0pt;font-family:"Segoe UI","serif";color:#0078D7"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank"><span style="text-decoration:none">cisco-voip
Info Page - puck.nether.net</span></a><o:p></o:p></span></p>
</div>
<div style="margin-top:7.5pt;margin-bottom:12.0pt" id="LPMetadata_14836361655850.1686103262661508">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:10.5pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">puck.nether.net<o:p></o:p></span></p>
</div>
<div id="LPDescription_14836361655850.6028421826394865">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:15.0pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">A list for people interested in using Cisco VoIP equipment in a variety of environments, including service provider,
enterprise and over the public internet.<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri;color:black"><br>
> <<a href="http://redir.aspx?REF=Q0xvE6QhrtwdbhdSU4yCw00_M5B1gple7JwhRqQn2Tim_Zi2QzHUCAFodHRwczovL3B1Y2submV0aGVyLm5ldC9tYWlsbWFuL2xpc3RpbmZvL2Npc2NvLXZvaXA." id="LPlnk4266">http://redir.aspx?REF=Q0xvE6QhrtwdbhdSU4yCw00_M5B1gple7JwhRqQn2Tim_Zi2QzHUCAFodHRwczovL3B1Y2submV0aGVyLm5ldC9tYWlsbWFuL2xpc3RpbmZvL2Npc2NvLXZvaXA.</a>><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
><br>
><br>
> cisco-voip mailing list<br>
><br>
><br>
> cisco-voip@puck.nether.net<br>
> <<a href="http://redir.aspx?REF=biwTSkHiNFHCEU2y0xToE6DOUzZ6WlPXpch4FSLON82m_Zi2QzHUCAFtYWlsdG86Y2lzY28tdm9pcEBwdWNrLm5ldGhlci5uZXQ." id="LPlnk314991">http://redir.aspx?REF=biwTSkHiNFHCEU2y0xToE6DOUzZ6WlPXpch4FSLON82m_Zi2QzHUCAFtYWlsdG86Y2lzY28tdm9pcEBwdWNrLm5ldGhlci5uZXQ.</a>><br>
><br>
><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" id="LPlnk534794">
https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></p>
<div style="margin-bottom:15.0pt;overflow:auto" id="LPBorder_GT_14836362258480.16178811399650816">
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="90%" style="width:90.0%;background:white;border-top:dotted #C8C8C8 1.0pt;border-left:none;border-bottom:dotted #C8C8C8 1.0pt;border-right:none">
<tbody>
<tr>
<td valign="top" style="border:none;padding:0cm 0cm 0cm 0cm">
<div id="LPTitle_14836362258460.0672592740341792">
<p class="MsoNormal" style="margin-top:15.0pt;mso-line-height-alt:15.75pt"><span style="font-size:16.0pt;font-family:"Segoe UI","serif";color:#0078D7"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank"><span style="text-decoration:none">cisco-voip
Info Page - puck.nether.net</span></a><o:p></o:p></span></p>
</div>
<div style="margin-top:7.5pt;margin-bottom:12.0pt" id="LPMetadata_14836362258470.10956605117853979">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:10.5pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">puck.nether.net<o:p></o:p></span></p>
</div>
<div id="LPDescription_14836362258470.9886213847040062">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:15.0pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">A list for people interested in using Cisco VoIP equipment in a variety of environments, including service provider,
enterprise and over the public internet.<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri;color:black"><br>
> <<a href="http://redir.aspx?REF=Q0xvE6QhrtwdbhdSU4yCw00_M5B1gple7JwhRqQn2Tim_Zi2QzHUCAFodHRwczovL3B1Y2submV0aGVyLm5ldC9tYWlsbWFuL2xpc3RpbmZvL2Npc2NvLXZvaXA." id="LPlnk124072">http://redir.aspx?REF=Q0xvE6QhrtwdbhdSU4yCw00_M5B1gple7JwhRqQn2Tim_Zi2QzHUCAFodHRwczovL3B1Y2submV0aGVyLm5ldC9tYWlsbWFuL2xpc3RpbmZvL2Npc2NvLXZvaXA.</a>><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
><br>
> cisco-voip mailing list<br>
><br>
> cisco-voip@puck.nether.net<br>
> <<a href="http://redir.aspx?REF=biwTSkHiNFHCEU2y0xToE6DOUzZ6WlPXpch4FSLON82m_Zi2QzHUCAFtYWlsdG86Y2lzY28tdm9pcEBwdWNrLm5ldGhlci5uZXQ." id="LPlnk551264">http://redir.aspx?REF=biwTSkHiNFHCEU2y0xToE6DOUzZ6WlPXpch4FSLON82m_Zi2QzHUCAFtYWlsdG86Y2lzY28tdm9pcEBwdWNrLm5ldGhlci5uZXQ.</a>><br>
><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" id="LPlnk607031">
https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></p>
<div style="margin-bottom:15.0pt;overflow:auto" id="LPBorder_GT_14836362865290.8624301638134493">
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="90%" style="width:90.0%;background:white;border-top:dotted #C8C8C8 1.0pt;border-left:none;border-bottom:dotted #C8C8C8 1.0pt;border-right:none">
<tbody>
<tr>
<td valign="top" style="border:none;padding:0cm 0cm 0cm 0cm">
<div id="LPTitle_14836362865270.9492603577726515">
<p class="MsoNormal" style="margin-top:15.0pt;mso-line-height-alt:15.75pt"><span style="font-size:16.0pt;font-family:"Segoe UI","serif";color:#0078D7"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank"><span style="text-decoration:none">cisco-voip
Info Page - puck.nether.net</span></a><o:p></o:p></span></p>
</div>
<div style="margin-top:7.5pt;margin-bottom:12.0pt" id="LPMetadata_14836362865280.5238305357780328">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:10.5pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">puck.nether.net<o:p></o:p></span></p>
</div>
<div id="LPDescription_14836362865280.42059384234743813">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:15.0pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">A list for people interested in using Cisco VoIP equipment in a variety of environments, including service provider,
enterprise and over the public internet.<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri;color:black"><br>
> <<a href="http://redir.aspx?REF=Q0xvE6QhrtwdbhdSU4yCw00_M5B1gple7JwhRqQn2Tim_Zi2QzHUCAFodHRwczovL3B1Y2submV0aGVyLm5ldC9tYWlsbWFuL2xpc3RpbmZvL2Npc2NvLXZvaXA." id="LPlnk539438">http://redir.aspx?REF=Q0xvE6QhrtwdbhdSU4yCw00_M5B1gple7JwhRqQn2Tim_Zi2QzHUCAFodHRwczovL3B1Y2submV0aGVyLm5ldC9tYWlsbWFuL2xpc3RpbmZvL2Npc2NvLXZvaXA.</a>><br>
><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" id="LPlnk181503">
https://puck.nether.net/mailman/listinfo/cisco-voip</a> <o:p></o:p></span></p>
<div style="margin-bottom:15.0pt;overflow:auto" id="LPBorder_GT_14836362865070.6441870884236316">
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="90%" style="width:90.0%;background:white;border-top:dotted #C8C8C8 1.0pt;border-left:none;border-bottom:dotted #C8C8C8 1.0pt;border-right:none">
<tbody>
<tr>
<td valign="top" style="border:none;padding:0cm 0cm 0cm 0cm">
<div id="LPTitle_14836362865040.5099385170447708">
<p class="MsoNormal" style="margin-top:15.0pt;mso-line-height-alt:15.75pt"><span style="font-size:16.0pt;font-family:"Segoe UI","serif";color:#0078D7"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank"><span style="text-decoration:none">cisco-voip
Info Page - puck.nether.net</span></a><o:p></o:p></span></p>
</div>
<div style="margin-top:7.5pt;margin-bottom:12.0pt" id="LPMetadata_14836362865050.1901854438114461">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:10.5pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">puck.nether.net<o:p></o:p></span></p>
</div>
<div id="LPDescription_14836362865060.030038025780266375">
<p class="MsoNormal" style="margin-top:15.0pt;line-height:15.0pt"><span style="font-size:10.5pt;font-family:"Segoe UI","serif";color:#666666">A list for people interested in using Cisco VoIP equipment in a variety of environments, including service provider,
enterprise and over the public internet.<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:Calibri;color:black"><br>
><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/3dc6c223/attachment-0001.html" id="LPlnk988280">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/3dc6c223/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 4 Jan 2017 21:06:26 +0000<br>
From: "Schlotterer, Tommy" <tschlotterer@presidio.com><br>
To: Ben Amick <bamick@HumanArc.com>, Tim Warnock <timoid@timoid.org>,<br>
"'cisco-voip@puck.nether.net'" <cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
Message-ID:<br>
<cb29485432af47c689bf6c65c396fc49@sva-ex13-svr03.Presidio.Corp><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
The 7925 and 7926 phones are end of sale and soon to be end of life.<br>
<br>
<a href="http://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-7900-series/eos-eol-notice-c51-737580.html">http://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-7900-series/eos-eol-notice-c51-737580.html</a><br>
<br>
<br>
Tommy<br>
<br>
<br>
Tommy Schlotterer | Systems Engineer - Collaboration<br>
Presidio | <a href="http://www.presidio.com">www.presidio.com</a><br>
20 N Saint Clair 3rd Floor, Toledo, OH 43604<br>
D: 419.214.1415 | C: 419.706.0259 | tschlotterer@presidio.com<br>
<br>
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ben Amick<br>
Sent: Wednesday, January 04, 2017 8:31 AM<br>
To: Tim Warnock <timoid@timoid.org>; 'cisco-voip@puck.nether.net' <cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
<br>
I don't know about the issue with 802.11d, but the 7925/7926(+barcode scanner) is not EoL and is the successor in the same series. However, the newest wireless phone that they want us all to move to is the 8821.<br>
<br>
Ben Amick<br>
Telecom Analyst<br>
<br>
<br>
-----Original Message-----<br>
From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Tim Warnock<br>
Sent: Tuesday, January 03, 2017 11:12 PM<br>
To: 'cisco-voip@puck.nether.net' <cisco-voip@puck.nether.net><br>
Subject: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
<br>
Hi,<br>
<br>
Does anyone know how to either:<br>
<br>
A) Turn a 7921G-W-K9 -> 7291G-A-K9 or<br>
B) Disable the 7921G's reliance on country information being advertised via 802.11d<br>
<br>
It appears the World version needs 802.11d functioning in order to connect to the AP, and the AP in question doesn't support 802.11d<br>
<br>
Or suggest a suitable replacement (7921G is EOL)?<br>
<br>
Thanks<br>
-]Tim.<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="http://cp.mcafee.com/d/1jWVIe4wUpdEIfcLTphsudTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndKIK3HeffZvAm4rILfZuVtdBxDAS3hOC-UeWyaqRQRrCzB_BgY-F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jqrPb1IQJSBiRiVCIBziWq81NEVjh8BP1sGqejh0nd7NEw76zBd4ynQKld79JAsr9cjU">http://cp.mcafee.com/d/1jWVIe4wUpdEIfcLTphsudTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndKIK3HeffZvAm4rILfZuVtdBxDAS3hOC-UeWyaqRQRrCzB_BgY-F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jqrPb1IQJSBiRiVCIBziWq81NEVjh8BP1sGqejh0nd7NEw76zBd4ynQKld79JAsr9cjU</a><br>
<br>
<br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you _______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
<br>
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete
and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 4 Jan 2017 16:08:38 -0500<br>
From: Evgeny Izetov <eizetov@gmail.com><br>
To: Ryan Huff <ryanhuff@outlook.com><br>
Cc: Lelio Fulgenzi <lelio@uoguelph.ca>, Ben Amick<br>
<bamick@humanarc.com>, Cisco VoIP Group <cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
Message-ID:<br>
<CAKLHLoX9WXtr0931CL0-Sh3OVw5-TRMui87N-UJH-h_8sUwqMQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Ben, here's the link to the site and the session video:<br>
<a href="https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=89103&backBtn=true">https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=89103&backBtn=true</a><br>
<br>
On Wed, Jan 4, 2017 at 11:44 AM, Ryan Huff <ryanhuff@outlook.com> wrote:<br>
<br>
> Yes, TRP does have some drawbacks; video, binary floor control BUT, works<br>
> great for voice media. It's a heavy overhead and isn't a complete solution<br>
> but works in a pinch if you're dealing with some C Level users that "just<br>
> want the computer phone to work".<br>
><br>
> I have also been known to swap out the network card in user pcs for dual<br>
> interface cards, then use a persistent route in the PC to force the soft<br>
> phone's traffic to its call control server out of one interface that is on<br>
> the voice network (leaving the other interface on the data network).<br>
><br>
> A crude solution, but it worked well in a situation where the networking<br>
> gear wouldn't have supported what we would've needed to do with QOS. Dual<br>
> port PC network cards, even in bulk, are a heck of a lot cheaper than new<br>
> networking gear.<br>
><br>
> Yikes, giving myself flashbacks from rehashing all these memories of being<br>
> a network admin for a nonprofit .... need some coffee ....<br>
><br>
> On Jan 4, 2017, at 11:27 AM, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br>
><br>
> I would have loved to do MTP resources across the board... helps with<br>
> security as well, less holes to open up. But I found a few features that<br>
> wouldn't work, like desktop sharing, etc. If they supported all features<br>
> with MTP, I'd would have likely been able to justify a couple of routers to<br>
> do it.<br>
><br>
><br>
> ---<br>
> Lelio Fulgenzi, B.A.<br>
> Senior Analyst, Network Infrastructure<br>
> Computing and Communications Services (CCS)<br>
> University of Guelph<br>
><br>
> 519-824-4120 Ext 56354 <(519)%20824-4120><br>
> lelio@uoguelph.ca<br>
> <a href="http://www.uoguelph.ca/ccs">www.uoguelph.ca/ccs</a><br>
> Room 037, Animal Science and Nutrition Building<br>
> Guelph, Ontario, N1G 2W1<br>
><br>
><br>
><br>
> ------------------------------<br>
> *From:* cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Ben<br>
> Amick <bamick@HumanArc.com><br>
> *Sent:* Wednesday, January 4, 2017 11:18 AM<br>
> *To:* Evgeny Izetov; Ryan Huff<br>
> *Cc:* Cisco VoIP Group<br>
> *Subject:* Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
> Evgeny,<br>
><br>
> That?s great, and I was able to find the PDF from the session but I can?t<br>
> seem to remember how to find the site that has the recordings of the<br>
> sessions ? could you provide a link to that?<br>
><br>
><br>
><br>
> Ryan,<br>
><br>
> That sounds like a solid idea for when QoS is absolutely absolutely<br>
> necessary, but I have nowhere near enough MTP resources to do that for all<br>
> the softphones in my org.<br>
><br>
><br>
><br>
> *Ben Amick*<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> *From:* Evgeny Izetov [mailto:eizetov@gmail.com <eizetov@gmail.com>]<br>
> *Sent:* Tuesday, January 03, 2017 10:15 PM<br>
> *To:* Ryan Huff <ryanhuff@outlook.com><br>
> *Cc:* Ben Amick <bamick@HumanArc.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> *Subject:* Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> I saw a CiscoLive! session recently that seemed to recommend the ports and<br>
> access-lists approach. The idea is that you can now specify separate port<br>
> ranges for audio and video in SIP Profile. The session goes quite in depth<br>
> and is worth the watch:<br>
><br>
> BRKCOL-2616 - QoS Strategies and Smart Media Techniques for Collaboration<br>
> Deployments (2016 Berlin) - 2 Hours<br>
><br>
><br>
><br>
> On Tue, Jan 3, 2017 at 9:49 PM, Ryan Huff <ryanhuff@outlook.com> wrote:<br>
><br>
> I see; while this is by no means a complete solution, it may help. I'm<br>
> assuming Cisco based soft phones (CIPC, CSF, BOT, TAB ... etc).<br>
><br>
><br>
><br>
> You may try Trusted Relay Points (set in the device level configuration).<br>
> This does rely and depend on your media resource architecture and design;<br>
> i.e. you'll need to have media resources that support TRP available.<br>
><br>
><br>
><br>
> Using TRP on the device config for a soft phone will cause CUCM to<br>
> dynamically insert an MTP in the call flow which will allow for adherence<br>
> to QOS trust policies and offer a predetermined network path for call flows<br>
> in an otherwise untrusted network (presumably, the data network).<br>
><br>
> -Ryan<br>
><br>
><br>
><br>
><br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 9:30 PM, Ben Amick <bamick@HumanArc.com> wrote:<br>
><br>
> Only for softphones. Currently most of our servers live on the same LAN as<br>
> end users, so yeah. Hardphones have their own VLAN so its not as bad. In<br>
> the future it won?t be that way but for the time being it is.<br>
><br>
><br>
><br>
> *Ben Amick*<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> *From:* Ryan Huff [mailto:ryanhuff@outlook.com <ryanhuff@outlook.com>]<br>
> *Sent:* Tuesday, January 03, 2017 9:18 PM<br>
> *To:* Ben Amick <bamick@HumanArc.com><br>
> *Cc:* NateCCIE <nateccie@gmail.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> *Subject:* Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> Ben,<br>
><br>
><br>
><br>
> By flat network; I am to assume that there is no layer 2 partition between<br>
> rtp/signaling and general data traffic?<br>
><br>
><br>
> On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com> wrote:<br>
><br>
> Yeah, I have the luck of having MPLS right now, and I don?t see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn?t<br>
> my issue, it?s QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe **cough**developers**cough** seems to<br>
> have made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we?re having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
><br>
><br>
> *Ben Amick*<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> *From:* Ryan Huff [mailto:ryanhuff@outlook.com <ryanhuff@outlook.com>]<br>
> *Sent:* Tuesday, January 03, 2017 8:40 PM<br>
> *To:* NateCCIE <nateccie@gmail.com><br>
> *Cc:* Ben Amick <bamick@HumanArc.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> *Subject:* Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
><br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com> wrote:<br>
><br>
> Or take the most approach of do nothing.<br>
><br>
><br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
><br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com> wrote:<br>
><br>
> So, I know this is an age old question that?s debated, but I?ve been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn?t applicable with softphones.<br>
><br>
><br>
><br>
> I?ve heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
><br>
><br>
> Maybe I?m missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there?s the auto qos trust cisco-softphone for cisco switches, but<br>
> I don?t believe there?s a solution other than #1 for non-cisco switches)?<br>
><br>
><br>
><br>
> *Ben Amick*<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> <<a href="http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm">http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm</a>><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> <<a href="http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE">http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE</a>><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> <<a href="http://cp.mcafee.com/d/avndy1J5xVBwQsCzBMsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrud7bPBD7D-LOryrPPXWvnKnjh7cYMed7aqbz0XG8FHnjlKOeVkffGhBrwqrhdICXYyevvjvuhjsdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6_AaveFA54hfBPqrMVBAS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdwmX6sqwk">http://cp.mcafee.com/d/avndy1J5xVBwQsCzBMsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrud7bPBD7D-LOryrPPXWvnKnjh7cYMed7aqbz0XG8FHnjlKOeVkffGhBrwqrhdICXYyevvjvuhjsdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6_AaveFA54hfBPqrMVBAS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdwmX6sqwk</a>><br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/3f91479c/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/3f91479c/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 4 Jan 2017 21:08:59 +0000<br>
From: Ben Amick <bamick@HumanArc.com><br>
To: "Schlotterer, Tommy" <tschlotterer@presidio.com>, Tim Warnock<br>
<timoid@timoid.org>, "'cisco-voip@puck.nether.net'"<br>
<cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
Message-ID:<br>
<820C24BFE55F434C97807C60D4647ACE0F9DE390@E2k10-MB-HT1.humanarc.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Holy wow. Was not expecting that to happen so quickly, being as the 8821 just came out very recently, and the core 7900 hasn?t been EoS announced yet. Somehow I missed that announcement.
<br>
<br>
Ben Amick<br>
Telecom Analyst<br>
<br>
<br>
-----Original Message-----<br>
From: Schlotterer, Tommy [<a href="mailto:tschlotterer@presidio.com">mailto:tschlotterer@presidio.com</a>]
<br>
Sent: Wednesday, January 04, 2017 4:06 PM<br>
To: Ben Amick <bamick@HumanArc.com>; Tim Warnock <timoid@timoid.org>; 'cisco-voip@puck.nether.net' <cisco-voip@puck.nether.net><br>
Subject: RE: 7921g-w-k9 -> 7921g-a-k9<br>
<br>
The 7925 and 7926 phones are end of sale and soon to be end of life.<br>
<br>
<a href="http://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-7900-series/eos-eol-notice-c51-737580.html">http://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-7900-series/eos-eol-notice-c51-737580.html</a><br>
<br>
<br>
Tommy<br>
<br>
<br>
Tommy Schlotterer | Systems Engineer - Collaboration Presidio | <a href="http://cp.mcafee.com/d/2DRPow92gwd6Qm7CnT6jhOqem3tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPpEVgpsgsuvW_cKe3xTnKnjpd7d-suud7b7bnhIyyHsszOEuvkzaT0QSyrodTVeZXTLuZXCXCODbh-AA9lVsTeBypZpP-fN1iQvF92lundKc9zzob6Azh0ed7aq94KobBjhOq82VE-d40UQsFEAi-BOFEVdFL6_X41">
http://cp.mcafee.com/d/2DRPow92gwd6Qm7CnT6jhOqem3tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPpEVgpsgsuvW_cKe3xTnKnjpd7d-suud7b7bnhIyyHsszOEuvkzaT0QSyrodTVeZXTLuZXCXCODbh-AA9lVsTeBypZpP-fN1iQvF92lundKc9zzob6Azh0ed7aq94KobBjhOq82VE-d40UQsFEAi-BOFEVdFL6_X41</a><br>
20 N Saint Clair 3rd Floor, Toledo, OH 43604<br>
D: 419.214.1415 | C: 419.706.0259 | tschlotterer@presidio.com<br>
<br>
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ben Amick<br>
Sent: Wednesday, January 04, 2017 8:31 AM<br>
To: Tim Warnock <timoid@timoid.org>; 'cisco-voip@puck.nether.net' <cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
<br>
I don't know about the issue with 802.11d, but the 7925/7926(+barcode scanner) is not EoL and is the successor in the same series. However, the newest wireless phone that they want us all to move to is the 8821.<br>
<br>
Ben Amick<br>
Telecom Analyst<br>
<br>
<br>
-----Original Message-----<br>
From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Tim Warnock<br>
Sent: Tuesday, January 03, 2017 11:12 PM<br>
To: 'cisco-voip@puck.nether.net' <cisco-voip@puck.nether.net><br>
Subject: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
<br>
Hi,<br>
<br>
Does anyone know how to either:<br>
<br>
A) Turn a 7921G-W-K9 -> 7291G-A-K9 or<br>
B) Disable the 7921G's reliance on country information being advertised via 802.11d<br>
<br>
It appears the World version needs 802.11d functioning in order to connect to the AP, and the AP in question doesn't support 802.11d<br>
<br>
Or suggest a suitable replacement (7921G is EOL)?<br>
<br>
Thanks<br>
-]Tim.<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="http://cp.mcafee.com/d/1jWVIe4wUpdEIfcLTphsudTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndKIK3HeffZvAm4rILfZuVtdBxDAS3hOC-UeWyaqRQRrCzB_BgY-F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jqrPb1IQJSBiRiVCIBziWq81NEVjh8BP1sGqejh0nd7NEw76zBd4ynQKld79JAsr9cjU">http://cp.mcafee.com/d/1jWVIe4wUpdEIfcLTphsudTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndKIK3HeffZvAm4rILfZuVtdBxDAS3hOC-UeWyaqRQRrCzB_BgY-F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jqrPb1IQJSBiRiVCIBziWq81NEVjh8BP1sGqejh0nd7NEw76zBd4ynQKld79JAsr9cjU</a><br>
<br>
<br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you _______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="http://cp.mcafee.com/d/1jWVIp4x8e4zqb3PbXz9EVd7b1KVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVIQsEcK8effZvCn71MXHTbFICzC_eff6zBzBHEShhlKehVkffGhBrwqrjdI6XYDuZXTLuZPtPpesRG9pyPtyL0QDYu1K2qKMM-l9OwXnbiFqFsPmiNKtb4PWPDYvy2BE_ii4GYKrsoj76Mmd96y0sqekQi9sMnaCzAQg5PhYq81NEVjh8BZbBjhOrjudJENJj4Wz">http://cp.mcafee.com/d/1jWVIp4x8e4zqb3PbXz9EVd7b1KVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVIQsEcK8effZvCn71MXHTbFICzC_eff6zBzBHEShhlKehVkffGhBrwqrjdI6XYDuZXTLuZPtPpesRG9pyPtyL0QDYu1K2qKMM-l9OwXnbiFqFsPmiNKtb4PWPDYvy2BE_ii4GYKrsoj76Mmd96y0sqekQi9sMnaCzAQg5PhYq81NEVjh8BZbBjhOrjudJENJj4Wz</a><br>
<br>
<br>
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete
and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.<br>
<br>
<br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 4 Jan 2017 17:31:18 -0800<br>
From: Tom Sparks <tsparks@taosconsulting.com><br>
To: cisco-voip@puck.nether.net<br>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
Message-ID:<br>
<CAMQod5JehMxrVi8a5Bup_zNDoOTGBFAr996WckkxWVUSFdAOuA@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I believe that medianet plugin was discontinued by Cisco. But if anyone<br>
gets it working, please let me know.<br>
<br>
Here's a seemingly good blog on the whole topic also<br>
<br>
<a href="https://infrastructureland.wordpress.com/2015/02/07/jabber-12/">https://infrastructureland.wordpress.com/2015/02/07/jabber-12/</a><br>
<br>
Tom Sparks<br>
Taos Consulting<br>
Sr. Voice | Video Engineer<br>
tsparks@taosconsulting.com<br>
+1 415.515.2391<br>
<br>
<br>
On Wed, Jan 4, 2017 at 9:00 AM, <cisco-voip-request@puck.nether.net> wrote:<br>
<br>
> Send cisco-voip mailing list submissions to<br>
> cisco-voip@puck.nether.net<br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> cisco-voip-request@puck.nether.net<br>
><br>
> You can reach the person managing the list at<br>
> cisco-voip-owner@puck.nether.net<br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of cisco-voip digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: CUCM Patch Insight (NateCCIE)<br>
> 2. Jabber/CIPC and QoS (Ben Amick)<br>
> 3. Re: Jabber/CIPC and QoS (Lelio Fulgenzi)<br>
> 4. Re: Jabber/CIPC and QoS (Ben Amick)<br>
> 5. Re: Jabber/CIPC and QoS (Hodgeman, Samuel)<br>
> 6. Re: Jabber/CIPC and QoS (NateCCIE)<br>
> 7. Re: Jabber/CIPC and QoS (Ryan Huff)<br>
> 8. LiveData enhancements in UCCX 11.0 and 11.5<br>
> (Abhiram Kramadhati (akramadh))<br>
> 9. Re: Jabber/CIPC and QoS (Ben Amick)<br>
> 10. Re: Jabber/CIPC and QoS (Ryan Huff)<br>
> 11. Re: Jabber/CIPC and QoS (Ben Amick)<br>
> 12. Re: Jabber/CIPC and QoS (Ryan Huff)<br>
> 13. Re: Jabber/CIPC and QoS (Evgeny Izetov)<br>
> 14. 7921g-w-k9 -> 7921g-a-k9 (Tim Warnock)<br>
> 15. Re: Jabber/CIPC and QoS (Ben Amick)<br>
> 16. Re: Jabber/CIPC and QoS (Lelio Fulgenzi)<br>
> 17. Re: Jabber/CIPC and QoS (Ryan Huff)<br>
> 18. Re: 7921g-w-k9 -> 7921g-a-k9 (Ben Amick)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Tue, 3 Jan 2017 10:33:39 -0700<br>
> From: NateCCIE <nateccie@gmail.com><br>
> To: "'Jeffrey McHugh'" <jmchugh@fidelus.com>, "'Tim Franklin'"<br>
> <tim@tripplehelix.net>, <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] CUCM Patch Insight<br>
> Message-ID: <062901d265e7$8652f4c0$92f8de40$@gmail.com><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> I would wait for SU2 at this point. It will be soon.<br>
><br>
><br>
><br>
> From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of<br>
> Jeffrey McHugh<br>
> Sent: Tuesday, January 03, 2017 8:53 AM<br>
> To: Tim Franklin <tim@tripplehelix.net>; cisco-voip@puck.nether.net<br>
> Subject: Re: [cisco-voip] CUCM Patch Insight<br>
><br>
><br>
><br>
> Just did an SU1 upgrade, no issues reported but look into bug CSCux90747<br>
> depending on your esxi versions<br>
><br>
><br>
><br>
> I would expect SU2 soon as its named in the Expressway 8.9 release notes<br>
> for some MRA feature preview<br>
><br>
><br>
><br>
> From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of<br>
> Tim Franklin<br>
> Sent: Tuesday, January 3, 2017 10:44 AM<br>
> To: cisco-voip@puck.nether.net <<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a>><br>
> Subject: [cisco-voip] CUCM Patch Insight<br>
><br>
><br>
><br>
> Just curious if anyone on this list has any feedback as to the stability<br>
> of CUCM 11.5(1)SU1. I'm planning my upgrades out and I'm a bit leery to<br>
> deploy it given that it's been out since November. While that speaks to no<br>
> large defects to cause a deferral notice I'm also wondering if another SU<br>
> is on the horizon?<br>
><br>
><br>
><br>
> Thanks<br>
><br>
><br>
> Jeffrey McHugh | Sr. Collaboration Consulting Engineer | VCP-DCV, CCNP<br>
> Collaboration<br>
><br>
> <<a href="http://www.fidelus.com/">http://www.fidelus.com/</a>><br>
><br>
> Fidelus Technologies, LLC<br>
> Named <http://www.fidelus.com/fidelus-technologies-named-<br>
> best-unified-communications-provider-in-the-usa/> Best UC Provider in the<br>
> USA<br>
><br>
> 240 West 35th Street, 6th Floor, New York, NY 10001<br>
><br>
> +1-212-616-7801 office | +1-212-616-7850 fax | <<a href="http://www.fidelus.com/">http://www.fidelus.com/</a>><br>
> <a href="http://www.fidelus.com">www.fidelus.com</a><br>
><br>
> <<a href="http://www.linkedin.com/company/fidelus-technologies/products">http://www.linkedin.com/company/fidelus-technologies/products</a>> <<br>
> <a href="http://www.twitter.com/FidelusUCC">http://www.twitter.com/FidelusUCC</a>> <<a href="http://www.facebook.com/FidelusUCC">http://www.facebook.com/FidelusUCC</a>><br>
> <<a href="http://www.youtube.com/FidelusTraining">http://www.youtube.com/FidelusTraining</a>><br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/b7ece70c/attachment-0001.html><br>
> -------------- next part --------------<br>
> A non-text attachment was scrubbed...<br>
> Name: image001.png<br>
> Type: image/png<br>
> Size: 1989 bytes<br>
> Desc: not available<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/b7ece70c/attachment-0005.png><br>
> -------------- next part --------------<br>
> A non-text attachment was scrubbed...<br>
> Name: image002.png<br>
> Type: image/png<br>
> Size: 1500 bytes<br>
> Desc: not available<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/b7ece70c/attachment-0006.png><br>
> -------------- next part --------------<br>
> A non-text attachment was scrubbed...<br>
> Name: image003.png<br>
> Type: image/png<br>
> Size: 1526 bytes<br>
> Desc: not available<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/b7ece70c/attachment-0007.png><br>
> -------------- next part --------------<br>
> A non-text attachment was scrubbed...<br>
> Name: image004.png<br>
> Type: image/png<br>
> Size: 1450 bytes<br>
> Desc: not available<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/b7ece70c/attachment-0008.png><br>
> -------------- next part --------------<br>
> A non-text attachment was scrubbed...<br>
> Name: image005.png<br>
> Type: image/png<br>
> Size: 1632 bytes<br>
> Desc: not available<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/b7ece70c/attachment-0009.png><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Tue, 3 Jan 2017 21:25:20 +0000<br>
> From: Ben Amick <bamick@HumanArc.com><br>
> To: Cisco VoIP Group <cisco-voip@puck.nether.net><br>
> Subject: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <820C24BFE55F434C97807C60D4647ACE0F9D3DBB@E2k10-MB-HT1.<br>
> humanarc.com><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/4d9a63d8/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Tue, 3 Jan 2017 21:35:41 +0000<br>
> From: Lelio Fulgenzi <lelio@uoguelph.ca><br>
> To: Ben Amick <bamick@HumanArc.com>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <YTOPR01MB0251F94A8E59508021DD7D21AC6E0@YTOPR01MB0251.<br>
> CANPRD01.PROD.OUTLOOK.COM><br>
><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
><br>
> good question Ben. i look forward to reading this thread.<br>
><br>
><br>
> i've been meaning to read up on mediaNet, and it seems it's more required<br>
> than not, especially for QoS.<br>
><br>
><br>
> are you suggesting (with option 3) that there is software you can install<br>
> on desktops? what about mobile devices?<br>
><br>
><br>
> QoS, both wired and wireless, will definitely be an interesting challenge.<br>
><br>
><br>
><br>
> ---<br>
> Lelio Fulgenzi, B.A.<br>
> Senior Analyst, Network Infrastructure<br>
> Computing and Communications Services (CCS)<br>
> University of Guelph<br>
><br>
> 519-824-4120 Ext 56354<br>
> lelio@uoguelph.ca<br>
> <a href="http://www.uoguelph.ca/ccs">www.uoguelph.ca/ccs</a><br>
> Room 037, Animal Science and Nutrition Building<br>
> Guelph, Ontario, N1G 2W1<br>
><br>
><br>
> ________________________________<br>
> From: cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Ben<br>
> Amick <bamick@HumanArc.com><br>
> Sent: Tuesday, January 3, 2017 4:25 PM<br>
> To: Cisco VoIP Group<br>
> Subject: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
><br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
><br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/0a34315c/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 4<br>
> Date: Tue, 3 Jan 2017 22:02:42 +0000<br>
> From: Ben Amick <bamick@HumanArc.com><br>
> To: Lelio Fulgenzi <lelio@uoguelph.ca>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <820C24BFE55F434C97807C60D4647ACE0F9D3E0F@E2k10-MB-HT1.<br>
> humanarc.com><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> From what I understand, it's not so much as "software" as it is a plugin<br>
> for jabber that enables Jabber to send the medianet signaling. I don't<br>
> believe it's a function of iOS/android Jabber though, but I could be<br>
> mistaken<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Lelio Fulgenzi [<a href="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</a>]<br>
> Sent: Tuesday, January 03, 2017 4:36 PM<br>
> To: Ben Amick <bamick@HumanArc.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> Subject: Re: Jabber/CIPC and QoS<br>
><br>
><br>
><br>
><br>
> good question Ben. i look forward to reading this thread.<br>
><br>
><br>
><br>
> i've been meaning to read up on mediaNet, and it seems it's more required<br>
> than not, especially for QoS.<br>
><br>
><br>
><br>
> are you suggesting (with option 3) that there is software you can install<br>
> on desktops? what about mobile devices?<br>
><br>
><br>
><br>
> QoS, both wired and wireless, will definitely be an interesting challenge.<br>
><br>
><br>
><br>
><br>
> ---<br>
> Lelio Fulgenzi, B.A.<br>
> Senior Analyst, Network Infrastructure<br>
> Computing and Communications Services (CCS)<br>
> University of Guelph<br>
><br>
> 519-824-4120 Ext 56354<br>
> lelio@uoguelph.ca<<a href="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</a>><br>
> www.uoguelph.ca/ccs<<a href="http://www.uoguelph.ca/ccs">http://www.uoguelph.ca/ccs</a>><br>
> Room 037, Animal Science and Nutrition Building<br>
> Guelph, Ontario, N1G 2W1<br>
><br>
> ________________________________<br>
> From: cisco-voip <cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-<br>
> bounces@puck.nether.net>> on behalf of Ben Amick <bamick@HumanArc.com<br>
> <<a href="mailto:bamick@HumanArc.com">mailto:bamick@HumanArc.com</a>>><br>
> Sent: Tuesday, January 3, 2017 4:25 PM<br>
> To: Cisco VoIP Group<br>
> Subject: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
><br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
><br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/9591b6cd/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 5<br>
> Date: Tue, 3 Jan 2017 22:13:15 +0000<br>
> From: "Hodgeman, Samuel" <shodgeman@xo.com><br>
> To: Ben Amick <bamick@HumanArc.com>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <94004f6f0f8646e7a51539636329908b@TXPLANEXCH101.corp.inthosts.net><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> For option 1, using Windows... this can be implemented with Group<br>
> Policies, taking it out of the hands of end users, and can be associated<br>
> with specific application executable and/or specific IP address<br>
> source/destination.<br>
><br>
><br>
> - Sam H<br>
><br>
> From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of<br>
> Ben Amick<br>
> Sent: Tuesday, January 03, 2017 3:25 PM<br>
> To: Cisco VoIP Group <cisco-voip@puck.nether.net><br>
> Subject: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/3ef7729c/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 6<br>
> Date: Tue, 3 Jan 2017 17:53:14 -0700<br>
> From: NateCCIE <nateccie@gmail.com><br>
> To: Ben Amick <bamick@HumanArc.com><br>
> Cc: Cisco VoIP Group <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID: <05C8F1E2-B3DA-435C-BAB4-3C8278A0A726@gmail.com><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> Or take the most approach of do nothing.<br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> > On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com> wrote:<br>
> ><br>
> > So, I know this is an age old question that?s debated, but I?ve been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn?t applicable with softphones.<br>
> ><br>
> > I?ve heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
> > 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
> > 2. Configuring your switches with an access list that recognizes<br>
> the ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
> > 3. Installing Medianet services on all jabber clients; Configure<br>
> all switches for medianet tagging. Problem: (I think?) Requires newer<br>
> switches to use, maybe needs an additional server (I vaguely remember<br>
> possibly needing prime collab?)?<br>
> ><br>
> > Maybe I?m missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there?s the auto qos trust cisco-softphone for cisco switches, but<br>
> I don?t believe there?s a solution other than #1 for non-cisco switches)?<br>
> ><br>
> > Ben Amick<br>
> > Telecom Analyst<br>
> ><br>
> ><br>
> > Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > cisco-voip@puck.nether.net<br>
> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/0da1ffef/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 7<br>
> Date: Wed, 4 Jan 2017 01:39:30 +0000<br>
> From: Ryan Huff <ryanhuff@outlook.com><br>
> To: NateCCIE <nateccie@gmail.com><br>
> Cc: Ben Amick <bamick@HumanArc.com>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <BLUPR18MB0482767CF5DE727DDEE526FEC5610@BLUPR18MB0482.<br>
> namprd18.prod.outlook.com><br>
><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
><br>
> Or take the most approach of do nothing.<br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/f9b9e92b/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 8<br>
> Date: Wed, 4 Jan 2017 01:48:30 +0000<br>
> From: "Abhiram Kramadhati (akramadh)" <akramadh@cisco.com><br>
> To: Cisco VoIP Group <cisco-voip@puck.nether.net><br>
> Subject: [cisco-voip] LiveData enhancements in UCCX 11.0 and 11.5<br>
> Message-ID: <5C88B902-AED4-4603-8707-A2BAE18A1181@cisco.com><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> Hi all,<br>
><br>
> Happy 2017!<br>
><br>
> We just published a Field Notice about LiveData stabilization enhancements<br>
> done in 11.0(1)SU1 and 11.5(1)ES1.<br>
> <a href="http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64240.html">
http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64240.html</a><br>
><br>
> So, if you are on 11.0 or 11.5, our recommendation is to move to the<br>
> above-mentioned releases. You could be running on 11.0/11.5 with no LD<br>
> issues ? this is just a proactive measure.<br>
><br>
> [http://www.cisco.com/c/dam/assets/email-signature-tool/<br>
> logo_07.png?ct=1421802598153]<br>
><br>
> Abhiram Kramadhati<br>
> Technical Solutions Manager<br>
> Customer Solutions Success team, CCBU<br>
> akramadh@cisco.com<<a href="mailto:akramadh@cisco.com">mailto:akramadh@cisco.com</a>><br>
> Phone: +61 2 8446 6257<br>
><br>
> CCIE Collaboration - 40065<br>
><br>
> Cisco Systems Australia Pty Limited<br>
> The Forum<br>
> 201 Pacific Highway<br>
> 2065<br>
> St Leonards<br>
> Australia<br>
> Cisco.com<<a href="http://www.cisco.com/web/AU/">http://www.cisco.com/web/AU/</a>><br>
><br>
> [<a href="http://www.cisco.com/assets/social_media_icons/linkedin-16x16.png">http://www.cisco.com/assets/social_media_icons/linkedin-16x16.png</a>]<<br>
> <a href="http://wwwin.cisco.com/marketing/corporate/brand/intelbrand/brandstrat/">
http://wwwin.cisco.com/marketing/corporate/brand/intelbrand/brandstrat/</a><br>
> signature/Insert%20your%20LinkedIn%20link><br>
><br>
><br>
><br>
><br>
> [<a href="http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif">http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif</a>]Think before<br>
> you print.<br>
><br>
> This email may contain confidential and privileged material for the sole<br>
> use of the intended recipient. Any review, use, distribution or disclosure<br>
> by others is strictly prohibited. If you are not the intended recipient (or<br>
> authorized to receive for the recipient), please contact the sender by<br>
> reply email and delete all copies of this message.<br>
> Please click here<http://www.cisco.com/web/about/doing_business/legal/<br>
> cri/index.html> for Company Registration Information.<br>
><br>
><br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/fb4a3136/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 9<br>
> Date: Wed, 4 Jan 2017 02:15:06 +0000<br>
> From: Ben Amick <bamick@HumanArc.com><br>
> To: Ryan Huff <ryanhuff@outlook.com>, NateCCIE <nateccie@gmail.com><br>
> Cc: Cisco VoIP Group <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <820C24BFE55F434C97807C60D4647ACE0F9DE054@E2k10-MB-HT1.<br>
> humanarc.com><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> Yeah, I have the luck of having MPLS right now, and I don't see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn't<br>
> my issue, it's QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe *cough*developers*cough* seems to have<br>
> made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we're having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 8:40 PM<br>
> To: NateCCIE <nateccie@gmail.com><br>
> Cc: Ben Amick <bamick@HumanArc.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
> Or take the most approach of do nothing.<br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/74ba53d8/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 10<br>
> Date: Wed, 4 Jan 2017 02:18:06 +0000<br>
> From: Ryan Huff <ryanhuff@outlook.com><br>
> To: Ben Amick <bamick@HumanArc.com><br>
> Cc: NateCCIE <nateccie@gmail.com>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <BLUPR18MB04820158AE92067D655F5A57C5610@BLUPR18MB0482.<br>
> namprd18.prod.outlook.com><br>
><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> Ben,<br>
><br>
> By flat network; I am to assume that there is no layer 2 partition between<br>
> rtp/signaling and general data traffic?<br>
><br>
> On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> Yeah, I have the luck of having MPLS right now, and I don't see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn't<br>
> my issue, it's QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe *cough*developers*cough* seems to have<br>
> made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we're having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 8:40 PM<br>
> To: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>><br>
> Cc: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>>; Cisco<br>
> VoIP Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
> Or take the most approach of do nothing.<br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/46eda1b1/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 11<br>
> Date: Wed, 4 Jan 2017 02:30:35 +0000<br>
> From: Ben Amick <bamick@HumanArc.com><br>
> To: Ryan Huff <ryanhuff@outlook.com><br>
> Cc: NateCCIE <nateccie@gmail.com>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <820C24BFE55F434C97807C60D4647ACE0F9DE08E@E2k10-MB-HT1.<br>
> humanarc.com><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> Only for softphones. Currently most of our servers live on the same LAN as<br>
> end users, so yeah. Hardphones have their own VLAN so its not as bad. In<br>
> the future it won't be that way but for the time being it is.<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 9:18 PM<br>
> To: Ben Amick <bamick@HumanArc.com><br>
> Cc: NateCCIE <nateccie@gmail.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> Ben,<br>
><br>
> By flat network; I am to assume that there is no layer 2 partition between<br>
> rtp/signaling and general data traffic?<br>
><br>
> On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> Yeah, I have the luck of having MPLS right now, and I don't see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn't<br>
> my issue, it's QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe *cough*developers*cough* seems to have<br>
> made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we're having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 8:40 PM<br>
> To: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>><br>
> Cc: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>>; Cisco<br>
> VoIP Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
> Or take the most approach of do nothing.<br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> So, I know this is an age old question that's debated, but I've been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn't applicable with softphones.<br>
><br>
> I've heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I'm missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there's the auto qos trust cisco-softphone for cisco switches, but<br>
> I don't believe there's a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/564a50a0/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 12<br>
> Date: Wed, 4 Jan 2017 02:49:49 +0000<br>
> From: Ryan Huff <ryanhuff@outlook.com><br>
> To: Ben Amick <bamick@HumanArc.com><br>
> Cc: NateCCIE <nateccie@gmail.com>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <BLUPR18MB048225F237E9FCEFAF1C726FC5610@BLUPR18MB0482.<br>
> namprd18.prod.outlook.com><br>
><br>
> Content-Type: text/plain; charset="windows-1252"<br>
><br>
> I see; while this is by no means a complete solution, it may help. I'm<br>
> assuming Cisco based soft phones (CIPC, CSF, BOT, TAB ... etc).<br>
><br>
> You may try Trusted Relay Points (set in the device level configuration).<br>
> This does rely and depend on your media resource architecture and design;<br>
> i.e. you'll need to have media resources that support TRP available.<br>
><br>
> Using TRP on the device config for a soft phone will cause CUCM to<br>
> dynamically insert an MTP in the call flow which will allow for adherence<br>
> to QOS trust policies and offer a predetermined network path for call flows<br>
> in an otherwise untrusted network (presumably, the data network).<br>
><br>
> -Ryan<br>
><br>
><br>
><br>
> Sent from my iPhone<br>
> On Jan 3, 2017, at 9:30 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> Only for softphones. Currently most of our servers live on the same LAN as<br>
> end users, so yeah. Hardphones have their own VLAN so its not as bad. In<br>
> the future it won?t be that way but for the time being it is.<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 9:18 PM<br>
> To: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>><br>
> Cc: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>>; Cisco VoIP<br>
> Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> Ben,<br>
><br>
> By flat network; I am to assume that there is no layer 2 partition between<br>
> rtp/signaling and general data traffic?<br>
><br>
> On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> Yeah, I have the luck of having MPLS right now, and I don?t see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn?t<br>
> my issue, it?s QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe *cough*developers*cough* seems to have<br>
> made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we?re having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 8:40 PM<br>
> To: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>><br>
> Cc: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>>; Cisco<br>
> VoIP Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
> Or take the most approach of do nothing.<br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> So, I know this is an age old question that?s debated, but I?ve been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn?t applicable with softphones.<br>
><br>
> I?ve heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I?m missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there?s the auto qos trust cisco-softphone for cisco switches, but<br>
> I don?t believe there?s a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/2463d078/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 13<br>
> Date: Tue, 3 Jan 2017 22:14:31 -0500<br>
> From: Evgeny Izetov <eizetov@gmail.com><br>
> To: Ryan Huff <ryanhuff@outlook.com><br>
> Cc: Ben Amick <bamick@humanarc.com>, Cisco VoIP Group<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <CAKLHLoWZW6M62LgHccdQfzi12zfDwj+y8FoHJ07wjr5JOieMbQ@mail.<br>
> gmail.com><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> I saw a CiscoLive! session recently that seemed to recommend the ports and<br>
> access-lists approach. The idea is that you can now specify separate port<br>
> ranges for audio and video in SIP Profile. The session goes quite in depth<br>
> and is worth the watch:<br>
><br>
> BRKCOL-2616 - QoS Strategies and Smart Media Techniques for Collaboration<br>
> Deployments (2016 Berlin) - 2 Hours<br>
><br>
><br>
> On Tue, Jan 3, 2017 at 9:49 PM, Ryan Huff <ryanhuff@outlook.com> wrote:<br>
><br>
> > I see; while this is by no means a complete solution, it may help. I'm<br>
> > assuming Cisco based soft phones (CIPC, CSF, BOT, TAB ... etc).<br>
> ><br>
> > You may try Trusted Relay Points (set in the device level configuration).<br>
> > This does rely and depend on your media resource architecture and design;<br>
> > i.e. you'll need to have media resources that support TRP available.<br>
> ><br>
> > Using TRP on the device config for a soft phone will cause CUCM to<br>
> > dynamically insert an MTP in the call flow which will allow for adherence<br>
> > to QOS trust policies and offer a predetermined network path for call<br>
> flows<br>
> > in an otherwise untrusted network (presumably, the data network).<br>
> ><br>
> > -Ryan<br>
> ><br>
> ><br>
> ><br>
> > Sent from my iPhone<br>
> > On Jan 3, 2017, at 9:30 PM, Ben Amick <bamick@HumanArc.com> wrote:<br>
> ><br>
> > Only for softphones. Currently most of our servers live on the same LAN<br>
> as<br>
> > end users, so yeah. Hardphones have their own VLAN so its not as bad. In<br>
> > the future it won?t be that way but for the time being it is.<br>
> ><br>
> ><br>
> ><br>
> > *Ben Amick*<br>
> ><br>
> > Telecom Analyst<br>
> ><br>
> ><br>
> ><br>
> > *From:* Ryan Huff [mailto:ryanhuff@outlook.com <ryanhuff@outlook.com>]<br>
> > *Sent:* Tuesday, January 03, 2017 9:18 PM<br>
> > *To:* Ben Amick <bamick@HumanArc.com><br>
> > *Cc:* NateCCIE <nateccie@gmail.com>; Cisco VoIP Group <<br>
> > cisco-voip@puck.nether.net><br>
> > *Subject:* Re: [cisco-voip] Jabber/CIPC and QoS<br>
> ><br>
> ><br>
> ><br>
> > Ben,<br>
> ><br>
> ><br>
> ><br>
> > By flat network; I am to assume that there is no layer 2 partition<br>
> between<br>
> > rtp/signaling and general data traffic?<br>
> ><br>
> ><br>
> > On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com> wrote:<br>
> ><br>
> > Yeah, I have the luck of having MPLS right now, and I don?t see us going<br>
> > iWAN for a while for various reasons. QoS on the WAN right now even isn?t<br>
> > my issue, it?s QoS on the LAN. Right now we have a relatively flat<br>
> network,<br>
> > and certain segments of our troupe **cough**developers**cough** seems to<br>
> > have made our internal traffic ugly, to the point that I may have to do<br>
> an<br>
> > analysis of it, as we?re having just random periods here and there where<br>
> > calls just have horrible quality, of the type you normally see fixed by<br>
> QoS<br>
> ><br>
> ><br>
> ><br>
> > *Ben Amick*<br>
> ><br>
> > Telecom Analyst<br>
> ><br>
> ><br>
> ><br>
> > *From:* Ryan Huff [mailto:ryanhuff@outlook.com <ryanhuff@outlook.com>]<br>
> > *Sent:* Tuesday, January 03, 2017 8:40 PM<br>
> > *To:* NateCCIE <nateccie@gmail.com><br>
> > *Cc:* Ben Amick <bamick@HumanArc.com>; Cisco VoIP Group <<br>
> > cisco-voip@puck.nether.net><br>
> > *Subject:* Re: [cisco-voip] Jabber/CIPC and QoS<br>
> ><br>
> ><br>
> ><br>
> > It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> > it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> > Internet.<br>
> ><br>
> ><br>
> ><br>
> > Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> > public Comcast or Time Warner/Charter package.<br>
> ><br>
> ><br>
> > On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com> wrote:<br>
> ><br>
> > Or take the most approach of do nothing.<br>
> ><br>
> ><br>
> ><br>
> > My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> > OPUS, etc.<br>
> ><br>
> ><br>
> ><br>
> > So many business are getting rid of the QoS capable WAN and just doing<br>
> > VPNs, even if they have fancy names that make it sound better than public<br>
> > internet.<br>
> ><br>
> > Sent from my iPhone<br>
> ><br>
> ><br>
> > On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com> wrote:<br>
> ><br>
> > So, I know this is an age old question that?s debated, but I?ve been<br>
> > wondering if anyone here has a perspective here in regards to QoS for<br>
> > softphones. Obviously, with hardphones, you usually partition a separate<br>
> > VLAN with AutoQoS/DSCP tags, but that isn?t applicable with softphones.<br>
> ><br>
> ><br>
> ><br>
> > I?ve heard of three different options in the past, neither of which seem<br>
> > to be very simple to deploy, but all seem to be Jabber-centric.<br>
> ><br>
> > 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> > the switches they are connected to, as well as trusting the device.<br>
> > Problems: Requires users to be local admins, openings for abuse and<br>
> network<br>
> > impact due to blind PC trust.<br>
> ><br>
> > 2. Configuring your switches with an access list that recognizes the<br>
> > ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> > programs could theoretically use those ports<br>
> ><br>
> > 3. Installing Medianet services on all jabber clients; Configure all<br>
> > switches for medianet tagging. Problem: (I think?) Requires newer<br>
> switches<br>
> > to use, maybe needs an additional server (I vaguely remember possibly<br>
> > needing prime collab?)?<br>
> ><br>
> ><br>
> ><br>
> > Maybe I?m missing some things, but what approach have you guys taken for<br>
> > softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> > (I know there?s the auto qos trust cisco-softphone for cisco switches,<br>
> but<br>
> > I don?t believe there?s a solution other than #1 for non-cisco switches)?<br>
> ><br>
> ><br>
> ><br>
> > *Ben Amick*<br>
> ><br>
> > Telecom Analyst<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Confidentiality Note: This message is intended for use only by the<br>
> > individual or entity to which it is addressed and may contain information<br>
> > that is privileged, confidential, and exempt from disclosure under<br>
> > applicable law. If the reader of this message is not the intended<br>
> recipient<br>
> > or the employee or agent responsible for delivering the message to the<br>
> > intended recipient, you are hereby notified that any dissemination,<br>
> > distribution or copying of this communication is strictly prohibited. If<br>
> > you have received this communication in error, please contact the sender<br>
> > immediately and destroy the material in its entirety, whether electronic<br>
> or<br>
> > hard copy. Thank you<br>
> ><br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > cisco-voip@puck.nether.net<br>
> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > <http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
> ><br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > cisco-voip@puck.nether.net<br>
> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> > <http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
> ><br>
> ><br>
> > Confidentiality Note: This message is intended for use only by the<br>
> > individual or entity to which it is addressed and may contain information<br>
> > that is privileged, confidential, and exempt from disclosure under<br>
> > applicable law. If the reader of this message is not the intended<br>
> recipient<br>
> > or the employee or agent responsible for delivering the message to the<br>
> > intended recipient, you are hereby notified that any dissemination,<br>
> > distribution or copying of this communication is strictly prohibited. If<br>
> > you have received this communication in error, please contact the sender<br>
> > immediately and destroy the material in its entirety, whether electronic<br>
> or<br>
> > hard copy. Thank you<br>
> ><br>
> ><br>
> > Confidentiality Note: This message is intended for use only by the<br>
> > individual or entity to which it is addressed and may contain information<br>
> > that is privileged, confidential, and exempt from disclosure under<br>
> > applicable law. If the reader of this message is not the intended<br>
> recipient<br>
> > or the employee or agent responsible for delivering the message to the<br>
> > intended recipient, you are hereby notified that any dissemination,<br>
> > distribution or copying of this communication is strictly prohibited. If<br>
> > you have received this communication in error, please contact the sender<br>
> > immediately and destroy the material in its entirety, whether electronic<br>
> or<br>
> > hard copy. Thank you<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > cisco-voip mailing list<br>
> > cisco-voip@puck.nether.net<br>
> > <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> ><br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170103/3e0b8690/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 14<br>
> Date: Wed, 4 Jan 2017 04:12:13 +0000<br>
> From: Tim Warnock <timoid@timoid.org><br>
> To: "'cisco-voip@puck.nether.net'" <cisco-voip@puck.nether.net><br>
> Subject: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
> Message-ID:<br>
> <C978DD0EE401174299AA691E12A5025616A30C49@hermes.timoid.lan><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> Hi,<br>
><br>
> Does anyone know how to either:<br>
><br>
> A) Turn a 7921G-W-K9 -> 7291G-A-K9 or<br>
> B) Disable the 7921G's reliance on country information being advertised<br>
> via 802.11d<br>
><br>
> It appears the World version needs 802.11d functioning in order to connect<br>
> to the AP, and the AP in question doesn't support 802.11d<br>
><br>
> Or suggest a suitable replacement (7921G is EOL)?<br>
><br>
> Thanks<br>
> -]Tim.<br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 15<br>
> Date: Wed, 4 Jan 2017 16:18:28 +0000<br>
> From: Ben Amick <bamick@HumanArc.com><br>
> To: Evgeny Izetov <eizetov@gmail.com>, Ryan Huff<br>
> <ryanhuff@outlook.com><br>
> Cc: Cisco VoIP Group <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <820C24BFE55F434C97807C60D4647ACE0F9DE1E2@E2k10-MB-HT1.<br>
> humanarc.com><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> Evgeny,<br>
> That?s great, and I was able to find the PDF from the session but I can?t<br>
> seem to remember how to find the site that has the recordings of the<br>
> sessions ? could you provide a link to that?<br>
><br>
> Ryan,<br>
> That sounds like a solid idea for when QoS is absolutely absolutely<br>
> necessary, but I have nowhere near enough MTP resources to do that for all<br>
> the softphones in my org.<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Evgeny Izetov [<a href="mailto:eizetov@gmail.com">mailto:eizetov@gmail.com</a>]<br>
> Sent: Tuesday, January 03, 2017 10:15 PM<br>
> To: Ryan Huff <ryanhuff@outlook.com><br>
> Cc: Ben Amick <bamick@HumanArc.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> I saw a CiscoLive! session recently that seemed to recommend the ports and<br>
> access-lists approach. The idea is that you can now specify separate port<br>
> ranges for audio and video in SIP Profile. The session goes quite in depth<br>
> and is worth the watch:<br>
><br>
> BRKCOL-2616 - QoS Strategies and Smart Media Techniques for Collaboration<br>
> Deployments (2016 Berlin) - 2 Hours<br>
><br>
> On Tue, Jan 3, 2017 at 9:49 PM, Ryan Huff <ryanhuff@outlook.com<mailto:r<br>
> yanhuff@outlook.com>> wrote:<br>
> I see; while this is by no means a complete solution, it may help. I'm<br>
> assuming Cisco based soft phones (CIPC, CSF, BOT, TAB ... etc).<br>
><br>
> You may try Trusted Relay Points (set in the device level configuration).<br>
> This does rely and depend on your media resource architecture and design;<br>
> i.e. you'll need to have media resources that support TRP available.<br>
><br>
> Using TRP on the device config for a soft phone will cause CUCM to<br>
> dynamically insert an MTP in the call flow which will allow for adherence<br>
> to QOS trust policies and offer a predetermined network path for call flows<br>
> in an otherwise untrusted network (presumably, the data network).<br>
> -Ryan<br>
><br>
><br>
><br>
> Sent from my iPhone<br>
> On Jan 3, 2017, at 9:30 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> Only for softphones. Currently most of our servers live on the same LAN as<br>
> end users, so yeah. Hardphones have their own VLAN so its not as bad. In<br>
> the future it won?t be that way but for the time being it is.<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 9:18 PM<br>
> To: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>><br>
> Cc: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>>; Cisco VoIP<br>
> Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> Ben,<br>
><br>
> By flat network; I am to assume that there is no layer 2 partition between<br>
> rtp/signaling and general data traffic?<br>
><br>
> On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> Yeah, I have the luck of having MPLS right now, and I don?t see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn?t<br>
> my issue, it?s QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe *cough*developers*cough* seems to have<br>
> made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we?re having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 8:40 PM<br>
> To: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>><br>
> Cc: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>>; Cisco<br>
> VoIP Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
> Or take the most approach of do nothing.<br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
> So, I know this is an age old question that?s debated, but I?ve been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn?t applicable with softphones.<br>
><br>
> I?ve heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
> Maybe I?m missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there?s the auto qos trust cisco-softphone for cisco switches, but<br>
> I don?t believe there?s a solution other than #1 for non-cisco switches)?<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndy1J5xVBwQsCzBMsCrKrhhpvpj7<br>
> 3AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndA<br>
> SRtxIrsKrud7bPBD7D-LOryrPPXWvnKnjh7cYMed7aqbz0XG8<br>
> FHnjlKOeVkffGhBrwqrhdICXYyevvjvuhjsdTdAVPmEBCbdSaY3ivNU6U9GX<br>
> 33VkDa3JsJaBGBPdpb6_AaveFA54hfBPqrMVBAS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQ<br>
> b2hEwS21Ew0uEMrpsdwmX6sqwk><br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/f48be809/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 16<br>
> Date: Wed, 4 Jan 2017 16:27:26 +0000<br>
> From: Lelio Fulgenzi <lelio@uoguelph.ca><br>
> To: Ben Amick <bamick@HumanArc.com>, Evgeny Izetov<br>
> <eizetov@gmail.com>, "Ryan Huff" <ryanhuff@outlook.com><br>
> Cc: Cisco VoIP Group <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <YTOPR01MB02513B7A153261166E291393AC610@YTOPR01MB0251.<br>
> CANPRD01.PROD.OUTLOOK.COM><br>
><br>
> Content-Type: text/plain; charset="windows-1252"<br>
><br>
> I would have loved to do MTP resources across the board... helps with<br>
> security as well, less holes to open up. But I found a few features that<br>
> wouldn't work, like desktop sharing, etc. If they supported all features<br>
> with MTP, I'd would have likely been able to justify a couple of routers to<br>
> do it.<br>
><br>
><br>
> ---<br>
> Lelio Fulgenzi, B.A.<br>
> Senior Analyst, Network Infrastructure<br>
> Computing and Communications Services (CCS)<br>
> University of Guelph<br>
><br>
> 519-824-4120 Ext 56354<br>
> lelio@uoguelph.ca<br>
> <a href="http://www.uoguelph.ca/ccs">www.uoguelph.ca/ccs</a><br>
> Room 037, Animal Science and Nutrition Building<br>
> Guelph, Ontario, N1G 2W1<br>
><br>
><br>
> ________________________________<br>
> From: cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Ben<br>
> Amick <bamick@HumanArc.com><br>
> Sent: Wednesday, January 4, 2017 11:18 AM<br>
> To: Evgeny Izetov; Ryan Huff<br>
> Cc: Cisco VoIP Group<br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
> Evgeny,<br>
><br>
> That?s great, and I was able to find the PDF from the session but I can?t<br>
> seem to remember how to find the site that has the recordings of the<br>
> sessions ? could you provide a link to that?<br>
><br>
><br>
><br>
> Ryan,<br>
><br>
> That sounds like a solid idea for when QoS is absolutely absolutely<br>
> necessary, but I have nowhere near enough MTP resources to do that for all<br>
> the softphones in my org.<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> From: Evgeny Izetov [<a href="mailto:eizetov@gmail.com">mailto:eizetov@gmail.com</a>]<br>
> Sent: Tuesday, January 03, 2017 10:15 PM<br>
> To: Ryan Huff <ryanhuff@outlook.com><br>
> Cc: Ben Amick <bamick@HumanArc.com>; Cisco VoIP Group <<br>
> cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> I saw a CiscoLive! session recently that seemed to recommend the ports and<br>
> access-lists approach. The idea is that you can now specify separate port<br>
> ranges for audio and video in SIP Profile. The session goes quite in depth<br>
> and is worth the watch:<br>
><br>
> BRKCOL-2616 - QoS Strategies and Smart Media Techniques for Collaboration<br>
> Deployments (2016 Berlin) - 2 Hours<br>
><br>
><br>
><br>
> On Tue, Jan 3, 2017 at 9:49 PM, Ryan Huff <ryanhuff@outlook.com<mailto:r<br>
> yanhuff@outlook.com>> wrote:<br>
><br>
> I see; while this is by no means a complete solution, it may help. I'm<br>
> assuming Cisco based soft phones (CIPC, CSF, BOT, TAB ... etc).<br>
><br>
><br>
><br>
> You may try Trusted Relay Points (set in the device level configuration).<br>
> This does rely and depend on your media resource architecture and design;<br>
> i.e. you'll need to have media resources that support TRP available.<br>
><br>
><br>
><br>
> Using TRP on the device config for a soft phone will cause CUCM to<br>
> dynamically insert an MTP in the call flow which will allow for adherence<br>
> to QOS trust policies and offer a predetermined network path for call flows<br>
> in an otherwise untrusted network (presumably, the data network).<br>
><br>
> -Ryan<br>
><br>
><br>
><br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 9:30 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> Only for softphones. Currently most of our servers live on the same LAN as<br>
> end users, so yeah. Hardphones have their own VLAN so its not as bad. In<br>
> the future it won?t be that way but for the time being it is.<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 9:18 PM<br>
> To: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>><br>
> Cc: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>>; Cisco VoIP<br>
> Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> Ben,<br>
><br>
><br>
><br>
> By flat network; I am to assume that there is no layer 2 partition between<br>
> rtp/signaling and general data traffic?<br>
><br>
> On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> Yeah, I have the luck of having MPLS right now, and I don?t see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn?t<br>
> my issue, it?s QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe *cough*developers*cough* seems to have<br>
> made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we?re having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 8:40 PM<br>
> To: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>><br>
> Cc: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>>; Cisco<br>
> VoIP Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
><br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
><br>
> Or take the most approach of do nothing.<br>
><br>
><br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
><br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> So, I know this is an age old question that?s debated, but I?ve been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn?t applicable with softphones.<br>
><br>
><br>
><br>
> I?ve heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
><br>
><br>
> Maybe I?m missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there?s the auto qos trust cisco-softphone for cisco switches, but<br>
> I don?t believe there?s a solution other than #1 for non-cisco switches)?<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndy1J5xVBwQsCzBMsCrKrhhpvpj7<br>
> 3AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndA<br>
> SRtxIrsKrud7bPBD7D-LOryrPPXWvnKnjh7cYMed7aqbz0XG8<br>
> FHnjlKOeVkffGhBrwqrhdICXYyevvjvuhjsdTdAVPmEBCbdSaY3ivNU6U9GX<br>
> 33VkDa3JsJaBGBPdpb6_AaveFA54hfBPqrMVBAS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQ<br>
> b2hEwS21Ew0uEMrpsdwmX6sqwk><br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/2b838324/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 17<br>
> Date: Wed, 4 Jan 2017 16:44:52 +0000<br>
> From: Ryan Huff <ryanhuff@outlook.com><br>
> To: Lelio Fulgenzi <lelio@uoguelph.ca><br>
> Cc: Ben Amick <bamick@HumanArc.com>, Evgeny Izetov<br>
> <eizetov@gmail.com>, "Cisco VoIP Group" <<br>
> cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
> Message-ID:<br>
> <BLUPR18MB04820F67E5FD6398C9952F36C5610@BLUPR18MB0482.<br>
> namprd18.prod.outlook.com><br>
><br>
> Content-Type: text/plain; charset="windows-1252"<br>
><br>
> Yes, TRP does have some drawbacks; video, binary floor control BUT, works<br>
> great for voice media. It's a heavy overhead and isn't a complete solution<br>
> but works in a pinch if you're dealing with some C Level users that "just<br>
> want the computer phone to work".<br>
><br>
> I have also been known to swap out the network card in user pcs for dual<br>
> interface cards, then use a persistent route in the PC to force the soft<br>
> phone's traffic to its call control server out of one interface that is on<br>
> the voice network (leaving the other interface on the data network).<br>
><br>
> A crude solution, but it worked well in a situation where the networking<br>
> gear wouldn't have supported what we would've needed to do with QOS. Dual<br>
> port PC network cards, even in bulk, are a heck of a lot cheaper than new<br>
> networking gear.<br>
><br>
> Yikes, giving myself flashbacks from rehashing all these memories of being<br>
> a network admin for a nonprofit .... need some coffee ....<br>
><br>
> On Jan 4, 2017, at 11:27 AM, Lelio Fulgenzi <lelio@uoguelph.ca<mailto:leli<br>
> o@uoguelph.ca>> wrote:<br>
><br>
><br>
> I would have loved to do MTP resources across the board... helps with<br>
> security as well, less holes to open up. But I found a few features that<br>
> wouldn't work, like desktop sharing, etc. If they supported all features<br>
> with MTP, I'd would have likely been able to justify a couple of routers to<br>
> do it.<br>
><br>
><br>
> ---<br>
> Lelio Fulgenzi, B.A.<br>
> Senior Analyst, Network Infrastructure<br>
> Computing and Communications Services (CCS)<br>
> University of Guelph<br>
><br>
> 519-824-4120 Ext 56354<br>
> lelio@uoguelph.ca<<a href="mailto:lelio@uoguelph.ca">mailto:lelio@uoguelph.ca</a>><br>
> www.uoguelph.ca/ccs<<a href="http://www.uoguelph.ca/ccs">http://www.uoguelph.ca/ccs</a>><br>
> Room 037, Animal Science and Nutrition Building<br>
> Guelph, Ontario, N1G 2W1<br>
><br>
><br>
> ________________________________<br>
> From: cisco-voip <cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-<br>
> bounces@puck.nether.net>> on behalf of Ben Amick <bamick@HumanArc.com<br>
> <<a href="mailto:bamick@HumanArc.com">mailto:bamick@HumanArc.com</a>>><br>
> Sent: Wednesday, January 4, 2017 11:18 AM<br>
> To: Evgeny Izetov; Ryan Huff<br>
> Cc: Cisco VoIP Group<br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
> Evgeny,<br>
><br>
> That?s great, and I was able to find the PDF from the session but I can?t<br>
> seem to remember how to find the site that has the recordings of the<br>
> sessions ? could you provide a link to that?<br>
><br>
><br>
><br>
> Ryan,<br>
><br>
> That sounds like a solid idea for when QoS is absolutely absolutely<br>
> necessary, but I have nowhere near enough MTP resources to do that for all<br>
> the softphones in my org.<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> From: Evgeny Izetov [<a href="mailto:eizetov@gmail.com">mailto:eizetov@gmail.com</a>]<br>
> Sent: Tuesday, January 03, 2017 10:15 PM<br>
> To: Ryan Huff <ryanhuff@outlook.com<mailto:ryanhuff@outlook.com>><br>
> Cc: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>>; Cisco<br>
> VoIP Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> I saw a CiscoLive! session recently that seemed to recommend the ports and<br>
> access-lists approach. The idea is that you can now specify separate port<br>
> ranges for audio and video in SIP Profile. The session goes quite in depth<br>
> and is worth the watch:<br>
><br>
> BRKCOL-2616 - QoS Strategies and Smart Media Techniques for Collaboration<br>
> Deployments (2016 Berlin) - 2 Hours<br>
><br>
><br>
><br>
> On Tue, Jan 3, 2017 at 9:49 PM, Ryan Huff <ryanhuff@outlook.com<mailto:r<br>
> yanhuff@outlook.com>> wrote:<br>
><br>
> I see; while this is by no means a complete solution, it may help. I'm<br>
> assuming Cisco based soft phones (CIPC, CSF, BOT, TAB ... etc).<br>
><br>
><br>
><br>
> You may try Trusted Relay Points (set in the device level configuration).<br>
> This does rely and depend on your media resource architecture and design;<br>
> i.e. you'll need to have media resources that support TRP available.<br>
><br>
><br>
><br>
> Using TRP on the device config for a soft phone will cause CUCM to<br>
> dynamically insert an MTP in the call flow which will allow for adherence<br>
> to QOS trust policies and offer a predetermined network path for call flows<br>
> in an otherwise untrusted network (presumably, the data network).<br>
><br>
> -Ryan<br>
><br>
><br>
><br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 9:30 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> Only for softphones. Currently most of our servers live on the same LAN as<br>
> end users, so yeah. Hardphones have their own VLAN so its not as bad. In<br>
> the future it won?t be that way but for the time being it is.<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 9:18 PM<br>
> To: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>><br>
> Cc: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>>; Cisco VoIP<br>
> Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> Ben,<br>
><br>
><br>
><br>
> By flat network; I am to assume that there is no layer 2 partition between<br>
> rtp/signaling and general data traffic?<br>
><br>
> On Jan 3, 2017, at 9:15 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> Yeah, I have the luck of having MPLS right now, and I don?t see us going<br>
> iWAN for a while for various reasons. QoS on the WAN right now even isn?t<br>
> my issue, it?s QoS on the LAN. Right now we have a relatively flat network,<br>
> and certain segments of our troupe *cough*developers*cough* seems to have<br>
> made our internal traffic ugly, to the point that I may have to do an<br>
> analysis of it, as we?re having just random periods here and there where<br>
> calls just have horrible quality, of the type you normally see fixed by QoS<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> From: Ryan Huff [<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>]<br>
> Sent: Tuesday, January 03, 2017 8:40 PM<br>
> To: NateCCIE <nateccie@gmail.com<mailto:nateccie@gmail.com>><br>
> Cc: Ben Amick <bamick@HumanArc.com<mailto:bamick@HumanArc.com>>; Cisco<br>
> VoIP Group <cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>><br>
> Subject: Re: [cisco-voip] Jabber/CIPC and QoS<br>
><br>
><br>
><br>
> It's a shame really ... MPLS is far superior IMO, for many reasons. Call<br>
> it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public<br>
> Internet.<br>
><br>
><br>
><br>
> Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a<br>
> public Comcast or Time Warner/Charter package.<br>
><br>
> On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie@gmail.com<mailto:nat<br>
> eccie@gmail.com>> wrote:<br>
><br>
> Or take the most approach of do nothing.<br>
><br>
><br>
><br>
> My personal favorite is to use codecs where QoS matters less, like iLBC,<br>
> OPUS, etc.<br>
><br>
><br>
><br>
> So many business are getting rid of the QoS capable WAN and just doing<br>
> VPNs, even if they have fancy names that make it sound better than public<br>
> internet.<br>
><br>
> Sent from my iPhone<br>
><br>
> On Jan 3, 2017, at 2:25 PM, Ben Amick <bamick@HumanArc.com<mailto:ba<br>
> mick@HumanArc.com>> wrote:<br>
><br>
> So, I know this is an age old question that?s debated, but I?ve been<br>
> wondering if anyone here has a perspective here in regards to QoS for<br>
> softphones. Obviously, with hardphones, you usually partition a separate<br>
> VLAN with AutoQoS/DSCP tags, but that isn?t applicable with softphones.<br>
><br>
><br>
><br>
> I?ve heard of three different options in the past, neither of which seem<br>
> to be very simple to deploy, but all seem to be Jabber-centric.<br>
><br>
> 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on<br>
> the switches they are connected to, as well as trusting the device.<br>
> Problems: Requires users to be local admins, openings for abuse and network<br>
> impact due to blind PC trust.<br>
><br>
> 2. Configuring your switches with an access list that recognizes the<br>
> ports Jabber does outbound to attach DSCP tags to them. Problems: Other<br>
> programs could theoretically use those ports<br>
><br>
> 3. Installing Medianet services on all jabber clients; Configure all<br>
> switches for medianet tagging. Problem: (I think?) Requires newer switches<br>
> to use, maybe needs an additional server (I vaguely remember possibly<br>
> needing prime collab?)?<br>
><br>
><br>
><br>
> Maybe I?m missing some things, but what approach have you guys taken for<br>
> softphone/Jabber QoS? And on top of that, what options are there for CIPC<br>
> (I know there?s the auto qos trust cisco-softphone for cisco switches, but<br>
> I don?t believe there?s a solution other than #1 for non-cisco switches)?<br>
><br>
><br>
><br>
> Ben Amick<br>
><br>
> Telecom Analyst<br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQk<br>
> mnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzr<br>
> BPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-<br>
> F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2<br>
> rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-<br>
> e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpv<br>
> pj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdK<br>
> ndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5d<br>
> qWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY<br>
> 3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-<br>
> Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip%3cht">https://puck.nether.net/mailman/listinfo/cisco-voip<ht</a><br>
> tp://cp.mcafee.com/d/avndy1J5xVBwQsCzBMsCrKrhhpvpj7<br>
> 3AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndA<br>
> SRtxIrsKrud7bPBD7D-LOryrPPXWvnKnjh7cYMed7aqbz0XG8<br>
> FHnjlKOeVkffGhBrwqrhdICXYyevvjvuhjsdTdAVPmEBCbdSaY3ivNU6U9GX<br>
> 33VkDa3JsJaBGBPdpb6_AaveFA54hfBPqrMVBAS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQ<br>
> b2hEwS21Ew0uEMrpsdwmX6sqwk><br>
><br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <https://puck.nether.net/pipermail/cisco-voip/<br>
> attachments/20170104/640d3962/attachment-0001.html><br>
><br>
> ------------------------------<br>
><br>
> Message: 18<br>
> Date: Wed, 4 Jan 2017 13:31:15 +0000<br>
> From: Ben Amick <bamick@HumanArc.com><br>
> To: Tim Warnock <timoid@timoid.org>, "'cisco-voip@puck.nether.net'"<br>
> <cisco-voip@puck.nether.net><br>
> Subject: Re: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
> Message-ID:<br>
> <820C24BFE55F434C97807C60D4647ACE0F9DE0F3@E2k10-MB-HT1.<br>
> humanarc.com><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> I don't know about the issue with 802.11d, but the 7925/7926(+barcode<br>
> scanner) is not EoL and is the successor in the same series. However, the<br>
> newest wireless phone that they want us all to move to is the 8821.<br>
><br>
> Ben Amick<br>
> Telecom Analyst<br>
><br>
><br>
> -----Original Message-----<br>
> From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of<br>
> Tim Warnock<br>
> Sent: Tuesday, January 03, 2017 11:12 PM<br>
> To: 'cisco-voip@puck.nether.net' <cisco-voip@puck.nether.net><br>
> Subject: [cisco-voip] 7921g-w-k9 -> 7921g-a-k9<br>
><br>
> Hi,<br>
><br>
> Does anyone know how to either:<br>
><br>
> A) Turn a 7921G-W-K9 -> 7291G-A-K9 or<br>
> B) Disable the 7921G's reliance on country information being advertised<br>
> via 802.11d<br>
><br>
> It appears the World version needs 802.11d functioning in order to connect<br>
> to the AP, and the AP in question doesn't support 802.11d<br>
><br>
> Or suggest a suitable replacement (7921G is EOL)?<br>
><br>
> Thanks<br>
> -]Tim.<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> <a href="http://cp.mcafee.com/d/1jWVIe4wUpdEIfcLTphsudTdEEILIF">http://cp.mcafee.com/d/1jWVIe4wUpdEIfcLTphsudTdEEILIF</a><br>
> zxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbC<br>
> OrqKMSdKndKIK3HeffZvAm4rILfZuVtdBxDAS3hOC-UeWyaqRQRrCzB_BgY-<br>
> F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJa<br>
> BGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jqrPb1IQJSBiRiVCIBziWq8<br>
> 1NEVjh8BP1sGqejh0nd7NEw76zBd4ynQKld79JAsr9cjU<br>
><br>
><br>
> Confidentiality Note: This message is intended for use only by the<br>
> individual or entity to which it is addressed and may contain information<br>
> that is privileged, confidential, and exempt from disclosure under<br>
> applicable law. If the reader of this message is not the intended recipient<br>
> or the employee or agent responsible for delivering the message to the<br>
> intended recipient, you are hereby notified that any dissemination,<br>
> distribution or copying of this communication is strictly prohibited. If<br>
> you have received this communication in error, please contact the sender<br>
> immediately and destroy the material in its entirety, whether electronic or<br>
> hard copy. Thank you<br>
><br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of cisco-voip Digest, Vol 159, Issue 4<br>
> ******************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/e694f330/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/e694f330/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Thu, 5 Jan 2017 09:13:34 -0500<br>
From: David Zhars <dzhars@gmail.com><br>
To: "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><br>
Subject: [cisco-voip] User Address Book<br>
Message-ID:<br>
<CADe=jTFKZCNZ4cOcaAL1ujRy3vzevLaNY_GWGadD_98R3d-85A@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Wow, it's been awhile since anyone asked for this...<br>
<br>
I have a user who wants to be able to go to a webpage and enter his<br>
personal address book and make it available on his desktop phone (7942, UCM<br>
8).<br>
<br>
I can't even remember the URL for this....<br>
<br>
Someone dope-slap me please.<br>
<br>
Thanks,<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/3dd468b0/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/3dd468b0/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Thu, 5 Jan 2017 14:20:36 +0000<br>
From: "Sean E. Knight" <sean@14west.us><br>
To: David Zhars <dzhars@gmail.com>, "cisco-voip@puck.nether.net"<br>
<cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] User Address Book<br>
Message-ID:<br>
<1a150d27b52647f1b9417ff41de88406@SV-EXMB2013-P2.agora.local><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<a href="https://ServerIP:8443/ccmuser">https://ServerIP:8443/ccmuser</a><br>
<br>
<br>
From: cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] On Behalf Of David Zhars<br>
Sent: Thursday, January 05, 2017 9:14 AM<br>
To: cisco-voip@puck.nether.net<br>
Subject: [cisco-voip] User Address Book<br>
<br>
Wow, it's been awhile since anyone asked for this...<br>
I have a user who wants to be able to go to a webpage and enter his personal address book and make it available on his desktop phone (7942, UCM 8).<br>
I can't even remember the URL for this....<br>
Someone dope-slap me please.<br>
Thanks,<br>
<br>
<br>
Sean E. Knight<br>
Network and Telecommunications Administrator<br>
sean@14west.us<<a href="mailto:sean@14west.us">mailto:sean@14west.us</a>><br>
410-864-1805<br>
<br>
<<a href="http://www.agora-inc.com/%3e%5bcid:image40a98c.JPG@c59398cb.41a132e4%5d%3chttps:/internal-14west.icims.com/">http://www.agora-inc.com/>[cid:image40a98c.JPG@c59398cb.41a132e4]<https://internal-14west.icims.com/</a>><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/ae7ece7c/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/ae7ece7c/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image40a98c.JPG<br>
Type: image/jpeg<br>
Size: 12830 bytes<br>
Desc: image40a98c.JPG<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/ae7ece7c/attachment-0001.jpe">https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/ae7ece7c/attachment-0001.jpe</a>><br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Thu, 5 Jan 2017 09:20:51 -0500<br>
From: Brian Meade <bmeade90@vt.edu><br>
To: David Zhars <dzhars@gmail.com><br>
Cc: "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] User Address Book<br>
Message-ID:<br>
<CAGcuYh1zGeC+fbKYKunv2C5MYjpGn5Tx7MeB9xTm7unJYkr2fw@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I think you can see it in the user self care portal.<br>
<a href="https://x.x.x.x/ccmuser">https://x.x.x.x/ccmuser</a><br>
<br>
<br>
On Thu, Jan 5, 2017 at 9:13 AM, David Zhars <dzhars@gmail.com> wrote:<br>
<br>
> Wow, it's been awhile since anyone asked for this...<br>
><br>
> I have a user who wants to be able to go to a webpage and enter his<br>
> personal address book and make it available on his desktop phone (7942, UCM<br>
> 8).<br>
><br>
> I can't even remember the URL for this....<br>
><br>
> Someone dope-slap me please.<br>
><br>
> Thanks,<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> cisco-voip@puck.nether.net<br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/007a4565/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/007a4565/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Thu, 5 Jan 2017 09:46:13 -0500<br>
From: David Zhars <dzhars@gmail.com><br>
To: Brian Meade <bmeade90@vt.edu><br>
Cc: "cisco-voip@puck.nether.net" <cisco-voip@puck.nether.net><br>
Subject: Re: [cisco-voip] User Address Book<br>
Message-ID:<br>
<CADe=jTF5OOa9Ji4kLn1wXjw_LSp-eCm22xD5pr8Sc=nAiAH2OQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
D'oh!<br>
<br>
Thank you!<br>
<br>
On Thu, Jan 5, 2017 at 9:20 AM, Brian Meade <bmeade90@vt.edu> wrote:<br>
<br>
> I think you can see it in the user self care portal.<br>
> <a href="https://x.x.x.x/ccmuser">https://x.x.x.x/ccmuser</a><br>
><br>
><br>
> On Thu, Jan 5, 2017 at 9:13 AM, David Zhars <dzhars@gmail.com> wrote:<br>
><br>
>> Wow, it's been awhile since anyone asked for this...<br>
>><br>
>> I have a user who wants to be able to go to a webpage and enter his<br>
>> personal address book and make it available on his desktop phone (7942, UCM<br>
>> 8).<br>
>><br>
>> I can't even remember the URL for this....<br>
>><br>
>> Someone dope-slap me please.<br>
>><br>
>> Thanks,<br>
>><br>
>> _______________________________________________<br>
>> cisco-voip mailing list<br>
>> cisco-voip@puck.nether.net<br>
>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>><br>
>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/3e2ab959/attachment-0001.html">https://puck.nether.net/pipermail/cisco-voip/attachments/20170105/3e2ab959/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
cisco-voip@puck.nether.net<br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
<br>
------------------------------<br>
<br>
End of cisco-voip Digest, Vol 159, Issue 5<br>
******************************************<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:Calibri;color:black"><img border="0" width="1035" height="101" id="_x0000_i1027" src="https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/0fd3ed36/attachment-0001.png"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>