Large Seminar Sessions need to be scheduled 45 minutes before start of Session

In Adobe Connect 9.5 Seminar sessions need to be scheduled 45 minute(s) prior to the start time of large seminars to allow for implementing > 600 participants (license purchased for Webinar 1000 Managers)

9.5-SeminarSession

Instant sessions created from the large seminar room will only allow < 600 participants

9.5SeminarSessions

Previously with 9.4, the expected number of participants had to be selected in order to distinguish between regular Seminar Sessions (up to 600 Participants) and large Seminar Sessions (> 600 Participants)

Regular Sessions

This option is no longer listed with 9.5 since we now have dedicated webinar servers to accommodate large seminar licenses for both standby mode and scheduled sessions.

Attendee Pod in large Seminar appears in Presenter Only Area

In Adobe Connect 9.5, large Seminars (license purchased for Webinar 1000 Managers) are now by default launched on the Webinar Server (both in stand by mode and session scheduled)

Attendee Pod is functional only in “Presenter Only Area

AttendeePodListedEdited
Attendee Pod is NOT functional in “main meeting/seminar room area

AttendeePod

 (For reference only),

rtmps://na12wbn2.adobeconnect.com:443/?rtmp://PACNA12WBN02:8506/meetingas3app/1280557514/1424793651/

9.5 Large Seminar Attendee Pod

 

 

 

 

 

Benefits of this functionality

  • To conserve bandwidth and CPU load
  • Highly recommended when anticipating over 100 participants (drop down listing of participants viewed only by hosts/presenters)

Previously, with the 9.4 release, the Attendee List Pod was functional for large seminars only in the stand by mode (< 600 participants) when launched on FMS (Meeting server) and NOT on the Webinar Server

(For reference only),

rtmps://na12fms1.adobeconnect.com:443/?rtmp://PACNA12APP03:8506/meetingas3app/1280557514/1424426402/

9.4 LargeSeminar

 

Moving Meeting Rooms to User Seminars Folder

In Adobe Connect 9.5, Meeting Hosts now have the ability to move normal Adobe Connect Meetings into their own User Seminars folder if they are part of a Named Webinar Manager group.

Previously, with the 9.4 release, we added new Seminar licensing called ‘Named Webiner Managers’. This essentially gives users in that new group, the ability to create and manage their own Seminar rooms (under their User Seminars folder).   In Adobe Connect 9.5, if you are a Named Webinar Manager and you are in the Meeting Hosts group and want to move one or more of your Meetings from your My Meetings folder (User Meetings > {username}) or the Shared Meetings folder to your individual User Seminars folder, you can now do this in the UI.

move

You will notice the new link location for User Seminars in the Move functionality.

Patch for Connect Mobile on iOS9

The previously existing workflows for installing Connect Mobile on iOS9 from the browser no longer work. A server-side Connect patch and an updated Connect Mobile application is required:

  • The server-side patch can be applied to any Connect 9 version except 9.5
    • Users on Connect9.5 won’t need the server-side patch
    • There in not currently a patch available for Connect 8.x servers
  • The Connect version, after the server patch is installed will have the following notation:
    • iOS9_Mobile_patch
    • View-able in the version.txt file on the updated Connect server
  • Users with older versions of Mobile application who have not upgraded to iOS9 will not need the patch
  • Adobe Connect hosted account holders need only update the client Mobile application to version 2.4.10 or higher

The Connect Server Patch and Updater page is here and contains the iOS9 patch: http://helpx.adobe.com/adobe-connect/kb/connect-90-patches.html

See the following reference: iOS 9 release date, features and news

Named Vs Concurrent Pricing Model

Problem: What is the difference between a Named and a Concurrent pricing model?

Environment: Hosted/Licensed

In order to understand the difference we present you with two different accounts having Named and Concurrent pricing models.

Named Host Pricing Model

As an example, I would take up the example of my local account. Below is the license information of my account.

We read the following information for a Named Host license.  In Named Host Pricing Model, you need to check two values.

  • Meeting Hosts
  • Concurrent Users Per Meeting

Named Host Pricing Model
Meeting Hosts:   5 / 5      (Consider this value as Mx)

Meeting Peak Concurrent Users:   Unlimited   (Soft Limit: Unlimited)
Concurrent Users Per Meeting:   100   (Soft Limit: 100)  (Consider this value as Mn)

Burst Pack Minutes (Total Used/Total Purchased):   0 / 0
(Balance:0 – Disabled)

Max meetings that can run simultaneously <= Mx

Total number of users who can enter in a meeting <= Mn

In this case Mx=5 and Mn=100

So you can run 5 meetings simultaneously with a cap of 100 users in each of these meetings.

So not more than 100 user can be present in any of these meeting rooms.

See this hierarchy:

Named_Host

Concurrent Attendee Pricing Model

For Concurrent pricing models we only consider ‘Concurrent Users Per Meeting’, since there is no restriction on how many concurrent meetings you can run.

As an example of the license info on my local account below :

Concurrent Attendee Pricing Model
Meeting Hosts:   16 / Unlimited  (Consider this value as Mx)

Meeting Peak Concurrent Users:   100   (Soft Limit: 100)  (Consider this value as Mn) 

Concurrent Users Per Meeting:   Unlimited   (Soft Limit: Unlimited)
Burst Pack Minutes (Total Used/Total Purchased):   0 / 0
(Balance:0 – Disabled)

Mx=Unlimited Hosts(There is no restrictions on number of hosts, hence not limiting the number of meetings you can run)

Mn=No of users who can join a meeting when counted together in all the active meetings.

Here Mn=100 and say we are running 5 meetings so In total 100 users can join.

User in Meeting1+Meeting2+Meeting3….+Meeting5<=100.

See this hierarchy.

Concurrent_new

Please Note : The above license limit values have been used here for demonstration purpose. Individual user accounts would have their own limits as per the license they have purchased.

Please refer our official document for complete information about these licensing models : 

https://helpx.adobe.com/adobe-connect/kb/named-host-license-update-faq.html

Please contact support if you have further queries on the same.

Emails fail to send and keep returning to Pending status

Problem Overview :

There have been some important instances described in this article to prevent issues sending emails from Adobe Connect Events module :

http://blogs.adobe.com/connectsupport/ensuring-that-email-generated-by-adobe-connect-servers-is-received/

I’m just describing here another instance we noticed recently which might result in similar issue with events module or any other module in Connect.

If you’ve followed all the information in the above article, you may want to review this to see if you might be running something similar to below.

 

Environment : Adobe Connect Hosted (may affect On-Premise deployments as well)

Version : All

Behavior when issue occurs :

 

Email-2

 

Email-1

Reason Behind the behavior :

Check if your account is in active state at the moment and it might not have eventually reached expired state. If the account gets expired, all Adobe Connect Administrator users would get a similar notification as below upon first time logging in. Contact your Adobe Connect administrator for a confirmation.

The accounts which get expired, do remain in activated state for some time, however with limited functionality. Some account features like meetings/contents remain accessible for the users, however some functionality like emails are limited to only active accounts.

 

Email-3

 

Errors which might be noticeable in logs :

The requests on the server side might show partially complete status(‘C’), however should also be linked with Interrupted (‘I’) or Bounced  (‘B’) status.

[08-11 05:48:35,013] cqEmailer0 (INFO) doCQEmails: processing Action - Action Id:1393368804, Type:notification, Status:new, Scheduled Date:Tue Aug 11 05:15:00 PDT 2015
[08-11 05:48:35,027] cqEmailer0 (INFO) 3ms update com.macromedia.breeze.model.Action("1393368804",Tue Aug 11 05:48:36 PDT 2015,"C",40)
[08-11 05:48:35,017] cqEmailer0 (INFO)  2ms update com.macromedia.breeze.model.Action("1393368804","I",40)

 

Resolution : 

Contact support or your reseller to get your account renewed or extended for the functionality to work.

 

Not a valid email while creating a user for UN-Common email domain

Problem: Not a valid email error while creating a user for uncommon email domain

Description: Email validation discards the uncommon domain name

Method to replicate this problem

Step:1

Go to Administrations > User and groups > New users
2015-08-11 19_55_16-New User Information

Step:2

Fill the information for user and use the following email address abcd@org.world

Result: We will get an error message “Not a valid email address”

Expected:Connect should create a user.

Workaround

For Hosted Solution

1: Change the login policy , we need to go to Administration > User and Group > Edit Login and Password Polices and check “NO” on “Use e-mail address as the login”

login

2: Create the user without email.

2015-08-11 19_56_02-New User Information

Solution for On-Prem deployment

1: Download new version of Email Validator from here

2: Extract the files from ZIP and copy commons-validator-1.4.1.jar

3: Go to \Connect\9.3.1\appserv\web\WEB-INF\lib
Paste the commons-validator-1.4.1.jar
rename the existing commons-validator-1.4.0.jar to commons-validator-1.4.0.jar_old
rename commons-validator-1.4.1.jar to commons-validator-1.4.0.jar

4: Restart the connect service

5: Try creating user with .world domain it will work as expected

Additional Note: We identified this issue in 9.4 and logged as a bug #3988289 which has been fixed in Adobe Connect 9.5 version.

Troubleshooting On-premise Telephony SSL Handshake

The inability to save an audio profile is sometimes caused by a failure of the the ssl connection. Here is an example of a pop-up generated by an ssl handshake error using a telephony adaptor:

ssltel.fw

If the ssl handshake for a telephony adaptor connection fails, check the telephonyservice.conf file in C:\Connect\9.3.1\TelephonyService\conf

Backup the file and find the System properties definitions:

# System property definitions (-D) ( 50 … 99)
wrapper.java.additional.50=-Dapplication.home=..\TelephonyService
wrapper.java.additional.51=-Djava.endorsed.dirs=..\tomcat\bin
wrapper.java.additional.52=-Dcatalina.base=.
wrapper.java.additional.53=-Dcatalina.home=..\tomcat
wrapper.java.additional.54=-Djava.io.tmpdir=.\temp
wrapper.java.additional.55=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
wrapper.java.additional.56=-Djava.util.logging.config.file=..\tomcat\conf\logging.properties
wrapper.java.additional.57=-Dlibrary.service=WIN32

Add a line if needed:

wrapper.java.additional.58=-Djavax.net.debug=ssl:handshake

Save and restart the Adobe Connect Telephony service.

telephsvc.fw

In this example case an error was found in the Intercall_Adaptor.log; check the log appropriate to the adapter being used \logs\telephony\

logstelephony.fwssltel1.fw

Check the server to server connection (from the Connect server) using the URL in telephony-settings.xml in \TelephonyService\conf\ In this example:

https://iccapi.audiocontrols.net:8443/axis2/services/CCAPI?wsdl

ccapi.fw

Check the TelephonyService.keystore:

  • Connect\9.3.1\TelephonyService\cert
  • Connect\9.3.1\\jre\bin\keytool.exe

keystoredir.fw

From a command prompt (edit install directory location as required):

C:\Connect\9.3.1\jre\bin>keytool -list -v -keystore C:\Connect\9.3.1\TelephonyService\cert\TelephonyService.keystore

Check the cacerts in C:\Breeze\9.3.1\jre\lib\security\cacerts.txt

cacerdir.fw

Compare from a command prompt (edit install directory location as required):

C:\Connect\9.3.1\jre\bin>keytool -list -v -keystore C:\Breeze\9.3.1\jre\lib\security\cacerts.txt

Note: TelephonyService.keystore packaged with Connect expired on Nov 9 2013; this will be updated in version 9.6.

Check the SSL entry in the server.xml file in \Connect\9.3.1\TelephonyService\conf

<Connector port=”9443″ protocol=”HTTP/1.1″ SSLEnabled=”true”
maxThreads=”150″ scheme=”https” secure=”true”
keystoreFile=”${catalina.base}/cert/TelephonyService.keystore” keystorePass=”connect”
clientAuth=”false” sslProtocol=”TLS” URIEncoding=”UTF-8″ />

 The logs for each adaptor are depicted by name: \Connect\logs\telephony\-relevant-adaptor.xx.log

logstelephony.fw

The debug log is also often helpful: \Connect\logs\support\debug.xx.log

debuglog.fw

As is the telephony application log: \Connect\logs\support\apps\_defaultHost_\telephonyProviderTesterApp\instances\7\####\application.xx.log

teltestapplog.fw

Note: As a general rule, when sending logs to Adobe Connect Support for scrutiny of a telephony (or any server-side) issue, it is prudent to send all logs (if allowable) by truncating them to focus on the issue at hand:

  • Stop all services: FMS, FMG, Connect & Telephony
  • Rename or delete all log directories
  • Restart all services and recreate the problem being scrutinized
  • Stop all services and zip complete log directories focused on the issue at hand and provide them to the support consultant

And along those same lines, entire conf directories and custom.ini file can also will help us locate the source of problems as well:

  • C:\Connect\9.3.1\TelephonyService\conf
  • C:\Connect\9.3.1\comserv\win32\conf
  • C:\Connect\9.3.1\comserv\conf
  • \Connect\9.3.1\custom.ini

Troubleshooting FMG On-premise: “Error in joining Audio Conference”

If Flash Media Gateway cannot establish a connection, you may see this pop up message upon invoking Unified Voice: Error in joining Audio Conference:

fmg.fw uvtestfail.fw

 There are a number of potential causes; let’s consider some approaches to troubleshooting:

Restart the FMG service. Check the task manager to make sure that there is not a hanging FMG process. If fmgmain is hanging, terminate it manually through the task manager and then restart the FMG services. Here are the relevant services highlighted:

rel-svcs.fw

Manually check the FMG status from the Connect server  via a browser and telnet:

  • http://fmgIPAddress/2222/admin/getFMGStatus?auser=sa&apswd=fmgpassword

fmgcheck.fw

  • telnet from fmg to the Connect server on 8506
  • telnet from the Connect server to fmg on 2222
  • telnet from fmg to sip on 5060
  • Check to see if ports are listening:
    • netstat -an|find “8506”
    • netstat -an|find “2222”

Here is the flow illustrated with an eye toward the Intercall implementation:

Connect_FMG_Flow

These are the relevant logs for troubleshooting telephony issues; some Connect telephony adaptors leverage FMG:

  • \Flash Media Gateway\2.0.1.19_8x8\log\core.xx.log and master.xx.log, sip.xxxx.log

fmglogdir.fw

  • \Connect\logs\telephony\-relevant-adaptor.xx.log

logstelephony.fw

  • \Connect\logs\support\debug.xx.log

debuglog.fw

  • \Connect\logs\support\apps\_defaultHost_\telephonyProviderTesterApp\instances\7\####\application.xx.log

teltestapplog.fw

Note: When sending logs to Adobe Connect Support for scrutiny of a telephony (or any server-side) issue, it is generally prudent to send all logs if allowable by truncating them to focus on the issue at hand:

  • Stop all services: FMS, FMG, Connect & Telephony
  • Rename or delete all log directories
  • Restart all services and recreate the problem being scrutinized
  • Stop all services and zip complete log directories focused on the issue at hand and provide them to the support consultant

And along those same lines, the entire /conf/ directories, all four zipped will help us locate errors as well:

  • C:\Connect\9.3.1\TelephonyService\conf
  • C:\Flash Media Gateway\2.0.1.19\conf
  • C:\Connect\9.3.1\comserv\win32\conf
  • C:\Connect\9.3.1\comserv\conf

Relevant configuration files for troubleshooting may include:

  • \Flash Media Gateway\2.0.1.19_8x8\conf\sip.xml, rtmp.xml, http.xml, workflow.xml

fmgconfdir.fw

  • \Connect\9.3.1\TelephonyService\conf\telephony-settings.xml, server.xml

telconf.fw

  • \Connect\9.3.1\custom.ini

customdir.fw

FMG connection settings are configurable in the console on port 8510 on the Connect server. While it is recommended that FMG be installed and run on a separate server, in some cases, it is collocated with Connect. Check to make sure there are not two instances of FMG where only one is needed. This is possible as when distributing FMG onto a separate server as appropriate in a robust clustered environment, an oversight may be to leave it also installed locally on the Connect server as well:

fmg8510.fw

Delete superfluous instances and disable any local unneeded FMG service.

fmg85101.fw

  fmgsvc.fw