Error 1: If, when trying to connect using AVChat 3, you are getting this error message: Connection failed, media server might be down or firewall might be blocking the connection! like this: You need to check: your rtmp connection string inserted in the media server might not be running (you can check if Red5 is running by going to the media server might have not started properly (thus is not running, you can check the logs in Red5/log for any ERROR messages during startup) there is a firewall on the media server blocking TCP traffic over port 1935 (and 5080) the user trying to connect is behind a firewall that blocks the connection (either a personal one installed on[…]

Changing the license key: Why would I change the license key? Insert a new trial key Switch from trial to non-trial key Switch the domain on which the software will be used Upgrade from Lite to 40 users (for example) What do I have to do? Log in the video chat using the admin interface (admin.swf) Click the Settings button at the top In the window that shows up, delete the old key from the text field and insert the new key Press the [Change Key] button If successful, you should now see the new  limits/expiration date/domain above the license key text field! Resetting the license key: If something goes awfully wrong and you find yourself locked out of the[…]

To see what AVChat 3 build you have installed you need to right click on the video chat software. The first item in the menu that shows up is the build number: Why is the build number important? The build number allows you to check if you have the latest version of our software.  If your build number is 284 and on the blog we announce a  new release with the build number 340, then it means you should consider upgrading your installation! Each increment in the build number might represent any of the following things: code cleaning bug fix new feature new file new entry in the translation file new setting in the config files etc… but you should[…]

In the side menu for other people’s web cams, AVChat 3 now shows an estimation of how much it takes for the video and audio data to travel from the broadcaster to the viewer (trough the media server) . We call this value trip time but its also known as latency. The value is not always 100% exact but it is a really good estimation! For one to many broadcasts the trip time value  is not important, live TV broadcasts generally  have a 5-15 seconds delay to give broadcasters time to censor any audio needing censorship A low trip time is really important when the audio/video communication goes both ways, for example when 2 people are in a video conference.[…]

This article has been updated as of 30 April 2013 to add info about recording to .mp4 files and the H.264 video codec. AVChat 3 uses a media server (like Red5 and FMIS and Wowza) to stream audio and video between users. The audio and video data travels from the broadcaster user to the media server and from there to the receiver/viewer . While it passes  through the media server the audio and video data can be captured and stored in .flv file,  or, starting with build 2330, in .mp4 files. The file type that will be created depends on the video codec being used (Sorenson Spark or H.264). Codecs being used… The audio data will be encoded with wither the[…]

AVChat 3 , as all the other flash video chats out there, uses a media server (like Red5 and FMIS) to stream audio and video between users. The audio and video data travels from the broadcaster user to the media server and from there to the receiver user. Even tough there is no receiver (if there is no one watching) the stream still travels from the broadcaster to the media server, thus consuming bandwidth on the media server and on the broadcaster’s Internet connection. This is where AVChat 3’s “Dynamic Bandwidth Usage Reduction” kicks in. When this feature is activated (it is by default) the broadcaster streams audio and video to the media server ONLY WHEN IT HAS VIEWERS. Here[…]

1) Increase the video and audio quality settings (obviously 🙂 ): As a webmaster you most probably have control over the audio and video encoding settings used by your video chat software. These encoding settings directly affect the audio and video quality. In what regards sound, you should be able to change the sound rate (the higher the better). 44 is the maximum audio quality setting supported by Flash Player when capturing audio from mics but it also consumes the most bandwidth with 88kbits/s! Other values for the sound rate are 22 (44kbits/s) 11 (22kbits/s) and 8 (16kbits/s). In what regards the video quality you should have more control! You should be able to change at least the resolution, the[…]

Both AVChat 2 and AVConference save by default  all the text chat in text files on the video server. You will find these transcript files in these folders: If you use Red5: Red5/webapps/avchat22/avchat2_transcripts If you use Flash Media Server 2 or Flash Media Interactive Server look in this folder: FMS/applications/avchat22/logs You can also turn off the text chat logging: If you use Red5 edit this file red5/webapps/avchat22/ set the loggingEnabled variable to false (loggingEnabled=false) restart the Red5 server. If you use Flash Media Server 2 or Flash Media Interactive Server: edit this file FMS/applications/avchat22/settings.asc set the application.loggingEnabled variable to false (application.loggingEnabled=false;) reload the avchat22 application using the FMS Admin Console.

Both AVChat and AVConference load the words and phrases used in the admin and user interfaces from external .xml files. These .xml files are plain text files that can be edited with any text editor. In order to change a word in the interfaces, to translate the entire interface in another language or to change the initial welcome message you just need to edit these files and change whatever you need! You will find these .xml files in the /en/ folder: en/index_en.xml for the user interface texts en/admin_en.xml for the admin interface texts If you are using the chat software as a Joomla component, the files are most probably in components/com_avchat/en/ . IMPORTANT: After editing the .xml files and uploading[…]