Monthly Maintenance Releases

Adobe Connect continues to see growth with more meeting minutes each month.   As usage grows, Adobe endeavors to be even more responsive to customer support requests and reduce issue resolution time.  To accomplish this, we’ve moved to a monthly cadence for double-dot releases (e.g. 9.5.7).  To keep you informed of these regular releases account administrators will be receiving email notifications on the updates and bugs fixes for the release and the time of each maintenance window.  Thanks for your continued and growing use of Connect.

Adobe Connect Unified Voice and Cisco Call Manager

Most Unified Voice (UV) integration is between Adobe Media Gateway (AMG/FMG) and an external Session Initiation Protocol (SIP) server as depicted in the diagram below:


In the case of Cisco Call Manager (CCM), the AMG/FMG connection is commonly internal on the Local Area Network (LAN) based rather than external on the Wide Area Network (WAN) based as depicted below:


The LAN based flow is very similar to the WAN based flow. AMG/FMG to SIP for UV is simply replaced by AMG/FMG to CCM. Port 5060 must be opened between AMG/FMG and CCM for SIP communication and rort range 5000 – 6000 must be opened for the Real-time Transport Protocol (RTP) voice packets. DTMF mode RFC 2833 must be supported by CCM as well as by its carrier.

Specific CCM integration steps:

  • Create a username and password based SIP account on CCM
  • Login into CCM and navigate to Device -> Phone -> Add new
  • Select Third Party Basic Device
  • Select SIP profile as the Standard SIP Profile
  • Select Digest User as the LDAP ID of a User X
  • Check the block for  Media Termination Point Protocol


  • Navigate to User Management > End User
  • Search for the LDAP User ID of the SIP account
  • The user-id, LDAP User is the CCM SIP user
  • The pin is the password for the CCM-based SIP


Configure the Connect UV SIP account settings using the username and password of the SIP account. For additional help with setting up UV in Connect see the video tutorial: Audio in Adobe Connect Meetings

Safeguarding the Newly Edited State of a Connect Meeting

Environment : Hosted, ACMS, Managed ISP and On-premise

Hosts should select the End Meeting menu option instead of clicking the “x” in the upper right of the Meeting Addin or browser at the conclusion of a Meeting in order to insure the state of the Meeting is immediately saved and the Meeting processes terminated.

When a Meeting Host deliberately ends a Connect Meeting using the Meeting room Meeting menu option as depicted, the Meeting room state is saved and the supporting Meeting processes are ended.


If the Meeting Host ends the Meeting by clicking on Meeting >End Meeting menu option then the Meeting session is ended for all the users in that Meeting room; users will get a message stating that the meeting has ended. This action triggers the Connect server to save the state of Meeting and end the supporting processes. This is a safe and tidy way to manage Meetings; it ensures that the meeting is ready for next session along with all the content which was added during the previous session.



Alternatively, if a Meeting Host closes the Meeting room by clicking the “x” in the upper right side of the Meeting Addin or browser, then the Meeting will remain active until all users have left the Meeting room before closing. The Meeting will wait for up to 12 hours before timing out and closing the Meeting room if participants keep open any Addin or browser sessions in the Meeting room. Keeping a Meeting open this long runs some inevitable risks to the recently edited current state of a prolonged Meeting.

Note: If there are multiple Meeting Hosts, any host leaving prior to others may choose to Exit Adobe Connect as well:


Connect on-premise: Tunnelling and connectivity issues when running Stunnel 5.34

Customers running Connect on-premise with Stunnel to terminate SSL connections are advised to stay clear of Stunnel version 5.34.

A few of our customers reported issues where meeting connections would always fall back to tunnelling or at times meeting connections never complete when running Stunnel 5.34.

A quick lab test shows that versions 5.25, 5.33 and even the beta 5.35b4 do not cause this behaviour. You can find archived versions of Stunnel on one of the mirror sites listed on the Stunnel download page.



Error while uploading license file “there is already another item with this name”

This applies to On-Premise accounts only.

In rare situations, you may face a problem while uploading the license file in Adobe Connect.

Error: “There is already another item with this name”.  While checking the debug.log you find below (or similar) log snippet

[06-30 14:18:06,893] console-8510-6 (INFO)  1ms spid:332 com.adobe.connect.dal.PrincipalDAL.getGroupByType(“7”,event-admins)

[06-30 14:18:06,894] console-8510-6 (INFO)  1ms spid:332 update com.macromedia.breeze.model.AclEntry(“7″,”30″,”11016”)

[06-30 14:18:06,895] console-8510-6 (INFO)  1ms spid:332 com.adobe.connect.dal.ConsoleDAL.getShortcutScoByType(shared-training-templates,7)

[06-30 14:18:06,896] console-8510-6 (INFO)  1ms spid:332 com.adobe.connect.dal.ConsoleDAL.updateScoURLPath(“/f1185513619/”,”11020″)

[06-30 14:18:06,898] console-8510-6 (INFO)  0ms spid:332 com.macromedia.airspeed.db.SQLServerUtilityQueries.setIsolationLevel(Disable Isolation)

[06-30 14:18:06,899] console-8510-6 (INFO) Response status: invalid/duplicate

We can find from the logs that it is pointing to Shared-training-templates and giving us a url_path “/f1185513619/” and sco-id “11020“.

Get path details from this api: [Connect domain]/api/xml?action=sco-nav&sco-id=11020

Get to this path and rename the training template folder.  Re-upload license file.  This should resolve the issue.

Connect On-premise: Hosting the Adobe Connect Addin on your own server

This is applicable to Connect 9.5.x, I have not verified the steps in older versions, but Connect 9.0 and higher should share the configuration.

By default even in on-premise environments downloads of the Connect Addin are done from, but you can change the default download location to point to your own server.

To do so, find the AddInInfo.xml here:


And update these two lines with the local path to the addin install files:

<m id=”addInLocation” platform=”Windows”>default</m>
<m id=”addInLocation” platform=”Mac OS 10″>default</m>

with the new local path:
<m id=”addInLocation” platform=”Windows”>/common/addin/setup.exe</m>
<m id=”addInLocation” platform=”Mac OS 10″>/common/addin/AdobeConnectAddin.z</m>


This will give you the Addin that came with your server during install and it may not be up to date. If you want to make sure you provide the very latest addin, download it from our Updates page “Adobe Connect Downloads and Updates“. The Windows version you can download comes in a Zip file which contains a file called AdobeConnectAddin.exe and not setup.exe. Extract the AdobeConnectAddin.exe to the your Connect server in the path as above and update the path in the AddInInfo.xml to reflect the new filename.



If you have a reason to continue using an older version of the Windows Addin you should rename the setup.exe in order to workaround a reported vulnerability.

Just go to this path /common/addin/setup.exe on your server and rename the setup.exe file to something else, i.e. AdobeConnectAddin.exe.

Then, update the download location in the AddInInfo.xml files accordingly:

<m id=”addInLocation” platform=”Windows”>/common/addin/AdobeConnectAddin.exe</m>




Connect 9.5 Bandwidth Utilization Estimates Illustrated


Adobe Connect bandwidth utilization will vary based on use case. Variables such as Meeting size, Connect features employed, disposition of clients and type of Connect server hosting, all have an effect on the network bandwidth utilized and as well as on where the bandwidth on a network will be most affected.

This article focuses on bandwidth and not on latency: Latency and bandwidth are different topics that are often confused or inappropriately lumped together. Although in some cases there may be a correlation between bandwidth and latency as when exceeding available bandwidth will drive up latency, nevertheless, the relationship between them is often inappropriately overstated. Bandwidth refers to the size of the network pipe while latency refers to the speed over the network or the time it takes for the data to travel. Connect clients with excess bandwidth may still experience latency with Connect for reasons unrelated to bandwidth such as network distance, transmission errors, resource performance (server, DB or client), maintenance schedules and imposed constraints such as QoS or blocking the RTMPS protocol and thereby forcing inefficient tunneling of RTMPS encapsulated in HTTPS.


For information on latency see the following articles:

Tunneling with RTMP encapsulated in HTTP (RTMPT) should be avoided as it causes latency

Connect Meeting RTMP VS/VIPs on Load-Balancers

Adobe Connect Database Performance and Monitoring

 Connect on VMWare – some deployment tips

Below are some references on the topic of Connect bandwidth; these are often referred to as a general guide; the examples sited later in this article however are from baseline testing described herein:

Estimating Bandwidth Consumption in Connect Meetings

Best Practices for Adobe Connect

Adobe Connect best practices for large events and seminars

VoIP Bandwidth and Microphones

The Connect Cluster:

The context of the Connect bandwidth utilization is important and should be included among pre-deployment architectural considerations when rolling out Connect. There are basically two primary Adobe Connect deployment models for consideration: In the cloud and on-premise. The disposition of the clients attending the meeting has an effect where the on the network bandwidth will be utilized for any Connect Meetings or Webinars. To support these two broad deployment paradigms of cloud or local on-premise, there are three basic Adobe Connect licensing models.

  1. Adobe Connect Multi-tenancy Hosted
  2. Adobe Connect Managed Services (ACMS) single domain hosting
  3. Adobe Connect On-Premise licensed single domain

Note: An Adobe Connect on-premise license need not only be deployed within the customer’s LAN infrastructure. Adobe Connect Partners offer Managed ISP hosting options and an on-premise license deployment can be cloud-based as well.

Cloud or LAN:

For the purposes of considering the relationship of bandwidth to architecture, an Adobe Connect cloud-based deployment and an on-premise deployment within a customer’s LAN present different concerns with reference to the disposition of bandwidth rather than with the specific license type.

Primary differences with reference to bandwidth when comparing cloud-based Connect server clusters with on-premise based Connect server architecture is with the handling of external clients and the direction of the network traffic. There will be less internal network traffic on the LAN when external users (with possible lower-impact exceptions such an SSO server) remain external. Note that VPN users in remote offices are considered internal users.

See the following diagrams comparing a 2-server cloud-based cluster with a 2-server on-premise cluster hosted on a customer LAN. Both assume the need for internal and external users to participate in Meetings.


With a cloud deployment, the external users have little or  no impact on the internal LAN of the Connect account owner. The biggest bandwidth hit is at the cloud-based hosting facility. The primary concerns for the Connect owner’s IT will be routing RTMPS around third-party proxy servers and making sure client profiles and other internal restriction, limitations and constraints do not prevent or enervate Connect usage:



With a LAN-based on premise deployment, internal Connect users will normally have great performance on the average corporate back-plane by avoiding any mitigating and often unpredictable WAN variables. External users may be hosted on a reverse proxy Connect Edge server in the local DMZ to meet security requirements. All external traffic is terminated in the DMZ where the remote Edge server does all the heavy lifting. The Edge connections to the internal cluster consolidate the external connections and reduce the overall internal impact of external users by limiting them to the external firewall and DMZ:


Connect Meeting Features and Bandwidth:

Screen-sharing and the use of multiple live web cameras are the two most bandwidth intensive activities in any Connect Meeting or Webinar. The latter requires that a Meeting Host or Presenter project the client screen up to the Connect servers and then back down to each user in the Meeting. The more users with cameras, the more upload and download activity.

The features employed in any Connect Meeting determine the amount of bandwidth utilized.  Depending on the Connect use case, you could use between 5 to 10 Mbps per 100 participants. These general rules apply:

    • The typical average is 50 kbps per user
    • It depends on what Connect Meeting users are doing
    • For example, on the high end one client measured regularly uses 20 Mbps for 150 users in a Connect Meeting room.
    • More typically there is a max of 100 Mbps at the firewall (outgoing, incoming is never that high)
    • With just over 1000 users a safe estimate is < 100kbps per user totaling 12 MB
    • 5 Mbps per 100 is the low average (or 6MB per 1000 users using best practices for large Webinars).
    • Things like video and screen sharing tend to use more bandwidth
    • A one-to-many broadcast of an uploaded PowerPoint deck uses less bandwidth
      • PPTX should always be uploaded to the Meeting room
      • Do not present a PPTX using screen-sharing as it wastes bandwidth

Bandwidth Utilization Use Case Baseline Tests:

The following tests corroborate these guidelines listed above and offer a model to test bandwidth utilization for any Meeting or Webinar use case; it is prudent to do these type of tests with your specific use Webinar case as part of your rehearsals to get accurate bandwidth utilization baselines:

First bandwidth test: I uploaded a 15.5 MB PPTX to a Connect Meeting room and advanced thru all the slides while monitoring the download stream to each client; the average for each client was 50 kilobits; see below:


Second bandwidth test: I then tested with a camera pod set to the highest quality and wide screen option: Meeting>Preferences>Video; see my host camera settings below:


The average download stream at each client when I had the camera pod sized small in the upper corner of the meeting while flipping slides was under 200 kbps (kilobits); The host screen capture below corroborates; my host client in the Connect addin is pushing 121 kilobits up to the server; see below:


The average when I expanded the camera pod and moved around create some activity on screen (waving etc.) was 300kbps download streaming to each client; see below my upload from host client to server is 381 kbps; see below (wow- my hair is getting thin):


Third bandwidth test: I then tested screen-sharing a slide deck from my desktop to simulate application sharing live demonstrations and found a significant variance based on the screen resolution of the host sharing the screen:

  • Host screen-sharing at 1920×1080 resulted in an average  download to each participant of 700 kbps
  • Host screen-sharing at 1288×768 resulted in an average download to each participant of 200 kbps
  • The participant experience was very similar. I see no reason to waste the bandwidth on the higher host screen-resolution: Lower screen resolution resulting in very economical bandwidth utilization while sharing the screen
  • See the bandwidth indicator while I share my screen flipping through multiple jpegs at 1288×768. I am pushing up 338 kbps to the Connect server while actively changing jpeg images on a second monitor that I am sharing.


Fourth bandwidth test: Video – I created an mp4 using the following settings: Appropriate quality settings are a major variable determining the amount of bandwidth used and the playback experience of mp4 video in Connect:

  • I used: H.264, 720×404, Frame Rate 30, bitrate CBR, target rate 1Mbps, Key Frame Dist 90.
  • Best practice encoding for video in Connect imperative: Rehearsal and testing of any Video used is prudent prior to any Meeting or Webinar. It is easy to test playback experience and bandwidth consumption per client participant. Note also here (in the highlighted bandwidth indicator) how my remote office client experiences some latency albeit manageable  (595kbps down) that not affect the video playback experience – no choppiness at all watching the pups wrestle (the Jack-Russell ends up winning although this capture shows him as the underdog):


Bandwidth Utilization Use Cases:

Using the baselines from these tests, here is a list of potential use cases from a recent customer inquiry with the predicted overall account-wide bandwidth usage estimates running Connect 9.5.

Case 1: A 1500 user seminar room with a PowerPoint and a desktop share:

Estimate: 1500 users x 50 kilobits each for the PPTX use case =75000 kilobits or 9MB. Add to that a desktop share with conservative screen-resolution (1280×768) 1500×200=300000 kilobits or 37MB. Add them together (75000+300000) for an average of 375000 kilobits or 47MB. Realistically it will be less at any given time because it is rare to simultaneously do both activites at once in a meeting. It is more common to share either flip PPTX slides or share an application thereby lowering the actual bandwidth utilized at any given time.

 Note: There is an important caveat with reference to an initial spike caused by the PPTX SWF download of 1000 kbps per client participant for a few seconds each. This affects every use case with SWF content is a share pod. Assuming 1/3 at a time as participants enter the layout with the PPTX on stage in a share pod even if downsized in a corner or hidden behind another pod, and assuming that there will not be any screen-sharing initially during the downloading: 1500/3 = 500x1000kbps for a few seconds each = 50000 kilobits or 62.5MB. A worst case spike scenario of all entering at once due to host error or a late upload due to last minute editing (this should be avoided if possible): 1500×1000=1500000 kilobits or187MB Spike for up to 10 seconds depending on latency effects on the initial SWF download. This spike may be missed in testing if you rely on the Meeting room bandwidth indicator as it may happen too fast to register; it is better measured using Wireshark on a client in the Meeting.

Case 2: A 1500 user seminar room with a PowerPoint and a 10 minute MP4 Video played:

Estimate: 1500 users x 50 kilobits each for the PPTX=75000 kilobits or 9MB. Assuming a medium quality MP4 (as discussed above) uploaded to the meeting room and meted out at an average 600 kbps per participant with intermittent spikes to 1200 kbps: 1500×1000=1500000 kilobits or187MB + 9 = 196MB while the video is being played with the PPTX still onstage visible in another pod. Note: Until the Video is played, this room is at 9MB just meting out PPTX SWFs after the initial SWF downloads are complete.

 Note: PPTX download spike variables as described in case # 1 above applies.

Case 3:  A 1500 user seminar room with a PowerPoint and two, 3 minute videos played:

Estimate: Same as case 2 above assuming that the videos are played one at a time.

Case 4: Two 1500 user seminars with just PPTs for content (uploaded to the Meeting room and not screen-sharing) and jpeg pictures for Presenter head-shots in lieu of a camera:

Estimate: 1500 users x 50 kilobits for the PPTX=75000 kilobits or 9MB x 2 seminar rooms = 18MB

 Note: Assuming the seminars will not start both at the same time and will nevertheless overlap, the brief PPTX download spike variables as described in case # 1 above applies albeit multiplied by two: 126 MB for 1/3rd and worst case of both seminars doing a last minute deck upload at the start of the Meeting: 274MB until initial SWF downloads complete. Staggering slightly the start of each seminar will mitigate the overall spike as will allowing users to trickle into a prepared room with assets on stage.

Case 5:  Two 1500 user seminars with just PPTs for content (uploaded to the Meeting room and not screen-sharing) and PPTs for headshots shared, PLUS 100 separate Connect meetings of 20 users each, with 10 of those meeting rooms sharing one web camera:

Estimate: 1500 users x 50 kilobits each for the PPTX=75000 kilobits or 9MB x 2 = 18MB, plus 90 meeting rooms with 20 users each doing the same activity, 1800×50 kilobits=90000 kilobits or 11MB, plus the 10 meetings with cameras added 10 x 20 users each x 200 kilobits=40000 kbps or 5MB; also add the upload for each camera 10 cameras x 200 kilobits =2000 kbps or .25MB. Total =.28000 kilobits or 35MB.

Note: Assuming the various meetings will be starting at different times the spike estimates for #4 above apply.

Case 6:  Two 1500 user seminars with just PPTs for content and PPTs for headshots shared, PLUS 100 separate Connect meetings of 20 users each, with 10 of those meeting rooms sharing one web camera, PLUS one 500 user seminar with a PowerPoint shared(uploaded to the Meeting room and not screen-sharing).

Estimate: Add 500 users x 50 kilobits each = 25000 kilobits or 4MB. Add this to use case 5 depicted above: 35MB+4=39MB.

Note: Assuming the various meetings will be starting at different times the spike estimates for use cases #4 and #5 above apply here.

Case 7: Two 1500 user seminars with just PPTs for content and PPTs for headshots shared,  PLUS 50 separate Connect meetings of 20 users each with 10 of those meeting rooms sharing one web camera, and one 500 seminar with just a PowerPoint shared (uploaded to Meeting room and not screen-sharing):

Estimate: 1500 users x 50 kilobits each  for the PPTX=75000 kilobits or 9MB x 2 = 18MB, plus 40 meeting without cameras x 20 users each=800x50kbps= 40000kbps or 5MB, add the 10 meetings with cameras 10 meetings x 20 users x 200 kilobits=40000 kbps or 5MB; also add the upload for each camera 10×200=2000 kbps or .25MB. Total= 232000 kilobits or 29MB.

 Note: Assuming the various meetings will be starting at different times the spike estimates for use case #4, #5 and #6 above apply.


It is easy to avoid both overestimating and underestimating the bandwidth needed account-wide for Connect deployments on-premise or in the cloud. For large Webinars, a quick rehearsal with a small sample audience of external and internal users as appropriate is prudent. Best practices in large Meetings make a substantial difference in the amount of bandwidth utilized: Proper camera use, screen-sharing and video-encoding are all very important considerations.  Although it may at this point seem like a mantra, a basic best practice that so many Connect users miss is to upload a PowerPoint to the Meeting room share pod rather than use screen-sharing to run through a slide-deck. Maybe some Presenters are just overly possessive and have an innate refusal to let their work upload – whatever the reason, I will surely be in a Meeting today and some Presenter will share a PowerPoint from their desktop via screen-sharing and I will need to avert my eyes to maintain my light grasp on sanity. Used properly, Adobe Connect is the best means to deliver rich collaboration experiences while minimizing the impact on bandwidth utilization.

What Triggers the Low-bandwidth Pop-up While Screen-sharing in Connect?

Inquiring minds have asked what is the bandwidth threshold that triggers the low bandwidth toast pop-up while screen-sharing in Connect:


The answer: We show this message when the available bandwidth (BW) drops to 1/4 of the initial BW set in the meeting. The initial BW is set based on the chosen quality setting the host picks for screen sharing under Meeting>Preferences>Screen Share Settings Quality:


Following are the BW settings and the thresholds:

Quality Settings Bandwidth (kbps) BW toast threshold (kbps)
Low 500 125
Medium 800 200
Standard 1200 300
High 2000 500

These BW settings are the default and may be edited in the  application.xml file for on-premise customers.

Adobe Connect 9.5.3 On-Premise Servers on Windows 2003

Note: This article applies only to Connect on-premise customers running Connect on Windows 2003 servers.

For on-premise Adobe Connect customers running Windows 2003, it is vital to upgrade the servers to at least 2008 (or higher) prior to upgrading Connect to 9.5.3. The Connect command-line converter will not run on Windows 2003 and will fail with the following error in the Connect debug logs:

CreateProcess error=193, %1 is not a valid Win32 application

The release notes for Connect 9.5.3 are here:

The 9.5.3 updater is here:

Connect Meeting RTMP VS/VIPs on Load-Balancers

This article applies to on-premise Adobe Connect servers running behind hardware-based load-balancing devices or SSL accelerators.

A common cause of performance problems in Adobe Connect Meetings stems from the improper configuration of the Virtual Server (VS) Virtual IP Address (VIP) handling Real Time Messaging Protocol (RTMP) traffic in on-premise Connect deployments.

An Adobe Connect Meeting Server is at least two servers in one (possibly more if AEM/Events and UV telephony are incorporated); it is at least always a Tomcat-based HTTP application server and an Adobe Media Server (AMS) using RTMP. The two servers are fully integrated to work together in tandem to support Adobe Connect Meetings.

The most popular load-balancing and SSL acceleration  option in the Adobe Connect on-premise enterprise is the F5 BIG-IP Local Traffic Manager (LTM). This tech-note will illustrate the proper configuration of an RTMP VIP supporting Adobe Connect Meeting on an F5 LTM. The concepts apply to any load-balancing device and SSL accelerator.

The first thing to note is that the general configuration of a Connect server or cluster running behind an SSL accelerator or load-balancing device always requires more then one VIP. There are no exceptions to this rule and any attempts at shortcuts will result in delayed deployments and support cases. Attempts to place all traffic on a single VS/VIP are as common as they are incapacitating. General Connect cluster architecture tech-notes are here:

Adobe® Connect™ server pools/clusters and hardware-based load-balancing devices with SSL acceleration

Adobe Connect Servers and Hardware-based Load-balancing Devices

A simple diagram of an Adobe Connect server behind an F5 LTM follows; see the two VS/VIPs and Fully Qualified Domain Names (FQDNs) for each on the LTM:


Below we add a server to show a basic Connect cluster VIP configuration; see how each Connect Meeting server has its own VS/VIP while one VS/VIP servers both HTTPS application servers.


Note: Neither of these basic diagrams depicts advanced configurations such as the integration of the Adobe Experience Manager (AEM) Events module. This article focuses on the performance of the Adobe Connect Meeting RTMP VIP in its basic context.

There is usually not an option for RTMP in the VIP profile of a hardware-based load-balancing device. A basic TCP profile is the correct choice. Here it is depicted on an F5 BIP-IP LTM:


With detail:




Note that the symptom for an improperly configured VS/VIP is either the inability to launch a Connect Meeting or excessive latency in the Meeting due to RTMP tunneling (RTMPT) encapsulated within HTTP when the RTMP VIP is blocked or inoperable.

The presence of a capitol “T” in the latency indicator of an Adobe Connect Meeting indicates tunneling as depicted in this tech-note:

Tunneling with RTMP encapsulated in HTTP (RTMPT) should be avoided as it causes latency

Further diagnosis is usually warranted by using the Connect Meeting Addin in logging mode as depicted here:

Enable Logging in the Meeting Addin

Also here:

Troubleshooting Verbose Meeting Addin Logging

When the RTMP VS/VIP profile is improperly configured, the Connect Meeting addin verbose log will show it clearly, particularly when it is compared with the server-side debug log.

Example snippet from a Connect Meeting addin verbose log:

18:51:55    16844    PLAYER_TRACE    SSL connection closed.
18:51:55    16844    PLAYER_TRACE    SSL DoSSLHandshake WaitHandshake not in ssl_active state. (State is 0.) Failing.
18:51:55    16844    PLAYER_TRACE    SSL DoSSLHandshake WaitForSocket not in ssl_active state, failing.
18:51:55    16844    PLAYER_TRACE    SSL Receive socket read error 0x0.
18:51:55    16844    ACTION_TRACE    5/10/2016 14:51:55.101 [DEBUG] breezeLive.main.FCSConnector [attempt 1 of 60] Trying fallback tunneling connection rtmps://
18:51:55    17179    PLAYER_TRACE    NetConnectionIO::DoConnect rtmps protocol, HTTP(S) tunneling, tunnel open succeeded.

The corresponding snippet in the server debug log as well as the application logs will read: RTMPT and often reconnect=true:

               Line 23456: 2016-01-17  14:25:06              32260    (s)2641173          Asc-Room               IA_CONNECT      [dID:32, ticket:123456789xyz, phase:, uID:, name:]             New client connecting:  { ip=, protocol=rtmpt, player=MAC 11,9,971,247, savedConnectionSpeed=undefined, reconnect=true }                        –

[11-05 15:08:05] FCSj_Worker:18 (INFO) params: {bytesdown=0, protocol=rtmpt, ticket=123456789xyz, status=C, reconnect=true, nickname=John Doe, action=register-client, role=v, bytesup=0, session-timeout=12}

Correct configuration of the RTMP VS/VIP is extremely important; a Connect Meeting VS/VIP must have a dedicated FQDN.  It must have its own SSL certificate if SSL is accelerated through the load-balancing device and the VS/VIP must not have an HTTP profile; a TCP profile is needed.

For some additional information about troubleshooting Connect architecture with reference to hardware-based load-balancing devises and SSL accelerators, see the following tech-notes:

The Adobe Connect Deployment Guide on the F5 Website needs Updating

Configuring application-level health monitors for Connect on BIG-IP Local Traffic Manager