Polycom 3804-11530-222 Outstanding Issues, No Layer 2 QoS support for signaling protocol TCP

Models: 3804-11530-222

1 68
Download 68 pages 12.81 Kb
Page 66
Image 66

Release Notes - SIP Application

Notes

3.2 Outstanding Issues

The following issues will be fixed in a subsequent release.

Note: Polycom has switched to a different issue tracking system which has caused the reference numbers in these release notes to be different to earlier versions. When the issues are addressed the numbers in this release note can be used to track in which version the issue is addressed.

24398: No Layer 2 QoS support for signaling protocol (TCP)

Workaround: The default QOS parameters will still be used for TCP signaling packets, and these may be specified in the sip.cfg configuration file. Layer3 QoS settings are supported.

24805: Cannot answer an incoming call while directory is being saved

Workaround: None.

26615: Subnet mask forces all packets through gateway when not using DHCP and when using the wrong subnet mask for the network class in use, for example using 192.168.X.X addresses with a 255.255.0.0 subnet mask Workaround: Use the correct subnet mask.

26920: Centralized conference fails due to RTP port being slow to open in some cases

Workaround: None.

27469: Local Conferencing on IP4000 phones is disabled if G.729 is in the

Codec preference list

Workaround: Disable G.729 as a Codec option on the phone by setting voice.codecPref.IP_4000.G729AB=””

28508: Phone crashes after receiving high call rate (4 unanswered calls every 18 seconds)

Workaround: Reduce the incoming call rate.

29344: HTTP Digest Authentication does not work on IIS

Workaround: Use a different form of authentication, a different protocol or a different server

29946: Log files are not uploaded if an Apache 2.0.X boot server requires authentication

Workaround: Turn off authentication or use version 1.3.3X of the Apache server.

30086: Boot servers running explicit FTPS are not supported

Workaround: Use implicit FTPS or HTTPS.

30371: Pattern generator for tones does not work well for the case of a single repeating chord

Workaround: Start the pattern with a short period of silence then the desired initial chord. Loop back to the desired initial chord instead of the initial silence.

30903: Packet Loss statistics ‘jump’ if calls are transferred.

Workaround: If using the packet loss statistics for troubleshooting purposes make a note of the Packet Loss value after the transfer and apply a correction based on this to subsequent calculations.

Page 60

Copyright © 2007 Polycom, Inc.

Page 66
Image 66
Polycom 3804-11530-222 manual Outstanding Issues, No Layer 2 QoS support for signaling protocol TCP