FIRMWARE RELEASE NOTES ====================== Products covered: AXIS 250S MPEG-2 Video Server Release date: 2004-10-08 Release type: Production Firmware version: 3.20 Filename: 250s_320.bin Previous release: 3.10 --------------------------------------------------------------------- Upgrade instructions: Important: 1. Ensure that active applications (e.g. event-based or continuous video transmission from the AXIS Video Server) are disabled prior to initiating the upgrade. 2. You must be at the command prompt and in the directory that contains the upgrade file. Example: C:\Axis\250s\3_20> 3. From the command prompt, open an FTP connection to the unit you wish to upgrade. (Do not use Windows-based FTP-programs for this purpose - use only command line FTP programs!) 4. Log in as root. The default password for the root user is "pass", unless this has been changed by the user. You must be logged in as the root user to upgrade the unit. 5. Change to binary transfer mode by typing "bin" and press enter. 6. Type "hash" and press enter. (This will allow you to see how the upgrade progresses) 7. Type the command "put XXX.bin flash" where XXX.bin is the name of the upgrade file you downloaded (and maybe decompressed) from our site. This file is typically named 250s_320.bin or axis250s.bin. 8. Wait for the flash load to finish, which may take 1-10 minutes. Always wait at least 10 minutes for the flash upgrade to complete. 9. Your unit will automatically restart using the new firmware. Release 3.20: ============= New in 3.20 =========== 3.20:1 The MPEG-2 stream is now VBR (Variable Bit Rate) compared to previous CBR (Constant Bit Rate). 3.20:2 Added support for reducing frame rate in the video stream (frame skip ration). This can reduce bandwidth when full frame rate is not needed. See Advanced settings under "Audio & Video". 3.20:3 Added and corrected resolution settings 4CIF (704x576 PAL, 704X480 NTSC) and FD1 (720x576 PAL, 720X480 NTSC). 3.20:4 Third party software licenses text added to the product's web interface. 3.20:5 Stopping a recording with a manual trigger button terminates the recording regardless what the "Split upload into" parameter defines. 3.20:6 Added support for the following PTZ devices: Cohu iView 3950 Daiwa DMP23-h2 Dennard Type 2050 Dome Sony EVI-D70/D70P JVC TK-C676 VCL Orbiter Gold (18X) 3.20:7 Axis Media Control has been upgraded. Corrections in 3.20 =================== 3.20:8 Corrections for security issues that enable a remote attacker to execute arbitrary shell script commands. 3.20:9 Some servers such as qmail were rejecting the mails generated by the client. The mail client now complies with the RFC, regarding bare LF, which solves the issue with qmail. 3.20:10 Issue with the video signal loss are resolved now. 3.20:11 There are no longer unnecessary 'too many clients' messages. 3.20:12 The firewall is now automatically disabled when the last IP is deleted. 3.20:13 When date/time was included in the user data, the MPEG-2 data could be trashed occasionally (approx 1 error per 3000 - 10000 frames, i.e. approx 10 errors per hour). This works now correctly. 3.20:14 NTP time update could fail after a while. This is corrected now. 3.20:15 A rare problem with e-mails not been sent upon alarm has been corrected. 3.20:16 Events crossing midnight now work if changes were made on event, video or audio configuration. 3.20:17 Replies sent by some FTP servers (BulletProof) could include quotes, causing the FTP server 'connection test' to be corrupted. This is corrected. Application developer information: ================================== 3.20:18 Added properties parameters (HTTP-API) The following HTTP API groups are supported in the HTTP API version 1.11 and above: Group Exceptions ===== ========== General MPEG-2 PTZ I/O output.cgi?monitor Serial port The following HTTP API groups are supported from the HTTP API version 2.00: param.cgi Builtin templates for dynamic parameters are: 'event' - Event 'tcp' - TCP Notification 'http' - HTTP Notification 'ftpclient - FTP Upload 'ip' - Firewall For more information please see the HTTP API document available on the camera developer pages at www.axis.com.