Posts in Category "Administration"

Error creating or editing a UV profile

This article is applicable only to customers using Universal Voice telephony profiles and running into a very specific error in the user interface.  If you are not experiencing the exact problem below, you do not need to worry about this article.

The error: ‘This field only accepts valid DTMF commands and phone numbers (+,0-9,*,#,-,space,A,B,C,D).

uv.jpg

Issue: Recently an issue has cropped up with editing existing (or creating new) Universal Voice (UV) profiles.  This is directly related to a required change that was introduced in the latest version of the Adobe Flash Player.  The behavior is that if you try to go into My ProfileMy Audio Profiles > and click the ‘New Profile’ button  or  My Profile > My Audio Profiles > and select an existing UV profile and click the ‘Edit‘ button, you will get this error (above) when trying to SAVE the profile.

This issue is resolved in the upcoming Adobe Connect release (9.5.3).  In the interim (for Adobe Hosted customers while they wait to be upgraded) or for Licensed (on-premise) customers who may be on an older version of the application and not able to upgrade to 9.5.3 right away when it comes out, there are basically 3 ways around this problem…

    • [1] Downgrade Flash player to a version prior to version 21 or use a browser or machine that has an older version of the Flash Player (prior to 21).  This would require you to uninstall the Adobe Flash player in a browser where it is not embedded as part of the actual browser, and install an older version from the archived versions here.
    • [2] Create (or just edit an existing) mms.cfg file on the system and add the following flag (line) in the file (this will ONLY work for the next 3 months approximately).  This is only a temporary solution and the Flash Player team plans to remove support for this flag in upcoming updates but for now, it can be used until we deliver possible patches for older Connect versions and fix this in the upcoming 9.5.3 release.


      enablePCRE2=0

This mms.cfg file can be created on your system in a simple text editor if it doesn’t already exist on your computer.  First do a search for it.  If it doesn’t exist, simply create a new file in Textpad or Notepad or Textedit or whatever you use for a simple text file editor.  Add the one line above and save the new or existing mms.cfg file (with that line as either the only line in the file or added to the bottom of whatever else is in that file).

On Windows systems, the mms.cfg file would be (or needs to be) placed in:

C:/Windows/system32/Macromed/Flash (32-bit Windows) and C:/Windows/SysWOW64/Macromed/Flash (64-bit Windows).

On Mac systems, the mms.cfg file would be (or needs to be) placed in:

 MainDisk:Library:Application Support:Macromedia

    • [3] Use the XML API.  As this is only a Flash Player issue and only affects users who are using the UI in Adobe Connect, if you are familiar with the XML API, you can use the ‘telephony-profile-update‘ API as a workaround. If you are not familiar with the XML API, the documentation for the API is here.  If this is still confusing for you and you are not quite sure how to execute XML API calls, the steps below will not be for you.  If you need clarity on the below, please contact Adobe Connect support as you normally would.

The workflow is as follows for the API (again if you are not familiar with the API, you need to either familiarize yourself with the product documentation, ask and admin for assistance, or use one of the other workflows above to work around this issue):

For existing profile updates:

1) Find the profile-id by making this API call in the browser once you’ve logged into your Adobe Connect account: https://{yourConnectURL}/api/xml?action=telephony-profile-list

It will list out all your profiles.  Search for the one you want to edit and make note of the ‘profile-id‘ value (numeric) and the ‘provider-id‘ value (also numeric).

2) Get the field-ids by running this API: https://{yourConnectURL}/api/xml?action=telephony-profile-info&profile-id=xxxxxxxx  (where the profile-id = the numeric value of the profile from call 1 above).

This will show you an XML response with telephony-profile-fields listed.  You may have a field for a certain moderator pin or other value you need to edit.  The field will be listed as an ‘x-tel‘ field.  It will be in a format that looks like this: ‘x-tel-123456789‘ or something similar with numbers after the ‘x-tel’.

You can also get the fields for the provider by taking the provider-id and running this API: https://{yourConnectURL}/api/xml?action=telephony-provider-field-list&provider-id=xxxxxxxx

This will show you all the ‘x-tel-xxxxxxx’ values you need to use.

3) To update that field, you would make this API call:  https://{yourConnectURL}/api/xml?action=telephony-profile-update&profile-id=xxxxxxxx&provider-id=xxxxxxxx&field-id=x-tel-123456789&value=xxxxxxx&profile-status=enabled   (where profile-id, provider-id both equal their corresponding numeric values from the first API call above…and where the field-id= the x-tel value from call 2…. and where value= the new value you need to edit)…

For creating NEW profiles:

1) Find the provider ID you want to create a new UV profile from with this API call: https://{yourConnectURL}/api/xml?action=telephony-provider-list .   The provider-id value gets returned in this result.

2) Obtain a list of all the applicable provider fields by running this API call: https://{yourConnectURL}/api/xml?action=telephony-provider-field-list&provider-id=xxxxxxx (where the provider-id = the numeric provider-id for that UV provider).

3) Run this API to create a new UV profile: https://{yourConnectURL}/api/xml?action=telephony-profile-update&provider-id=xxxxxxxx&profile-name=xxxxxxx&field-id=x-tel-xxxxxxxxx&value=xxxxxxx&profile-status=enabled  (where the provider-id= the numeric provider-id for that UV provider… field-id= the x-tel field you want to populate …. value = the value (numeric) of that field…. profile-name = the name of your new profile …. profile-status=enabled ).

Of course, you could have more than one field to populate as everyone’s UV providers/profiles could be custom and unique to a requirement.

If you are unsure, you need to talk to your Connect admin or contact Adobe support of course for any questions regarding the above profile creation or update steps.  A support agent can assist you with identifying values and creating / updating profiles if needed.

Virtual Classrooms and Account Limit Reached Error

This article is applicable ONLY to Adobe Connect users who have purchased a Named Virtual Classroom Manager license within the Training Module and are running into Account Limit Reached messages unexpectedly when they are launching Virtual Classrooms.

With the release of Adobe Connect 9.4 in May of 2015, we introduced a new training license model called the “Named Virtual Classroom Manager”.  This is specifically for Connect users to create and host Virtual Classrooms (plus it gives you access to the Events module).  It is basically another way we are licensing access to Virtual Classrooms.  This means there are technically two different types of Virtual Classrooms that can be created when you have the Training module enabled:

  1. The ‘traditional’ model of Virtual Classrooms (VC) which use the Concurrent Learner seat quota on the account (up to 100 seats per room), and…
  2. The Named Virtual Classroom Manager (NVCM) model of Virtual Classrooms which use a built-in 200 seat quota and does not use any Concurrent Learner seats.

When accounts are provisioned and quotas and features purchased, customers have the option of buying ONLY a Named Virtual Classroom Manager license.  They do not need to buy any additional training seats for Concurrent Learners.  In the older traditional model, in order to use a Virtual Classroom, you had to buy Concurrent Learner seats (say 250 seats for sake of discussion).  When a training manager created a VC, it would utilize seats out of that (in this example) 250 seat quota, up to 100 attendees (the rest of the concurrent seats could be used for another VC or other training content).  It was capped at 100 per VC.  With the new Named Virtual Classroom Manager license, you can now have only the NVCM feature enabled (and essentially have purchased no other training seats…so Concurrent Learner quota =0) or you can have it in conjunction with other training seats purchased in case you have a need for on-demand courses and curriculum, etc.. The NVCM model VC will not use any Concurrent Learner seats. It has a built-in 200 seat quota per room.  However, the caveat here is that the VC created for intended use with the NVCM model needs to have one of a few conditions in place in order to take on that NVCM model.  Otherwise, it may inadvertently take on the behavior of a traditional model VC and it could lead to unexpected circumstances like an ‘Account Limit Reached’ when the very first person joins the VC.

Let’s explain…

To create a Virtual Classroom, no matter what type of training features/quotas were purchased, all you need to be is a Training Manager, Named Virtual Classroom Manager, or Administrator.

The process of creating a VC is always the same.  You click on the “New Virtual Classroom” button from within the Training module.

Each time a Virtual Classroom is launched, Adobe Connect checks a few conditions to see how the VC should be licensed when it launches.  The result of which will dictate the quota used for the seats.  Where this becomes very problematic and confusing for customers is when the customer ONLY purchases a NVCM license and doesn’t have any Concurrent Learner seats (so Concurrent Learner = 0).  It is possible for a customer to create and launch a VC that is trying to use a Concurrent Learner quota by mistake.  If that happens, you will get the error ‘Account Limit Reached‘ right away.

For the sake of the scenarios below that explain how the VC’s are licensed when they launch, I will also mention that when a VC is created in a NVCM’s individual user folder under the Training tab, it automatically is a NVCM model room.  If it’s created under the Shared Training area of the Training tab, then there is a setting you can check or uncheck called ‘Named Virtual Classroom Model‘.

nvcm

The value can either be Yes or No.  Below in the listed scenarios, that is what ‘set to yes’ or ‘set to no’ means.

Also below in the listed scenarios, a ‘NVCManager‘ is a person who is in the group ‘Virtual Classroom Managers’ in the Users and Groups area of Connect.  That is what gives that person the ability to utilize the NVCM model.  A ‘non-NVCManager‘ indicates someone who is NOT in that group.  This would be a normal Training Manager or Administrator.

Here are the conditions and scenarios (assuming the room is Public) where a VC can be launched with or without the 200 seat expected NVCM quota:

Green = NVCM is used and quota will be 200 seats
Red = traditional model is used and quota will be taken from Concurrent Learner seats and could result in an “Account Limit Reached” error if that quota is 0.
Orange = NVCM is used but there could be some confusion due to the lack of NVCM in the room or permissions for that NVCM.

Scenarios:

  • VC created in My Training folder by NVCManager – launched by NVCManager = Will use NVCM license (quota 200)
  • VC created in My Training folder by NVCManager – launched by non-NVCManager = Will use NVCM license (quota 200) however will not have the host present even if non NVCM who launched the room is a host (permission-wise).  A NVCM needs to be present for the room to have an initial host, similar to Named Host Meeting.  If the VC is ‘public’ as far as access level, it will launch and use the 200 seat quota for that owner, but if the owner isn’t in the room, the users who have entered will be participants.
  • VC created in Shared Training folder by NVCManager (set to yes) – launched by NVCManager = Will use NVCM license (quota 200)
  • VC created in Shared Training folder by NVCManager (set to yes) – launched by non-NVCManager = Will use NVCM license (quota 200) however will not have the host present even if non NVCM who launched the room is a host (permission-wise).  A NVCM needs to be present for the room to have an initial host, similar to Named Host Meeting.  If the VC is ‘public’ as far as access level, it will launch and use the 200 seat quota for that owner, but if the owner isn’t in the room, the users who have entered will be participants.
  • VC created in Shared Training folder by NVCManager (set to no) – launched by NVCManager = Will use NVCM license (quota 200)
  • VC created in Shared Training folder by NVCManager (set to no) – launched by non-NVCManager = Will use Traditional VC license (quota 100 taken from Concurrent Learners quota).  IF there is no quota for Concurrent Learners purchased, user will get ‘Account Limit Reached’ error.
  • VC created in Shared Training folder or My Training folder by non-NVCManager (set to yes) – launched by NVCManager = Will use NVCM license (quota 200)
  • VC created in Shared Training folder or My Training folder by non-NVCManager (set to yes) – launched by non-NVCManager – the room will behave like a Named VC and will use the 200 quota. But The room will not be owned by anyone, to be more precisely, there will not be an active host until an Named VC manager enters the room. Also all other non-NVCM hosts and presenters will be downgraded to participants until NVCM, who is assigned as a host, arrives.
  • VC created in Shared Training folder or My Training folder by non-NVCManager (set to no) – launched by NVCManager = Will use NVCM license (quota 200)
  • VC created in Shared Training folder or My Training folder by non-NVCManager (set to no) – launched by non-NVCManager  = Will use Traditional VC license (quota 100 taken from Concurrent Learners quota).  IF there is no quota for Concurrent Learners purchased, user will get ‘Account Limit Reached’ error.

So ultimately if you have purchased a NVCM license and you are expecting a VC to open and allow 200 seats, but you are getting an Account Limit Reached error either right away OR after a lower number of people access the room (so under 200), then most likely one of the situations above (in RED) has occurred.  To confirm, make sure that the creator of the room is in the NVCM group, the room exists inside of a NVCM’s My Training folder, the host launching the room is a NVCM, or at the very least the room has ‘YES’ set for the ‘Named Virtual Classroom License Model’ setting if the room is in the Shared Training area.

New Adobe Connect Support Blog Subscription Option

Now you can stay on top of the new articles and posts by subscribing to the Adobe Connect Support Blog. Simply go to the Adobe Connect Support Blog home page and enter your email address and check off the categories about which you would like to be notified. Click “Subscribe me” and you will begin receiving  regular updates:

subscribe.fw

 

 

Connect Meeting Room “NOT FOUND” Error when Launching

This blog article is pertinent to Adobe Connect HOSTED customers who have an account on the following clusters:

NA1, NA2, NA6, NA8, NA9, NA12

We have discovered a new bug recently with the 9.5.2 update (now live on accounts hosted on the clusters mentioned above) which can cause an issue for customers.

 

ISSUE:

You may try to launch a room and get a “NOT FOUND” error instead of the room opening as expected (image below):

notfound

 

This is because if the template from which a meeting room was created happens to have been deleted, then the meeting could result in the ‘Not Found’ state after 9.5.2 upgrade.   Meetings can have many ‘layers’ of templates under them.  Rooms created off of a template created off of a template created off of a template….and so on.  This will only affect a room if the template immediately underneath it is deleted.  Otherwise, if a template many layers underneath a room is deleted, this bug will not be present.  If you are not in the habit of deleting templates, you shouldn’t have to worry about this issue.  If for some reason you run into a room that will not launch and the attempt results in a ‘Not Found’ error screen as seen above, it could be because it’s template was inadvertently or intentionally deleted by the host, and admin, or any other user who has access to modify and administer that template.  Sometimes admins and meeting hosts go into Template folders (either My Template or Shared Template folders) and purge old, no longer used templates.  This could lead to rooms that were created off of those templates, experiencing this problem now as of the 9.5.2 upgrade that was performed this past weekend (February 7th).

Support has a way of recovering templates if they were recently deleted.  They should be contacted as soon as possible so that content (the template) can be recovered if it is still available on our storage devices and backups.

We are working on a hot-fix patch ASAP (we are targeting end of week internally and it should not impact the 9.5.2 rollout scheduled for the remaining clusters).  This fix should alleviate this issue and make it so that the meetings that were created off of a now deleted template, will still launch as expected.

Please contact support for any questions / concerns on this issue or if you are a partner/reseller and have customers who are experiencing this issue.  Again, it will only affect meetings on the clusters mentioned above, where the template used directly underneath a meeting, has been deleted.  Multiple layers down won’t affect the highest level meeting but any template underneath that has a template directly below it, will also be in this state if launched.

 

Behind the Curtain: Making Multiple Connect Meetings or Seminars Appear as One

On those occasions when a Meeting invitation may attract more participants than expected or planned for at the last minute so that you are unable to increase Seminar capacity in a timely manner, a skilled host can use two or more Connect Meeting rooms and project them to participants as though it were one room as an emergency workaround. Here is a basic outline of how to split a large meeting onto multiple servers. It is prudent to not just have more than one Meeting in these cases, but also to make sure each Meeting is hosted on a separate server in a cluster to add robustness to the meeting. Load-balancing is a wonderful thing and you should always use it to its fullest.

Assume an example of a three-server cluster/pool of Connect servers and that you want to split a Connect Meeting onto all three servers; a simple 3-server cluster is depicted here to use as an example:

C9SSLCluster3Simple

For a working example, let’s place a Connect Meeting room hosted on each server; to do this you will need three separate URLs: One URL for each 1/3rd  of your attendees. Getting the attendees distributed among the three rooms can be tricky. One effective technique is to either send out three different invitations, with each targeting 1/3rd of your audience and each offering a different URL, or just point everyone to a page with  all three URLs and request/instruct the participants to alphabetically arrange themselves in subsets of users by URL selection. That way it is not random; I have seen this technique work fine; here are sample meeting URLs based on our picture above:

http://connect.domain.com/splitmeeting1
http://connect.domain.com/splitmeeting2
http://connect.domain.com/splitmeeting3

To make certain the each meeting is hosted on a separate server (rather than all three on one as load-balancing could easily prescribe), it will require some effort to keep entering and leaving the room until your meeting lands on the server you want. Using multiple browsers may be helpful as well. Working on this well in advance of the meeting is prudent as there is a session timeout factor to consider. The load balancing algorithm will eventually get the sessions distributed but it may take some effort.

The way to tell which server you are on is simple: In any meeting room click Help and while holding down the shift key click About Adobe Connect. This will pop up an RTMP string that will identify the server that Meeting is hosted on and also which server a client is coming through as each client can be using multiple servers (just to add not only to the complexity, but also the overall robustness).

Here is what the RTMP strings might look like for each of the three servers in our simple example above ( I am inserting some URL parameters from a hosted meeting as I write this in order to create our hypothetical example RTMP strings – rtmp://arfms3.adobeconnect.com:1935/?rtmp://pcparapp07:8506/meetingas3app/89676385/630888204/)

rtmps:// connectmtg01.domain.com/?rtmp://connapp01:8506/meetingas1app/847483075/1086833045/
rtmps:// connectmtg02.domain.com/?rtmp://connapp02:8506/meetingas2app/847483076/1086833046/
rtmps:// connectmtg03.domain.com/?rtmp://connapp03:8506/meetingas3app/847483077/1086833047/

The first name in the string (connectmtg0#) is the built-in Connect Edge server and the second name (connapp0#)  is the Connect origin server  hosting the meeting (each Connect servers runs both AMS/FMS and Tomcat together). The second name is the important one for our technique of splitting the attendees onto separate meeting servers.

In the hypothetical RTMP string samples above, I have made these artificially neat and tidy, the truth is that the first part of the string can be any of the three for any meeting participant regardless of the application server hosting the meeting. For example, you could come in to connapp01 through connectmtg03 – any combination is possible. Load balancing is done at more than one level as Connect leverages both a hardware-based load-balancing device and also its own internal clustering capabilities; combinations for various clients (including the hosts and presenters) in our example cluster depicted  above might include:

rtmps:// connectmtg01.domain.com/?rtmp://connapp02:8506/meetingas2app/847483076/1086833046/
rtmps:// connectmtg02.domain.com/?rtmp://connapp02:8506/meetingas2app/847483076/1086833046/
rtmps:// connectmtg01.domain.com/?rtmp://connapp03:8506/meetingas3app/847483077/1086833047/
rtmps:// connectmtg03.domain.com/?rtmp://connapp03:8506/meetingas3app/847483077/1086833047/
rtmps:// connectmtg02.domain.com/?rtmp://connapp01:8506/meetingas1app/847483075/1086833045/
rtmps:// connectmtg03.domain.com/?rtmp://connapp01:8506/meetingas1app/847483075/1086833045/

The key to remember is that the second name is the one that matters; a distribution of participants approximating 1/3rd on each server is the goal targeting: connapp01, connapp02 and connapp03. After this is set-up, the pre-meeting preparation part is complete (this should be done at least one hour prior to the meeting).

Next comes the creative hosting venture during the split meeting: As the host, you will need all three meetings open in front of you to manage them as one. From the perspective of the participants, there is only one meeting (ignore the host behind the curtain). Be sure to hide the Attendee List Pod in the Presenter-only area as it will only present those participants in that specific Connect Meeting thereby allowing a peek behind the curtain or misrepresenting the size of the entire three meeting combination.

And here is where the techniques are very much up to you:

  • Splitting video among the three rooms is possible using a third-party option, one we have used successfully is: Splitcam.com.
  • For audio, if using integrated audio, be sure to use the same integrated telephony number for all three rooms.
  • If using VoIP, then allow one speaker only at a time to send audio via VoIP.

Some ways in which you can limit the amount of data being processed in your room and to improve the overall performance of these sessions are:

  • Optimize room bandwidth. In a Connect Meeting, at the top of the screen click on MEETING > Preferences. Under the preferences menu you are able to adjust screen sharing, video and VoIP quality setting separately.
  • Turn off cameras whenever they are not in use.
  • When in use, multiple cameras should probably be set to SLOW images (depending on how many and other variables).
  • Turn off VoIP if not talking.
  • Participants should directly connect to the fastest internet connection available and be on a dedicated DSL connection, at a minimum.
  • No clients or hosts on wireless – allow no exceptions.
  • Shut down Email, instant messaging, and any programs NOT being used for the presentation.
  • Shut down any VPNs as a VPN will potentially destroy the possibility for success.

When large Connect Meetings or Seminars become commonplace in your enterprise, this cumbersome workaround quickly becomes impractical and you should increase your Seminar or Webinar licensed capacity as needed to avoid this complexity and manual work. With that said however, this technique will work in a bind and will provide a robust Connect Meeting experience for a very large audience even if it challenges a seasoned Connect Meeting host.

Changing the License Serial Key in Connect

This article applies to on-premise and managed ISP Connect users. It does not apply to multi-tenancy hosted or ACMS.

On rare occasions it may be necessary to change the serial key in Adobe Connect. Here are the steps:

  1. Navigate to: \Connect_installation_directory\appserv\conf\config.ini and change the value of  SERIAL_KEY=  to reflect the new serial number
  2. In \Connect_installation_directory\custom.ini,  if there’s a serial key value listed (SERIAL_KEY=), replace it there as well.
  3. Using MSSQL Studio Express (or your choice of SQL editing options), view the serial key currently being used by Connect by running this command: SELECT * from pps_accounts WHERE name=’Enterprise Account’
  4. To get Connect to accept the new license you must change the serial key that is currently in the database by running this SQL command: UPDATE pps_accounts SET serial_key = ‘NEW_SERIAL_NUMBER’ WHERE serial_key = ‘OLD_SERIAL_NUMBER’
  5. Restart the services: Application Server (Connect) and the Meeting Server (AMS or FMS depending on the version of Connect) services.fw
  6. Open the Administration Console (port 8510 locally on any Connect server)

connconfig.fw

7. Go to License Settings and upload the new license file.

connconfiglic.fw

8. Restart the AppServer (Connect) and the Meeting server (AMS or FMS depending on version) again and the  new license file will be applied

services.fw

Troubleshooting: If there are any problems, do the following to troubleshoot:

  • Shut down the Connect and AMS or FMS Services
  • Open and verify \Connect_installation_directory\appserv\conf\config.ini and update the entry for SERIAL_KEY
  • Open and verify  \Connect_installation_directory\custom.ini and update  the entry for SERIAL_KEY
  • Open SQL Server and choose the Connect database and run the following script (replacing the text as appropriate):

“Input New Serial Key Here” with the New Serial Key but leaving the quotes.
DECLARE @NEW_SERIAL VARCHAR(32)
SET @NEW_SERIAL=’Input New Serial Key Here’

UPDATE PPS_CONFIG
SET VALUE = @NEW_SERIAL
WHERE SECTION=’cps’ AND NAME=’serial_key’

UPDATE PPS_ACCOUNTS
SET SERIAL_KEY = @NEW_SERIAL
WHERE ACCOUNT_ID=7

UPDATE PPS_ENUM_DATA_HOSTS
SET LICENSE = @NEW_SERIAL
WHERE HOST_ID > 0

db.fw_

  • Start the Connect and FMS services

Problems will ensue when the license is reducing the allowed usage of Connect (if you are downsizing) and you leave an overage in place. For example, if you have 100 meeting hosts assigned, and you are changing to a license that only allows 50 named meeting hosts then when you  apply the license you will get an error unless you have reduced the number to accommodate the new licensed restriction.

Adobe Connect ID’s are changing from INT to BIGINT

UPDATE: THIS ARTICLE IS FOR XML API DEVELOPERS ONLY.  If you are not using the XML API with Adobe Connect to write your own custom built applications that integrate with Adobe Connect, please do not worry about the message below as it will not apply to you.


Due to the growing popularity of Adobe Connect, more and more customers rely on Adobe Connect for their collaboration needs and this naturally requires that we make adjustments to accommodate the growth.  We want to make you aware of an upcoming adjustment to the ID values in Adobe Connect databases to support longer values which will accommodate growing customer use of Adobe Connect.

What is being changed?

Starting with release 9.5.2, Adobe Connect will migrate the ID values in Connect databases from INT to BIGINT/Long.

What is the impact?

This change will impact any applications using Adobe Connect Web Service APIs.

How will Adobe Connect Web Service APIs be affected?

The change is for those APIs which consume/return id values i.e. which have a parameter in request/response which is an Id. (examples: sco-id, account-id, folder-id, etc).  The id fields in such APIs would return/accept larger values. The support and behavior of existing APIs remains same.

What does this mean for you?

In case you are interpreting ids as integers the new values might overflow. We strongly recommend using strings to represent id values. In case you still need to represent/store ids as a numeral please use integral data type with higher capacity. (Preferably 64 bit)

What is the timing?

We expect to release Connect 9.5.2 in the first quarter of 2016, so the change should be made as soon as possible in order to be ready prior to the release.

Estimating Bandwidth Consumption in Connect Meetings:

Estimating bandwidth consumption in Connect 9.x Meetings using:

The following tables may be used for estimating the amount of bandwidth that will be required for a Connect Meeting based on the features used.

Screen Share:

Screen Share Frame Rate Quality Bandwidth
(kbps)
Low 2 65 500
Medium 4 80 800
Standard 6 90 1200
High 8 100 2000

VoIP:

With reference to VoIP, it is independent of any settings. There is no metric comparable to frame rate or quality or bandwidth with VoIP;  a single metric of micRate is used. Currently we use following values:

Number of VoIP users Without UV With UV
<4 22 kHz 22 kHz
>=4 11 kHz 8 kHz

Note: In a simple test during which a song was played via VoIP for a single user, up bandwidth consumed was 44 kbps when the number of VoIP users was < 4.

Webcam video:

Webcam Video Frame Rate Resolution Quality Bandwidth
(kbps)
Normal Widescreen
Low 4 160×120 214×120 70 200
Medium 4 320×240 427×240 70 300
Standard 8 320×240 427×240 70 300
High 20 640×480 854×480 90 600

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.

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.