Release Notes
ViaVideo 5.1
•
The computer is restarted and the application is launched while the camera is
powered on.
The camera software may fail to load when the customer is using a non-powered USB
hub. Complete the following steps to load the software to the camera:
1. Power off the ViaVideo camera.
2. Disconnect the USB cable from the back of the ViaVideo camera.
3. Verify that the Polycom ViaVideo device driver has been removed from the
computer’s device manager.
4. Reconnect the USB cable to the back of the ViaVideo camera.
5. Power on the ViaVideo camera.
6. Verify the existence of the Polycom ViaVideo device driver in the computers
device manager.
Note
: If the Polycom ViaVideo device driver is not present, restart the computer
and repeat steps 1-5.
7. Launch the ViaVideo application software.
VideoMail Issues
If you are having difficulty saving a VideoMail file, it may be because Windows has not
appended the .asf extension correctly in the File Save dialog box.
If you explicitly enter the .asf extension as part of the file name, the file will be saved
correctly. For example, in the file name field, enter the file name as
MyVideoMail.asf
.
Recording a video mail is interrupted when an incoming call is automatically answered.
To resolve this issue, turn off the Auto-Answer feature.
If you leave the VideoMail drop-down box open after recording a VideoMail message
and then place a call, you cannot play or record VideoMail until you close the VideoMail
drop-down box and then reopen it.
The VideoMail feature cannot be used while in a call and the VideoMail control panel is
disabled.
Interoperability and Compatibility Issues
Cisco VPN
This version of ViaVideo supports Cisco VPN software version 4.02 and higher. To
upgrade your Cisco VPN software, go to
www.cisco.com
.
Cisco Pix Firewall
Users with a Cisco Pix Firewall will be unable to establish a videoconference call with
the default setting on the Cisco Pix Firewall. Complete the following steps to correct:
1. Turn off Fixup protocol H.323 1720 with the following command:
no fixup protocol h323 h225 1720
2. Conduits or access list assignments must be configured for the following ports:
TCP 1720
TCP/UDP 3230 – 3235
TCP 3603
rel_vv510.doc
updated 10.14.2003
- 8 -
