This is a somewhat unique case which may not be experienced by many Cisco customers, but there is a chance that there are others that are hitting the same defect. I was delaying this post for a while, hoping to find a resolution to the issue that I’ve been working on for over a month now.
Also waiting for some feedback from Cisco Jabber/CWMS Product Teams so hopefully will have an update for you soon. Another workaround is to set Chrome or Firefox as your default browser or use those browsers exclusively to launch WebEx meetings until a fix is released. So far, adding the FQDN of the CWMS to the Trusted Sites list seem to have done the trick for some users (you may need to tweak the Trusted Sites security zone to achieve the right effect). Use a tested compatible version of Jabber as per documentation: This is not compatible with CWMS and causes WebEx meetings to be unable to start from IE/Productivity tools due to being unable to match the activex control used by CWMS when launching a meeting from IE/PT
When running Jabber 11 and 2.5 MR5+, Jabber 11 changes the GPC patch to C:\Program Files (x86)\Cisco Systems\Cisco Jabber\MeetingSDK\JabberMeeting\NewDS\MyWebex\ieatgpc.dll However, the TAC engineer who was assigned to our case just advised us of the defect CSCuu81060 which reads as follows: After playing with Trusted Sites list and zone security settings, it seemed that we had found the workaround. We’ve opened a case with Cisco TAC to troubleshoot the issue further. Hence, this defect has not been detected. Surely, prior to this massive deployment, IT has extensively tested this and all prior (beta) Jabber 11 releases under EAP, but no one in IT had IE set as default browser (can’t blame them). All affected users had Jabber 11.0 installed on their workstations – clue #2. Error GpcUrlRoot“:Īll affected users had IE as their default browser – that was clue #1. The error (in a form of pop-up) reads as follows: “ Setup was unsuccessful. Shortly after, our end users started complaining about inability to start or join WebEx meetings.
Since Jabber 11.0 has been officially released and posted on CCO, we have done a company-wide upgrade from 10.6 to 11.0. Hope it works for you if you are having the same issue. The above workaround has worked flawlessly.
If you are attempting to add a subscriber node to an existing Cisco Unified Presence Server cluster across the WAN, chances are you will get the following error during network configuration validation: Limited support (from MS Office applications only) Presence indicators in Microsoft applicationsįederation with other standards-based clients I have tried to summarize all features of the two in the following table: Feature The two share some similarities and clearly leave other competing products far behind – as Gartner analysts clearly suggest. Many are wondering how Cisco Jabber compares to OCS/Lync in terms of features and user experience.