4 configuration file parameter changes, 1 added or changed features, 2 removed features – Polycom SOUNDPOINT 3804-11530-222 User Manual

Page 53: 3 corrections

Advertising
background image

Release Notes - SIP Application

Changes

Copyright © 2007 Polycom, Inc.

Page 47

• 15162: Phone clears application log file during a warm boot even if the upload

to the boot server failed

2.18.4 Configuration File Parameter Changes

.cfg
File

Action Parameter

Description

sip added voIpProt.server.dhcp.available

1

= check with the DHCP server for SIP

server IP address.
0 = do not check with DHCP server.
Default = 0.

sip added voIpProt.server.dhcp.option

Option

to request from the DHCP server if

voIpProt.server.dhcp.available = 1.
Allowable range is 128 – 255. There is no
default value for this parameter, it must be
filled in with a valid value.

sip

added

voIpProt.server.dhcp.type

0 = IP address
1 = string
Type to request from the DHCP server if
voIpProt.server.dhcp.available = 1.
There is no default value for this parameter,
it must be filled in with a valid value.

sip added tcpIpApp.sntp.address.overrideDHCP

and
tcpIpApp.sntp.gmtOffset.overrideDHCP

These parameters determine whether
configuration file parameters override DHCP
parameters for the SNTP server address
and GMT offset. The default is 0 which
means that DHCP values will override
configuration file parameters. A value of 1
means that configuration file parameters will
override DHCP values.

2.19 Version 1.6.4

2.19.1 Added or Changed Features

• 12278: Added support for SAS-VP v3 XML configuration transactions
• 12883: Added sending and processing the “early-only” flag in the “replaces”

header to support RFC 3891 in call pickup

• 12890: Added accepting SDP with telephone-event on the first line
• 13492: Disabled CA certificate expiry checking when SNTP has not been

configured

2.19.2 Removed Features

None.

2.19.3 Corrections

The following issues have been resolved with this release:

• 7707: LED which shows mute and incoming-call and message-waiting status

can show incorrect state

• 8598:

There is no "1/A/a" soft key when editing Forward contact

Advertising