INTRODUCTION: - Cisco Community



DESKTOP SHAREContents TOC \o "1-3" \h \z \u INTRODUCTION: PAGEREF _Toc417314263 \h 3WEBEX SHARE PAGEREF _Toc417314264 \h 4EXPLAINATION: PAGEREF _Toc417314265 \h 4HOW TO ESCALATE USING JABBER: OPTION 1 PAGEREF _Toc417314266 \h 4HOW TO ESCALATE USING JABBER: OPTION 2 PAGEREF _Toc417314267 \h 5POP-UP SHOWN TO OTHER USER: PAGEREF _Toc417314268 \h 5LOADING SCREENSHARE: PAGEREF _Toc417314269 \h 5SCREENSHARING TOOL: PAGEREF _Toc417314270 \h 6SCREEN THAT OTHER USER SEES: PAGEREF _Toc417314271 \h 6IM ONLY SHARE PAGEREF _Toc417314272 \h 7EXPLAINATION: PAGEREF _Toc417314273 \h 7HOW TO ESCALATE USING JABBER: PAGEREF _Toc417314274 \h 7POP-UP SHOWN TO OTHER USER: PAGEREF _Toc417314275 \h 7SCREEN THAT OTHER USER SEES: PAGEREF _Toc417314276 \h 8PORT RANGES: PAGEREF _Toc417314277 \h 8SCREEN THAT OTHER USER SEES: PAGEREF _Toc417314278 \h 9HOW TO DISABLE: PAGEREF _Toc417314279 \h 9EXPLAINATION: PAGEREF _Toc417314280 \h 10HOW TO ESCALATE USING JABBER: PAGEREF _Toc417314281 \h 10SCREEN THAT OTHER USER SEES: PAGEREF _Toc417314282 \h 10NO POP-UP SHOWN TO OTHER USER: PAGEREF _Toc417314283 \h 11PORT RANGES: PAGEREF _Toc417314284 \h 11HOW TO DISABLE: PAGEREF _Toc417314285 \h 11STANDARD WEBEX MEETING PAGEREF _Toc417314286 \h 12EXPLAINATION: PAGEREF _Toc417314287 \h 12HOW TO ESCALATE USING JABBER: PAGEREF _Toc417314288 \h 12INTRODUCTION:There is 4 types:Webex share – Available when BFCP or IM only is not availableBFCP Share – Available when on a callIM Only Share – Available when chatting over IM.Escalate to a meeting and shareWEBEX SHAREEXPLAINATION:This type of share is the default share type if BFCP and IM Only share is not available. When the other integrations are disabled or if you are sharing with a user that doesn’t have those capabilities, then it will default to this share. It can also be started by the first two options that I outlined below. The user experience is similar to the Webex connect clientHOW TO ESCALATE USING JABBER: OPTION 1 (when others types are enabled)HOW TO ESCALATE USING JABBER: OPTION 2 (when others types are enabled)HOW TO ESCALATE USING JABBER: OPTION 3 (when others types are disable/other users doesn’t have the capability)POP-UP SHOWN TO OTHER USER:LOADING SCREENSHARE:SCREENSHARING TOOL:SCREEN THAT OTHER USER SEES: (NO red-line around it)IM ONLY SHAREEXPLAINATION:IM Only share is point to point. To initiate an IM only share, you need to open a chat window with someone and select “Share screen”. The person sharing will see a red line around their screen. See below. The port range is huge so so some customer firewalls will have it blocked.HOW TO ESCALATE USING JABBER:POP-UP SHOWN TO OTHER USER:SCREEN THAT OTHER USER SEES:PORT RANGES:SCREEN THAT OTHER USER SEES: HOW TO DISABLE: (via jabber-config)BFCP SHAREEXPLAINATION:BFCP goes through CUCM. Has a similar user experience to IM only share. To initate a BFCP share, you need to be a call and then select “Share screen”. See below.HOW TO ESCALATE USING JABBER:SCREEN THAT OTHER USER SEES: (red box around it)NO POP-UP SHOWN TO OTHER USER:If you escalate in a call, there is no pop-up and it goes straight to a desktop share.PORT RANGES:HOW TO DISABLE: (via jabber-config)STANDARD WEBEX MEETINGEXPLAINATION:This is a standard webex meeting. You can escalate to a meeting and then share your screen like a normal meeting.HOW TO ESCALATE USING JABBER:HOW SCREENSHARE WORKS ACROSS THE CLIENTS (CLOUD)No. 2 is wrong if MAC user is using a BFCP supported version. In that case a MAC and Windows user will do BFCP.DEBUGGINGDEBUGGING NETWORK ISSUES (p2p desktop share)Unfortunately wireshark does not show the RDP packets so it can’t be used to see if network packets are being sent between the two machines.However you can use a MS tool called: Microsoft Message Analyzer, use it you simple go to:Start local trace.The trace you see will be something like below:The address’s are in ipv6 so you’ll need to know the host and remote address in ipv6 format.TEST WITH MICROSOFT SCREENSHARE TOOLDownload the following tool:DOWNLOAD: 1: Copy the files in the download to both machines.Step 2: On machine one, unzip the file and navigate to this folder: WinPresenterFinal\WinPresenter\WinSharer\bin\DebugStep 3: Click on WinSharer.exe.Step 4: Select “Start presentation”. This creates an xml called inv.xml.Step 5: On machine two, unzip the file and navigate to this folder: WinPresenterFinal\WinPresenter\WinViewer\bin\DebugStep 6: Copy inv.xml into this folder.Step 7: Click on WinViewer.exe.Step 8: Select connectIf the sharing doesn’t work, then this proves it’s not a Jabber issue with P2P desktop share and is likely a network issue.CONFLICTING SOFTWARECalabrio Monitoring and Recording Desktop Recording Service has a known conflict with Jabber and P2P desktop sharingTo see if this service is running, do the following.Go to RunType in “services.msc”Scroll down to “Monitoring and Recording Desktop Recording Service” to see if its running.The following is a response from the Calabrio support team:“This OS API that both QM and Jabber use is the Microsoft Windows Desktop Sharing API. This API has the limitation where only one application can use it at a time. Earlier comments in the case notes indicate that the customer wanted to share screens using the Jabber application. In that case, they can disable Live Screen Monitoring in QM Administrator under "Interface Settings", just uncheck the box next to "Enabled". You will need to restart the desktop recording services in order for the Live Screen Monitoring functionality to be turned off so that Jabber can be used to share screens.”FIPSJabber P2P desktop share does not support FIPS mode.SAMPLE LOGS FOR P2P DESKTOP SHARELOCALSTART SERVICE :2015-02-27 13:34:40,211 DEBUG [0x00003890] [es\impl\DesktopShareServiceImpl.cpp(121)] [csf-unified.services.DesktopShareServiceImpl] [DesktopShareServiceImpl::initService] - Enter Init desktop share service.CHECK-CAPS:2015-02-27 13:35:56,435 DEBUG [0x00003890] [\PrivacyPolicyFeatureSubsetImpl.cpp(139)] [imp.service] [PrivacyPolicyFeatureSubsetImpl::ProbePolicy] - Policy: DesktopShare uri: coflaher@ result: AllowedSTART SHARE:2015-02-27 13:36:38,959 DEBUG [0x00003890] [es\impl\DesktopShareServiceImpl.cpp(280)] [csf-unified.services.DesktopShareServiceImpl] [DesktopShareServiceImpl::initiateShare] - Initiating share for conversation 100 with rectangle: 0,0,1920,12002015-02-27 13:36:38,959 DEBUG [0x00003890] [es\impl\DesktopShareServiceImpl.cpp(499)] [csf-unified.services.DesktopShareServiceImpl] [DesktopShareServiceImpl::onLocalShareStarted] - Local share has started for conversation 100Line 51561: 2015-02-27 13:36:39,029 DEBUG [0x00003890] [s\impl\DesktopShareServiceImpl.cpp(1258)] [csf-unified.services.DesktopShareServiceImpl] [DesktopShareServiceImpl::onSharingSessionCreated] - Sharing session has been successfully created for 100, invite is: <E><A KH="MM0A22e3hUj4oo8449rFW1p/T1M=" ID="T64cq42sAMdSa3tZqQh69z0VbP1X4xokqVPc4hWC7LC02n/HSdYY++bBf+uJklsR"/><C><T ID="1" SID="2184299749"><L P="49522" N="fe80::cd9f:c68a:f7fc:539a%12"/><L P="49523" N="10.184.18.244"/></T></C></E>SEND MESSAGE:Line 51566: 2015-02-27 13:36:39,029 DEBUG [0x00003890] [ubsets\P2PChatFeatureSubsetImpl.cpp(106)] [csf-unified.imp.P2PChatFeatureSubset] [P2PChatFeatureSubsetImpl::SendInstantMessageCommand] - jid: rbilling@ssd., cmd: IMCMD_P2P_DESKTOP_SHARE_INVITE, cmdContent: r7L/5LCR7rifAjJfNJe7xw==<E><A KH="MM0A22e3hUj4oo8449rFW1p/T1M=" ID="T64cq42sAMdSa3tZqQh69z0VbP1X4xokqVPc4hWC7LC02n/HSdYY++bBf+uJklsR"/><C><T ID="1" SID="2184299749"><L P="49522" N="fe80::cd9f:c68a:f7fc:539a%12"/><L P="49523" N="10.184.18.244"/></T></C></E>SHARE STOPPED:Line 51875: 2015-02-27 13:37:10,967 DEBUG [0x00003890] [lugin\MicroModeCallControlStrip.cpp(134)] [plugin-runtime] [OnStopShareClick] - MicroModeControls: Stop share button pressed.Line 51885: 2015-02-27 13:37:10,967 DEBUG [0x00003890] [pters\imp\commands\P2PImCommands.cpp(48)] [csf-unified.imp.P2PImCommands] [IMPStackCap::P2PImCommands::SendIMCommand] - [jid=coflaher@] [command=IMCMD_P2P_DESKTOP_SHARE_INVITE_REVOKED] [screenCapture=false]REMOTE:RECEIVED SHARE:015-02-27 13:34:51,268 DEBUG [0x00002388] [s\impl\DesktopShareServiceImpl.cpp(1385)] [csf-unified.services.DesktopShareServiceImpl] [DesktopShareServiceImpl::OnInstantMessageCommandReceived] - Desktop share invite received from maniamn@ssd., invite string: r7L/5LCR7rifAjJfNJe7xw==<E><A KH="MM0A22e3hUj4oo8449rFW1p/T1M=" ID="T64cq42sAMdSa3tZqQh69z0VbP1X4xokqVPc4hWC7LC02n/HSdYY++bBf+uJklsR"/><C><T ID="1" SID="2184299749"><L P="49522" N="fe80::cd9f:c68a:f7fc:539a%12"/><L P="49523" N="10.184.18.244"/></T></C></E>ACCEPTING:2015-02-27 13:35:04,991 DEBUG [0x00002388] [es\impl\DesktopShareServiceImpl.cpp(617)] [csf-unified.services.DesktopShareServiceImpl] [DesktopShareServiceImpl::acceptDesktopShareInvite] - Accepting desktop share invite for john@ comand maniamn@ssd.CREATING WINDOW:Line 32500: 2015-02-27 13:35:04,992 DEBUG [0x00002388] [gin\TelephonyDesktopSharePlugin.cpp(686)] [plugin-runtime] [onRemoteShareStarted] - Creating remote share windowACCEPTED:Line 32509: 2015-02-27 13:35:05,020 DEBUG [0x00002388] [es\impl\DesktopShareServiceImpl.cpp(650)] [csf-unified.services.DesktopShareServiceImpl] [DesktopShareServiceImpl::acceptDesktopShareInvite] - Successfully accepted remote share from john@ ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download