This release note applies to the released versions of the KWS8000 Firmware. This version
specifically applies to version PCS03N_ of the firmware. This release replaces the
PCS03M_ release as the latest generally available (GA) release.
2. Distribution Files
Click here >> to find the software image of the KWS8000.
3. Changes
3.1 Version PCS03N (Q3/2010)
3.1.1 Added or Changed Features
1) Implemented exchange/system ringing for analogue trunks. (Until OAM support is
possible, the function can be controlled in Command mode.) Exchange ringing is
selected by default. When set to exchange ringing, the ringing of the handset follows
the ringing cadence of the analogue line. When set to system ringing, the handset
follows its own ringing pattern.
2) Every time a handset is subscribed or switched on (location registration), an EMD
message is sent to the serial or IP interface.
3.1.2 Removed Features
None.
3.1.3 Corrections and Improvements
1) System, configuration and trace file (and of course the email report) have been
improved/extended.
2) Handling of EMD events with wrong length has been improved. The EMD developer
will now get more and better feedback.
3.1.4 Configuration File Parameter Changes
None.
3.2 Version PCS03M_ (Q2/2010)
3.2.1 Added or Changed Features
1) Driver support for BIF02 cards.
2) Support for depopulated backplane (KWS8000-light backplane).
2) Added content to log file generation from OAM program / email report.
3.2.4 Configuration File Parameter Changes
None.
3.3 Version PCS03K_ (Q2/2010)
3.3.1 Added or Changed Features
1) Added email report content.
2) From Command mode it is possible (via the T command) to see the last 3000 trace
messages.
Implemented EMD access to the following features: (This will be available from OAM
program in next version 0.1.0.5x)
3) Enable or disable “MSF between PP” functionality.
4) Change temporary standby text via MSF.
5) Alien DECT systems seen by RFP5. This is used to indicate how many other DECT
systems (ARI code and RSSI) the RFP can see.
6) Get system report (like email report - or an extended version of “Save configuration
statistics on PC”.
7) Get Cable Delay Values (CDV) statistics (every 64 sec. the CDV is read on every
connected RFP). If too many different values are read, it can indicate (together with
sync errors from the RFP) that the cable or connector needs some extra attention.
8) Added more debug info when receiving an “unsupported clip / message type”.
9) Supporting clip in POLYCOM 2010 DECT handset. When clip is received with only
DN and no NAME, the content of DN is copy to NAME field.
10) Improved RFP interface robustness.
11) Removed not relevant functions from Trace mode.
12) New messaging and hardware extension facilities for use with 60- and 70-Handsets.
3.3.2 Removed Features
None.
3.3.3 Corrections and Improvements
Fixed bug introduced in PCS03G_ regarding mails in single shelf system.
3.3.4 Configuration File Parameter Changes
None.
3.4 Version PCS03G_ (February/2010)
3.4.1 Added or Changed Features
1) Can now read HW_PCS from RFP5. (Available from Command mode – until OAM
SW supports the facility). Also available in email report.
2) Allows setup of different baud rates on the serial port (default is 115200 baud).
2) In a linked system, RFP sync and reset errors were stored in statistics only if the
RFP card was in the first shelf.
3) Added receiver gain for clip module (FSK) and receiver gain for DTMF gain.
4) The RFP’s could reset due to a few sync errors. The sensitivity has been decreased.
5) Improved handling of telnet EMD connection (requires KWS8000 OAM program -
0.1.0.44 or later).
6) Corrected error that could cause RFP to hang (power on, but not able to restart).
7) More engineering debugging.
8) Improved stability and performance.
9) Corrected error that caused system to reset. When an incoming call was made on
an analogue line where no user was created, the system could either reset or go into
a non-defined mode (and a number of undefined things could happen).
10) New engineering debug file(s) is attached to mail.
11) Corrected bug that caused only one ringing when handset was signed up as
dect2dect user.
12) Changed format on LID in trace messages when using analogue lines.
3.6.4 Configuration File Parameter Changes
None.
3.7 Version PCS02C_ (August/2009)
3.7.1 Added or Changed Features
1) Support for AB08 cards.
2) Support for Clip - DTMF, FSK Bellcore 202 and FSK_V23
a) The clip type is set from Command mode. (When the next version of the OAM
program is available it can be done from the Analogue settings tab.)
Go to Command mode, go to the Trace tab, and then click the Send button at the
bottom of the screen (the Main menu appears.)
b) Place the cursor in the Command field and type A to go to the Analogue menu
(the Analogue menu appears). Make sure that internal clip is disabled by typing
D in the Command field.
1) Enhanced security. Possible to calculate new encryption key for every new call.
2) Error when disconnecting RFP during call.
3) Another manufacturer’s GAP DECT handsets were not allowed to subscribe.
4) When no analogue or base station card was inserted in the system, the system
configuration was not shown properly and valid.
3.7.4 Configuration File Parameter Changes
None.
3.8 Version PCS02_ (Q3/2009)
3.8.1 Added or Changed Features
• Encryption of voice in the air.
Not all RFP’s support encryption. If a negative acknowledgement is received on an
attempt to enable encryption, it is probably because some or all RFP’s do not
support encryption.
If a “none encryption supporting” RFP is added while encryption is enabled, the RFP
is rebooted and a trace message can be viewed in the OAM program.
Encryption can be set to 3 levels.
1) Encryption turned off.
2) Encryption enabled – in case of encryption reject (PP or RFP can or will not
cipher the call), the call will be allowed to continue.
3) Encryption enabled – in case of encryption reject (PP or RFP can or will not
cipher the call), the call will be released.
Encryption is turned off by default. We recommend that you use RFP5 (SW part
number: 14170201) SW PCS03C_ or newer.
• Authentication of incoming and outgoing calls.
In older SW versions authentication is only done when a PP is turned on (doing a
location registration – and receiving standby text). With the current SW release, it is
also possible to authenticate a PP when starting or receiving a call.
• Configuration of IP addresses gateway and netmask.