Aastra SIP DECT Software Release Notes for SW Version 2.1 ServicePack 2

Transcription

1 To R&D, PLM, Tier 3 support TEM1 Software Mobility Infrastructure Aastra SIP DECT Software Release Notes for SW Version 2.1 ServicePack 2 1 Software Identification Current Delivery Dependencies Last Delivery 2 2 Reason for Software Release New Functionality Corrections Other Reasons Open Issues 6 3 Restrictions 7 4 Additional Information 8 Aastra 1

2 1 Software Identification 1.1 Current Delivery SIP DECT Software Version 2.1SP2 - RFP SW including the OpenMobility Manager (OMM) for the RFP target - PC OMM SW including the Aastra 6x0d Firmware package OM Configurator 2.1SP2 (OMC) OM Management Portal 2.1SP2 (OMP) OM Locating 2.1SP2 (OML) Aastra 6x0d Firmware 3.03 Deliverable aafon6xxd.dnld omm_ffsip.tftp OM_Configurator.jar OML.war omm_ffsip_install.bin OMP.jar MD5sum digest (binary mode) 2033ade6c87db d171f7529a f80f089928b98db82c469f6d22a2600b 9facd62f90b6dd9f02ab5e4537eed53a d0cf d8c6a6cb9a1271b1b4e10 e8cb1c821d0d791e65f6f4266f8242a8 c5eaf8ad4a8247e318b341dfa2c7ddaa 1.2 Dependencies Aastra 142d Firmware Last Delivery SIP DECT Software Version RFP SW including the OpenMobility Manager (OMM) for the RFP target - PC OMM SW including the Aastra 6x0d Firmware package OM Configurator 2.1 (OMC) OM Management Portal 2.1 (OMP) OM Locating 2.1(OML) Aastra 6x0d Firmware 3.03 Deliverable aafon6xxd.dnld MD5sum digest (binary mode) 2033ade6c87db d171f7529a Aastra 2

3 omm_ffsip.tftp OM_Configurator.jar OML.war omm_ffsip_install.bin OMP.jar 6f779e09e57856d0386f68b9d a2d0453a f4739db00f207f fa192c12f4cde28bda967cf88e9148b0 f96727c1ab dc84e023f8a2 8b30c3993d3cb26e6918b4afabb31418 Aastra 3

4 2 Reason for Software Release 2.1 New Functionality SIP-DECT supports the Danish dial tone schema (country 104). Remote or forced log out If a user is still logged in to a DECT handset while logging in to another DECT handsets with the same credentials then the access to the first DECT handset is automatically terminated. This action is documented in the event and syslog e.g. " /05/23 16:44: EPR : Moved login for user '2222' from device PPN(00001) [RFP(0001) 'rfp 2'] to device PPN(00002) [RFP(0000) 'rfp 1']" 2.2 Corrections The following problems have been solved: CTBbe33644: RFP detected new SW but did not used it If a RFP detected a new SW while not connected to the OMM then the RFP did not restart automatically to load the new SW. CTBbe33772: IMA does not delete all messages in escalation-state and autodel.=true In collision cases (two messages received in parallel), it rarely happened, that one message remained in the queue. Afterwards messaging was not possible any longer for this handset user. Only a switch off/on of the handset could break the blocking state. CTBbe33786: Endless loop of sending REGISTER and receiving 401 The SIP registration of a handset could result in an endless loop of registration attempts, if the registrar answers an authorized REGISTER request with a 401 response requesting again authorizations. CTBbe33829: Stand-by OMM takes too long to detect connection loss It took up to 6 minutes for the stand-by OMM to detect a connection loss if the network failed. CTBbe33943: Manual db import via file server doesn't work sporadically When the "Download over Air" feature was switched on the import of configuration files from file server did not work sporadically. CTBbe33950: call forwarding problems, if digit treatment matches. CTBbe33955: SOS/Man Down call does not work in ringing state. A SOS or sensor initiated call e.g. Man Down were not setup successfully if the handset was in ringing state. Aastra 4

5 CTBbe33089: Android web browser freezes the OMM web service The attempt to access the OMM web service with an Android web browser blocks the web service until a restart of the OMM. CTBbe33784: OM Locating does not support Firefox 4.0 CTBbe33793 / defect 2447: new call after released early media conn. fails. This problem occurred in case of an outgoing call with early media when the call is rejected with a 4xx response. Afterwards, the first call was impossible (no INVITE or an INVITE with wrong calling number was sent out). After pressing hook on all following calls were possible again. CTBbe33809: Connection of OM Locating to OMM blocked In large and high traffic environments the connection between OM Locating and OMM could be blocked. CTBbe33893: attended transfer issue with A142d. Attended transfers performed with a 142d were not finished properly. CTBbe33919: Two ringback tones during outgoing calls. During an outgoing call, when the SIP proxy started an early media by sending a 183 response with SDP followed by 180 response, the early media and the internal ringback tone was played the same time. Now, as soon as early media is activated no internal tones will be played anymore. CTBbe33513: invalid user name if UD_Name not set If UD_Name was not set then the user name in the handset display remain "Please login". Now, the user name is set to "Name #<number>". CTBbe33614: changing TFTP server for the RFP SW does not change download over air URL automatically If the URL for the RFP SW has been modified then the RFP OMM did not use automatically this modified URL for the 600d SW. CTBbe33710: Feature access code can be configured twice The same feature access code could be configured for alarm trigger and system features but a FAC must be unique. Now, the OMM rejects the attempt to use a FAC for more than 1 feature simultaneously. CTBbe33776: Conflict between portable part user login type configuration via Web/OMP and common_user.cfg The portable part user login type could be configured inconsistently via Web/OMP and common_user.cfg. To avoid conflicts between the setting of the portable part user login type in the common_user.cfg and the OMM the parameter cannot be set via the common_user.cfg anymore. CTBbe33785: Automatic ringback does not show CLIP An automatic ringback e.g. after failed transfer did not show the calling party information. CTBbe33816: Messaging: missing paging timeout for message in certain collision cases. Aastra 5

6 In collision cases (see also CTBbe33772) the messaging server did not get any information, that one message could not be sent due to paging timeout. CTBbe33857: Call forwarding settings could get lost, after switching handset off/on. Switching a handset off/on sporadically caused the lost of the forwarding configuration. CTBbe33876: Short ringback tone when calling busy extension. During an outgoing call sometimes a short ringback could be heard before the busy tone was played for a busy calling side. CTBbe33980: LDAP settings lost during SW update to 2.1 During a SW update from 1.8.x to 2.1 the LDAP settings was lost. Multiple smaller fixes and improvements 2.3 Other Reasons None 2.4 Open Issues The OM Locating application presents SIP-DECT 2.1SP2 Build 0 as version number instead of SIP-DECT 2.1SP2. Aastra 6

7 3 Restrictions The DECT Monitor has been replaced by OMP but the DECT Monitor can still been used without warranty for SIP DECT installations with a standard PARK and up to 256 RFPs all within paging area 0. This release requires DECT Monitor release 2.0 or higher. Older DECT Monitor releases will not work. OMM Web service system page: The value US (FCC/CI) for the selection of the Regulatory Domain is only valid with FCC compliant RFP32/34 NAs. The RFP version information presented on the RFP Web services or OMP has the following format Major.Minor.X and does not support the scheme Major.Minor SP RC X (SP-Service Pack, RC Release Candidate). Aastra 7

8 4 Additional Information With the introduction of the enhanced digit treatment overlap sending requires always to terminate the dial process with a dial terminator. A new licensing concept has been introduced with 2.0. Please check the licensing condition before updating from 1.x to 2.x or later. Some features introduced with 2.x require an update of the RFP booter SW or the 600d handset SW. These features are not available until the SW has been updated. - New Booter features e.g. o Multicast-TFTP o TFTP-server redundancy The booter update will be performed automatically. - New handset features e.g. o Text messaging and related features like VCard support o User login/logout The SW update can be performed automatically over the air. As in the past, the database built with this release is not backward compatible with older releases. A downgrade to an older release will require a database matching the older release. Before upgrading the SIP-DECT SW a database backup is strongly recommended. The OM Management Portal (OMP) and the OM Configurator (OMC) requires Java Runtime environment version 1.6 or higher. The browser used for service access has to be at least Microsoft Internet Explorer 6.0 or Mozilla Firefox 1.5 and must have frame support, JavaScript and cookies enabled. After an upgrade from a 1.1.x to a 1.8.x SIP-DECT release or later, the login password of user 'omm' is reset to the default value 'omm'. With the first login on the Web interface after update there will be a mandatory requirement for changing the passwords for the omm and root account. The default password of root is Supplementary services and the improved user interface are running with Aastra DECT 142 / 142d handsets only with SW or higher. When upgrading or downgrading the SIP-DECT software please delete the cookies and the cache in your browser after the upgrade / downgrade and before connecting with the new OpenMobility Manager (OMM). Otherwise it may happen that the OMM Web service is locked. Firefox offers the possibility to delete the cookies only for a certain IP address, whereas in the Microsoft Internet Explorer all cookies have to be removed. Aastra 8

9 After an upgrade from 1.1.x to 1.8.x SIP-DECT release or later, the sending of User-Agent/Server header information is switched off by default. This can be activated again via the Web service (System->SIP->User agent info). After an upgrade from 1.x.x to 2.x.x SIP DECT release the booter of the RFPs will be updated to Version 3.4.x. The OM Configurator 2.x.x is required to configure all features of this new booter version. If you downgrade the RFPs to an older release the booter will not downgrade automatically. After an upgrade from 1.1.x to 1.8.x SIP-DECT release or later, the booter of the RFPs is login protected by the full access username and password (this is set in the Web service of the OMM). Aastra 9