There are three primary reasons for this error:

1. Your PC or Mac hardware is outdated, or
2. You are running an older/wrong version of Flash Player
3. You are on a Mac and are not keeping the browser window in focus during connection to the OnSync server

1. Your PC or Mac hardware is outdated

See: What are the system requirements for OnSync clients?

If your system does not meet these requirements, please upgrade your hardware.

2. You are running and older / wrong version of Flash Player

See What plugins are required to run OnSync? Is ActiveX ...

If you find you are running an old version of Flash Player, please upgrade it. It is recommended you completely uninstall your flash player prior to installing a new version. Please follow this link to adobe's website for software and instructions:

http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14157

Once you have uninstalled your flash player, please install the latest version by visiting:

http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash

NOTE: Mac users please read this additional information.

Since Flash Player version 9 there are two types of players available, one for PowerPCs (PPC) and the other for Intel-based Macs. Running the PPC version on an Intel-based Mac is very inefficient and will often cause the "script running slowly" error message.

If you are using an Intel-based Mac, make sure you install the Universal Binary for Intel-based Macs.

3. You are on a Mac and are not keeping the browser window in focus during connection to the OnSync server

OS X has integrated resource management which means that if you take focus off a window, in safari for example, system resources are moved to the application with focus. The reduced resources that OnSync has available if it is not in focus during connection to the server can cause this message to pop up. In fact it is quite likely to appear.

The way to fix this is to make sure you keep the OnSync browser window in focus while you are connecting to OnSync - This means making sure the browser window loading OnSync is the active window on your computer. You can see the status of OnSync connection in the loading/splash screen. Once the message "Establishing connection..." disappears and is replaced by "Creating Workspace..." you can safely take the focus off the window.

A typical example would be a user emitting a webinar to a large, geographically dispersed audience. The video stream would pass from the user to his closest edge server straight to the origin server. The origin server would then disseminate the single stream to all edge servers which in turn would disseminate the stream to all users connected to the edge servers with each user being served by the edge server closest to them. The edge servers will therefore do the heavy lifting and alleviate the load on the origin server. This means that only a single stream will have to pass from one location to another before being disseminated to all users connected to the particular edge server and thereby allowing bandwidth optimized communications.

Edge servers will always connect to an origin server and any information passed between clients will always pass via the origin server. In some cases this may lead to slightly increased latency in live communications. Every deployment scenario differs in its particular restrictions and bottlenecks. The flexible nature of Origin/Edge architecture allows deployments to be optimized and create high user collaboration environments which otherwise would not be possible.

The following figure shows the typical Edge/Origin architecture which may be used to connect large numbers of clients in different geographic locations:

Source: http://www.adobe.com/de/products/flashmediaserver/pdfs/
fms_wp_ue.pdf

Edge servers can also be chained to provide you with further flexibility in your deployment scenarios.

Typically, only the communications server of OnSync will require clustering which carry the most bandwidth intensive activity. The webserver and (optional) document conversion server would typically not require clustering and be deployed in the same phsyical location as the origin server (although this is not a requirement).

Please note, special licensing conditions apply to Origin/Edge deployments and OnSync clusters, please contact sales for more information. Typically, Digital Samba will handle all installation and configuration of your Origin/Edge servers on your infrastructure together with your engineers.

OnSync takes advantage of the Origin/Edge architecture provided by Adobe Flash Media Server 3 or later. Please refer to Adobe's documentation for more detailed information.

Further reading:
http://www.adobe.com/de/products/flashmediaserver/pdfs/
fms_wp_ue.pdf

Hardware requirements:

• Intel® Pentium® 4, 3.2 GHz (Dual Xeon® or higher recommended)
• 2 GB of RAM (4GB or more recommended)
• 100MB of available disk space for installation, 80GB+ recommended for Content Storage
• CD-ROM Drive (optional)
• Gigabit Network Adapter
• RAID Drive recommended

Supported OS:

• Microsoft® Windows Server® 2003 SP1 (All 32-bit editions), or
• Linux® Red Hat® 4 (32-bit only)

Software requirements:

• Flash Media Interactive Server

Web server

Hardware requirements:

• Celeron, 2GHz
• 512 MB of RAM (1GB recommended)
• 100MB of available disk space for installation, 10GB+ recommended for Content Storage
• CD-ROM Drive (optional)
• Gigabit Network Adapter
• RAID Drive (optional)

Supported OS:

• Windows 2003 Server, or
• Windows 2000 Server, or
• Windows NT 4.0 Server (SP6 or later), or
• Linux, or
• Mac OSX

Software requirements:

• Apache webserver (Apache 2 recommended)
• PHP 4.3 or newer (PHP 5.x recommended)
• MySQL 3.23 or newer

For Linux installations please read "Preparing your Linux servers for OnSync" (pdf, 41 kb)

]]> http://www.digitalsamba.com/archive/ds3/support/faq/index.php?action=artikel&cat=3&id=12&artlang=en Mon, 14 Jul 2008 07:12:20 GMT Explanation of CreditPacks and the following terminology:

Variable	Definitions
Time Limit (minutes)	Total quantum of credit available in the pack, in terms of number of user minutes. A typical 1 broadcaster + 9 viewer (aka 1b+9v) conference lasting 1 hour would consume 600 minutes.
Data Limit (GB)	Total quantum of credit available in the pack, in terms of number of total data traffic throughput on the server. In order to prevent abuse of the services which are offered and thereby prevent a negative effect on service performance for all users, Digital Samba has implemented certain Fair-Use Policy limits for all users @ http://www.digitalsamba.com/products/fair_use.php A similar limit is imposed on all packs purchased by partners. The limits are based on calculations on the transfer rates used by the top 5% of users which are responsible for more than half of the total data transfer. The following calculations serve as a guideline only and may vary depending on several variables such as video sizes selected and type of video signal being broadcast. A typical 1 broadcaster +9 viewers (aka 1b+9v) conference lasting 1 hour at a widescreen / small video setting would consume around 400 to 450 MB of data traffic. Generally speaking, approximately 23 to 25 streams of 1 hour each consume around 1 GB of bandwidth. In order words, each stream consumes around 40 to 45 MB of data traffic per hour. This may vary on the video sizes selected in the application. Multi-way videoconferencing can use more bandwidth where the consumption is calculated at (bitrate * broadcasters2) + (broadcasters * bitrate * viewers).
Validity Limit (days)	Total quantum of credit available in the pack, in terms of number of days the pack remains active and valid. A pack expires as soon as the validity period, in terms of days, elapses. The validity period starts with the Contract Start Date on the order form.
Bandwidth Cap (Mbps)	Maximum concurrent server side bandwidth available. Expressed in Mbps = 1024 Kbps = 1,000,000 bits per second. Instead of a restrictive "number of concurrent users" limit, Digital Samba imposes a "maximum concurrent bandwidth" limit on the server side, allowing partners to work with numerous combinations. A typical 10-participant conference with 10 streams - 1 broadcaster in widescreen-small mode and 9 viewers requires 768Kbps to 1 Mbps concurrent bandwidth For eg, Pack A with a limit of 10Mbps will allow … ... one concurrent 1 broadcaster +99 viewers (aka 1b+99v) conferences OR ... two concurrent 1 broadcaster + 48 viewers (1b+48v) conferences OR … ten concurrent 1broadcaster + 9 viewer (aka 1b+9v) conferences. Naturally, Pack C will allow 10 times as much. This is based on the assumption that there’s only 1 concurrent broadcaster only in small to medium sized video. If there is more than 1 concurrent broadcaster, the bandwidth consumption increases dramatically because every single viewer needs to consume a separate multiple broadcasting stream. The formula for calculating total number of streams = (b X v) + (b X b). For example, a 1b+14v conference = (14 X 1) + (1 X 1) = 15 streams. But a 2b+13v conference = (13 X 2) + (2 X 2) = 30 streams Broadcasting rights can be passed around in a conference and participants can take turns to be broadcasters one by one. OnSync also supports multiple concurrent broadcasters.
Storage Cap (GB)	Total server disk space available for storing conference files and recordings. This is a total quantum spread over all customers. Storage cap refers to the maximum disk space available to the partner pack. All presentations, files, etc. uploaded during a conference are permanently stored in that conference unless those files or that conference itself is explicitly deleted by the account holder. All recordings of conferences also consume a certain amount disk space based on several variables including but not limited to the video size selected, type of video broadcasted, amount of screen share activity.
Divisibility (Customers)	Maximum number of unique customers, a partner is licensed to sign up in the pack. For example, Pack A allows a partner to sign up 10 different customers and up to 100 users. There is no limitation as to how these 10 customers use the total number of users contracted – Partner could decide to sign up 10 customers with a conference room capacity of 10 users each, or could decide to sign up 1 customer with a capcity of 82 users and 9 customers with a capacity of 2 users. Any denomination will work as long as the limit of paying customers is not exceeded.
Users Contracted	Maximum number of users a partner can assign amongst his customers. This is a total quantum spread over all customers. Conference rooms when sold are associated with a user limit, defining the capacity of the conference room similar to a real word conference room. A Partner can choose how he splits these users amongst his customers but the total sold must never exceed this limit. Using Pack A as an example, if Partner has sold 5 accounts to clients with 20 users each Partner cannot sign up another client because the contracted users limit of 100 has been reached, even though the Divisibility (customers) limit would technically still allow signing up of further customers.
Cost (Euros)	Net amount receivable by Digital Samba from partner in advance for buying the pack exclusive of applicable taxes/charges. Pack expires as soon as any one of the following 3 limits is reached: Time, Data or Validity. Pack is bound by the following usage caps: Bandwidth, Storage, Divisibility and Users Contracted.

]]> http://www.digitalsamba.com/archive/ds3/support/faq/index.php?action=artikel&cat=5&id=175&artlang=en Mon, 07 Jul 2008 09:52:27 GMT