Description : The Adobe Connect Web Services API accepts special characters such as (+,$,# etc) if you encode the characters. For example:
If a user Login employs the credentials shown below on the User Interface, it will work without issue.
User Name :- firstname.lastname@example.org
Password :- Passw0rd
However, when the user uses the following API “/email@example.com&password=Passw0rd”
The plus sign is interpreted as though it were a space and the Login looks like this “abc firstname.lastname@example.org” resulting in the following:
- <status code=”no-data”/>
In order to employ these special characters, you must encode them and then execute the API. For instance in the above case we will execute an API as shown below :
Special character encoding reference information is found under URL :- w3schools This reference is useful for those users who are trying to run API with special characters.
Description : In meeting room, with poll pods.
– If we do not end the poll and rather we close the meeting room directly, which as a result would close the poll automatically.
- If we leave the meeting room ideal and do not end the poll, then meeting session expires after few hours, which as a result closes the poll.
– If we close/End the Poll Pod.
In any case where the meeting session closes the “update-poll-results” query would still triggers and send the captured results to the Data Base, which as a result should be visible in the reporting of that particular Live Session.
It was always designed to update the poll results in CPS whenever poll ends/explicit meeting end/automatic meeting unload. So if user ends the meeting without ending the Poll Pods, this procedure would still work. In ideal sessions also, after certain time if session is closed, all users’ connection are closed and meeting app gets unloaded at FMS server. Hence poll reports will be sent to the CPS when meeting app gets unloaded.
This is resolved as of 2014-12-02 12:08 EST.
We are actively working to solve an intermittent issue with Connect restarts on some servers in DA2 clusters.
This issue is causing outbound connections to be dropped. This will result in outbound connections to mail, SIP and telephony providers to drop. It will not prevent regular http and rtmp traffic as they go through a different firewall. The issue is that the Connect scheduler relies on mail going out, and if the queue builds it can cause problems with the Connect service. The exact clusters affected are in DA2: NA3, NA4, NA5, NA7, NA10 and NA11.
The root cause is isolated to a change made by one of our service providers last night and we are working aggressively to get it resolved. It is affecting other Adobe products as well as Connect.
You may check http://status.acrobat.com/ for updates.
While using InterCall as a teleconferencing provider, sometimes the option “Further dial in Numbers” under Adobe Connect –> My Profile –> My Audio Profiles is missing.
This setting is controlled by InterCall itself. They must enable their Global Access Settings under the user’s teleconference settings to get this link under the Connect audio profiles.
An interesting question came up that others may have: What are the supported video input resolutions for Connect? I am testing a Matrox MXO2 Mini that allows me to send a variety of different resolutions through a USB shim that can be used in Connect. I have tried a number of resolutions that will either not show a full frame of video or no video at all. Can I get a list of the supported video input resolutions?
Another question came up on the same topic that will be of interest. Similar to something Hippasus might ask Pythagoras: If there are three supported resolutions per aspect ratio why are there four settings for video quality under video preferences?
Answer: Apart from Video Resolution, there are other parameters as well which define the video quality such as Frames/sec and Video Compression Quality. These four settings have different combinations of these variables:
Resolution Frames/sec Video Compression %
High 640×480 20 90
Standard 320×240 10 80
Medium 320×240 8 75
Low 160×120 4 70
For the 16:9 aspect ratio, the settings are the same as their 4:3 counterparts. For example, if 4:3 resolution for any quality setting is 320×240, then its 16:9 counterpart will always be 427×240.
When using the Nellymoser codec, one microphone might produce more bandwidth over against another. Nellymoser accepts five different microphone rates values: 5, 8, 11, 22 and 44. Each of these rate values consumes bandwidth of roughly double its value. For example the 8kHz setting consumes roughly 16kbps and 11kHz setting consumes roughly 22 kbps. The default rate value is 8kHz. This may vary depending on the sound capture device in use.
The Flash Player microphone reference documentation reads:
“The default value is 8 kHz if your sound capture device supports this value. Otherwise, the default value is the next available capture level above 8 kHz that your sound capture device supports, usually 11 kHz.”
It is possible for two different microphones to consume different amounts of bandwidth.
In case of the Speex codec, it has a fixed sampling rate of 16kHz. Speex allows control of the quality by offering us 11 different encoding quality options. See the following reference table :
|Quality (EncodeQuality)Mic rate is fixed at 16
||Quality (Mic Rate)
Adobe Connect supports three Speex settings:
- Fast : Encode Quality 4
- Good : Encode Quality 6
- Best : Encode Quality 8
Increasing the encoding quality will increase the quality of the stream but will also require greater bandwidth. The Speex codec is optimized for voice and also includes voice activity detection that allows it to reduce bandwidth.
Adobe Connect 9.3 Concurrent Learner Licensing Updates
As we released Adobe Connect 9.3, we began to more accurately track Concurrent Learner licensing usage (i.e., licensing of the Adobe Connect Training Module), with reporting available in the “Reports” section of Adobe Connect Central to provide specific usage metrics. With increased accuracy of concurrency measurement introduced in version 9.3, you may reach your concurrency limits more quickly due to this change. Here is an FAQ around this update:
Issue : Connect meeting shows active after the Meeting is over
Environment : Hosted and On-premise
Reason : If the host just closes the Meeting browser by clicking the X in the upper right side of the add in or browser, then the Meeting will remain active and will wait for all users to leave the Meeting room; it could wait for up to 12 hours before closing the Meeting room. Keeping a Meeting open this long runs risks that could affect the Connect server’s ability to martian Meeting state.
Meetings that remain active and in process will appear as active in reports. End the meeting by clicking on Meeting >End Meeting. If you click on Meeting > End Meeting then session is ended for all the users currently in that meeting room and all users would get message that the meeting has ended. This triggers the Connect server to save the state of meeting and end the supporting processes. This is safe since it ensures that the meeting is ready for next session with all the content which was used during the last session.
Hosts should select the End Meeting option instead of clicking the “X” in the upper right of the browser or add in. Notice also that in the case of multiple hosts, one may choose to Exit Adobe Connect as well. See the GUI options under the Meeting menu highlighted below:
NOTE : For PPU Accounts, if a Meeting host exits from a Meeting clicking the “X” in the upper right of the browser or add in, instead of Ending the Meeting , the Meeting will continue in a billable mode and the customer will continued to get charged until the Meeting is ended by the server timeout.
Problem: Adobe Connect could not process this document for viewing. (Either the full document does not upload or some pages of within a document do not upload)
Adobe Connect Hosted/Licensed
Use the “Sanitize Document” Feature to get rid of all the following types mentioned in the image attached below. Depending on the version of Acrobat you are running, you may need to install a trial version of Adobe Acrobat Pro to use this feature.
Whiteboard features on Mobile are not OS dependent, rather, they are device dependent. While whiteboard content display is available on phones, whiteboard authoring is supported on tablets. This is completely independent of the OS and applies to both iOS and Android.
The screen size is the primary mitigating factor; traditionally even the best phones have been too small to be used for effective whiteboard authoring: Pixel dimensions and resolution on phones have limitations that do not affect tablets. More specifically, while smartphone users can view the markup objects drawn by both tablets and desktop users, the following editable whiteboard feature are available on tablets:
- drawing with the pencil tool or pen
- the arranging object tool
- the rectangle, ellipse, star and cross
- the highlighter
- move objects
- delete objects
- advance slide
- hide/unhidden menu
- the line tool
- single arrow, double arrow and 3D arrow
- check mark
Note: The green pointer must be enabled by the Host on a computer. Mobile devices can display the green pointer.