lgf_2gbtsum_2012_36

LGF-2GBTSum-2012-36 Nokia Siemens Networks CONFIDENTIAL APPROVED 1.0 Page 1

List of Generic Faults LGF-2GBTSum-2012-36

GSM/EDGE BTS

UltraSite and MetroSite EDGE BTS

CX(M)8 CX(M)8.1


Table of Contents 1. Open problems ............................................................................................................................ 5

1.1 Open problems waiting for correction target .......................................................................... 5 1.2 Open problems targeted for CX(M)9 ...................................................................................... 5

1.2.1 HW Inventory - BCF Data CVSG Object missing ............................. 5 1.3 Open problems targeted for CX8.1 PP1.4.............................................................................. 5

1.3.1 TRX Faulty due to Alarm 7606 Interface problems between O&M and DSP SW Alarm ........................................................................................................ 6

1.4 Open problems targeted for CX8.1 PP1.3.............................................................................. 6 1.4.1 CSSR and SDCCH Abis fail ............................................................ 6 1.4.2 Cell reselection failure on E_BCCH BTS from 2G to TD .................. 7

2. Corrected problems ..................................................................................................................... 8 2.1 Open problems corrected in CX8.1 PP1.2 ............................................................................. 8

2.1.1 Alarm 7606 TRX FAULTY Interface problems between O&M and DSP SW unexpectedly raised. .............................................................................................. 8

2.2 Open problems corrected in CX(M)8.1 PP1.1 ........................................................................ 8 2.2.1 Traffic Channel Activation Alarm 7725 generated on some GP timeslots ........................................................................................................ 8

2.3 Problems corrected in CX(M)8.1 MP1.0 ................................................................................ 9 2.3.1 Traffic Channel Activation Alarm 7725 generated on some GP timeslots ........................................................................................................ 9

2.4 Problems corrected CX(M)8 MP1.0 and CX(M)8.1 ................................................................ 9 2.4.1 MetroSite Traffic Manager does not always show ABIS EDAP Configuration after MetroSite BTS Commissioning ......................................................... 10

2.5 Problems corrected in CX(M)8 ..............................................................................................10 2.5.1 Unexpected 7606 TRX Faulty alarms raised in Antenna Hopping Sector ...................................................................................................... 10 2.5.2 A lock / unlock of BCCH TRX causes incorrect log writing in BCSU ...................................................................................................... 11 2.5.3 Antenna Hopping Sector gets stuck in configuring when Alarm 7995 is cancelled ...................................................................................................... 11

2.6 Problems corrected in CX(M)7 MP4.0 and CX(M)8 ..............................................................11 2.6.1 One BTS of common BCCH segment goes into faulty state with all its TRXs when common BCCH is configured with RF & Antenna hopping. ................... 12 2.6.2 Alarm 7606 TRX FAULTY "Antenna Connection Faulty" appears randomly ...................................................................................................... 12 2.6.3 Alarm 7606 TRX FAULTY "No data is received from DIBA Asic traffic channel ...................................................................................................... 12

2.7 Problems Corrected in CX(M)7 PP3.2 ..................................................................................13 2.7.1 Since enabling Extended CCCH there is increase in TCH RF losses ...................................................................................................... 13 2.7.2 Increase in SDCCH failures following Extended CCCH activation ...................................................................................................... 13 2.7.3 Increase in TBF failures following Extended BCCH activation ...................................................................................................... 14 2.7.4 Alarm 7606 TRX FAULTY "No data is received from DIBA Asic traffic channel ...................................................................................................... 15

2.8 Problems corrected in CX7 MP3.0 ........................................................................................15 2.8.1 Site does not work after Lock/Unlock in IDD 4UD with ECCCH and BB hopping ...................................................................................................... 15


2.8.2 Cannot make Mobile Terminated call under two cells with Extended CCCH ...................................................................................................... 16 2.8.3 Reconfiguration of BCCH doesn't take place in an Antenna Hopping sector when an alarm is already present in the sector. ................................................ 16

2.9 Problems corrected in CX7 MP2.0 ........................................................................................17 2.9.1 Site Synchronization loss .............................................................. 17 2.9.2 Abis loop test gives false reason - Hardware Failure ..................... 17 2.9.3 SW UltraSite CX5 CD 4.0 and Satellite Abis.................................. 17 2.9.4 UltraSites Generating 2993 Alarms and increased dropped calls. ...................................................................................................... 18 2.9.5 High interference levels in case of PWSB failure ........................... 18

2.10 Problems corrected in CX(M)6 MP3.0 ..................................................................................19 2.10.1 UltraSites Generating 2993 Alarms and increased dropped calls. ...................................................................................................... 19 2.10.2 Site Synchronization loss .............................................................. 20 2.10.3 Abis loop test gives false reason - Hardware Failure ..................... 20 2.10.4 Voice quality issues on several BSCs after new BTS SW load ...................................................................................................... 20

2.11 Problems corrected in CX(M)7 MP1.0 ..................................................................................21 2.11.1 TRX are going to Blocked TRX after enabling Antenna Hoping ...................................................................................................... 21 2.11.2 Non-EDGE TSPA 1900 radios possible incompatibility with new sw load ...................................................................................................... 21 2.11.3 Voice quality issues on several BSCs after new BTS SW load ...................................................................................................... 22 2.11.4 Alarm 7606 TRX faulty BOI detected that connection to TRX is lost reported for working TRX in IDD/4UD configuration. ............................................... 22 2.11.5 SDCCH drops with baseband hopping .......................................... 22 2.11.6 MOS value is lower in Ater interface .............................................. 23 2.11.7 BCCH Transmission fluctuates ...................................................... 23 2.11.8 TRX Test fails on some of the time-slots in IDD-Ultra with RF Hopping enabled. ...................................................................................................... 24 2.11.9 FBUS Hardware failure ................................................................. 24 2.11.10 TRX Test shows invalid behaviour when IDD is enabled on site ...................................................................................................... 25 2.11.11 Repeated TAC in AHS calls when A-bis link is disturbed on GSM hardware ...................................................................................................... 25 2.11.12 BTS not passing transmission alarms ........................................... 25 2.11.13 BTS sends STATE CHANGE message for the faulty TRX. ........... 26 2.11.14 Incorrect RX DIV cabling defined in the configuration wizard ......... 26 2.11.15 Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled ...................................................................................................... 27 2.11.16 Cannot make a call with second MetroSite BTS in chain after BTS SW upgrade ...................................................................................................... 27 2.11.17 Calls are possible on a GSM TRX, which is locally blocked, after STIRC enable/ disable. ...................................................................................................... 27

2.12 Problems corrected in CX(M)7 ..............................................................................................28 2.12.1 7607 VSWR monitoring alarm following AHOP activation .............. 28 2.12.2 Unable to perform Manual MMI Commissioning of Ultra BTS ........ 29 2.12.3 Average RACH busy count is low in CCCH Load Indicationl ......... 29


2.12.4 Transmission unit alarms are not cleared at BSC and NetAct ...................................................................................................... 29 2.12.5 Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled ...................................................................................................... 30

Contact:

Contact your local Nokia Siemens Networks support Summary of changes:

05-09-2012 Official Version Updated


1. OPEN PROBLEMS

1.1 Open problems waiting for correction target

This section lists the major problems, which are currently being investigated as BTS problems. However, as the root cause has not been found, no target has yet been set to these problems.

1.2 Open problems targeted for CX(M)9

This section lists all the existing problems, which have been targeted for correction in BTS SW CX(M)9 release.

1.2.1 (NEW) HW Inventory upload to Netact shows incorrect PSU type

Problem report: NA05054253 Exists in: CXM7 MP2.0 Correction Target: CXM9 Severity: C-Minor Reported date: Jan 2012 Closed date: Jun 2012 Description: It has been observed that if a CVSG power supply unit (PSU) is installed to the BTS site then the hardware inventory uploaded to Netact shows the PSU type to be HVSA instead of CVSG. The problem has been found to be incorrect unit identity code for the CVSG unit which is stored in the PSU eeprom. Solution / Workaround: - System Impact: None

1.3 Open problems targeted for CX8.1 PP1.4

This section lists all the existing problems, which have been targeted for correction in BTS SW CX8.1 PP1.4 release.


1.3.1 (NEW) Alarm 7606 TRX Faulty Interface problems between O&M and DSP SW Alarm is unexpectedly started

Problem report: NA05110010, NA05108678, NA05193055, NA05202287,NA05191832 Exists in: CX(M)8.1 MP1.0 Correction Target: CX(M)8.1 PP1.3 Severity: A-Critical Reported date: May 2012 Closed date: Jul 2012 Description: After upgrading UltraSite BTS SW to CX8.1 MP1.0 or later, occasionally the alarm 7606 TRX Faulty -" Interface problems between O&M and DSP SW ALARM" is reported randomly on UltraSite BTS. In this case the BTS HW can be either EDGE or none EDGE (a previous case NA05082487reported against Non-EDGE TRX with BB2F HW). Solution / Workaround: - System Impact: TRX remains blocked and no traffic can be carried.

1.4 Problems targeted for CX8.1 PP1.3

This section lists all the problems, which have been corrected in BTS SW CX8.1 PP1.3 release.

1.4.1 CSSR and SDCCH Abis fail

Problem report: NA05195617 Exists in: CX(M)8.1 MP1.0 Correction Target: CX(M)8.1 PP1.3 Severity: A-Critical Reported date: Jul 2012 Closed date: Jul 2012 Description: The reported problem is seen, when upgrading the BTS SW from CX7 MP4.0 to CX8.1 MP1.0 the SDCCH drop rate (SDCCH_ABIS_FAIL) increased affecting the customer network. In the SW build CX8.1 MP1.0 BTS is not sending the Chan Act Ack and RF Chan Rel Ack for significant numbers of Chan Act and RF Chan Rel respectively for SDCCH. In such scenario counter 001075 (SDCCH_ABIS_FAIL) is being pegged which results in higher SDCCH drop rate. Solution / Workaround: N/A System Impact:


SDCCH drop rate degradation causes bad impact on customer Network performance. .

1.4.2 Cell reselection failure on E_BCCH BTS from 2G to TD

Problem report: NA05218266 Exists in: CX(M)7 MP4.0 Correction Target: CX(M)8.1 PP1.3 Severity: A-Critical Reported date: Jul 2012 Closed date: Jul 2012 Description: For UltraSite EDGE BTS sites in the network having configuration as E-BCCH+CCCHE, index 1 & 3 of SI2 quarter informations are missing and only index 0 & 2 SI2 quarter informations are reported in idle state causing cell reselection procedure failure to TD-SDMA cells. Solution / Workaround: N/A System Impact: Cell reselection failure to TD-SDMA for MS in idle mode.


2. CORRECTED PROBLEMS

2.1 Open problems corrected in CX8.1 PP1.2

This section lists all the existing problems, which have been corrected in BTS SW CX8.1 PP1.2 release.

2.1.1 Alarm 7606 TRX FAULTY Interface problems between O&M and DSP SW unexpectedly raised.

Problem report: NA05082487 Exists in: CX(M)8.1 MP1.0 Correction Target: CX(M)8.1 PP1.2 Severity: B-Major Reported date: Feb 2012 Closed date: Apr 2012 Description: During piloting phase of CX(M)8.1 MP1.0 7606 TRX Faulty alarms were unexpectedly reported. Investigation revealed that the problem occurs when the STIRC parameter is ON with the combination of Non-EDGE TRX with BB2F. When STIRC is set to OFF the 7606 alarms clear. Solution / Workaround: Set STIRC to off in the BTS System Impact: Unexpected Alarms raised prior to implementation of Workaround.

2.2 Open problems corrected in CX(M)8.1 PP1.1

This section lists all the existing problems, which have been corrected in BTS SW CX(M)8.1 PP1.1 release.

2.2.1 Traffic Channel Activation Alarm 7725 generated on some GP timeslots

Problem report: NA05043684 Exists in: CX(M)7 MP4.0 Correction Target: CX(M)8.1 PP1.1 Severity: B-Major Reported date: Feb 2012 Closed date: Mar 2012 Description: In Master-slave configuration (DCS1800), after total BSC restart, the Slave site was found out of Sync. (BL-BCF state) with alarm reported 7600 BCF Faulty BSS Sync. Failed, While the Master site was in supervisory state. The recovery of Slave site was possible after logical reset (BCF Lock/Unlock). The problem could be seen randomly at some of sites in the network after BSC total restart


Solution / Workaround: BCF Lock/Unlock to recover System Impact: Loss of slave site requiring BCF Lock/Unlock to recover.

2.3 Problems corrected in CX(M)8.1 MP1.0

This section lists all the existing problems, which have been corrected in BTS SW CX(M)8.1 MP1.0 release.

2.3.1 Traffic Channel Activation Alarm 7725 generated on some GP timeslots

Problem report: NA05050505 Exists in: CX(M)8.1 Correction Target: CX(M)8.1 MP1.0 Severity: B-Major Reported date: Jan 2012 Closed date: Feb 2012 Description: The Traffic Channel Activation alarm 7725 is unexpectedly generated for some GP timeslots (configured as TCHD) when

both sub channels on the same timeslot are used for speech and the call on sub channel 0 is released prior to sub channel 1

sub channel 0 is idle and sub channel 1 is being used for a voice call

The problem occurs because when the RF channel is released and GPRS synchronisation (for GPRS territory upgrade) between the timeslot and PCU is not re-established. The alarm is cancelled when sub channel 0 of the problematic timeslot is used again for a voice call and is released when sub channel 1 remains idle. Solution / Workaround: Used fixed GP territory allocation, or disable HR. System Impact: No GPRS activity on problem timeslot until situation has recovered

2.4 Problems corrected CX(M)8 MP1.0 and CX(M)8.1

This section lists problems, which have been corrected in BTS SW CX(M)8 MP1.0 and CX(M)8.1 releases.


2.4.1 MetroSite Traffic Manager does not always show ABIS EDAP Configuration after MetroSite BTS Commissioning

Problem report: NA04862774 Exists in: CXM7 Correction Target: CXM8 MP1.0 and CXM8.1 Description: Traffic Manager does not always show ABIS EDAP Configuration after Metrosite BTS Commissioning. Traffic Manager always shows TS-0 as TRX-1 EDAP timeslot (although TRX-1 is a non Edge BTS) Traffic Manager does not show TRX-3 and TRX-4 as part of EDAP pool, only TRX-3. On occasions after BTS commissioning when Traffic Manager has been selected incorrect EDAP timeslots were visible in the transmission map Solution / Workaround: None System Impact:

Operator will see mismatch between the settings that he has given during commissioning and settings which are fetched from traffic manager after commissioning is complete

2.5 Problems corrected in CX(M)8

This section lists all the problems, which have been corrected in BTS SW CX(M)8.

2.5.1 Unexpected 7606 TRX Faulty alarms raised in Antenna Hopping Sector

Problem report: 21479ESPE06 Exists in: CX7(M) MP3.0 Correction Target: CX8 Description: During lab testing with the BTS configuration 4 (RF hopping) + 4 (RAH - Antenna Hopping with RF Hopping), following a sector reset, alarm 7606 TRX Faulty there is disturbance in the serial DL Bus or Bus is broken was raised in the the RAH sector. After a short period alarm 7606 TRX Faulty: The RF receiver frequency hopping synthesizer is not locked is then raised and the TRXs remain in BL TRX state at the BSC. A local sector reset recovers the situation. Solution / Workaround: BCF Reset System Impact: Calls are not possible on the blocked TRXs.


2.5.2 A lock / unlock of BCCH TRX causes incorrect log writing in BCSU

Problem report: 52946ESPE01 Exists in: CX7(M) MP2.0 Correction Target: CX(M)8 Description: Incorrect log writing has been observed on the BCSU when a BTS sector is locked and then unlocked when the sector has BB Hopping and ECCH feature enabled and each TRX in the sector is assigned to a DAP. The problem occurs because the BTS sends two ACK messages to the BSC for the BCCH TRX in response to a BTS CHA ADM STATE message from the BSC. Solution / Workaround: - System Impact: -

2.5.3 Antenna Hopping Sector gets stuck in configuring when Alarm 7995 is cancelled

Problem report: 18188ESPE07, 18147ESPE07 Exists in: CX7(M) MP2.0 Correction Target: CX8 Description: It has been observed that in the following configuration 4 (RAH - Antenna Hopping with RF hopping) + 4 (BB Hopping) + 4 (BB Hopping) after alarm 7995 is raised and then cancelled, calls are dropped in the Antenna Hopping sector and it remains in Configuring state. Solution / Workaround: Perform a BTS lock / unlock at the BSC for the Antenna Hopping sector. System Impact: Calls in the Antenna Hopping sector are dropped.

2.6 Problems corrected in CX(M)7 MP4.0 and CX(M)8

This section lists all the problems, which have been corrected in BTS SW CX(M)7 MP4.0 and CX(M)8.


2.6.1 One BTS of common BCCH segment goes into faulty state with all its TRXs when common BCCH is configured with RF & Antenna hopping.

Problem report: 4329C02 Exists in: CX6 UltraSite Correction Target: CX7 MP4.0 andCX8 Description: In case of common BCCH segment with RF hopping being enabled; if duplexer units are used that support different frequency ranges of the same band, and BCCH frequency is not in range of the Duplexer which is being used in non-BCCH sector; then all TRXs of non BCCH sector go into faulty state one by one with the alarm 7606 TRX Faulty, failure detected during TRX configuring. Solution / Workaround: Change the duplexer to which the BCCH ARFN is supported. System Impact: The alarm 7606 TRX Faulty failure detected during TRX configuring is reported for the non BCCH sector in common BCCH segment.

2.6.2 Alarm 7606 TRX FAULTY "Antenna Connection Faulty" appears randomly

Problem report: NA04517340 Exists in: CX6 CD1.0 UltraSite Correction Target: CX7 MP4.0 andCX8 Description: Alarm 7606 TRX FAULTY "Antenna Connection Faulty" appears in E-GSM 900 BTS sectors with BB Hopping enabled when non-EDGE HW (BB2A+TSGA) is installed. The alarm occurs on a non-BCCH TRX and is random in nature. The alarm may reappear after days or weeks. Solution / Workaround: The problem is cleared by restarting the BTS sector, although the alarm may reappear some time later. This issue is not seen with Non-hopping or RF-hopping sectors or when an EDGE capable BB2F is used. The correction is available for BSS14 customers and in Priority Package CX7 PP2.1 on request. System Impact: The alarming TRX is out of service until BB-hopping sector is restarted.

2.6.3 Alarm 7606 TRX FAULTY "No data is received from DIBA Asic traffic channel

Problem report: NA04714262 Exists in: CX6 MP3.0 UltraSite Correction Target: CX7 MP4.0 & CX7 PP3.2 and CX8 Description:


Alarm 7606 TRX FAULTY "No data is received from DIBA Asic traffic channel " appears randomly to BTS sectors with BB Hopping enabled when non-EDGE HW (BB2A) is installed. After restarting the sector, the alarm may reappear. Solution / Workaround: Disable BB-hopping or change the BB2A plug-in unit to BB2E or BB2F. The correction is available for BSS14 customers with Priority Package CX7 PP3.1 on request. System Impact: The alarming TRX is out of service until the BB-hopping sector is restarted.

2.7 Problems Corrected in CX(M)7 PP3.2

This section lists all the problems, which have been corrected in BTS SW CX(M)7 PP3.2.

2.7.1 Since enabling Extended CCCH there is increase in TCH RF losses

Problem report: NA04737527 Exists in: CX(M)7 MP3.0 Correction Target: CX(M)7 PP3.2 Description: During piloting of new BTS SW CX(M)7 MP3.0 it was noticed that KPI following TCH failures increased. The increase was seen only in 3 BTS sites where the Extended CCCH feature was active. All the remaining BTSs in the pilot clusters (total of 4 BSCs) were performing normally. The CCCHE TSL was configured to TSL 2 only. The Extended BCCH feature was active at the same time as Extended CCCH. Extended BCCH active alone will cause KPI degradation, however the problem is more visible when both features are active at the same time. - BSC support for Extended CCCH with BB-hopping configurations: The BSC SW earlier than S14 MP6.0 does not support BB-hopping with BCCH TRX when Extended CCCH is used. This will cause a loss of BB-hopping gain in the BCCH TRX radio path for CCCHE, SDCCH and TCH signalling. Further improvements in BB-hopping algorithm are scheduled to be made in BSC SW after MP6.0 to support Extended CCCH with BB-hopping BTS sector. Solution / Workaround: Disable Extended BCCH or Extended CCCH feature. System Impact: Increase of the daily amount of TCH RF failures and TCH Failure Rate KPI.

2.7.2 Increase in SDCCH failures following Extended CCCH activation

Problem report: 25561ESPE05 Exists in: CX(M)7 MP3.0


Correction Target: CX(M)7 PP3.2 Description: During piloting of new BTS SW CX(M)7 MP3.0 the SDCCH Failure Rate KPI increased in some BTSs after enabling Extended CCCH feature. All the remaining BTSs without the feature active were working OK.

Some old mobile models do not fully support The Extended CCCH feature. The problem seen during the pilot might be partially caused by old mobile models. The Extended BCCH feature was active at the same time as Extended CCCH. Extended BCCH active alone will cause KPI degradation, however the problem is more visible when both features are active at the same time. - BSC support for Extended CCCH with BB-hopping configurations: The BSC SW earlier than S14 MP6.0 does not support BB-hopping with BCCH TRX when Extended CCCH is used. This will cause a loss of BB-hopping gain in the BCCH TRX radio path for CCCHE, SDCCH and TCH signaling. Further improvements in BB-hopping algorithm are scheduled to be made in BSC SW after MP6.0 to support Extended CCCH with BB-hopping BTS sector.

Solution / Workaround: Disable Extended BCCH or Extended CCCH feature. System Impact: Increase in SDCCH Failure Rate KPI.

2.7.3 Increase in TBF failures following Extended BCCH activation

Problem report: 25560ESPE05 Exists in: CX(M)7 MP3.0 Correction Target: CX(M)7 PP3.2 Description: During piloting of new BTS SW CX(M)7 MP3.0 the GPRS TBF Success Rate KPI decreased with the BTS sites were Extended CCCH and Extended BCCH features were active. The issue was visible in both Uplink and Downlink TBFs and with both PCU1 and PCU2. The issue does have only minor impact to the end user data services, as some retransmissions will happen due to TBF failures. The Extended BCCH feature was active at the same time as Extended CCCH. Extended BCCH active alone will cause KPI degradation, however the problem is more visible when both features are active at the same time. - BSC support for Extended CCCH with BB-hopping configurations: The BSC SW later than S14 MP6.0 does not support BB-hopping with BCCH TRX when Extended CCCH is used. This will cause a loss of BB-hopping gain in BCCH TRX radio path for CCCHE, SDCCH and TCH signaling. Further improvements in BB-hopping algorithm will be made in BSC SW side to support Extended CCCH with BB-hopping BTS sector.

Solution / Workaround: Disable Extended BCCH or Extended CCCH feature


System Impact: Decrease in TBF Success Rate KPI.

2.7.4 Alarm 7606 TRX FAULTY "No data is received from DIBA Asic traffic channel

Problem report: NA04714262 Exists in: CX6 MP3.0 UltraSite Correction Target: CX7 MP4.0 & CX7 PP3.2 (CX7 PP3.1 on request) Description: Alarm 7606 TRX FAULTY "Antenna No data is received from DIBA Asic traffic channel " appears randomly to BTS sectors with BB Hopping enabled when non-EDGE HW (BB2A) is installed. After restarting the sector, the alarm may reappear. Solution / Workaround: Disable BB-hopping or change the BB2A plugin unit to BB2E or BB2F. The correction is also available for BSS14 customers with Priority Package CX7 PP3.1 on request. System Impact: The alarming TRX is out of service until the BB-hopping sector is restarted.

2.8 Problems corrected in CX7 MP3.0

This section lists all the problems, which have been corrected in BTS SW CX(M)7 MP3.0

2.8.1 Site does not work after Lock/Unlock in IDD 4UD with ECCCH and BB hopping

Problem report: 18098ESPE06 Exists in: CX7 MP2.0 UltraSite (Extended CCCH feature) Correction Target: CX7 MP3.0 Description: BTS is configured with BB-hopping, IDD and 4UD. Extended CCCH is configured for TS 2 in BCCH TRX. Steps to reproduce the problem: 1. BTS is in supervisory state and there is no alarms active. 2. Sector is Locked from the BSC (MML:ZEQS:BTS=BTS ID:l;). 3. Sector is Unlocked from the BSC. The BTS does not come up. An error message is seen on MML terminal " BSC DATABASE UPDATED

/*** BTS SITE NOT UPDATED ***/ /*** DX ERROR: 154 ***/ /*** TIME LIMIT EXCEEDED IN MESSAGE WAITING ***/"

On Abis trace it is seen that after Lock command the BTS does not Acknowledge or NAck the BTS CHAN ADM STATE" commands from BSC for BCCH TRX. This creates problem after unlocking the sector. Solution / Workaround: The problem does not happen when BCF Lock is used instead of BTS Lock. The problem is cleared by Lock/Unlock the BCF.


System Impact: BTS service is down until BCF is restarted.

2.8.2 Cannot make Mobile Terminated call under two cells with Extended CCCH

Problem report: 18623ESPE07, NA04694591 Exists in: CX7 MP2.0 UltraSite (Extended CCCH feature) Correction Target: CX7 MP3.0 Description: The mobile terminated calls under BTSs with Extended CCCH are not successful when the Paging is done using Extended CCCH Paging channels. This occurs randomly but is typically seen once within 12 hours after a site restart. The problem occurs with BTS sectors where the CCCH parameter MFR (number of multiframes) equals 3,5,6,7 or 9. Solution / Workaround: The problem is cleared by restarting the BCF. Change the MFR value to 2, 4 or 8. The correction is available for BSS14 customers also in Priority Package CX7 PP2.2 on request System Impact: No mobile terminated calls are possible if Paging message is sent using Extended CCCH paging channels.

2.8.3 Reconfiguration of BCCH doesn't take place in an Antenna Hopping sector when an alarm is already present in the sector.

Problem report: 15298ESPE07 Exists in: CX6 UltraSite Correction Target: CX7 MP3.0 Description: A non BCCH TRX (TSx) from an Antenna Hopping BTS sector is locked at the BSC. When the locked TRX is removed from the cabinet, alarm 7606 TRX Faulty: There is disturbance in the serial DL bus or bus is broken is activated and can be seen in BTS Manager. If the BCCH TRX is removed (or it is faulty) from the Antenna Hopping BTS sector, no alarm is received either at the BSC or in BTS Manager. A sector BCCH reconfiguration does not take place. Note: When the non BCCH TRX is not locked at the BSC and the BCCH TRX is removed (or is faulty), normal behaviour is observed and a BCCH reconfiguration in the sector occurs as expected. Solution / Workaround: Restart the BTS sector (BTS lock then unlock at the BSC) to perform the BCCH reconfiguration. BCCH reconfiguration takes place when there is no antenna hopping in the sector. System Impact: The BCCH signal is down and no calls are possible until the sector is restarted.


2.9 Problems corrected in CX7 MP2.0

This release does not include any corrections to MetroSite EDGE BTS as the BTS SW was not released due to lack of content.

2.9.1 Site Synchronization loss

Problem report: NA04527054, NA04508947 Exists in: CX5 UltraSite Correction Target: CX7 MP2.0 & CX6 MP3.0 Description: After a mains power outage or fluctuation in transmission lines the slave cabinet might not recover and follow the master cabinet synchronisation. The DAC value can drift out from the correct value and the slave cabinet can not handle any calls. The problem is rare and random in nature. Solution / Workaround: Restart the slave cabinet BCF. When the same scenario happens with the corrected BTS SW, a new alarm is activated: 7601 BCF OPERATION DEGREADED RESYNCHRONIZATION IN PROGRESS. When the system recovers, the alarm is cancelled. System Impact: No calls are possible with the slave cabinet until the cabinet BCF is restarted.

2.9.2 Abis loop test gives false reason - Hardware Failure

Problem report: NA04579914 Exists in: CX(M)5 UltraSite and MetroSite Correction Target: CX(M)6 MP3.0 & CX7 MP2.0 Description: When Abis Loop Test is run from a BSC for a TRX which is carrying traffic the test result may fail and the reason is Hardware Failure. When calls are on the TRX under testing, the tested timeslots before the one carrying a call will fail with reason Hardware Failure. Solution / Workaround: Repeat the testing when there is no calls ongoing or use Cell Barring from BSC. System Impact: The TRX might be sent over HW services even there is no real HW problem with the unit.

2.9.3 SW UltraSite CX5 CD 4.0 and Satellite Abis

Problem report: NA04189039 Exists in: CX5 CD1.1 UltraSite Correction Target: CX7 MP2.0 Description:


BTS using satellite Abis may during high traffic situations see an unexpected increase in Immediate Assignment Reject. The BTS fails to deal correctly with a signalling overload in the Abis. Solution / Workaround: - System Impact: Increase in Immediate Assignment Reject messages.

2.9.4 UltraSites Generating 2993 Alarms and increased dropped calls.

Problem report: NA04506855, NA04555083 Exists in: CX6 CD1.0 UltraSite Correction Target: CX7 MP2.0 & CX6 MP3.0 (original target was CX7 MP1.0) Description: 2993 BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS INTERFACE alarms are repeating (start/cancel) several times for the same timeslot and will increase the call drop ratio in problem cells. The problem has been reported with BB2A cards only. The alarm can be caused also for other reasons than a BTS SW failure. In other cases, this alarm only informs the user that calls are cleared due to unsatisfactory transmission or equipment failure, but it does not directly indicate the faulty equipment, for example, a plug-in unit. This issue was originally fixed with BTS SW CX4.1 CD3.0 but due to SW integration with other SW changes, the fault has been reintroduced with BTS SW CX6 CD1.0. The fault has not been seen with MetroSite but the same correction applies to MetroSite BTS SW as well. During the pilot of CX(M)6 MP3.0 the correction for 2993 alarm problem in Non EDGE UltraSites was verified in live customer network. Initial results would seem to indicate that the number of 2993 alarms has been reduced to a negligible level, however this is based on the results received from 2 BSCs over a 2 week period when compared to the number of 2993 alarms prior to the SW CX(M)6 MP3 being piloted. Pilot customer (2993 issue report) have indicated that although initial results look good, confirmation that the 2993 issue has been resolved cannot occur until the SW has been deployed network wide. Pilot customer have agreed that there is nothing shown in the KPIs or alarm history that would defer or postpone their acceptance of CX(M)6 MP3.0. Solution / Workaround: A TRX reset or a BTS reset (BB hopping or UltraSite BTS Antenna Hopping) clears the situation, but the alarm can be repeated after several days. System Impact: Slight increase in call drop ratio.

2.9.5 High interference levels in case of PWSB failure

Problem report: 23261ESPE05 Exists in: CX5 CD1.0 UltraSite Correction Target: CX7 MP2.0


Description: Power supply unit PWSB alarm 7602 Power supply unable to read MHA current can cause DVxx units to be set to high gain mode if antenna is configured with MHAs. The use of High gain mode will increase interference levels for the TRX receiver side for all antennas where a working MHA is providing increase in RX gain. During the failure, the interference levels which BTS reports to BSC changes from 0 to 3 and the DVxx unit is set to have +32dB extra gain. Solution / Workaround: The failed power supply has to be replaced because of the alarm 7602 Power supply unable to read MHA current. Until it is possible to replace the unit, check the interference levels using BSC (MML: use ZERO command to check ILEV). If the interference levels are abnormally high then connect to the site locally or remotely with BTS Manager, open HW Configurator and set MHA the co-siting option ON. System Impact: High interference level in receiver side will cause unnecessary HOs, bad RX quality and increase in call drop ratio.

2.10 Problems corrected in CX(M)6 MP3.0

Please note that the SW is build on top of CX(M)6 CD2.0 thus it does not contain all corrections from CX(M)7 or CX(M)7 MP1.0.

2.10.1 UltraSites Generating 2993 Alarms and increased dropped calls.

Problem report: NA04506855, NA04555083 Exists in: CX6 CD1.0 UltraSite Correction Target: CX(M)7 MP2.0 & CX(M)6 MP3.0 (original target was CX7 MP1.0) Description: 2993 BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON ABIS INTERFACE alarms are repeating (start/cancel) several times for the same timeslot and will increase the call drop ratio in problem cells. The problem has been reported with BB2A cards only. (MetroSite with non EDGE HW only). The alarm can be caused also for other reasons than a BTS SW failure. In other cases, this alarm only informs the user that calls are cleared due to unsatisfactory transmission or equipment failure, but it does not directly indicate the faulty equipment, for example, a plug-in unit. This issue was originally fixed with BTS SW CX4.1 CD3.0 but due to SW integration with other SW changes the fault has been reintroduced with BTS SW CX6 CD1.0. The fault has not been seen with MetroSite but the same correction applies to MetroSite BTS SW as well. During the pilot of CX(M)6 MP3.0 the correction for 2993 alarm problem in Non EDGE UltraSites was verified in live customer network. Initial results would seem to indicate that the number of 2993 alarms has been reduced to a negligible level, however this is based on the results received from 2 BSCs over a 2 week period when compared to the number of 2993 alarms prior to the SW CX(M)6 MP3 being piloted. Pilot customer (2993 issue report) have indicated that although initial results look good, confirmation that the 2993 issue has been resolved cannot occur until the SW has been


deployed network wide. Pilot customer have agreed that there is nothing shown in the KPIs or alarm history that would defer or postpone their acceptance of CX(M)6 MP3.0. Solution / Workaround: A TRX reset or a BTS reset (BB hopping or UltraSite BTS Antenna Hopping) clears the situation, but the alarm can be repeated after several days. System Impact: Slight increase in call drop ratio.

2.10.2 Site Synchronization loss

Problem report: NA04527054, NA04508947 Exists in: CX5 UltraSite Correction Target: CX7 MP2.0 & CX6 MP3.0 Description: After a mains power outage or fluctuation in transmission lines the slave cabinet might not recover and follow the master cabinet synchronisation. The DAC value can drift out from the correct value and the slave cabinet can not handle any calls. The problem is rare and random in nature. Solution / Workaround: Restart the slave cabinet BCF. When the same scenario happens with the corrected BTS SW, a new alarm will be activated: 7601 BCF OPERATION DEGREADED RESYNCHRONISATION IN PROGRESS. When the system is recovered the alarm will be cancelled. System Impact: No calls are possible with the slave cabinet until the cabinet BCF is restarted.

2.10.3 Abis loop test gives false reason - Hardware Failure

Problem report: NA04579914 Exists in: CX(M)5 UltraSite and MetroSite Correction Target: CX(M)6 MP3.0 Description: When Abis Loop Test is run from a BSC for a TRX which is carrying traffic the test result may fail and the reason is Hardware Failure. When calls are on the TRX under testing, the tested timeslots before the one carrying a call will fail with reason Hardware Failure. Solution / Workaround: Repeat the testing when there is no calls ongoing or use Cell Barring from BSC. System Impact: The TRX might be sent over HW services even there is no real HW problem with the unit.

2.10.4 Voice quality issues on several BSCs after new BTS SW load

Problem report: NA04538392, NA04571961, NA04577966, NA04595422 Exists in: CX(M)6 CD1.0 UltraSite and MetroSite


Correction Target: CX(M)7 MP1.0 & CX(M)6 MP3.0 Description: Some customers have complained of audio muting problems during Mobile Originating (MOC) Calls using certain mobile models. The call is made and end-user begins talking, when there is a pause in the conversation and speech starts again, end-user will hear a 5 to 10 second muting. Problem can be heard in both ends of the call. Problem is observed after CX(M)6 CD1.0 (CX(M)6 CD2.0 or CX(M)7) activation with UL DTX active and AMR HR only. Solution / Workaround: Disable UL DTX usage or use any BTS SW level prior to CX(M)6 CD1.0. System Impact: End users will experience 5 to 10 second muting periods which will be heard throughout the conversation.

2.11 Problems corrected in CX(M)7 MP1.0

This section lists all the problems, which have been corrected in BTS SW CX(M)7 MP1.0

2.11.1 TRX are going to Blocked TRX after enabling Antenna Hoping

Problem report: NA04491681 Exists in: CX6 UltraSite Correction Target: CX7 MP1.0 Description: Alarm 7606 TRX Faulty BOI detected that connection to TRX is lost was seen in Antenna Hopping sector after a transmission unit restart with alarm 8148 Equipment reset. Solution / Workaround: Restart the site or disable Antenna Hopping. System Impact: Antenna Hopping TRX is out of service if transmission alarm 8148 is reported.

2.11.2 Non-EDGE TSPA 1900 radios possible incompatibility with new sw load

Problem report: NA04543654 Exists in: CX5 UltraSite Correction Target: CX7 MP1.0 Description: When Antenna Hopping is accidentally activated in a sector equipped with EDGE BB2x and a TSPA (Non EDGE Transceiver unit) the alarm 7606 Non EDGE TRX device type used accidentally in EDGE capable mode is not reported and the TRX continues to carry traffic without Antenna Hopping. The TSPA does not support Antenna Hopping feature. Solution / Workaround:


Change all transceiver units to EDGE capable TSPB if Antenna Hopping support is needed. BCF restart is needed or Antenna Hopping need to be reactivated by turning it first off and then back on. System Impact: When the 7606 alarm is not activated, the affected TRX will take traffic but the traffic will not use Antenna Hopping with that TRX. The affected sector is operating at a degraded level as Antenna Hopping is not working properly.

2.11.3 Voice quality issues on several BSCs after new BTS SW load

Problem report: NA04538392, NA04571961, NA04577966, NA04595422 Exists in: CX(M)6 CD1.0 UltraSite and MetroSite Correction Target: CX(M)7 MP1.0 & CX(M)6 MP3.0 Description: Some customers have complained of audio muting problems during Mobile Originating (MOC) Calls using certain mobile models. The call is made and end-user begins talking, when there is a pause in the conversation and speech starts again, end-user will hear a 5 to 10 second muting. Problem can be heard in both ends of the call. Problem is observed after CX6 CD1.0 (CX6 CD2.0 or CX7) activation with UL DTX active and AMR HR only. Solution / Workaround: Disable UL DTX usage or use any BTS SW level prior to CX(M)6 CD1.0. System Impact: End users will experience 5 to 10 second muting periods which will be heard throughout the conversation.

2.11.4 Alarm 7606 TRX faulty BOI detected that connection to TRX is lost reported for working TRX in IDD/4UD configuration.

Problem report: 10551ESPE06 Exists in: CX5 CD4.0 UltraSite Correction Target: CX7 MP1.0 Description: Alarm 7995 MAINS BREAKDOWN WITH BATTERY BACK-UP was generated to activate the BCCH Shutdown Mode. During Intelligent Shutdown, the alarm 7606 TRX faulty BOI detected that connection to TRX is lost was activated for TRX 1. The configuration used was IDD/4UD with RTC. Solution / Workaround: Restart (Lock/Unlock) the TRX or sector to get the TRX working again. System Impact: The TRX is out of service until restarted.

2.11.5 SDCCH drops with baseband hopping

Problem report: NA04428838 Exists in: CX5 UltraSite Correction Target: CX7 MP1.0


Description: High SDCCH drop rate is observed when BB hopping is enabled on some sectors. When BB hopping is turned off no SDCCH drops are observed. The problem is observed only with the following configuration: - BB-hopping enabled - SDCCH channels on TS0 - GP timeslots on the same TRX as SDCCH Alarms 7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD and 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD are observed during the SDCCH drop problem. Solution / Workaround: Three different workarounds: - Turn off BB hopping - Configure SDCCH on TS 1 (No TRX with SDCCH on TS0) - Change GP Timeslot configuration to NON SDCCH TRX and set GTRX=N for SDCCH TRXs System Impact: High SDCCH drop rate.

2.11.6 MOS value is lower in Ater interface

Problem report: NA04511287, NA04539154, 11386ESPE07 Exists in: CX(M)5 UltraSite and MetroSite Correction Target: CX(M)7 MP1.0 Description: In a mobile network, speech frames carried between the BTS and the BSC are encoded / decoded in either a Transcoder or a Media Gateway (MGW). In Adaptive Multi Rate (AMR) full rate (FR) or half rate (HR) channels the codec that offers the best speech quality for the current radio conditions is chosen. It has been observed that when a Media Gateway is used for transcoding, the perceived speech quality on GSM HR channels is degraded (according to the PESQ MOS P.862.1 algorithm). The description had an error which referred to AMR HR codec. However the problem is visible with GSM HR only. Solution / Workaround: Please contact to Media Gateway Technical Support for workaround instructions. System Impact: Lower than expected speech quality in GSM HR channels when the MGW is used.

2.11.7 BCCH Transmission fluctuates

Problem report: 22618ESPE05 Exists in: CX5 UltraSite Correction Target: CX7 MP1.0


Description: When the LapD of a BCCH TRX is blocked (MML) in a BB hopping sector, BCCH is re-configured to another TRX. After the reconfiguration the BCCH TRX timeslot 0 is using constant power, however timeslots 1 to 7 are fluctuating. The problem does not happen if the BCCH reconfiguration is caused by a faulty TRX or LapD link failure. Solution / Workaround: Do not use LAPD link blocking to trigger a BCCH TRX reconfiguration in BB-hopping sector. Restart the sector to clear the problem or Unblock the LapD link. System Impact: The BCCH TRX traffic channels will drop calls until the sector is restarted.

2.11.8 TRX Test fails on some of the time-slots in IDD-Ultra with RF Hopping enabled.

Problem report: 5938C02 Exists in: CX5 UltraSite Correction Target: CX7 MP1.0 Description: When a BTS is configured to use both IDD and RF hopping then sometimes there will be unexpected failures for TRX tests run both from the BSC and from BTS Manager. Due to design limitation it is not possible to successfully test TSL0, TSL1 or TSL2 for TRX other than the BCCH or the FBUS master. From the BSC the failure reason is erroneously given as Hardware Failure and from BTS Manager Unable to measure TRX power. A change will be made to O&M so that a more descriptive reason is given; at the BSC the text will be Test Not Possible and using BTS Manager Requested test cannot be carried out Note: Features that make use of the internal FBUS such as IDD and BB hopping require one of the TRX to act as the designated master. Solution / Workaround: Disable either IDD or RF hopping and repeat the test. System Impact: Diagnostic tests are not fully available when both IDD and RF Hopping are in use.

2.11.9 FBUS Hardware failure

Problem report: 10751ESPE06 Exists in: CX5 CD4.0 UltraSite Correction Target: CX7 MP1.0 Description: A script from BSC was used to test NONE shutdown mode with BB-hopping BTS. The test was generating and cancelling NONE shutdown mode for several hours. A FBUS HW failure alarm was observed on some TRXs after 10-12 hours of testing.


When the NONE shutdown state is cleared a new BTS configuring data is received from a BSC. Occasionally the new configuration fails and 7606 TRX Faulty FBUS HW Failure alarm is activated. Solution / Workaround: Restart the sector with MML Lock/Unlock or with BTS Manager. System Impact: Unnecessary TRX blocking alarm is raised. The TRX is out of service until the BB-hopping BTS is restarted.

2.11.10 TRX Test shows invalid behaviour when IDD is enabled on site

Problem report: 10548ESPE07 Exists in: CX5 UltraSite Correction Target: CX7 MP1.0 Description: During Commissioning of a BTS with IDD, the IDD information is declared in the starting pages of commissioning. When the manual button is selected in the commissioning window for running the TRX test it lists all the TRXs (main + auxillary). The radio button for selecting the Main /Auxiliary TRX is disabled. Although as per the required functionality, only the Main TRXs and the TRXs for which IDD is not defined should be shown in the TRX list. Solution / Workaround: Do not select Aux TRX as a target for TRX testing. System Impact: During commissioning the TRX testing is enabled for Aux TRXs. The test will fail as it should not be enabled for Aux TRXs.

2.11.11 Repeated TAC in AHS calls when A-bis link is disturbed on GSM hardware

Problem report: 3035C01 Exists in: CX(M)5 UltraSite and MetroSite Correction Target: CX(M)7 MP1.0 Description: High number of Time Alignment Commands (15-20) are seen, when the Abis link is disconnected for short durations (between 300-900ms). The issue is seen only with Non EDGE TRX HW. Solution / Workaround: - System Impact: Short A-bis link disturbance causes degradation in Speech quality/UL MOS for AMR HR calls.

2.11.12 BTS not passing transmission alarms

Problem report: NA04439425


Exists in: CX(M)5 UltraSite and MetroSite Correction Target: CX(M)7 MP1.0 Description: Supervisory Substations (SSS) are used to collect external alarms from Radio Access sites. Originally these were being supervised (ie BTS polling) by Talk family base stations via their Q1 connections. When one of these Talk sites was replaced by an UltraSite/MetroSite the alarms were no longer transferred to the BSC. A remote session confirmed that external alarms were active at the SSS, but these could not be seen locally at the BTS using BTS Manager, or at the BSC. Solution / Workaround: Use BSC polling to supervise the SSS. BSC polling requires spare transmission capacity to carry the service channel from the BSC to the SSS. System Impact: No external equipment alarms are visible to the BSC or locally at the BTS when Supervisory Substation is polled by a BTS via Q1.

2.11.13 BTS sends STATE CHANGE message for the faulty TRX.

Problem report: 10470ESPE07 Exists in: CX5 UltraSite Correction Target: CX7 MP1.0 Description: A BB-hopping 4TRX BTS is configured with mixed configuration (BB2F with 2 TSxB & BB2A with 2 TSxA) when ST-IRC is enabled. Alarms for the non-EDGE capable TRXs is activated Non EDGE TRX device type used accidentally in Edge Capable Mode. BSC sends new BTS configuration data when the faulty TRXs are removed from the BB-hopping group. After reconfiguration the BTS sends State Changed message to the BSC including the faulty TRXs which are not now in the hopping configuration anymore. The STATE CHANGE message should not be sent for the faulty TRX for which an alarm is active. Solution / Workaround: Lock/Unlock the faulty BB-hopping sector. System Impact: Incorrect status for some of faulty TRXs at the BSC. However, the occurrence is rare.

2.11.14 Incorrect RX DIV cabling defined in the configuration wizard

Problem report: 5139C01 Exists in: BTS Manager/HW Configurator CX5 Correction Target: BTS Manager/HW Configurator CX7 MP1.0 Description: When a 6+6 (4:1) sector configuration is selected from the Configurator Wizard in the HW Configurator application the RX Div cabling defined for both the sectors are from the same antenna as Main RX path cabling. The RX path from second antenna is never used.


Solution / Workaround: The RX antenna settings need to be changed manually from HW Configurator. System Impact: When the RX cabling is incorrectly set the antenna monitoring with RSSI might not work correctly.

2.11.15 Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled

Problem report: NA04202512 Exists in: CXM5.0 UltraSite and MetroSite Correction Target: CXM7 MP1.0 Description: After the MetroSite BTS SW is upgrade from CXM4.1 CD4.0 to CXM5 CD4.0, TRX test from BSC for GMSK always fails if STIRC is enabled. The same TRX test works with CXM4.1 CD4.0. The TRX test functions correctly with CXM5 CD4.0 if the STIRC feature is not used. The test functions correctly with CXM4.1 CD4.0 both with and without the STIRC feature active. Solution / Workaround: If a TRX test is required and STIRC is active, disable STIRC and perform the test. STIRC may be re-enabled after the TRX test has been performed. System Impact: After BTS SW upgrade no TRX test is possible when the STIRC feature is active.

2.11.16 Cannot make a call with second MetroSite BTS in chain after BTS SW upgrade

Problem report: NA04543929 Exists in: CXM6 CD2.0 MetroSite Correction Target: CXM7 MP1.0 Description: Two chained MetroSite EDGE BTSs are upgraded from CXM4.1 CD4.0 to CXM6 CD2.0. Sometimes the second BTS in chain will stop to transmit BCCH. Ongoing calls remain connected, however, no new calls can be originated. Only BTS alarm 7725 Traffic Channel Activation Failure is raised. Solution / Workaround: Either a BTS Lock/Unlock from BSC or a restart from BTS Manager can clear the problem. System Impact: New calls are failing until the BTS is restarted.

2.11.17 Calls are possible on a GSM TRX, which is locally blocked, after STIRC enable/ disable.

Problem report: 10161ESPE06 Exists in: CXM6 MetroSite Correction Target: CXM7 MP1.0


Description: STIRC is enabled for the 1st sector in a Non hopping 2+2 GSM MetroSite BTS configuration. Alarm "7606 TRX FAULTY: Non EDGE TRX device type used accidentally in Edge Capable Mode" is reported for TRX 1. TRX 1 goes into BL-TRX at BSC. Alarm "7603 BTS FAULTY: Non EDGE TRX device type used accidentally in Edge Capable Mode" is reported after some time. 1st sector and BCCH TRX are in BL-BTS state at BSC. BCCH transmission is stopped. When the non BCCH TRX (TRX1) is blocked from BTS manager the BCCH transmission starts for around 20 seconds and then stops - this is the expected behaviour. When STIRC is disabled from the 1st sector TRX 1 remains in local block state and TRX 2 comes up in working state. Alarms related to STIRC are cancelled. However the locally blocked TRX 1 is in WO state at the BSC and calls are then allocated to that TRX. Solution / Workaround: Instead of local block please use Lock command (ZERS) from BSC (MML). System Impact: The TRX under local maintenance is able to handle traffic as it is accidentally in the WO state at the BSC.

2.12 Problems corrected in CX(M)7

2.12.1 7607 VSWR monitoring alarm following AHOP activation

Problem report: NA04445483 Exists in: CX5.0 UltraSite Correction Target: CX7 Description: When the Antenna Hopping feature is activated to BTS sites and these sites also have VSWR monitoring activated in the HW Configurator then there will be spurious 7607 Fault in VSWR antenna monitoring alarms generated. For successful VSWR monitoring the BCCH has to be continuously transmitting into the antenna being monitored. In the case of AHOP then the BCCH is hopping and therefore the monitoring is not possible. The two features are mutually incompatible. From the release of CX7 the VSWR monitoring alarms are automatically ignored when Antenna Hopping is enabled thus disabling monitoring from HW Configurator manually is not needed. Solution / Workaround: Disable VSWR monitoring on the AHOP sectors from HW Configurator. System Impact: TRX will be blocked and service unavailable. In addition a sector reset will be caused as individual manipulation of TRXs is not possible within an Antenna Hopping sector.


2.12.2 Unable to perform Manual MMI Commissioning of Ultra BTS

Problem report: NA04447952 Exists in: BTS Manager CX5 Correction Target: BTS Manager CX7 Description: During BTS commissioning, with no Abis connection, the TRX tests are not run automatically. There is a button to Manually run these tests. Although the UltraSite is in Configuring, or if sufficient time has elapsed, Supervisory state, pressing this button raises a warning box No TRX in Configuring or Supervisory state and will not allow test execution. Allowing commissioning to finish allows the TRX test to be run successfully from the Test menu, although the UltraSite will normally appear to be in the same state as itt was prior to completion of commissioning. Solution / Workaround: Ignore manual test and finish commissioning. TRX test can then be run, but results will not be in commissioning report. System Impact: Commissioning report does not include TRX testing results and the testing has to be started manually from BTS Manager after commissioning.

2.12.3 Average RACH busy count is low in CCCH Load Indicationl

Problem report: 4357C02 Exists in: CX(M)5 UltraSite and MetroSite Correction Target: CX(M)7 Description: The Busy RACH counter in CCCH Load Indication message from BCCH TRX to the BSC does not show correct values, with the counter values being less than expected. The problem is observed when adding interference on UL direction for BCCH channel with Combined channel configuration. Solution / Workaround: - System Impact: The reported Busy RACH counter value is less than the actual value.

2.12.4 Transmission unit alarms are not cleared at BSC and NetAct

Problem report: NA04177553, NA04178176 Exists in: CX(M)4.1 UltraSite and MetroSite Correction Target: CX(M)7 Description: Several transmission alarms including 8059, 8060, 8066, 8064 are not cleared at NetAct or BSC even the alarm is already cancelled at the equipment. This causes increased work and efforts in the maintenance of these ghost alarms as they have to be removed manually from NetAct or BSC. The transmission unit has to be checked remotely that there are no problems or alarms.


Nokia Siemens Networks has identified one possible scenario which is leading to a situation where the alarm is not cancelled properly. There are several theoretical methods by which ghost alarms may be generated and it is not possible for this correction to resolve all of these. Therefore some alarms may still be seen in the network which should have been cancelled automatically. Solution / Workaround: - System Impact: Alarms have to be cancelled manually after checking that transmission units are OK.

2.12.5 Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled

Problem report: NA04202512 Exists in: CX5.0 UltraSite Correction Target: CX7 Description: After the BTS SW is upgrade from CX4.1 CD4.0 to CX5 CD4.0, TRX test from BSC for GMSK always fails if STIRC is enabled. The same TRX test works with CX4.1 CD4.0. The TRX test functions correctly with CX5 CD4.0 if the STIRC feature is not used. The test functions correctly with CX4.1 CD4.0 both with and without the STIRC feature active. Solution / Workaround: If a TRX test is required and STIRC is active, disable STIRC and perform the test. STIRC may be re-enabled after the TRX test has been performed. System Impact: After BTS SW upgrade no TRX test is possible when the STIRC feature is active.


Disclaimer

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks. All rights reserved.

1. OPEN PROBLEMS1.1 Open problems waiting for correction target1.2 Open problems targeted for CX(M)91.2.1 (NEW) HW Inventory upload to Netact shows incorrect PSU type

1.3 Open problems targeted for CX8.1 PP1.41.3.1 (NEW) Alarm 7606 TRX Faulty Interface problems between O&M and DSP SW Alarm is unexpectedly started

1.4 Problems targeted for CX8.1 PP1.31.4.1 CSSR and SDCCH Abis fail1.4.2 Cell reselection failure on E_BCCH BTS from 2G to TD

2. CORRECTED PROBLEMS2.1 Open problems corrected in CX8.1 PP1.22.1.1 Alarm 7606 TRX FAULTY Interface problems between O&M and DSP SW unexpectedly raised.

2.2 Open problems corrected in CX(M)8.1 PP1.12.2.1 Traffic Channel Activation Alarm 7725 generated on some GP timeslots

2.3 Problems corrected in CX(M)8.1 MP1.02.3.1 Traffic Channel Activation Alarm 7725 generated on some GP timeslots

2.4 Problems corrected CX(M)8 MP1.0 and CX(M)8.12.4.1 MetroSite Traffic Manager does not always show ABIS EDAP Configuration after MetroSite BTS Commissioning

2.5 Problems corrected in CX(M)8 2.5.1 Unexpected 7606 TRX Faulty alarms raised in Antenna Hopping Sector 2.5.2 A lock / unlock of BCCH TRX causes incorrect log writing in BCSU 2.5.3 Antenna Hopping Sector gets stuck in configuring when Alarm 7995 is cancelled

2.6 Problems corrected in CX(M)7 MP4.0 and CX(M)82.6.1 One BTS of common BCCH segment goes into faulty state with all its TRXs when common BCCH is configured with RF & Antenna hopping.2.6.2 Alarm 7606 TRX FAULTY "Antenna Connection Faulty" appears randomly2.6.3 Alarm 7606 TRX FAULTY "No data is received from DIBA Asic traffic channel

2.7 Problems Corrected in CX(M)7 PP3.22.7.1 Since enabling Extended CCCH there is increase in TCH RF losses2.7.2 Increase in SDCCH failures following Extended CCCH activation2.7.3 Increase in TBF failures following Extended BCCH activation2.7.4 Alarm 7606 TRX FAULTY "No data is received from DIBA Asic traffic channel

2.8 Problems corrected in CX7 MP3.02.8.1 Site does not work after Lock/Unlock in IDD 4UD with ECCCH and BB hopping 2.8.2 Cannot make Mobile Terminated call under two cells with Extended CCCH2.8.3 Reconfiguration of BCCH doesn't take place in an Antenna Hopping sector when an alarm is already present in the sector.

2.9 Problems corrected in CX7 MP2.02.9.1 Site Synchronization loss2.9.2 Abis loop test gives false reason - Hardware Failure2.9.3 SW UltraSite CX5 CD 4.0 and Satellite Abis2.9.4 UltraSites Generating 2993 Alarms and increased dropped calls.2.9.5 High interference levels in case of PWSB failure

2.10 Problems corrected in CX(M)6 MP3.02.10.1 UltraSites Generating 2993 Alarms and increased dropped calls.2.10.2 Site Synchronization loss2.10.3 Abis loop test gives false reason - Hardware Failure2.10.4 Voice quality issues on several BSCs after new BTS SW load

2.11 Problems corrected in CX(M)7 MP1.02.11.1 TRX are going to Blocked TRX after enabling Antenna Hoping2.11.2 Non-EDGE TSPA 1900 radios possible incompatibility with new sw load2.11.3 Voice quality issues on several BSCs after new BTS SW load2.11.4 Alarm 7606 TRX faulty BOI detected that connection to TRX is lost reported for working TRX in IDD/4UD configuration.2.11.5 SDCCH drops with baseband hopping2.11.6 MOS value is lower in Ater interface2.11.7 BCCH Transmission fluctuates2.11.8 TRX Test fails on some of the time-slots in IDD-Ultra with RF Hopping enabled.2.11.9 FBUS Hardware failure2.11.10 TRX Test shows invalid behaviour when IDD is enabled on site2.11.11 Repeated TAC in AHS calls when A-bis link is disturbed on GSM hardware2.11.12 BTS not passing transmission alarms2.11.13 BTS sends STATE CHANGE message for the faulty TRX.2.11.14 Incorrect RX DIV cabling defined in the configuration wizard2.11.15 Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled2.11.16 Cannot make a call with second MetroSite BTS in chain after BTS SW upgrade2.11.17 Calls are possible on a GSM TRX, which is locally blocked, after STIRC enable/ disable.

2.12 Problems corrected in CX(M)72.12.1 7607 VSWR monitoring alarm following AHOP activation 2.12.2 Unable to perform Manual MMI Commissioning of Ultra BTS2.12.3 Average RACH busy count is low in CCCH Load Indicationl2.12.4 Transmission unit alarms are not cleared at BSC and NetAct2.12.5 Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled

lgf_2gbtsum_2012_36

Documents