Author Archive: Frank DeRienzo

In Connect Meeting, Clicking “Don’t show this dialog again” has no Effect on the Tips Dialog

Issue: Upon startup, Tips for using Adobe Connect for Hosts is displayed. After clicking on “Don’t show this dialog again” and dismissing the dialog, the next time Connect is launched the dialog is again displayed.

dialog.fw

This is caused by a problem storing the changes locally available to flash applications on client machines. Here are workaround steps:

  1. Open the connect meeting in the IE/Firefox. You can append launcher=false to the meeting URL to open it in browser: <url>/?launcher=false
  2. Right click on the meeting and select Settings; the  flash dialog GUI will appear:

flash1.fw

3. Click on the folder icon:

flash2.fw

4. Check that the variable for storage is allowed and is greater than 0 and also check to see if the Currently used variable is equal to the allowed value.

5. If the Currently used variable is showing 0 then close this dialog and again right click on meeting and open the Global Settings. The following dialog will appear:

flashglobal.fw

6. Click on Local Storage Settings by Site:

flashglobal2.fw

7. Make sure that the Adobe Connect server is listed there and it is allowed as depicted in the third column. If it is not allowed, then allow it using the drop-down menu.

Adobe Connect Offline Recording Option Captures and Records Local Client Screen Activity

Adobe Connect Offline Recording Option Captures & Records Local Screen Assets:

While in the process of creating an offline recording in Connect, the recording will capture extraneous desktop application activity if Windows is in Non-Aero mode

To stop extraneous recording,  turn on the Aero theme: Control Panel\All Control Panel Items\Personalization – choose any Aero theme.

aero.fw

This workaround will limit the offline recording to the Connect Meeting archive.

Here is the related forum discussion for reference: https://forums.adobe.com/message/6629306#6629306

Adobe Connect Meeting becomes Unresponsive with Clients Running Mac OS X 10.9 Mavericks

Adobe Connect supports Mac OS X 10.9 (also known as Mavericks). In some rare instances clients running Mavericks consistently experience freezing and disconnection issues. The root cause has not yet been identified; here are recommendations that have addressed the issue for some users:

-        Ensure latest Adobe Connect add-in and Flash Player are installed:  https://www.adobe.com/support/connect/downloads-updates.html

-        Set the correct sand-box settings in Safari as documented in these tech-notes:

Apple support also provided these recommendations:

-        Enable Sandbox mode in Safari. Make sure you have the Adobe Connect room open when you try and add the webpage.

-        Change the DNS settings to Google’s server, and disable prefetching. Make sure that you reset the computer after changing the DNS: http://support.apple.com/kb/ts3408

We have not reproduced this issue with either OS X 10.9.5 or Mac OS X 10.10 (also known as Yosemite).

The issue is still under investigation with Adobe and Apple.

Web Services API call: sco-session-seminar-list

We have opened a bug around a recent undocumented change in the Web Services API actions.

The action, sco-session-seminar-list, which prior to 9.2.2 returned all seminar sessions for which the authenticated user had Host permissions, now requires the alternative action: sco-seminar-sessions-list. Use sco-seminar-sessions-list instead of sco-session-seminar-list until we resolve the open issue around this change; we have logged bug number: Watson: 3772441.

Consider this sample action (wherein FQDN designates your fully qualified domain name) as an example: Instead of running the action:  https://FQDN/api/xml?action=sco-session-seminar-list&sco-id=1369951914 to get all the seminar sessions under the seminar license with the sco-id of 1369951914 you ought to run this API instead: https://FQDN/api/xml?action=sco-seminar-sessions-list&sco-id=1369951914

To list all the sessions that are linked to a meeting room under one license, put a filter on the source-sco-id as in this example action: http://FQDN/api/xml?action=sco-seminar-sessions-list&sco-id=sco-id-of-the-seminar-license&filter-source-sco-id=sco-id-of-the-meeting-room

Ensuring that Email Generated by Adobe Connect Servers is Received

There have been more than a few incidents reported on the topic of email messages from Adobe Connect servers not getting delivered. These include messages generated by the Adobe Connect Events module as well as system email messages such as that generated by changing a password.

The first thing to avoid to prevent this problem is that of using special characters in the host’s name. This is scheduled to be fixed in Connect 9.3, but currently, in 9.2, if you place a comma in the Event host’s name such as Frank D., El Presidente’  it will cause an error identified in our server logs by a messaging exception.

The second thing to avoid is inviting over 20,000 participants to an Event. This generates an operation size error and causes problems with email messages being sent out. We also plan to address this ceiling tentatively in Connect 9.3.

With specific reference to Adobe Connect Hosted accounts, we just made the following change to ameliorate email problems: As of April 28th, 2014, administrative email notifications sent from Adobe Connect servers will now be coming from admin@adobeconnect.com instead of admin@acrobat.com This will help by disassociating Connect-generated email from that of the Acrobat domain which could be potentially blocked by virtue of its identification with document storage. We also made some internal changes to the way the Connect servers handle email and we worked with our Web infrastructure partners to insure that Connect generated email was not being treated as SPAM on the Web.

There is a bit of a conundrum here. If Adobe Connect Events email invitations are sent out in massive mailings to those who perceive the email as SPAM, then the Adobe Connect servers could be tagged as producing SPAM by those end-user recipients. An overzealous Events manager may cause Gmail and other providers to treat Adobe Connect email as SPAM. When an Event that is capped at 500 participants sends out 5000 email invitations, it is expected that many recipients will at best ignore the inbound email traffic and many more may consider the traffic to be a nuisance. We are investigating possible approaches to ameliorate this problem and plan in 9.3  to add an opt-out option for Events invitations that will offer a convenient alternative to any SPAM reply option for recipients to invoke.

We love large Events and Adobe Connect handles them very well; this is a case when our success can potentially lead to some problems. Currently the Adobe Hosted Service is green for SPF record checks.  We pass all major email providers and are not blacklisted according to common checker tools on the internet.  This should resolve the lion’s share of current email issues and the upcoming changes in 9.3 will serve to harden this capability for future Events.

How to make Connect use a browser-based email client to send Meeting invitations

When invoking a browser-based email client to invite participants to a Connect Meeting from within a Connect Meeting you will see this error message unless you first make the browser-based email your default email service:

 

bb-email.fw

 

Sending a browser-based email invitation from within a Connect Meeting is possible if you first make the browser-based email option your default email program. As an example, you can use the instructions at the following links to make Gmail your default email program :

http://email.about.com/od/gmailtips/qt/et_default_prog.htm

http://www.pcdailytips.com/set-gmail-as-default-email-using-chrome-or-firefox/

Note that once you enable a browser-based email client and invoke it from within a Connect Meeting, the behavior will be different based on whether the host issuing the invitation is using the Connect Meeting addin or the Flash Player. In the addin it will look like this:

Using the Connect Meeting addin, invoke the invitation: Meeting> Manage Access & Entry > Invite Participants

bb-email-1.fw

bb-email-2.fw

See how the invitation is fully populated with important details:

bb-email-3.fw

Following the same procedure using the Flash Player instead of the addin (?launcher=false) also works, but with an abbreviated invitation message:

bb-email-4.fw

 

Specifications for MP4 Conversion for Connect Recordings

Here are the specifications for the MP4 conversion; they are similar to our FLV specifications albeit with better compression:

  • Resolution: 1024X768
  • Frames Per Second: 8 FPS
  • Video Bitrate: 1024kbps
  • Audio:
    • Codec – AAC (Advanced Audio Codec)
    • Profile – Main@3.1
    • Bit Rate – ~55Kbps (VBR)
    • Channels – 1 (Mono)
    • Sampling rate – 44.1Khz

Be Aware of the Closed Captioning Pod Defaults

Last week we found out that Caption Colorado changed their IP address and port number for the Closed Captioning pod downloadable from the Connect Exchange Website. Here is the direct link to the Connect version 9 Closed Captioning Pod

The new Caption Colorado information includes:

If you are experiencing any trouble with the Closed Captioning pod while using it in a Connect Meeting with Caption Colorado, please set your host to “captionedtext.com” and to port 11100 in the adobe pod. Note that the new IP, 54.193.31.11, depending on your infrastructure’s network security settings, may need to be white-listed.

For an updated user’s guide referencing the Closed Caption Pod, see this PDF: http://platinum.adobeconnect.com/cc/

 

 

Estimating the Size of Archive Meeting Recordings

I was recently asked if I had any test data showing how big a recording becomes based on the use case during the Connect Meeting being recorded. While plenty of anecdotal information exists,  I thought it prudent to begin a list of use cases and show what the size was after five minutes of each use case. This article will be a work in progress as I add different use cases in order to offer various concrete examples to use as a basis to estimate recording size based on what is being recorded, whether multiple Video pod camera feeds or screen-sharing or VoIP, etc. Among its purposes, this exercise will help meeting hosts to avoid exceeding the 2GB limit on Adobe hosted clusters for recording size.

Most relevant among the variables considered is the notion that recording size is affected by the streams present in the meeting being recorded. Typically a Video pod with VoIP (640X480) shared per hour will result in an FLV of around 200MB. Sharing a screen in a meeting (1680X1050) will result in an FLV size of around 150 MB. PPT/PPTX files uploaded to a meeting room and displayed while recording will not play a significant part in recording size because the recordings link to external content rather than contain that content intrinsically. For example,  a meeting with two Video pod streams could have recording size of around 400MB and a meeting having a single Video pod stream with VoIP and screen-sharing could end up around 350MB. The actual results may differ as the screen resolution of the publisher, the type of sharing and the amount of movement are all variables that can affect recording size: If there is little movement on screen or in the Video pod stream, the recording size will be less than it would be with a lot of movement.

Here are some concrete examples to use for planning; each recording is approximately five minutes in length:

A meeting with a single video feed for the Presenter to display and scroll through an uploaded PowerPoint file while using integrated telephony:Title: Recording Size Test_0
Type: Recording
Duration: 00:05:31
Disk usage: 8335.3 KB

rec-size1.fw

 

A recording of a meeting with six video feeds and an uploaded PowerPoint file
Title: Planning Troubleshooting and Support Meeting Room _15
Type: Recording
Duration: 00:05:48
Disk usage: 13873.8 KB

rec-size2.fw

 

A recording of a meeting with four video feeds and screen sharing an application with normal activity
Title: Planning Troubleshooting and Support Meeting Room _16
Type: Recording
Duration: 00:05:56
Disk usage: 21660.8 KB

rec-size3.fw

More examples to follow.

How Meeting Folder Permissions Affect Access to a Meeting Room

The question keeps coming up, what happens to Meeting accessibility and permissions if I move a Meeting room from the a User Meeting folder to the Shared Meetings folder?

Let’s look at it from multiple angles beginning with the permissions on Shared Meeting folder itself and then moving to the Meeting room access options and then to the Meeting roles.

1. The Shared Meeting folder itself has two permissions options: Manage and Denied:

sharedfolderperm.fw

If a registered user is granted Manage permission over the Shared Meeting folder by an Administrator, then that registered user can gain (at a minimum), participant access to every meeting in the Shared Meetings folder. Of course, a participant can do very little within a room:

sharedfoldermeeting.fw

Manage permissions on the Shared Meetings folder does not, by itself, allow the power to change room settings. The settings will be viewable but cannot be changed:

editinfo.fw

Clicking save will quickly manifest insufficient permissions:

notauth.fw

Manage permissions on the Shared Meeting folder allows for deletion of  a meeting in the Shared Meetings folder:

delemeet.fw

delemeet1.fw

2. Separate from the Shared Folder permissions, are the room access options under Connect Central for any Meeting Room:

editinfoopt.fw

These Meeting access options do not override the folder options. While a user with Manage permissions over the Shared Meetings folder will still need to enter a passcode if one is set, the manage permissions allow the passcode to be viewed in Connect Central :

passcd.fw

 

passcdview.fw

3, Meeting roles set will not be affected by folder permissions even if the Denied Access is chosen at the Shared Meeting folder level:

denied.fw

A user who has Denied access to the Shared Meetings folder cannot view the the folder Connect Central:

notauth.fw

Meeting access permissions and roles apply however when directly hitting the Meeting URL even if the user is denied access to the Shared Meetings folder:

notstart.fw

in.fw