Meeting fails to load in Firefox under Ubuntu Linux

Some users running Ubuntu Linux and use Firefox may see problems connecting to meetings.

The same meeting loads fine in other browsers like Chrome or Chromium.

This can be related to a Security Certificate not being set for use with websites in Firefox.

Follow these steps to verify and correct this:

1. Open Firefox and select “Edit”, “Preferences”.

2. Select the “Advanced” Tab and click on “Encryption” .

3. Select “View Certificates” to open the certificate manager.

4. Select the “Authorities” Tab.

5. In the list of certificates find the one called “Verisign Class 3 Secure Server CA – G3″.

6. Select the certificate and click “Edit”.

7. Check “This certificate can identify websites” and click OK to confirm your changes.

8. Restart Firefox and retry the connection to your meeting.

 

FirefoxCertManager

 

 

 

Select Captivate content will not publish directly to an Adobe Connect server

Issue: When attempting to publish Captivate content that includes a random question slide linked to an empty question pool directly to an Adobe Connect server Captivate crashes. We reproduced this issue with a Captivate file composed of a quiz with a set of random questions near the end of the project. Upon clicking on the publish button, a dialog box pops up stating that there are more random question slides than questions available in the pools. The options are to click “yes” to publish or to click “no” to invoke the question pools manager and edit the quiz. Upon clicking yes to publish the file, the error message ensues warning that your attempt to publish your project to the Adobe Connect Server has failed.

Result: Captivate crashes aborting the publishing process.

3203688.fw

Workaround: Publishing the Captivate project as a .zip file works fine.

Expected: Captivate content that includes a random question slide linked to an empty question pool should publish directly to an Adobe Connect server without any issues.

This problem is scheduled to be addressed in Connect 9.3 with Captivate 8

Adobe Connect 9.2 upgrade checklist

We’re soon starting to upgrade our Adobe Connect Hosted clusters to version 9.2, the upgrade for on-premise installations will be available soon as well.

Please make sure to go through the upgrade checklist:  http://helpx.adobe.com/adobe-connect/kb/connect-92-upgrade-checklist.html

You can check your upgrade date here: http://www.adobe.com/support/connect/downloads-updates.html

 

Content Availability & Replication among Clustered Connect Servers

This article addresses how to make sure every URL int a Connect cluster pops up like your grandmother’s trustworthy old pop-up-toaster.  If some published content will not play or display properly from your Connect cluster, do the following:

  • Make sure that the load balancing device in front the Connect cluster is not using sticky sessions or session awareness.
  • If you are using a Big-IP LTM, make sure that Nagle’s Algorithm is turned off .
  • Make sure that Clustered servers communicate with each other on ports 8506 and 8507. A simple netstat -an from the command prompt on each server will make certain each server is listening on 8507.
  • Don’t try to cheat on the number of documented VIPs required on the load-balancing device or SSL accelerator. Only one VIP is not the right answer.
  • When the servers cannot communicate, trouble ensues.Clustered servers need to be able to communicate with each other on port 8507. When they cannot communicate, the links to content will be broken and end users may experience hanging videos or unavailable content.
  • Search in your debug log for “cluster-”
    • [01-31 18:20:23,729] cluster-8507-696969 (INFO) MirrorHandler: waiting for commands”    2014-02-10T16:30:23.739-0600….
    • If you do  not see cluster-8507 then there is a replication communication problem on 8507
  • To help facilitate troubleshooting, during setup and during upgrades, if possible, allow the servers to have external access – at least allow the monitored and screened ability to toggle external access on and off by special request if needed. This will allow you access to Adobe’s license server and also to troubleshooting tools.
  • Install telnet on each server. Telnet is a great test tool. Placing telnet on each server and actually testing connectivity to each and from each server on ports 8506 and 8507 is prudent.
  • It is also prudent to have a useful browser on each server. I often install FireFox on each server along with the latest available Flashplayer. You may want to install Flashplayer on IE as well even though enhanced security will render it a challenge to use for any useful troubleshooting purposes. Useful flash-enabled browsers will facilitate direct tests on any problematic content on the servers from the servers thereby eliminating network and load-balancing variables when isolating issues.

Controlling Recording Playback through the URL

When added to a Connect archive recording URL, the following suffixed commands will force the prescribed behavior. This may help with projects that include the embedding of archive recording URLs.

  • pbEIOpen=true – the event index would come up opened
  • pbEIOpen=false – the event index would come up closed
  • pbEIOverlay=true – the event index would show up in overlay mode
  • pbEIOverlay=false – the event index would show up in persistent mode
  • pbMode=normal – open in normal playback mode
  • pbMode=edit – open in editing mode
  • archiveOffset=parameter in milliseconds – open to a specific time in the recording

You can modify the URLs along these lines; use an “&” to concatenate multiple parameters.

Every recording will automatically append ?launcher=false&fcsContent=true. You cannot play a recording in the Connect Meeting addin; if you append ?launcher=true, it will toggle to ?launcher=false and open the recording in the browser:

This URL is an example of what a normal URL would look like during recording playback:

https://connect.mydomain.com/recording1/?launcher=false&fcsContent=true&pbMode=normal

To change this to open with the index closed, append pbEIOpen=false like this:

https://connect.mydomain.com/recording1/?launcher=false&fcsContent=true&pbMode=normal&pbEIOpen=false

Customize Event Registration confirmation message

When a new participant completes the registration form for an Event they are shown the Registration confirmation message.

The default message reads:

“Thank you for your registration request. Your information has been submitted to the event host.”

Here’s how you can customize this message.

  1. Login to Connect and select the “Event Management” tab.
  2. Click on Event Templates
  3. Select the Event Template from the drop-down list.
  4. Select “Edit template”

EditEventTemplate

 

“Edit template” takes you to a new window / tab in your browser where you can edit the template.

EventRegistration_Edit

In this view, select “Event Registration” and right-click on the field where it reads “Registration Form” and “Registration confirmation message […]” as in the screenshot below and select “Edit” in the drop down menu.

rightClickEdit

Hitting “Edit” takes you here:

OnRegistrationConfirmation_dropdown

Select the first item “On Registration Confirmation” by opening the drop down menu. Here you can edit the Registration Confirmation Message text.

Make your changes and click “ok”.

regConfirmation_changeText

To make sure your changes are applied you need to activate the template. You can do this in this floating menu on the right of your screen:

 

CQ_activateTemplate

Once the template is activated the change is applied to all Events based on the template you chose to edit.

 

 

Demystifying Mixing VoIP and Telephony in a Meeting

With Unified Voice (UV) enabled and selected from within a meeting room:

The host may choose: Meeting>Preferences>Audio Conference>Allow participants to use Microphones: When Allow participants to use Microphones is checked, participants have power to enable their own microphones within the meeting. When it is unchecked, the host must enable microphones first and then the participant can enable the microphone with host permission within the meeting:

uv-1.fw

In either case, checked or unchecked, the host needs to first start the audio conference within any meeting:

uv-1b.fw

And the participant needs to choose the microphone option and enable it (even though the host has enabled it manually within the meeting or set it as permanently enabled within the room):

uv-1a.fw

Note that by default, when UV is in use, the telephony option is checked for the participant:

UV2.fw

The participant must select the microphone option in order to use the microphone instead of the phone; this will allow the microphone to broadcast to the users in the meeting using UV telephony:

UV3.fw

With all these settings in place, VoIP microphones can talk to telephony and telephony to VoIP and both will be audible in an archive recording for playback on demand.

How to stop Event pages (CQ) from being indexed

This article (and link below) is intended for Licensed (On-Premise) customers who have a standalone instance or cluster of CQ servers to serve up the Events Management piece of the Adobe Connect platform.  If you would like to stop event pages from being indexed in search engines like Google, you can follow this quick article below on adding robots.txt to the root of the CQ instances.

http://crxdelight.com/2012/02/04/how-to-protect-your-cq-instances-from-google-searches/

Adobe Connect Addin; Unable to screen share with PPAPI plugin enabled in Google Chrome

If you are using Google Chrome and trying to share your screen in a meeting session, you might encounter one of the below issues :

Problem#1

Users cannot screen share when using Google Chrome

Solution:

Add [*.]adobeconnect.com to Google Chrome list of exceptions

Steps:

1. Launch Google Chrome

2. Enter chrome://settings/contentExceptions#ppapi-broker in the address bar

3. Add the exceptions as follows:

3a. Under the Hostname pattern, add this string: [*.]adobeconnect.com

3b. Under Behavior: Allow

3c. Click Done

4. Launch your Connect meeting in the add-in mode

 

Problem#2

Users launch meeting in the Flash Player (launcher=false),  when clicking on the ‘Share My Screen’ button, users get an error “Adobe Connect Add-in is incompatible with default settings of your version of Google Chrome.”

Solution:

1. Adding the exceptions to Google Chrome by following the steps in Problem#1

2. Close the meeting

3. Re-launch the meeting within the Connect add-in (launcher=true)

 

Following error might be visible in the meeting room upon screen sharing :

Addin_error

 

Environments in which the scenario might produce :

Windows , Adobe Connect Addin , Google Chrome browser, Hosted/On-Premise Solution

 

How to Solve Port 80 Problems when running Adobe Connect on windows server and logs shows port 80 is already in use.

Mostly in such situation the homepage wouldn’t show up however the console page works just fine.

There are a number of well-known Windows programs which use port 80:

IIS
The most likely culprit is Microsoft Internet Information Server.

SQL Server Reporting Services
SSRS can remain active even if you uninstall SQL Server. To stop the service:

  1. Open SQL Server Configuration Manager.
  2. Select “SQL Server Services” in the left-hand pane.
  3. Double-click “SQL Server Reporting Services”.
  4. Hit Stop.
  5. Switch to the Service tab and set the Start Mode to “Manual”.

Or

You can also stop the services from services.msc

Whats Using Port 80?

Further detective work is necessary if IIS and SSRS are not to blame. Enter the following on the command line:

netstat -aon

The active TCP addresses and ports will be listed — locate the line with local address “0.0.0.0:80″ and note the PID value.

Now right-click the task bar and select Start Task Manager. Navigate to the Processes tab and, if necessary, click View > Select Columns… to ensure “PID (Process Identifier)” is checked. You can now locate the PID you noted above. The description and properties should help you determine which application is using the port.

The Task Manager allows you to kill the process, but be a little wary about doing that — especially if it’s “NT Kernel & System”.

I Hope this would be helpful at some instances

Thanks