Number: 17/2004 Date: 15th December 2004 Issue : 1. Nortel Networks Integrated DECT - Technical Support Update

Transcription

1 Number: 17/2004 Date: 15th December 2004 Issue : 1 Nortel Networks Integrated DECT - Technical Support Update Purpose The intention of this Newsflash is provide an update to issues described in the previous DECT Newsflash issued in September 2004 (NF 14/2004), and to provide additional important information on the Nortel Networks Integrated DECT Product. C4010/4020 handset Latest version of the C4010/4020 handset firmware is 0.51L. The up-issue from 0.51K to 0.51L is to facilitate production only, there are no problem fixes. C4040 handset The C4040 handset does not support SARI. There is a known problem with the C4040 handset subscribed to the PARI while the SARI is broadcast on the DECT system. The handset may not lock to the nearest base station when roaming in idle mode. In this event, the handset will lock to the nearest base station after going off-hook followed by on-hook. The problem is intermittent and does not occur when roaming in active mode therefore there are no call drops. In this event, ensure that the SARI is not broadcast and the handset is subscribed to the PARI of each DECT system where networking is required (MSMN). The C4040 can be subscribed to 10 DECT systems. A common PARI may also be used as a workaround where there are more than 10 DECT systems in the network to reduce the number of independent PARIs in the network below 10. C4050 Handset Latest version of the C4050 handset firmware is; Flash EEPROM This firmware version contains the following updates: Resolves intermittent noise problem. Improves scanning of strong RSSI signals from neighbouring base stations. There are currently no issues with this software Nortel Networks Limited. All Rights Reserved Page 1 of 7

2 C4030 Handset If Failed is displayed on the handset, then please ensure that: The site is deployed correctly. The site is configured correctly. There are no rogue DECT handsets. MPLR13166 installed where applicable. DMC software / (SNMP) is installed. That the C4030 remains within the coverage area as much as possible. The C4030 can occasionally go into a "failed" mode when it goes out of coverage and back into coverage again. Although this only happens rarely this should be taken into account when designing multiple DECT systems on single campus where people regularly walk from one system to the other. The term "rogue handsets" means handsets that have been de-subscribed using OTM while they are out of range and then subsequently come back into range. Handsets which are configured on the DECT system but not configured on the M1 are also termed as 'rogue handsets'. For regulatory reasons, the C4030 has a lower receive audio level than other DECT handsets. We recommend setting the System to Handset gain to +3dB (standard setting is 0 db) in the System Parameters. The C4030 battery status indication is lost if the handset is powered off. This is design intent as no circuits are left running when the handset is powered OFF. Note that a switched OFF handset will automatically switch ON when placed in the charger. When the Vibrator is enabled, only Melodies 1 and 2 are supported. Industrial Handset The latest version of the Industrial handset software is Va. This software includes: Support for DECT Messaging (E2 Messaging). Support of SARI. Changes to Voice Mail functionality and display. Support for SOS functionality emergency button on top of the handset calls preprogrammed DN. The handset software and User Guide are available on the TSC. Note that the content of the phonebook is lost following handset upgrade. The Phonebook40XX application to store/load the contents of the phonebook during upgrade is available on the TSC. A special docking station is required to upgrade the handset, this is available for loan on request. DECT Messaging Patch Information Latest patch for Nortel DECT Messenger is Patch also incorporates problems fixed in patches and The patch can be downloaded from the TSC Nortel Networks Limited. All Rights Reserved Page 2 of 7

3 The following indicates what problems were fixed with each patch: DMS Patch After approximately 2000 SNPP messages the DMS stops. This was due to the SNPP client failing to send a QUIT command and the DMS not freeing the resources. The JVM eventually ran out of memory. The DMS restarts after apparent socket problems. This then delays messages that were being sent at the time. DMS Patch SNMP authorization requests were failing. This was due to the third party SNMP libraries using Strings instead of byte arrays. Windows JVM translated any unrecognized bytes to? The third party code has now been updated to use bytes throughout. DMS Patch After several days of sending messages over SNPP the DECT Messaging System shuts down. This was due to multiple SNMP requests failing. These failures were due to multiple SNMP timers being started when only one is required. Patch installation Here we assume that DECT Messaging Software has previously been correctly installed and is operating on the machine. The user needs to do the following to apply the patch: Shut down the DECT Messaging System During the installation of the Release 1.6.x, we must have already defined an install directory for the DECT Messaging System. We will refer to this as $DECT, and we must now find this folder on the machine (by default $DECT will be C:\dectms). Within $DECT\lib\ we will find a number of jar files which the DECT Messaging System uses (including NORG.jar) Backup the current norg.jar by renaming it to norg_v1_6_x.jar Then backup the current jmgmt.jar by renaming it to jmgmt_v1_6_x.jar Where x is the current version of the DMS software installed. Copy the new norg.jar file to the $DECT\lib\ directory Copy the new jmgmt.jar file to the $DECT\lib\ directory Then the DECT Messaging System should be restarted. Handle Count Problem There is a known memory leakage problem with the Rainbow Technologies Superpro Server 6.1 which is used with the Nortel Messenger. This memory leakage causes the handle count for the Superpro Server process to increase to the point where the DECT Messaging Server memory resources are used up and the application will no longer operate. The Superpro Server Service should be stopped and startup type set to manual instead of automatic. This done as follows on Windows 2000: 2004 Nortel Networks Limited. All Rights Reserved Page 3 of 7

4 1. Click on Start Control Panel Administrative Tools Services 2. Right click on the Service name SuperProServer 3. Select Stop 4. Right click on the Service name SuperProServer 5. Select Properties 6. Under Startup type select manual from the drop down menu 7. Click OK Backup There is no supported means of backing up the DECT Messaging Server database. DMC Card Software Latest version of software for the DMC cards is: DMC DMC There are currently no reported issues with this software. Non-Concentration on DECT It is recommended to upgrade to Concentration mode if investigating DECT problems on X11 software version or greater. Permanent Hold not Supported with MDECT From X21 software Release 4.5, the Permanent Call Hold (PHD) feature will not be configurable on DECT sets. It was inherited from the basic 500/2500 set PBX configuration. There is no need for this feature on DECT sets as the Mute key on the DECT handset has the same effect. In the unlikely event that this has been configured on a DECT handset, then the next service change on the handset will cause the PHD feature to be automatically removed from the set and the craft person notified with a SCH1589 warning message. NTPs DECT Release 4 NTP has been updated to include: DECT Performance Manager User Guide. Remote modem connection to the DMC card. Debug Port User Guide. Deployment Kit2 User Guide. New Deployment Kit2 The Manual which accompanies each new DECT Deployment Kit2 has been updated to correct errors and provide additional information. More details can be found in DECT Release 4 NTPs. OTM DECT Enhancements The latest version of OTM is The following important issues have been resolved: The DECT Performance Manager can be run on a complete DECT system. Correct file naming and directory for the DECT Performance Manager. Both PARK and ARI are displayed in the subscriptions window. The PARK value is calculated from the ARI and is used to facilitate the subscription of DECT handsets Nortel Networks Limited. All Rights Reserved Page 4 of 7

5 DECT Performance Manager The latest version of the DECT Performance Manager is The Performance Manager Software and User Guide are available on the TSC. Secondary Access Rights Identifier (SARI) The following DECT handsets support SARI: - C C C Industrial Handset from s/w release Va. The PARI (Primary Access Rights Identifier) is a unique number belonging to a DECT system. The SARI (Secondary Access Rights Identifier) can be the same identifier, used on each DECT system in a DECT Network (MSMN) configuration. The DECT system can transmit both PARI and SARI as identification DECT signals, both PARI and SARI have the same function. If the handset detects a DECT signal in the air, it checks whether the PARI of that signal matches with its own data in the subscription record. If so, the handset "locks" to that signal. If not, the handset does a second check but now on the received SARI. If that matches, the handset "locks" to that signal. SARI can be used to subscribe DECT handsets to a number of DECT systems in the Multi-site Mobility Networking (MSMN) configuration. The handset uses the same subscription record (comprising the PARK, IPUI and UAK) in the handset for PARI or SARI. When MSMN was initially introduced, SARI was not supported. The capability to configure SARI was introduced with OTM. When using SARI, the handset must be subscribed to the SARI of one DECT system (Home), the subscription record is then copied to the other DECT systems (Visiting), all having the same SARI. That handset does not need to be subscribed to the other DECT systems in the network. Where there is already an existing installation and the handsets are subscribed to the PARI, all handsets requiring MSMN using SARI must be re-subscribed because the subscription record for each handset is incorrect. All subscriptions must be removed from each DECT system to configure SARI on OTM. It is only necessary to move to SARI on an existing network if it is desired to add network nodes, and then only the new nodes need to use SARI subscription. The existing network can continue using PARI. This avoids the need to re-subscribe the handsets Nortel Networks Limited. All Rights Reserved Page 5 of 7

6 Here s an example: Using SARI on 3 DECT systems DECT System X (Home) PARI = B4 SARI = A Ext. # X Subscription record for PP with SARI = Copy subscription record to: RFP Subscription record for PP with SARI = A PARI = SARI = A Ext. # X DECT System Y (Visiting) Subscription record for PP with SARI = RFP This subscription record matches the 3 DECT systems. Each DECT system has the same extension number X. PP = handset PARI = 10009E35 SARI = A Ext. # X DECT System Z (Visiting) Subscription record for PP with SARI = RFP The above figure gives an example of three different DECT systems in an MSMN configuration. There are three different PARI s and one common SARI. In this example the handset (PP) is subscribed to the SARI of system X. The other systems have the same SARI therefore the subscription record can be copied from DECT System X to DECT System Y and Z using OTM. When the handset receives radio signals from system Y or system Z, it first checks the PARI of that system and if that doesn't match the subscription record, it will do a check for the SARI of that system. The SARI matches with the PARK in the handset, and because the subscription data was copied, the UAK will also match. The handset can lock on systems Y and Z Nortel Networks Limited. All Rights Reserved Page 6 of 7

7 Latest DECT Service Pack for M DECT M1 Service Pack version 9 MPLR14005 Contains DECT related patches: MPLR DECT: Prompt WRLS set to YES automatically using "cpy" command. MPLR DECT: Dect diagnostic log swamped by message waiting audit signals. MPLR DECT: GROUP CALL CAUSES BLOCKED DCS SETS MPLR DECT: DECT BLIND TRANSFER FAILS MPLR DECT: Locked out DECT (DCS) set keeps channel busy. MPLR DECT: Incorrect protocol when Dect set is activated. MPLR DECT: DLAT timer does not work when the ATT calls a DECT phone. MPLR DECT: MDECT SETS DO NOT DISPLAY INCOMING CLID IF ORIG IS DASS2 MPLR DECT: BUG085 FROM DISCONNECT MESSAGE FROM DECT SET IN RINGING STATE. MPLR DECT: DECT SET USER ON UNIT 0 GETS THEIR CALL CUT OFF. MPLR DECT: Cannot place DCS DN into group hunt list. MPLR MERGE: MPLR MPLR MPLR MPLR DECT: ERR140 PRINTED FOR A NON-CONCENTRATED DECT SET. MPLR DECT: BUG6244 ON DECT CALLS. MPLR DECT: TWINNED DCS CONTINUES TO RING AFTER ATTN RLS CALL. ALSO, ATTN ENHANCED SECRECY IS REMOVED AFTER CFNA BACK TO THE ATTN. MPLR MERGE: MPLR13259 AND MPLR15428 MPLR DECT SET LOCKED AFTER MPO DAR RECALL MPLR DECT: Campon does not work with twinned DCS set MPLR MERGE: MPLR MPLR MPLR12977 MPLR CAN'T MOVE ANALOGUE TYPE (500 OR WRLS) PHONE SET (GET SCH0334) MPLR UNABLE TO MOV 500 SETS FROM EEPE TO SUPL MPLR DECT: CAN'T REMOVE 500 SETS ON A PHANTOM LOOP Latest Deplist Pack for M and 25.40B Euro Networking M1 Dep List Pack version 10 MPLR16006 Contains DECT related patches: MPLR13166 ( ISS 1) DECT: DECT SET LOCKUP OR OTHER SERIOUS PROBLEMS CAUSED BY MW LAMP AUDIT. MPLR14329 ( ISS 3) DECT: Locked out DECT set keeps channel busy. MPLR15095 ( ISS 1) DECT: PRINT OF DCS CONFIGURED ON SHELF 1 GIVES WRONG DMC LOOP MPLR15576 ( ISS 1) DECT: DTLAT timer does not work when the ATT calls a DECT phone MPLR15719 ( ISS 1) DECT: BUG085 from disconnect message from dect set in ringing state MPLR15720 ( ISS 1) DECT: Calls lost when MDECT set uses MPO DISD with CallPilot *** MPLR15908 ( ISS 1) DECT: DECT set user on unit 0 get there calls cut off. Reference: EMEA EV Copyright 2004 Nortel Networks Limited - All Rights Reserved. Nortel, Nortel Networks, the Nortel logo, Globemark, CallPilot, DMS, Meridian 1 are trademarks of Nortel Networks Limited. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. To access more technical documentation, search our knowledge base, or open a service request online, please visit Nortel Technical Support on the web at: If after following this guide you are still having problems, please ensure you have carried out the steps exactly as in this document. If problems still persist, please contact Nortel Technical Support (contact information is available online at: Nortel Networks Limited. All Rights Reserved Page 7 of 7