Posts in Category "General"

Some Basic Facts about VOIP(Voice Over Internet Protocol),UV(Unified Voice) and Integrated Telephony in regards to Adobe connect.

Description:- The basic facts of these three components of connect meeting audio element( VOIP,UV and Integrated Telephony)  ( This Article is for License/on premises software users however hosted users can also use this to understand the concept behind these elements)

Connect can record both VOIP and telephony streams only if UV(Unified Stream) is there. To be able to configure UV on connect, user has to have FMG setup/configured and a SIP provider or probably an on premises SIP server of their own.

Now there are many options to disable a provider to use UV:

  • First No FMG server setup
  • No/incorrect dial-in sequence in telephony-setting.xml for any particular adaptor.
  • UV is not enabled by itself for any adaptor unless FMG is configured with connect server.

In all the above situations you will see a Radio Button in the audio conference settings as shown below:

R-L

Radio button implies that you can either use VOIP or Integrated Telephony in the meeting room. If you choose VOIP all the streams are available to connect and hence can be recorded at the Connect end itself. However if you choose ‘Using Phone’ radio button, connect system doesn’t know about the telephony streams due to absence of FMG/UV. In this situation recording will be done remotely at the audio bridge end ( in other words at provider end ) and will later be integrated with the connect recording.

Now If FMG is Present and configured and UV is enabled :

Connect system knows whereabouts of both the VOIP and the integrated telephony streams and hence doesn’t need remote recording. But again there is an option in Connect console, where you can force recordings to be done at the Bridge end, this just acts as an insurance in case Connect fails to record something at its end, remote recording can be integrated later with the Connect-voice-less recording.

In case of UV only providers – the one that you create by providing a dial-in-sequence in My Audio providers in Connect webapp – you always have a dial-in sequence, so you will always see check-boxes in the meeting room audio conference settings. In this case remote recording is NOT used, as Connect has all the voice streams information it needs to create a recording.

R-L

I hope this helps in understanding some facts about voip,uv and integrated telephony.

Thanks

Aspect Ratio 16:9 for video pod does not apply on MAC computers

Description:- When you select 16:9 aspect ratio it displays a 4:3 ratio in a window with empty space on MAC computers however A true 16:9 aspect ratio will fill out that whole empty space, which works fine on windows machines.

Reason Being : It was a bug according to which, on Mac computers it is a Limitation that cameras cannot support wide screen (16:9) Aspect Ratio. This was basically more of a flash player limitation which at present, is set as by design.

 

Pods that connect mobile app supports.

Description: Many a times user has questions like “Are we allowed to download files from file share pod on an IPAD or any android device?”

I have attached an image below describing all the pods(Host view) that connect mobile supports:

The navigation icons on the left side of the app indicate what Connect mobile supports and File share and Web Links pods are not supported.

Connect-App

I hope this helps answer some of your questions related to IPAD/IOS device.

Thanks

Editing Connect On-premise Email Send Source Options

Adobe Connect hosted customers have long enjoyed the option of having their Connect account administrative email sent out to users on behalf of a specified email source rather than the system email parameter configured during installation of the Connect server.  In order to exploit this option for on-premise Connect deployments, you first need to apply the following SQL update statement.  This will  add a row into the pps_account_features table:

insert into PPS_ACCOUNT_FEATURES
(ACCOUNT_ID, FEATURE_ID, DATE_BEGIN, DATE_END)
values (7, 71, ’2014-02-20 00:00:00.000′,’3000-01-01 00:00:00.000′)

After adding this row, check the system email settings with the SQL statement below to make sure it is correctly configured:

select * from PPS_CONFIG
where name like ‘%email%

The results of the query above should correspond with the settings prescribed on local port 8510 on the Connect server settings page in the Connect server configuration wizard.

SECTION              NAME    VALUE   COMMON_NAME
hosted   validation-emaillist                         NULL
main      config-bcc-email              NULL     NULL
main      config-support-email      admin@connectaccount.com         NULL
main      config-system-email        admin@connectaccount.com        NULL

After making the prescribed database changes, they will either take effect immediately after you cycle the Adobe Connect and Flash Media services or after 10 minutes. You do not need to cycle the services unless the change must be immediate.

With the above settings in place, if you create a user in Connect with the email address  joe@connectaccount.com and then you add  Joe to the Meeting Hosts group, the admin designated in the system-email parameter on the server settings page will send email on Joe’s behalf.

To prove this, simply log in, as Joe, create a meeting and add the user with email admin@connectaccount.com (or anyone you chose) as a meeting participant and send that person a meeting invitation. It should read: admin@connectaccount.com; on behalf of; joe@connectaccount.com:

The meeting invitation will look something like this:

From: admin@connectaccount.com [mailto:admin@connectaccount.com] On Behalf Of Joe
Sent: Sunday, February 23, 2014 5:30 PM
To: WhoeverIChoose@wherever.com; WhoeverIChoose
Subject: Adobe Connect – Meeting Invitation to “My most excellent meeting”
When: February 23, 2014 5:30 PM-6:30 PM (UTC-05:00) Eastern Time (US & Canada).
Where: http://meeting.connectaccount.com/meeting/

Please join me in an Adobe Connect Meeting.

Meeting Name:  The Only Meeting <snip>

Note: This will not affect password reset email messages.

How long does it take to publish Connect recordings as MP4s?

An MP4 recording will be published and posted within 24 hours of invoking the conversion.

  • the actual amount of time it takes to convert a recording depends on many factors including:
  • the length of recording
  • the queue of recordings to be published on the publishing servers
  • the queue of recordings within Connect prior to transfer to the publishing servers (they are submitted in parallel to the conversion servers)
  • the time it takes to download the converted MP4s from the conversion servers back to Connect
  • and variables commensurate with asynchronous processing

Note also that if for any reason the conversion to MP4 should fail,  we will retry multiple times depending on the cause of the failure. Retries will extend the processing time required before the recording is available. The two most significant variables are the length of the recording and how many recordings are ahead in the queue.

Connect Console Values Populate to Wrong Profile in the sip.xml File

Issue: When installing FMG as part of an on-premise Connect deployment, the fresh installation of FMG includes many default profiles in the sip. xml file. When you enter values from Connect console (port 8510 locally on the server), those values are populated to the first profile that is listed in sip.xml (sipPhone) and not to the correct sipGateway profile which is called from the workflow.xml file.

The expected behavior is that the values from Connect console should update the sipGateway profile rather than the first profile in sip.xml

Workaround: The Adobe Connect Support team is using currently approaching this problem from one of two possible ways:

  • You may copy a sipGateway profile from a vertsion of FMG prior to version 2.x and paste that into FMG 2.x.
  • You may call sipPhone profile from workflow.xml

Note: In FMG prior to version 2.x, sipGateway was the first profile listed in sip.xml.  The workflow.xml file checks the input  number and on the basis of that chooses the profile from sip.xml. With default FMG settings it will be using ‘SipGateway’ most of the time. This is scheduled to be fixed in Connect 9.3.

Using a Named Instance of SQL Server with Adobe Connect

Issue: When using  a named instance of SQL server with Adobe Connect, if you enter the name of the instance during installation, the connection to the database will fail.

Workaround: Instead of using the name of the instance, you may enable TCPIP on the instance and use the IP address and then enter the port number for which the named instance is configured on the separate line as appropriate; if the named instance is listening on port 1833 (instead of 1433), then you would use the IPAddress (192.168.1.1)  and then the port number (1833) in the appropriate fields.

Using the instance name during installation after Connect version 8 will not work. The best approach is to use the port number of the instance and the IP Address of the database server.

To troubleshoot this, use SQL Server Configuration Manager:

Screen Shot 2014-02-21 at 7.59.05 AM

  • Make sure the instance has TCP/IP enabled.
  • Check to see what port the instance is listening on for that IP.
  • Use the IP address as server name (no instance name).  Put the port number in the port number field.
  • Make sure the named instance is listening on the port entered in Connect

Screen Shot 2014-02-21 at 7.59.41 AM

Screen Shot 2014-02-21 at 8.00.24 AM

Beginning with Connect version 8, the installer changed; in previous earlier versions, you would need to enter the the server instance and port on the same line.  The  newer installer has the port on a separate line:

HOST: INSTANCE-IP-ADDRESS
PORT: INSTANCE PORT-NUMBER
DATABASE NAME: SAMPLE-NAME
USER: SAMPLE-USER
PASSWORD: ****************
CONFIRM PASSWORD: ****************

The changes in the installer (beginning with Connect version 8) caused some confusion with named instances.

A named instance will work on an initial installation.  Sometimes, in an effort to troubleshoot you may initially point to a conventional instance of SQL in order to establish the installation and then point the established Connect installation to a named instance. The DB connection from an established Connect installation is more robust and forgiving than that of an initial installation.  After the installation is complete, you can modify custom.ini to include the instance name.

Note: You could use the server name, but you would need to ensure that the named instance has NAMED PIPES enabled.

Sharing Application in Multi-Monitor Setup

In Connect versions through 9.2, there is a known issue relating to sharing applications in a multi-monitor setup.

The behavior can be duplicated as follows:

  1. From within a Connect meeting room, click “Share My Screen” in a Share Pod
  2. In the Start Screen Sharing dialog that appears, choose to share “Application”, and select an application to share and click the “Share” button
  3. The application window needs to be located on the second monitor of the user who is sharing (you may need to drag the application window to the second monitor)

At this point, other users attending the meeting will not be able to see the shared application.

This issue is expected to be fixed in Connect 9.3

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