Polycom KIRK WIRELESS SERVER 300 FIRMWARE PCS06A User Manual

KIRK Release Notes

KIRK Wireless Server 300

Firmware Version PCS06A_

October 13, 2010

Release Notes – KIRK Wireless Server 300 – October 13, 2010

		Table of Contents
1.	GENERAL...................................................................................................................................		1
	1.1	IMPORTANT NOTES ................................................................................................................	1
	1.2	FEATURE LICENSE AND PLATFORM LIMITATIONS ..................................................................	1
	1.3	SYSTEM REQUIREMENTS........................................................................................................	1
2.	DISTRIBUTION FILES ............................................................................................................		1
3.	CHANGES...................................................................................................................................		1
	3.1	VERSION PCS06A_ OCTOBER 13, 2010.................................................................................	1
	3.1.1 Added or Changed Features .............................................................................................		1
	3.1.2	Removed Features.............................................................................................................	3
	3.1.3	Corrections .......................................................................................................................	3
	3.1.4 Configuration File Parameter Changes ...........................................................................		4
	3.2	VERSION PCS05D_ JULY 13, 2010........................................................................................	5
	3.2.1 Added or Changed Features .............................................................................................		5
	3.2.2	Removed Features.............................................................................................................	5
	3.2.3	Corrections .......................................................................................................................	5
	3.2.4 Configuration File Parameter Changes ...........................................................................		5
	3.3	VERSION PCS05C_ Q3, 2010 ................................................................................................	5
	3.3.1 Added or Changed Features .............................................................................................		5
	3.3.2	Removed Features.............................................................................................................	7
	3.3.3	Corrections .......................................................................................................................	7
	3.3.4 Configuration File Parameter Changes ...........................................................................		8
	3.4	VERSION PCS05B_ Q2, 2010 ................................................................................................	8
	3.4.1 Added or Changed Features .............................................................................................		8
	3.4.2	Removed Features.............................................................................................................	9
	3.4.3	Corrections .......................................................................................................................	9
	3.4.4 Configuration File Parameter Changes ...........................................................................		9
	3.5	VERSION PCS05_ Q1, 2010.................................................................................................	10
	3.5.1 Added or Changed Features ...........................................................................................		10
	3.5.2	Removed Features...........................................................................................................	11
	3.5.3	Corrections .....................................................................................................................	11
	3.5.4 Configuration File Parameter Changes .........................................................................		12
	3.6	VERSION PCS04B_ OCTOBER 20, 2009...............................................................................	13
	3.6.1 Added or Changed Features ...........................................................................................		13
	3.6.2	Removed Features...........................................................................................................	13
	3.6.3	Corrections .....................................................................................................................	13
	3.6.4 Configuration File Parameter Changes .........................................................................		13
	3.7	VERSION PCS04A_ OCTOBER 12, 2009...............................................................................	13
	3.7.1 Added or Changed Features ...........................................................................................		13
	3.7.2	Removed Features...........................................................................................................	13
	3.7.3	Corrections .....................................................................................................................	14
	3.7.4 Configuration File Parameter Changes .........................................................................		14
	3.8	VERSION PCS04_ Q4, 2009.................................................................................................	14
	3.8.1 Added or Changed Features ...........................................................................................		14

		Copyright © 2010 Polycom, Inc.	Page i

Release Notes – KIRK Wireless Server 300 – October 13, 2010

3.8.2		Removed Features...........................................................................................................	15
3.8.3		Corrections .....................................................................................................................	15
3.8.4 Configuration File Parameter Changes .........................................................................			15
3.9	VERSION PCS03B_ Q3, 2009 ..............................................................................................		17
3.9.1 Added or Changed Features ...........................................................................................			17
3.9.2		Removed Features...........................................................................................................	18
3.9.3		Corrections .....................................................................................................................	18
3.9.4 Configuration File Parameter Changes .........................................................................			18
3.10 VERSION PCS03A_ Q2, 2009..............................................................................................			18
3.10.1 Added or Changed Features .......................................................................................			18
3.10.2		Removed Features.......................................................................................................	19
3.10.3		Corrections .................................................................................................................	19
3.10.4 Configuration File Parameter Changes .....................................................................			19
3.11 VERSION PCS03_ Q1, 2009.................................................................................................			20
3.11.1 Added or Changed Features .......................................................................................			20
3.11.2		Removed Features.......................................................................................................	20
3.11.3		Corrections .................................................................................................................	20
3.11.4 Configuration File Parameter Changes .....................................................................			20
3.12 VERSION PCS02_ Q4, 2008.................................................................................................			23
3.12.1 Added or Changed Features .......................................................................................			23
3.12.2		Removed Features.......................................................................................................	24
3.12.3		Corrections .................................................................................................................	24
3.13	VERSION PCS01B_..............................................................................................................		24
4. OUTSTANDING ISSUES........................................................................................................			24

Page ii

Release Notes – KIRK Wireless Server 300 – October 13, 2010

1. General

These release notes apply to released firmware versions for the KIRK Wireless Server 300 (hereinafter referred to as KWS300). This version specifically applies to version PCS06A_ of the firmware. This release replaces the PCS05D_ release as the latest generally available (GA) release.

1.1Important Notes

•Starting from PCS05B_ the KWS300 is produced with DHCP enabled per default.

Previously the default setting was a static IP address. This only affects new devices and not devices that are upgraded. The change is performed in response to customer demands.

•If downgrading from PCS04A_ or newer to PCS04__ or older, the firmware needs to be loaded and rebooted twice to work correctly.

•If upgrading from PCS01B__ to a newer version and subsequently downgrading from the newer version back to PCS01B__ the user database will be lost. It will however be possible to restore a backup made while running PCS01B__.

1.2Feature License and Platform Limitations

None

1.3 System Requirements

Hardware Platform	Description
KWS300 HW PCS 10 or newer	KWS300 Server

2. Distribution Files

Click here >> to find the firmware image of the KWS300.

3. Changes

3.1 Version PCS06A_ October 13, 2010

This release replaces the PCS05D_ release as the latest generally available (GA) release.

3.1.1 Added or Changed Features

•Major upgrade of the provisioning handling including several enhancements to address the scenarios where a KWS is hosted by a service provider.

Earlier local changes made through the web GUI would not be reverted by provisioning. This would make provisioning server settings and local settings inconsistent. Now the provisioning server settings, user data and firmware always take precedence over any local changes. I.e:

-The config.xml file on the provisioning server takes precedence over settings on the KWS.

-The users.xml file on the provisioning server takes precedence over user data on the KWS.

-The firmware.bin file on the provisioning server takes precedence over the version

Page 1

Release Notes – KIRK Wireless Server 300 – October 13, 2010

on the KWS. A side effect of this is that provisioning (if activated) will revert firmware if updated via the GUI. I.e. if provisioning is configured and someone upgrades (or downgrades) the firmware from the version that is on the provisioning server, the provisioning process will revert the firmware version to the one available on the provisioning server.

•Added provisioning configuration merge functionality. This means amongst other things that provisioning will only initiate a reboot if a setting is changed that requires a reboot to become active. In previous releases any change to the configuration files located on the provisioning server would initiate a reboot.

•Eliminated several reboot scenarios. Some settings that previously required a reboot before a change would become active do no longer require a reboot to become active.

Do not require a reboot to enable/disable XML-RPC.

Do not require a reboot for provisioning method, URL, interval and time.

•Do not store default values in config.xml. This means that any setting which is left at the default value will not be saved in the config.xml file. Furthermore empty configuration keys are deleted from the file, thus the config.xml file has become much smaller and radically easier to read.

•More robust flash upgrade process. Reboot is now handled centrally to ensure that the KWS is not rebooted while flashing the firmware.

•Add Reboot when idle function. This way it is now possible to schedule a reboot to take place when no calls are active on the system.

•Remote syslog improvements.

It is now possible to send debug messages via remote syslog. Furthermore it is possible to configure which log levels to send via remote syslog. All of the changes to the remote syslog can be made without restarting the KWS. This means that e.g. in a hosted environment the provider can increase or decrease the level of logging from a specific KWS without affecting the users of the KWS. In e.g. a troubleshooting scenario the provider/administrator can increase the log level while debugging and subsequently decrease the level again.

•Distinguish between transport and timeout errors when displaying error messages in the handset.

In earlier firmware versions all transport and timeout errors were reported as being transport errors. Now the transport and timeout errors are reported separately. A transport error is when a request cannot be delivered to the destination due to for example failed DNS lookup. A timeout error is when a response is not received within a reasonable time.

•Make SIP client transaction timeout configurable. Increase this time to eliminate timeout errors towards the SIP Provider or decrease it to reduce fail over time if you have several SIP proxies configured. If you have a “not-so-reliable” connection to your SIP provider/IPBX, it may be an advantage to increase this value. The value specifically controls timer B and F as specified in RFC3261.

•Log (with level notice) when settings are changed either from the GUI or using provisioning. Indicate whether the change requires a reboot.

•Added support for RFC 3326 Reason header. This allows the PBX to control if the handset will display “Missed call” when part of a ring group. As an example if 2 handsets are part of a ring group an INVITE is sent to both handset. If handset 1 answers the call, the PBX can send a CANCEL with reason header “Call Completed

Page 2

Release Notes – KIRK Wireless Server 300 – October 13, 2010

Elsewhere” to handset 2, which will result in the fact that no missed call indication will be displayed on handset 2. This is supported by e.g. Asterisk 1.6.

Support for this is expected to become available in the 50xx, 60xx and 70xx series handset Q1 2011.

•Allow "+" in outgoing B-no. If. e.g. "+45123456" is received as a calling party number a redial from the handset will now be allowed.

Support for this is expected to become available in the 50xx, 60xx and 70xx series handset Q1 2011.

•Add broadcast of 60xx & 70xx series handset XML-RPC messages SMSSetupReq and ExtendedHwReq.

•Handling of SIP registrations improved. A new queuing technique allows for faster SIP registering of endpoints. In connection with e.g. reboots SIP registrations of many users is now handled faster.

•More verbose when ping or traceroute fails.

•LogMessage "HL_ME_U_PLANE_ind Me-Instance null. (Pmid:xxxxxx)" downgraded from warning to debug because it is misleading. The warning is logged before an abnormal release but is caused by the abnormal release.

•LogMessage "Users download complete" downgraded from info to debug.

•LogMessage "Configuration download complete" downgraded from info to debug.

•LogMessage "Firmware version download complete" downgraded from info to debug.

•Added info LogMessage "Firmware check complete".

•LogMessage "Provisioning reboot requested" upgraded from info to notice.

•When no CODEC matches for an incoming call, respond correctly with 488 Not Acceptable Here and not 503 Service Unavailable.

•Do not complain about unknown configuration key sip.dtmf.

When the SIP DTMF settings were changed the KWS complained about an unknown configuration key. This was not an error.

3.1.2 Removed Features

•Removed debug log level from the message filter on the status logs page in the GUI.

The debug messages were not available through the GUI anyway.

•The Derived Cipher Key which is used for encryption of voice data in the air is no longer stored at each handset location registration. It is stored at handset subscription and not subsequently. If authentication of calls is enabled a new derived Cipher Key will be calculated at each call. The only reason for storing the Derived Cipher Key after each location registration was to support the scenario where authentication of calls is disabled while encryption of calls is enabled. This scenario is no longer supported, to prevent problems with mismatching Derived Cipher Keys between PP and FP, authentication of calls is no longer optional if encryption is activated. This ensures that a new Derived Cipher Key is generated at every call.

•If the kgap crashes a crash log is no longer written to the flash. This could in some rare conditions result in corruption of the flash file system.

3.1.3 Corrections

•Handle UPDATE requests correctly for incoming calls. This fixes an issue with some call transfer scenarios encountered on a CUCM and on an Avaya Aura™ Session

Manager.

Page 3

Release Notes – KIRK Wireless Server 300 – October 13, 2010

•Always set to-tag in SIP responses except 100. This fixes an issue encountered in interoperability testing against Avaya Aura™ Session Manager version 6.0, regarding handling of call forwarding (302 Moved Temporarily).

•RTP check that data is coming through the jitter buffer and if not reset the session. Addresses DECTESC-204 which is an issue with one-way voice in the second of two subsequent calls to the same number on an Aastra PBX.

•Do not crash when Referred-By header is missing in REFER, DECTESC-207 Avaya IPOffice.

•For outgoing calls only check the ARI and not the RPN, fixes problem with DistyBox 300 reported in DECTESC-208.

When a handset performs an outgoing call the ARI of the system is sent to the system and checked. This failed for DistyBox 300 because the RPN was included in the ARI.

•Send BYE from transferor if transfer target does not send BYE.

Addresses DECTESC-215 where a PBX does not send a BYE in an attended transfer scenario causing a hanging call on the PBX. The scenario was identified on an IPECS Call Server.

•Bug fixed. May cause configuration daemon to crash if no network.domain is defined.

•Disabling MSF did not work, this is now corrected. MSF was reported as disabled but was still active.

•Shutdown uPnP properly if disabled.

•Pressing save in the web-GUI for a user in the user list would initiate a new SIP register even in the case where nothing was changed for the user in question. This is corrected.

•Indicate “reboot required” for endpoint separate local ports (a setting on the

Configuration | SIP page of the web GUI). This setting requires a reboot and this was not indicated in earlier releases.

•Do not truncate the last character of a broadcast request sent via XML-RPC.

•Fix bug not allowing CLMS to a single handset via MSF.

•Fix group number in CLMS via XML-RPC. Previously it was interpreted as hexadecimal, now it is interpreted as decimal.

•Only write DNS configuration when we have something to put in it - avoid overwriting DHCP.

•If HTTP request line contains a full url, strip scheme and host part.

3.1.4 Configuration File Parameter Changes

File	Action	Parameter	Description
config.xml	Added	sip.client_transaction_timeout	Specifies the timeout for
			client transactions. This
			controls timer B and F as
			specified in RFC3261.
			Values: Milliseconds
			(1000-32000).
			Default: 4000.

Page 4

Release Notes – KIRK Wireless Server 300 – October 13, 2010

3.2 Version PCS05D_ July 13, 2010

3.2.1 Added or Changed Features

•None

3.2.2 Removed Features

• None

3.2.3 Corrections

• Provisioning: Do not handle SIP NOTIFY check-sync events while updating the firmware.

If a SIP NOTIFY check-sync event was received while provisioning was updating the firmware, the device could reboot. This could make the device unable to start up afterwards.

This is only a problem if the firmware is updated via provisioning and SIP NOTIFY check-sync events are used.

3.2.4 Configuration File Parameter Changes

• None

3.3 Version PCS05C_ Q3, 2010

3.3.1 Added or Changed Features

•Implemented auto-answer feature which can be used for intercom and loudspeaker call. If an INVITE with an Alert-Info header, a Call-Info header or an Answer-Mode header is received, it is possible to make a Polycom handset automatically answer the call, mute the microphone and turn on speakerphone.

The reason for handling several headers for activating this feature is that different

SIP-PBXs have different default implementations. The following list of headers will activate auto answer:

•Alert-Info: Auto Answer

•Alert-Info: info=alert-autoanswer

•Alert-Info: Ring Answer

•Alert-Info: info=RingAnswer

•Alert-Info: Intercom (This is the default setting on Trixbox)

•Alert-Info: info=intercom

•Call-Info: =\;answer-after=0

•Call-Info: ;answer-after=0

•Answer-Mode: Auto (This is according to RFC 5373)

The feature is implemented in the 50-, 60and 70-Handset series (except 7010 which does not have speakerphone). The feature requires a recent firmware for the handsets.

Handset	Firmware version
5020 and 5040 series handsets	PCS08Ja (or newer) released 2010-Q3
6020 and 6040 series handsets	PCS06Da (or newer) released 2010-Q3

Page 5

+ 19 hidden pages