Вы находитесь на странице: 1из 2

Call Blocked/issue

- Location update rejected:

Need check CGI definition for 2G and SAC definition 3G at core side after definition at SRC side are
correct according to RF data.

(2G) Below example table data required for CGI definition for Core side:

Site RNC ID or Neighbor Neighbor


NAME 2G BSC SPC BSC name LAC SAC/CELL LAC SAC/CELL MSC

4596 2G 4479 SRC215 22321 45961 22321 40781 HO11,HO12,HO13,HO14

4596 2G 4479 SRC215 22321 45962 22321 40781 HO11,HO12,HO13,HO14

4596 2G 4479 SRC215 22321 45963 22321 40781 HO11,HO12,HO13,HO14

(3G) Below example table data required for SAC definition for Core side:

Neighbor Neighbor
Site NAME 3G RNC ID RNC LAC SAC/CELL LAC SAC/CELL MSC

DXB1131 3G 411 RNC411 41100 11312 41100 29264 HO11/12/13/14

DXB1131 3G 411 RNC411 41100 11313 41100 29264 HO11/12/13/14

DXB1131 3G 411 RNC411 41100 11311 41100 29264 HO11/12/13/14

DXB1131 3G 411 RNC411 41100 11314 41100 29264 HO11/12/13/14

For 3G also need to check Primary Scrambling Code (PSC) according to RF data.
- Silent Call

Silent call happened if the destination of SCTPLNK IP from Node side doesnt match with IPPOOL index
on SRC. Below are the steps how to check:

SRC side:

1. LST ADJNODE (Etisalat : Adj Node ID for 2G is site ID + 1000, for 3G is site ID + 9000)
Check item Transmission Resource Pool Index.
2. LST IPPOOLIP ( Check the IP with corresponding Transmission Resource Pool Index)
3. LST SCTPLNK (Local IP should be the same IP from Transmission Resource Pool Index )
4. MOD SCTPLNK

BTS side:

1. LST SCTPLNK
2. MOD SCTPLNK
3. MOD IPRT

Below the capture from above definition:

Вам также может понравиться