Author Archive: pawakuma

H.264 encoded FLV not displayed when it is reshared again in share pod

Issue: H.264 encoded FLV not displayed when it is re-shared again in share pod.

Steps to reproduce:

1. Share H.264 encoded FLV in a share pod.
2. Stop sharing (without viewing it completely).
3. Share the FLV again from the share history.

Result:Video bar progresses but the audio and video is not rendered.

Reason: The FLV encoded in H.264 has this limitation that unless initialized from beginning it will not render video (and audio)  frames. When we share it from ‘recently shared content’ it is not initialized from the beginning. Server tries to play it from the last cue point, which causes this issue. If we seek it to a position it starts to play well.
The behavior is not seen in VP6 encoded FLVs.


  1. Seek to start of the recording. Once initialized, we can seek to any point and it will play just fine.
  2. Re-encode the FLV with VP6 codec.

Recording duration shown as “Null” when a recording zip file is uploaded as content to connect server.

Problem description:- Recording duration shown as “Null” when a recording zip file is uploaded as content to connect server.

Method to create it

1)Create a recording.

2)Download the recording as zip.

3)Upload the recording to content.

4)Observe new content info page.

Result:  Duration is not shown.

Expected: Duration should be shown.

Workaround: None

This is not a supported work flow and hence “No fix”


On clicking twice on correct hot spot option in a content and then unselecting one, the answer is shown as incorrectly answered and report doesn’t show any option selected by the user

Problem Description :-  On clicking twice on correct hot spot option in a content and then unselecting one, the answer is shown as incorrectly answered and report doesn’t show any option selected by the user.


1. Upload a PPTX file in content library that has a Hot Spot type question.

2. Click twice inside the correct hot spot (option 1 in the attached PPTX case).

3. Click on any of the 2 hot spots above to un-select one.

4. Now press submit button.

Result: You will see a message that you have incorrectly answered the question. In the reports, No response is shown in ‘By Answers’ section.

Expected: As the answer was correct, user should see You have answered the question correctly. Reporting should be fine too.

Note: The same issue can be seen with P8 too.

This is currently scheduled to be fixed in connect version 9.2

Adobe Connect supported cameras and mic

Adobe Connect supports most cameras and video cards.  Adobe doesn’t maintain a list of supported cameras and video cards because there are too many combinations to test.We essentially have a statement about what we do support in theory.

To broadcast video from the Camera and Voice pod in Adobe Connect Meeting, the operating system must have a valid camera driver. If the operating system doesn’t have a valid camera driver, Adobe Connect cannot use the camera.  Adobe Connect uses the operating system API to check for the camera driver.  Typically most cameras, including high def and professional cameras will support this.

If your camera or video card doesn’t work with Adobe Connect, you can provide the camera and video card specifications from the manufacturer to us and we can determine if this is compatible.

All that said, we’ve certainly had customers use professional camera setups (multiple cameras with a switch) or video production quality cameras with operators following the action in live events, etc, but at the very end of the setup, the feed has to be going into a PC that is hooked into Adobe Connect and that connection is the one you’d bring into the Camera and Video pod.  We have had customers with very high end setups with audio and video mixers, etc. but the camera feed needs to go into a supported video card in a computer that is running an Adobe Connect session, and that feed needs to be brought into the Camera pod.

You can try any type of camera you have access to, as long as there is a valid webcam driver that Flash Player (Connect Meeting Addin) can detect in the Operating System.  It’s essentially the same mechanism if you use Google’s Gmail with Video Chat.  When you try to select a camera in the dropdown in Gmail settings, it will detect the available camera/drivers.  Connect is the exact same thing.

The following webcams don’t work well in the meeting Video Pod.

  • Creative VF0260
  • Microsoft VX 3000
  • Osprey 230 video card

Problem: use osprey 230 video card and publish camera stream and when user resizes the video pod or changes the layout which has a  bug video pod the camera stream freezes.

*** This issue is fixed in 9.1 that is coming out later this year (with a new add-in).

Enable Universal Voice for Integrated Telephony Adaptor

The basic purpose of this changes would be to combine the features of UV and Integrated Telephony

1. Enable Audio Broadcast in Meeting for VOIP users (available in UV however not in Integrated telephony). VOIP and telephony users collaborate.

2. Dial Out from meeting, enabled users to be able to dial themselves from the meeting room (available in Integrated telephony however not in UV)

Prerequisite: Flash Media Gateway configured with SIP settings.

Add the following snippet within the <telephony-adaptor></telephony-adaptor> tag for any provider you want to enable for UV.

For PGI NA Adaptor:


For PGI EMEA Adaptor:


For Intercall Adaptor:


Additional information:

<conf-num>: The phone number for the audio conference. This element must be first in the dial-in-sequence. You can only have one <conf-num> element. The adaptor provides the value in the curly brackets {}.
<delay>: A delay in the dialing sequence, in milliseconds.
<dtmf>: A DTMF (dual-tone multi-frequency) tone. A DTMF value can be any number or letter on a telephony keypad, including * and #.

Text Limitation in Connect Meeting Chat Pod

User may often complain about text missing from Chat Pod of the meeting. The purpose of this guide to to explain how Chat History in retained in various aspects.

  • Total history of chat saved at the server is 5,000 messages (public + pvt). This is the same history that will be e-mailed to the hosts, if they ask for it.
  • When a client connects for the first time, he receives only the last 250 chat messages from the server.
  • All future chats are added to his chat area.
  • However when the characters in chat window exceed 50,000 it is trimmed to half i.e. all complete chat lines are kept such that   total characters are less than 25,000.
  • It is to be noted here that total characters present counted here are of html formatted text and also include the html tags.
  • Hence number of chat lines seen at the client end are not fixed and depend upon the length of the chats and formatting.