<div dir="ltr">I don't think it's that simple Ryan.<div><br></div><div><div>The first and most important document is the Enterprise Mobility Design Guide</div><div><br></div><div>Reference Link:</div><div><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">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></div><div><br></div><div>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:</div><div><br></div><div><a href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/Jabber_in_WLAN/b_Jabber_in_WLAN.html">http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/Jabber_in_WLAN/b_Jabber_in_WLAN.html</a></div><div><br></div><div>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.</div><div><br></div><div>Reference Link:</div><div><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">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></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 12, 2016 at 1:22 PM, Ryan Ratliff (rratliff) <span dir="ltr"><<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
The difference between computers and 7925s primarily being that one walks down the hall and the other sits on a desk.
<div>If you can keep the PC from roaming then it’s just a matter of proper QOS and available bandwidth, yes?</div><span class="HOEnZb"><font color="#888888">
</font></span><div><span class="HOEnZb"><font color="#888888"><br>
<div>-Ryan </div></font></span><div><div class="h5">
<br>
<div>
<div>On May 12, 2016, at 2:18 PM, NateCCIE <<a href="mailto:nateccie@gmail.com" target="_blank">nateccie@gmail.com</a>> wrote:</div>
<br>
<div>
<div dir="auto">
<div>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</div>
<div><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:<br>
<br>
</div>
<blockquote type="cite">
<div>I’ll take a slight issue with the original response about CIPC not being stable over wireless.
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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. </div>
<div>The apps themselves can handle the transport just fine, it’s the network that sometimes can’t handle the apps. </div>
<div><br>
<div>-Ryan </div>
<br>
<div>
<div>On May 12, 2016, at 7:23 AM, Thomas LeMay <<a href="mailto:thomaslemay@comcast.net" target="_blank">thomaslemay@comcast.net</a>> wrote:</div>
<br>
<div>
<div style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Hi, Ryan,<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thank you for the information.<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Tom<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div>
<div>
<div style="border-style:solid none none;border-top-color:rgb(181,196,223);border-top-width:1pt;padding:3pt 0in 0in">
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"><span> </span>Ryan Huff [<a href="mailto:ryanhuff@outlook.com" target="_blank">mailto:ryanhuff@outlook.com</a>]<span> </span><br>
<b>Sent:</b><span> </span>Wednesday, May 11, 2016 11:15 PM<br>
<b>To:</b><span> </span>Thomas LeMay; 'Ryan Burtch'; 'Nick Barnett'<br>
<b>Cc:</b><span> </span>'Cisco VoIP Group'<br>
<b>Subject:</b><span> </span>Re: [cisco-voip] [cisco-VoIP] UCCE agents on wireless IP Communicator?<u></u><u></u></span></div>
</div>
</div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<u></u> <u></u></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color: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 ...<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color: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).<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color: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> </span><u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color: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).<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif">Thanks,<u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div>
<div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif">= Ryan =<u></u><u></u></span></div>
</div>
</div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></div>
<div>
<div class="MsoNormal" align="center" style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;text-align:center;background-color:white;background-position:initial initial;background-repeat:initial initial">
<span style="font-family:Calibri,sans-serif">
<hr size="2" width="98%" align="center">
</span></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span>cisco-voip <<a href="mailto:cisco-voip-bounces@puck.nether.net" style="color:purple;text-decoration:underline" target="_blank">cisco-voip-bounces@puck.nether.net</a>>
on behalf of Thomas LeMay <<a href="mailto:thomaslemay@comcast.net" style="color:purple;text-decoration:underline" target="_blank">thomaslemay@comcast.net</a>><br>
<b>Sent:</b><span> </span>Wednesday, May 11, 2016 10:42 PM<br>
<b>To:</b><span> </span>'Ryan Burtch'; 'Nick Barnett'<br>
<b>Cc:</b><span> </span>'Cisco VoIP Group'<br>
<b>Subject:</b><span> </span>Re: [cisco-voip] [cisco-VoIP] UCCE agents on wireless IP Communicator?</span><span style="font-family:Calibri,sans-serif"><u></u><u></u></span></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-family:Calibri,sans-serif"> <u></u><u></u></span></div>
</div>
</div>
<div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">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><span><u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span><u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Tom</span><span><u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span><span><u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"><span> </span>cisco-voip [<a href="mailto:cisco-voip-bounces@puck.nether.net" style="color:purple;text-decoration:underline" target="_blank">mailto:cisco-voip-bounces@puck.nether.net</a>]<span> </span><b>On
Behalf Of<span> </span></b>Ryan Burtch<br>
<b>Sent:</b><span> </span>Wednesday, May 11, 2016 2:58 PM<br>
<b>To:</b><span> </span>Nick Barnett<br>
<b>Cc:</b><span> </span>Cisco VoIP Group<br>
<b>Subject:</b><span> </span>Re: [cisco-voip] UCCE agents on wireless IP Communicator?</span><span><u></u><u></u></span></div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>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></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span><br clear="all">
<u></u><u></u></span></div>
<div>
<div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>Sincerely,<u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>Ryan Burtch<u></u><u></u></span></div>
</div>
</div>
</div>
</div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>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" style="color:purple;text-decoration:underline" target="_blank">nicksbarnett@gmail.com</a>>
wrote:<u></u><u></u></span></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>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></span></div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>A cursory look at the 10.0 SRND didn't show any hits for "wired" or "wireless".<u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>thanks,<u></u><u></u></span></div>
</div>
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span>Nick<u></u><u></u></span></div>
</div>
</div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" style="color:purple;text-decoration:underline" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" style="color:purple;text-decoration:underline" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></span></div>
</div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif;background-color:white">
<span> <u></u><u></u></span></div>
</div>
</div>
</div>
</div>
</div>
</div>
<span style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">_______________________________________________</span><br style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">cisco-voip
mailing list</span><br style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span style="font-family:LucidaGrande;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span></div>
</div>
<br>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
</div>
</blockquote>
</div>
</div>
</div>
<br>
</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>