Adobe Connect access level explained

Problem: Some of the users get confused on the various access levels given to the users on adobe connect account.

Environment: Licensed/Hosted

Reason:  An administrator is not actually the administrator as it also requires other group’s membership to perform some tasks. Given below is a diagram that explains the access levels.

Access level3

Click on image to enlarge.

A Super admin on adobe connect is a user having group memberships of meeting host and administrator.

Admin user enters into the meeting room as participant.

 

Problem: Admin user enters into the meeting room as participant.  This issue only occurs in “Named Host Pricing Model”.

Environment: Hosted/ Licensed

Reason: In Named Host Pricing Model users have to be part of Meeting Hosts Group in order to enter into the meeting as Host.  Only being member of Administrator group will not allow the user to enter as a host in his own meeting.

Solution:

  • Make sure that you are listed as a host for the meeting room under Edit Participants link.

Image-1

  • Make sure that you are a part of Meeting Hosts group. In order to know your group membership click on my profile>group membership. If you don’t see meeting hosts listed there then follow the instructions given below.
  • Go to Administration>Users and Groups.
  • Select Meeting hosts>Choose Information>View group members.  Add your name to this group.

Image-22

 

You can now try to enter the room.  If you are still getting the same issue contact Adobe Connect Support.

 

Adobe Presenter Version Compatibility with Adobe Connect

Problem Description : Is Adobe Presenter old and new versions compatible with Adobe Connect 9.2 ?

Answer:

All versions of Presenter should work with the Web Application (e.g Content, Courses, Curriculum’s, etc ). However the issue is with Meeting as Connect version 6 and version 7 are AS2- based(Action Script 2)  Meetings, thus content will launch in Connect 6/7 Meetings only. Similarly, AS3 based content will work with Connect version 8 and 9 Meetings.

Action Script version comparison :

•    C6 & C7 = Presenter up to 7.0.6. AS2
•    C8 &C9 = Presenter 7.0.7 and higher.  AS3

Hope this helps in understanding some concepts, relates to Presentations published using Presenter on connect.

Thanks,

 

 

 

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

 

Connect 9.1.x on-premise server – “Send Invitations” checked by default

When creating a new meeting you are asked if you want to send out meeting invitations by email.

In Connect 9.1.x the option to send invitations is selected by default.

If you do not wish to send out invitations for your meetings you have to select “Do not send invitations” every time you create a new meeting.

sendInvitations

You can change this behavior to make  “Do not send invitations” the default when creating a new meeting.

To do so, edit the notify.xsl file which is located in \Connect\9.1.1\appserv\apps\meeting\  ( but please remember to take a backup copy of the file).

1. Open the notify.xsl in an xml-friendly editor such as notepad++

2. Find this section:

<table cellpadding=”0″ cellspacing=”0″>
<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘send-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”/results/common/date”/>
<xsl:with-param name=”checked” select=”true()”/>
</xsl:call-template>

<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘no-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”‘ignore’”/>
<xsl:with-param name=”checked” select=”false()”/>
</xsl:call-template>
</table>

3. Change “false” to “true” and “true” to “false” to swap the selection.

It should now look like this:

<table cellpadding=”0″ cellspacing=”0″>
<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘send-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”/results/common/date”/>
<xsl:with-param name=”checked” select=”false()”/>
</xsl:call-template>

<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘no-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”‘ignore’”/>
<xsl:with-param name=”checked” select=”true()”/>
</xsl:call-template>
</table>

 

4. Save the file and restart the services.

5. Check your changes by creating a new meeting. If you encounter any issues, restore the original file.

 

 

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

Enable Video Vs Enable Webcam for Participants

In Connect 9.2, there are two ways you can allow a ‘participant’ to turn their camera on – but each has slightly different results.

Enable Video – this option gives full rights to the video pod, same as a host. Or in other words, if you enable Video for any participant, that particular participant will get presenter rights over the Camera pod just like in case of Enhanced rights over any pod.

 

 

Untitled

Enable Webcam For Participants – this doesn’t give overall video pod rights (the participants can’t Force Presenter View, or choose who is in the main Filmstrip, etc.), but it allows them to turn their camera on. However you cannot be selective with this option – everyone will be able to turn on their camera.

Untitled1

FYI, If you “enable video” for a participant and then “enable webcam for participants” you lose the ability to “disable video” for any already enabled participant until you first “Disable Webcam for participants”

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/

 

 

XML API Tips: Arkadin Profile Creation – Display Numbers

Previously I posted a blog entry on creating audio profiles via the XML API (http://blogs.adobe.com/connectsupport/xml-api-tips-creating-telephony-profiles-via-the-xml-api/).  This is an add-on article describing one additional step for finalizing an Arkadin profile.

Once you complete the Arkadin profile, you may notice the Conference Numbers aren’t showing up at the bottom of the profile (in the UI).  When you build a profile in the UI (without the API) and you save the profile, it will display the Conference Number and Conference Number Toll Free in a datagrid below the credentials.  When you create a profile with the API, it will not (unless you go into the UI and then click Edit and then Save again).

ark1

Notice no Conference Numbers listed in the grid below the Profile Status.

Also, if you create the profile with the API (and you don’t go into the UI and click Edit/Save), you may notice that the conference numbers are not displayed in the Dial In dialogue box in the meeting room for participants.  It will only list the Moderator and Participant codes.

ark3

Notice, no numbers appearing to call into…

To get the numbers to show up in the Profile and in the dial-in dialogue box inside of the meeting room itself, you need to add one additional web service call to your workflow as below:

Once you build your telephony profile from the previous article,  you need to take the profile-id value and make the ‘telephony-profile-dial-in-number-update‘ API call to input the new numbers as such:

/api/xml?action=telephony-profile-dial-in-number-update&profile-id=1379585623&location=Toll%20access%20number&conf-number=+1-8xx-xxx-xxxx&location=Toll%20free%20access%20number&conf-number=+1-xxx-xxx-xxxx

Where you add the profile-id
where you add all the ‘locations’ you want (the string for the conference number description)
where you add the applicable conference numbers for each (toll + toll free for instance)

After completing this step, if you view the profile in the UI again, you see the numbers appear:

ark2

Conference Numbers now listed in the grid below the Profile Status.

 

ark4

Notice now the number(s) appear.