<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div>Hey Ben,</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Screen capture does use the same mechanics as file sharing; and file sharing (native) does not work over MRA.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">According to PDI, the GUI Jabber code in the Windows/Mac client allows you to manipulate the "captured" image into the chat window using the cross hair sizing tool (Windows/Mac client), but under the hood, the file is being transferred
via point 2 point ... which is why that, and file sharing do not work over MRA, because Jabber's point 2 point connection cannot successfully traverse a proxy connection natively; and that does make sense to me. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">If one were using WeBEx Connect IM Messenger (Jabber Cloud) and also used Expressway to allow for collaboration edge call control, this wouldn't be an issue because the P2P connection would not be traversing Expressway, rather between
the client and WebEx cloud.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Termed "IM-Only Screen Share", does seem to sound more like remote screen control but could also be "IM-Only = non-interactive screen share", or in other words, screen capture.</div>
<div id="AppleMailSignature"><br>
This is where Cisco's inconsistent Jabber client and documentation experience comes into play; it should have been a single consistent experience across all devices (some would / will argue that is part of what Spark is about).</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">-Ryan</div>
<div><br>
On May 12, 2017, at 10:49 AM, Ben Amick <<a href="mailto:bamick@HumanArc.com">bamick@HumanArc.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Garamond",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Garamond",serif;color:#1F497D">Personally, I don’t read that line as that feature. IM-only screen
<b>share</b> I believe would imply the RDP-based live presenting instead of the in-call BFCP stream. Screen capture should theoretically be identical to the file transfer feature, so the fact that it doesn’t work is very strange. Can you copy-paste images from
windows snipping tool into the text box in MRA? That should theoretically be the same kind of data since it’s an in-stream picture with text.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Garamond",serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3B3838">Ben Amick<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#3B3838">Telecom Analyst</span><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#666666"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Garamond",serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><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">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Ryan Huff<br>
<b>Sent:</b> Friday, May 12, 2017 9:56 AM<br>
<b>To:</b> Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Jabber Screen share over MRA<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Nice find! Thank you! An odd thing to take a vendor to task over, but when screen captures are important ... I guess they are important.<br>
<br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 12, 2017, at 9:52 AM, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Found it. Not that it shouldn't have been easier to find, or logically grouped with the limitations in the release notes, but you know...it's Cisco documentation.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><image.png> <o:p></o:p></p>
<div>
<p class="MsoNormal">Source: <a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_8/cjab_b_planning-guide-jabber-118/cjab_b_planning-guide-jabber-118_chapter_010.html#CJAB_RF_S96EC4E9_00">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_8/cjab_b_planning-guide-jabber-118/cjab_b_planning-guide-jabber-118_chapter_010.html#CJAB_RF_S96EC4E9_00</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, May 12, 2017 at 6:41 AM Ryan Huff <<a href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">The native screen capture in the Jabber client does not work and is not supported over MRA (internal or WebEx Messenger IM Jabber works fine).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I believe it is actually covered by the same Expressway caveat that states native P2P file sharing won't work over MRA. By using MFT (Managed File Transfer), both should be allowed.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">My question to the group is, does anyone know where the Screen Capture over MRA limitation is specifically documented? It uses the same P2P technology that the file share does, so it makes sense that it doesn't work over a proxy like Expressway,
but I'm in need of specific documentation.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have opened a case with PDI to confirm my suspicion about the feature, so I am confident Screen Capture doesn't work over MRA (and why it doesn't work over MRA). I also found this bugId for the lacking statement in the Expressway docs: <a href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuu22458/?referring_site=bugquickviewredir" target="_blank">https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuu22458/?referring_site=bugquickviewredir</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="m_5255233750601442385AppleMailSignature">
<p class="MsoNormal">So my guess is this is an oversight by the technical writers and/or assumptive on Cisco's part that the reader would just "assume" the screen capture feature is really just a P2P file transfer under the hood, even though there is GUI magic
with a screen capture making the end user workflow a little different than a file transfer and leads many to believe otherwise.<br>
<br>
Has anyone ever seen anything to this regard, documented on official cisco docs?<o:p></o:p></p>
</div>
<div id="m_5255233750601442385AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="m_5255233750601442385AppleMailSignature">
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div id="m_5255233750601442385AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="m_5255233750601442385AppleMailSignature">
<p class="MsoNormal">Ryan<o:p></o:p></p>
</div>
</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="http://cp.mcafee.com/d/5fHCNAq3xEgdEI6zBxYQszCnC3tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPoWXF1Z4QsLZvAQQm7T7KLsKCOYeVAsYeouhWyaaRQRrIKsG7DR8OJMddECSjt-Kyyeso7nvd79KVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oTqlblbCqOmbAaJMJZ0kIToHMd9_7wqrhssu7f6MnWhEwdbtFkJkKpH9oQKCy02d84fyq81yQv-1EwEjSfCy2FDUCy0r1owrovdx3dwrNXjlS0r" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
</div>
</blockquote>
</body>
</html>