CELLULAR NETWORK CONFIGURATION ERROR 2745 (0486) 03 C3 000030A9 404 05 007D 645D 04 Supplementary info: Field 1: Unknown Cell

Identity (CI)-03 Field 8: Location area -7D, 1 FFFFH, FFFFH, if unknown-007D Field 3 : Signaling point-30A9 1 - 3FFFH (when SPC 14 bits) or 1 - FFFFFF (when SPC 24 bits) FFFFFFFFH, if unknown Field 7: CI - cell identifier- 645D Action: Confirm the bts is not defined in the MSS/MSC using ZEPO: LAC=lac id, CI=cell id; Confirm the bts is present in BSC using ZEQO: LAC=lac id, CI=cell id; and calls not happening in BTS except minor calls due to handover. 2745 CELLULAR NETWORK CONFIGURATION ERROR SWITCH

Note: BSC number of the cell id can be found from SPC given in field 3 using ZNVI: NA1,SPC No Define the BTS in MSC/MSS for the LAC/CI id using ZEPC: NO=Cell id, NAME=Cell name: LAC=lac id, CI=cell id:: CLN=cln no, TON=INT;

Note: Name of the cell id can be obtained from bts name in BSC end.CLN if not available for definition, can be obtained by taking a reference working site from same BSC and get the parameters from MSC using ZEPO: LAC=LAC of reference site, I=CI of reference site; Update the BSC number in the BTS definition using ZEPB: NO=number used in ZEPC: BSCNO=bscno;

Update the Routing zone using ZEPR: NO= number used in ZEPC: RZ=routing zone no; Note: Routing zone number if not available can be obtained from Reference site similar to CLN. Unlock the BTS in MSC using ZEPS: NO=number used in ZEPC: U;

Note: The Alarm will be stopped automatically after BTS is defined and check the call progress in BSC. Case 2: Adjacencies not updated with correct LAC. Description: LAC is not updated properly in some of the adjacencies in the network of the alarm generating CIs. ** ALARM CMU-1 1A001-10 CRH_SJ (1179) 2745 CELLULAR NETWORK CONFIGURATION ERROR 04 FF FFFFFFFF 0000 0000 00A6 B3FE 09 Supplementary info: Field 1: Unknown Location Area code (LAC) - 04 Field 6: Location area 1 FFFFH, FFFFH, if unknown- A6 Field 7: CI - cell identifier- B3FE Description: LAC is not updated properly in some of the adjacencies in the network of the alarm generating CIs. Action: Find the current LAC of the BTS from nd111 report. Find the BTS s in the network where target LAC is not correctly updated from the adjacencies logs. Delete the adjacencies with invalid LAC using ZEAD: BTS=source bts id:: LAC=current invalid lac, CI= target BTS cell id; Recreate the deleted adjacency with new LAC using ZEAC: BTS=Source BTS id=:: LAC=new current target LAC, CI=target cell id:NCC=of target CI,BCC=of target CI,FREQ=of target bts; The process need to be repeated for all BTSs in the network with invalid adjacencies due to invalid LAC.

Note: The Alarm will be stopped automatically after Correct LAC is defined for adjacencies. Cause 3: External LAC ids not defined mutually for inter msc handovers. Description: External LAC needs to be defined in source and target MSCs mutually. <HIST> MSS01 2009-04-24 09:36:05.76 ** ALARM CMU-1 CMU-1 1A001-10 CRH_SJ SWITCH

(1179) 2745 CELLULAR NETWORK CONFIGURATION ERROR 04 FF FFFFFFFF 0000 0000 006A 1A5F 09 Supplementary info: Field 1: Unknown Location Area code (LAC) 04 Field 6: Location area 1 - FFFFH FFFFH, if unknown-6A Field 7: CI - cell identifier 1A5F

Action: Find the BTS s having invalid adjacencies in the network with target LAC and CI given in alarm, even for correct LAC as target one. Confirm the Source BTS and target BTS in different MSCs using ZEDO: NO=bscno; Check the Source BTS LAC and target BTS LAC are defined as external LACs mutually in their MSCs using ZEIO:other MSC s LAC;. If external LAC not defined, create using ZEIA:LAC of other MSC, MISDN=of other MSC;

Note: MSISDN can be found from MSC Number of ZMVI; command in other MSC.