Posts in Category "Meeting"

Using iframe to Invoke an Adobe Connect-hosted URL

Make sure that the iframe reference is formatted correctly.

When referencing an a meeting archive recording, it is best to first move an archive from under its parent meeting to the Connect Central content library before referring to it via iframe.

Do not let the URL of the archive recording redirect to Connect Central login page. To bypass the login screen you may either parse a username and password as a parameter in the URL or you may set permissions on the referenced content URL in Connect Central to allow for public viewing.  The latter option is usually the best. To avoid exposing the genuine user’s password as plain text in a GET request, it is usually best to simply make the recording public in Connect Central then link it. Alternatively, you may also create a new user in Connect Central with no other permissions except access to the referenced URL.

Referencing content in Connect Central that is set to public viewing:

<iframe src=http://connectdomainname.adobeconnect.com/customurl1″></iframe>

Referencing content by parsing a username and password:

<iframe src=”http://connectdomainname.adobeconnect.com/username?login=username@adobe.com&password=userpassword&account-id=12345678” width=”600″ height=”600″></iframe>

When referring to multiple URLs whether archives or MP4s or other Connect-hosted links, be sure to use a separate iframe reference for each Conenct URL rather than attempting to wrap all URLs in a single iframe reference. For example, two public links together in a table might look like this:

  <tr>
    <td width=”600″><iframe src=”http://connectdomainname.adobeconnect.com/customurl1″></iframe></td>
  </tr>
  <tr>
    <td><iframe src=”http://connectdomainname.adobeconnect.com/customurl2″></iframe></td>
  </tr>

Connect 9.1.2b on-premise – PDF conversion may fail

When uploading a PDF to a share pod in a meeting on an on-premise server version 9.1.2b on some installations the file cannot be converted.

In the access.log you get a message like this:

“Internal error ‘Pdf to swf conversion failed with return code -1073741515′ occured”

If you run into this problem please verify that you have the “Microsoft Visual C++ 2010 Redistributable Package (x86)” installed on your server.

If it is not installed, install it from here: http://www.microsoft.com/en-us/download/details.aspx?id=5555

Make sure to install the 32bit version even if you have a 64bit OS.

If the file still does not convert after successful upload to a meeting, please contact support.

Passing in the Passcode for Meeting in the URL

If for whatever reason, you needed to pass in the Meeting Passcode for an Adobe Connect meeting room via the URL (yes this has been asked by Connect users in the past), there is one way to do this for 2 of the 3 meeting access levels that exist in Adobe Connect (that accept Guests).

When you setup an Adobe Connect meeting room and assign it a ‘Meeting Passcode‘, that parameter and value can be expressed as ‘meeting-passcode=xxxxxx‘ in the URL string of the Meeting itself.  You also need to make sure you have the meeting setup so that it is either:

Only registered users and accepted guests may enter the room‘ or ‘Anyone who has the URL for the meeting can enter the room

Those are the only 2 options for Access level that allow Guest access.  The ‘Only’ level will prompt the host to accept or decline the guest’s request to enter.  The ‘Anyone’ level will simply let the user right in (see below for the Passcode and Access level settings).

passcode

 

 

To pass a user directly into an Adobe Connect Meeting room that has a passcode, you can use the following formatted URL:

http://myConnectDomain/myMeetingURL?guestName=Jim&meeting-passcode=breeze

where ?guestName=XXXXX is appended to give the guest an identity in the room
where &meeting-passcode=XXXXX is appended to pass in the Meeting Passcode

 

Connect 9.1 on-premise Server – Audio Provider selected by default when creating a new meeting.

With Connect 9.1 when creating a new meeting the option to use an audio profile is preselected if one or more exist under “My Profile” >> “My Audio Profiles”.
This means, if you setup a new meeting it is assumed you also want to use your existing audio profile.

You can read about this change here: What’s new in Adobe Connect 9.1

If you prefer the old behavior and do not want to preselect an audio profile due to various reasons you can change this in the server configuration files.

audio_conference_settings

Please note, this change means you need to modify a file on your server, so please create a backup.

To go back to the behavior of Connect 9.0 and earlier versions follow these steps:

1. Log on to your server machine.
2. Browse to the Connect install directory.
3. Locate the directory \Connect\9.1.1\appserv\apps\meeting\.
4. Take a backup copy of the file “sco_edit.xsl”.
5. Open sco_edit.xsl in an XML friendly text editor such as Notepad++ or Textpad.
6. Go to the end of the file and replace these two lines:


</xsl:template>
</xsl:stylesheet>

with this:

<script>

            document.getElementsByName("inherit-telephony-settings")[0].checked=true;

            noTelephonySettings();

   </script>
</xsl:template>
</xsl:stylesheet>

 

script_view_in_editor

 

7. Save the changes and restart the Adobe Connect Service
8. Verify the changes by setting up a new meeting.

Please note, these changes might be overwritten when you install an upgrade or patch.

 

 

 

Adobe Connect Server Licensing for Disaster Recovery

This question is commonly asked: Does my license for On-Premise Adobe Connect allow me install Adobe Connect servers for disaster recovery purposes?

First let’s define the terms: Disaster Recovery Environment refers to your technical environment designed solely to allow you to respond to an interruption in service due to an event beyond your control that creates an inability on your part to provide critical business functions for a material period of time. That is to say, it refers to a secondary site that would not be utilized in production unless the primary site went offline due to a natural or human-inflicted disaster that is beyond your control. Use of Adobe Connect servers in Disaster Recovery Environments is within the scope of your license and no additional fees are due to Adobe Systems Incorporated. For example, for the architecture depicted here, you would need four Adobe Connect server licenses. 

 

Connect_DR_cluster

 

However, adding one or more Adobe Connect servers to a local cluster is outside the scope of your license, and you will need to purchase additional licenses from Adobe Systems Incorporated to accomplish this.  Additional licenses are needed when adding any Adobe Connect servers that increase scalability in the form of:

  • Availability — What percentage of time is Connect available to geographically distributed users?
  • Reliability — How often does Connect experience problems that affect availability?
  • Performance — How fast does Connect consistently and qualitatively respond to user requests?
  • Concurrency – How many users can a Connect deployment handle concurrently?

Information around cluster expansion is here: Adobe® Connect™ server pools/clusters and hardware-based load-balancing devices with SSL acceleration

If you were to geographically distribute an active Connect cluster by placing Adobe Connect servers into two separate data centers, that would also require additional licensing. Connect servers in a cluster cannot have more than 2-3ms of latency between and among Connect servers.  Generally you would not geographically distribute Adobe Connect servers into different data centers, however, there is a chapter in the aforementioned clustering article on the topic. With that said, the architecture depicted below, is an example of a distributed active Adobe Connect cluster that is is spread between two local data-centers with nominal latency between those data-centers (less than 3ms of latency). All four servers are in production and all are actively hosting meetings and serving on-demand content.  This Connect architecture example depicted in the diagram below requires a four-server Connect cluster license:

 

Cross-DC-CLUSTER

 

Where is the Connect Meeting Add-in Installed?

Here are the client-side installation locations for files required by Connect Meeting add-in and its mms.cfg configuration file.

1. In Connect version 9, the default installation directories on each client platform are:

Windows (32 and 64 bit machines)

  • %appdata%\Macromedia\Flash Player\www.macromedia.com\bin\adobeconnectaddin
  • or   C:\Users\<username>\AppData\Roaming\Macromedia\Flash Player\www.macromedia.com\bin\adobeconnectaddin

Macintosh :

  •  ~/Library/Preferences/Macromedia/Flash Player/www.macromedia.com/bin/adobeconnectaddin

2. The  configuration file, mms.cfg, for the add-in is located here: :

Windows (32 bit) :

  •  C:\Windows\System32\Macromed\Flash\mms.cfg
  • or C:\Windows\System32\mms.cfg

Windows 7 64 bit

  • In: c:\Windows\SysWOW64\Macromed\Flash\mms.cfg
  • or c:\Windows\SysWOW64\mms.cfg

Macintosh OS

  • <hard drive>/Library/Application Support/Macromedia/mms.cfg

Adding the Passcode Feature for Connect Meetings

You may add a passcode feature as an additional security option for Connect Meeting room access in Connect versions 8 and 9. Each Meeting room can have its own passcode.  The parameter will appear under the Edit Information tab of the Connect Meeting:

pc2.fw

This is a great option. For example, it allows you to pop up a fast ad hoc meeting with full guest access while requiring guests to apply a pass-code to enter:

pc.fw

It also allows an additional layer of security for registered users as well; they also would need to enter a passcode in addition to any permissions (even host-level) granted to the room.

pc1.fw

Once applied, when a users hits the Meeting URL they will be presented with the passcode field:

pc3.fw

To add this feature, simple log onto your on-premise adobe Connect server as a Connect Administrator and enter the following into the URL line in Connect Central:

http://YOURDOMAINNAME/api/xml?action=meeting-feature-update&account-id=7&feature-id=fid-meeting-passcode-notallowed&enable=false

Where “YOURDOMAINNAME” is actually your domain name.

If this executes correctly, you will see the following output when you follow-up by entering this command into the same URL line in Connect Central:

http://YOURDOMAINNAME/api/xml?action=meeting-feature-info&account-id=7

Output: feature-id=fid-meeting-passcode-notallowed

Alternatively you could simply check and see if the feature is available under the Edit Information tab of any Meeting.

Note: Your Meeting passcode can be up to 16 letters or numbers; keep in mind that it is a convenient supplementary security mechanism rather than a primary means. You will see this warning if your passcode is not supported go over that: Your passcode must be between 1 and 16 characters long (letters or numbers, no spaces).

In adding this feature you have invoked the Web Services API in Connect. If you are not familiar with the API see the following document; it is rich with options: http://help.adobe.com/en_US/connect/9.0/webservices/connect_9_webservices.pdf

Note also that with Connect 9.2, in Connect Central under Administration > Users and Groups > Edit Login and Password Policies, there are two relevant check boxes, one to enable and the other one to force the use of the passcode:

passcode.fw

The Mystery of Burst Packs for Meetings

Issue: Adobe Connect hosted customers sometimes ask how to predict the burst pack size needed for insurance that their large meetings with unexpected attendance will be handled.

Solution: Burst Packs will extend the capacity of the Named Host license by up to five times the ceiling. This means that a room with a ceiling of 100 is best covered by a burst pack of up to 500 attendees, or 400 above the standard capacity of 100.  The burst pack minutes will be depleted, for each minute each user exceeds the capacity of 100.  For example, if 110 people join your meeting at the same time, and all 110 stay for 10 minutes, this will require 100 burst pack minutes to accommodate the 10 additional attendees in overage multiplied by 10 minutes.

If during a meeting, you accidentally go over the number of attendees accommodated by your burst pack, then the burst pack  balance will appear as a negative number.  If the meeting is very well attended and the burst pack exceeds 1000, it will be disabled for future meetings so no more overage will be accrued.   For the initial meeting overage, it will go over 1000 (one-time) if a current meeting is on-going, and won’t shut down until that meeting ends. Adobe does not penalize you for your successful use of Connect, but the hard limit for overage is set to 1000.

The meeting will not kick people out because of an overage;  burst pack minutes will continue to accumulate, even if the burst pack is depleted in order to ensure the meeting is not disrupted.  Adobe will then take those overage minutes out of their next burst pack purchase.

Ask your sale representative about burst packs and how to add them to insure successful large meeting in Connect.

Vantage Point is not just about Bandwidth

Vantage Point from Refined Data works with Connect and provides remote control of Cameras, Microphones, Telephones, Volumes, Tech Support, Motion Detection, Mouse Detection, Continuous attendance tracking and reporting and much more so it’s not just about bandwidth reduction.

On the bandwidth front, Vantage Point publishes streams to Refined Data servers at 100Kbps for each participant in the room; this is less than Connect in most cases, but the Host only consumes as many streams as they can view at one time. The host can see as few as 5 or 6 students at one time or as many as 50 or more depending on their screen resolution, window size, Vantage Point settings, connectivity and bandwidth availability.

This means that even with 100 Participants in a Connect room and one Host the bandwidth consumption looks like this:

  • Participant Load: 100kbps Up (to publish their own camera to Vantage Point), 100kbps down (to view the Host in Connect). This is a small signature on the network.
  • Host Load: 100kbps Up (to publish their own camera in Connect), 2.5mbps down (assuming they view 25 participant cameras in Vantage Point at one time). The Host is the only one who needs a really good connection.
  • Total Load on Adobe Connect: 1 publish stream + 99 subscribers

The host can always reduce their own load simply by viewing fewer simultaneous Video pods in Vantage Point. The bandwidth load for students or participants is not affected at all by class size. Bandwidth load for Hosts rises linearly with class size but can be limited by the host at any time based on the maximum number of cameras they view at one time.

In Connect, the bandwidth load rises with the number of cameras being shared:

  • 4 Cameras: 16 Connections on the Server, each user publishes 100kbps and consumes 300kbps
  • 10 Cameras: 100 Connections on the Server, each user publishes 100kbps and consumes 900kbps
  • 20 Cameras: 400 Connections on the Server, each user publishes 100kbps and consumes 1.9mbps

Even if Connect could technically support 50 or 100 simultaneous web cams in a single meeting (2,500 streams risks significant latency), consider the requirement that participants would need 5-10mbps of bandwidth to support the load, before accounting for VoIP, screen-sharing and basic overhead. Anything above 10 simultaneous web cameras may be difficult for a host to manage and apart from any other considerations, there may not be enough real-estate for content if you are showing 10 or more web cams in the meeting room.

Vantage Point only publishes at 100kbps, most of the time; DSL and Standard quality is already more than twice this load in Connect and can easily rise higher if the room is set to use the Highest video quality at 16:9. With Vantage Point, Adobe Connect saves the server load, participants are not affected by class size, Hosts can see all of their students, all of the time and enjoy unparalleled control of the classroom environment.

Check it out at Refined Data: http://vantagepoint.refineddata.com/

Linux Sound Card Drivers cause a Crash during a Connect VoIP Session

To avoid problems with select Linux sound card drivers turn off Enhanced Audio in a Connect Meeting:

Meeting->Preferences>Microphone:

mic-enh.fw

Some crashes on Linux are avoided by turning off Enhanced Audio and canceling Acoustic Echo Cancellation Mode.