<div dir="ltr">Agreed :)</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><br><div><br></div><div><br></div><div>Sincerely,</div><div><br></div><div>Ryan Burtch</div></div></div></div>
<br><div class="gmail_quote">On Thu, May 12, 2016 at 4:59 PM, Norton, Mike <span dir="ltr"><<a href="mailto:mikenorton@pwsd76.ab.ca" target="_blank">mikenorton@pwsd76.ab.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-CA" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The thing people always seem to forget about Wi-Fi deployments is this:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">“This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not
cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.”<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">You have NO CONTROL over the Layer 1 medium and you share it with everybody. Pretending otherwise is futile.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-mn<u></u><u></u></span></p>
<p class="MsoNormal"><a name="m_8350003161475105985__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></a></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Ryan Ratliff (rratliff)<br>
<b>Sent:</b> May-12-16 1:27 PM<br>
<b>To:</b> Anthony Holloway <<a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>><br>
<b>Cc:</b> Cisco VoIP Group <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>></span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [cisco-voip] [cisco-VoIP] UCCE agents on wireless IP Communicator?<u></u><u></u></div></div><p></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I’m sure nothing in wireless is as simple as my tiny brain can comprehend :)
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">-Ryan <u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On May 12, 2016, at 2:58 PM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">I don't think it's that simple Ryan. <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">The first and most important document is the Enterprise Mobility Design Guide<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Reference Link:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide.html" target="_blank">http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-1/Enterprise-Mobility-8-1-Design-Guide/Enterprise_Mobility_8-1_Deployment_Guide.html</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">However, that document is really big and covers a lot more than just Jabber. When you get down to the topic at hand, a more manageable and bite sized version of that document can be read here:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/Jabber_in_WLAN/b_Jabber_in_WLAN.html" target="_blank">http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/Jabber_in_WLAN/b_Jabber_in_WLAN.html</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As a contrast, Jabber on a wired connection, is simply a matter of matching traffic flows from the client device (PC, Mac, mobile, etc.), and marking the packets. This allows us to maintain our trust boundary, but provide an exception
for the traffic flows matching Jabber.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Reference Link:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide_appendix_01111.html#CJAB_TK_DD601B77_00" target="_blank">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide_appendix_01111.html#CJAB_TK_DD601B77_00</a><u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Thu, May 12, 2016 at 1:22 PM, Ryan Ratliff (rratliff) <<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">The difference between computers and 7925s primarily being that one walks down the hall and the other sits on a desk.
<u></u><u></u></p>
<div>
<p class="MsoNormal">If you can keep the PC from roaming then it’s just a matter of proper QOS and available bandwidth, yes?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span><span style="color:#888888"><u></u> <u></u></span></span></p>
<div>
<p class="MsoNormal"><span style="color:#888888">-Ryan </span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On May 12, 2016, at 2:18 PM, NateCCIE <<a href="mailto:nateccie@gmail.com" target="_blank">nateccie@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">But I have yet to see a 7925 deployment that the end users are happy with. It is seemingly impossible for the wireless guys to get it perfect. <br>
<br>
Sent from my iPhone<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 12, 2016, at 10:29 AM, Ryan Ratliff (rratliff) <<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">I’ll take a slight issue with the original response about CIPC not being stable over wireless.
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I believe the intent of the response is that realtime voice and video over wireless can be a challenge for a wifi environment that isn’t designed specifically to handle it. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Personally I’ve used CIPC and now Jabber (as a softphone) for voice and video calls on my laptop both in the Cisco office and at home with very little issue. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">The apps themselves can handle the transport just fine, it’s the network that sometimes can’t handle the apps. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">-Ryan <u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On May 12, 2016, at 7:23 AM, Thomas LeMay <<a href="mailto:thomaslemay@comcast.net" target="_blank">thomaslemay@comcast.net</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi, Ryan,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Thank you for the information.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Tom</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Ryan Huff [<a href="mailto:ryanhuff@outlook.com" target="_blank">mailto:ryanhuff@outlook.com</a>] <br>
<b>Sent:</b> Wednesday, May 11, 2016 11:15 PM<br>
<b>To:</b> Thomas LeMay; 'Ryan Burtch'; 'Nick Barnett'<br>
<b>Cc:</b> 'Cisco VoIP Group'<br>
<b>Subject:</b> Re: [cisco-voip] [cisco-VoIP] UCCE agents on wireless IP Communicator?</span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif">Many moons ago in a land called Ohio, I rescued a small agent base from doing this ...</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif">Aside from the obvious QOS and reliable connection issues; in that client's case the agents would also occasionally want to use the speakerphone function without a
headset (PC Speaker / Mic) and without an HD/noise canceling mic this will usually inject audio artifacts from the speaker into the audio stream. The net effect is duplicated/mis understood DTMF (when using rtp-nte).</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif">If this is unavoidable though, and your client is going to travel this path despite all your warnings otherwise; I would recommend the agent's PC on a separate SSID
/ Interface from the Corporate SSID / Interface and put all the agent's PC traffic in the EF queue (or at least trust/mark the CIPC traffic) and make sure there is adequate radio coverage by each agent. </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif">If the client is looking at this as a telecommute option for employees, the issues are further exacerbated by the nature of having heterogeneous wireless connectivity
(unless the business standardizes and issues wireless devices to employees).</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif">Thanks,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif">= Ryan =</span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span style="font-family:"Calibri",sans-serif">
<hr size="2" width="98%" align="center">
</span></div>
<div>
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cisco-voip <<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank"><span style="color:purple">cisco-voip-bounces@puck.nether.net</span></a>>
on behalf of Thomas LeMay <<a href="mailto:thomaslemay@comcast.net" target="_blank"><span style="color:purple">thomaslemay@comcast.net</span></a>><br>
<b>Sent:</b> Wednesday, May 11, 2016 10:42 PM<br>
<b>To:</b> 'Ryan Burtch'; 'Nick Barnett'<br>
<b>Cc:</b> 'Cisco VoIP Group'<br>
<b>Subject:</b> Re: [cisco-voip] [cisco-VoIP] UCCE agents on wireless IP Communicator?</span><u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">How about Jabber? Is Jabber stable enough even though it does not support multiple lines? My thought would be no based on the same reason
for CIPC.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Tom</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank"><span style="color:purple">mailto:cisco-voip-bounces@puck.nether.net</span></a>] <b>On
Behalf Of </b>Ryan Burtch<br>
<b>Sent:</b> Wednesday, May 11, 2016 2:58 PM<br>
<b>To:</b> Nick Barnett<br>
<b>Cc:</b> Cisco VoIP Group<br>
<b>Subject:</b> Re: [cisco-voip] UCCE agents on wireless IP Communicator?</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">This is a terrible idea. CIPC not stable enough on wireless. Introduce VPN and this is a disaster waiting to happen.<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><br clear="all">
<u></u><u></u></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">Sincerely,<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">Ryan Burtch<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">On Tue, May 10, 2016 at 1:25 PM, Nick Barnett <<a href="mailto:nicksbarnett@gmail.com" title="Ctrl+Click or tap to follow the link" target="_blank"><span style="color:purple">nicksbarnett@gmail.com</span></a>> wrote:<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">Does anyone have any experiences running CIPC on wireless for UCCE agents? It sounds like a...um, bad idea to me. One of my customers is moving to this "design."<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">A cursory look at the 10.0 SRND didn't show any hits for "wired" or "wireless".<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">thanks,<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white">Nick<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank"><span style="color:purple">cisco-voip@puck.nether.net</span></a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank"><span style="color:purple">https://puck.nether.net/mailman/listinfo/cisco-voip</span></a><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"LucidaGrande",serif">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>