Method of Procedure

Nb over TDM Integration

MGW – MGW

SUMATERA AREA

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
1 GENERAL.................................................................................................................................... 3

2 HW AND SOFTWARE REQUIREMENT FOR Nb INTEGRATION............................................... 3

3 TOOLS......................................................................................................................................... 4

4 CREATING TDM INTERFACE WITH TDM BACKBONE............................................................. 4

5 CREATING ROUTING OBJECTS IN MGW FOR TDM RESOURCES CONTROLLED BY

MSC SERVER............................................................................................................................. 6

6 CONFIGURING USER PLANE ROUTING AND TOPOLOGY IN MSS MEDAN .......................... 9

7 TESTING CALL SCENARIO FOR PHASE 1 ............................................................................. 11

8 TESTING CALL SCENARIO FOR PHASE 2 – MIGRATION FOR NB OVER TDM................... 14

9 REFERENCE ............................................................................................................................. 19

10 SYSTEM SECURITY ................................................................................................................ 20

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
1. GENERAL

The aim of this testing is to verify Nb over TDM between 2 IPA2800 MGW’s. According to Indosat
requirements, Medan and Batam will be used for testing Nb over TDM.

This document specifies the sets of procedures prepared by Nokia Siemens Networks to verify Nb
interface over TDM functionality.

The test call will be conducted in two steps. The first step is conducted to test the functionality of Nb
interface. It will be tested by using selected subscriber in the coverage of MGW Medan and MGW
Batam. MO call test will be conducted between MGW Medan to MGW Batam and vice versa (A Number
in coverage MGW Medan and B number in coverage MGW Batam). MO call test is also conducted in
the coverage of MGW Medan and MGW Batam itself (A Number and B number in same coverage). The
MO call tested will be voice call and video call.

After first step is conducted successfully, then we will migrate the roaming number analysis in coverage
MGW Medan and MGW Batam to new destination with Nb over TDM interface. Then the Nb interface
will carry the load traffic for voice call and video call.

2. HW AND SOFTWARE REQUIREMENT FOR NB INTEGRATION

There are some HW and SW pre-requisite requirement must be completed before we can carry load
traffic with Nb interface. For hardware, it is necessary to have TDM Interface in MGW Medan and MGW
Batam (they can be NIWU, or IWS1E) as well as physical E1 interface connected between MGW Medan
and MGW Batam.

Both Indosat planning and NSN Planning team must calculate the numbers of physical E1 required for
carrying load traffic with Nb over TDM interface between MGW Medan and MGW Batam.

For SW requirement, it is required to have PDC 4558(FN 1566) installed in MSS/MSCi. This feature
enable optimization of TDM resource usage in interconnections. This PDC already installed at M13.1 as
General Base SW Feature.

MSS/MSCi in Indosat now is running with M13.5 MD6PA004 (CD4 Delivery) with sw env MD 8.7-0.

MGW Medan and MGW Batam now is running with U3B CD3 delivery (U331T103) with sw env U3 7.3-0.

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
3. TOOLS

The following tools are required during Nb Trial activity :

x Nethawk Analyzer

x Reflections or HIT Terminal

x Three or more GSM Mobille Phones (with video call capabilities)

x One PSTN Number

x SIM Card which consist of Matrix SIM Card, Mentari SIM Card, Smart SIM Card, Bright SIM
Card,

4. CREATING TDM INTERFACE WITH TDM BACKBONE

The figure below illustrates the possible TDM backbone solution. Assumption : NIWU here is used.

The steps in MGW is defined below :

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
4.1 Interrogate the ET’s current configuration with (ZYAI command)

ZYAI:ET;

4.2 Set the interface Operation Mode (ZYAE command)

Set the operation mode if you want to change it from E1 to T1/JT1 or from T1/JT1 to E1. The impedance
parameter can be given only if the operation mode given is E1.

ZYAE:<unit type>,<network interface unit index>, <interface operation mode>:[<impedance>];

Note : Parameter impedance is not valid for IWS1E and IWS1T.

If you change the impedance or the operation mode, you must restart the unit so that the changes are
taken into use.

4.3 Modify E1 functional modes if needed (ZYEC)

You can first output the ETSI-specific frame modes with the command

ZYEI;

If the current frame mode does not match with the frame mode of the interface unit that is connected to
the remote end of this line, you can modify it with the command

ZYEC:<unit type>,<unit index>:NORM,(DBLF|CRC4);

Example : Configuring PDH for TDM (ETSI/E1) in MGW Medan

1 Interrogate the current configuration.

ZYAI:ET;

2. Set the interface operation mode of NIWU with index number 16 to E1 and with impedance 120 ohm.

ZYAE:NIWU,16,E1:120:

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
3. Restart the Unit

ZUSU:NIWU,16;

4. Output the ETSI-specific functional modes.

ZYEI;

5. Modify E1 functional modes of the ET with index 264.

ZYEC:ET,264:NORM,CRC4;

Example : Configuring PDH for TDM (ETSI/E1) in MGW Batam

6. Interrogate the current configuration.

ZYAI:ET;

7. Set the interface operation mode of NIWU with index number 16 to E1 and with impedance 120 ohm.

ZYAE:NIWU,11,E1:120:

8. Restart the Unit

ZUSU:NIWU,11;

9. Output the ETSI-specific functional modes.

ZYEI;

10. Modify E1 functional modes of the ET with index 264.

ZYEC:ET,180:NORM,CRC4;

5. CREATING ROUTING OBJECTS IN MGW FOR TDM RESOURCES CONTROLLED BY MSC

SERVER

5.1 Create Special Circuit Group (SPE CGR) with the USE parameter

ZRCC:[TYPE = SPE | NCGR = <circuit group name>| CGR =<circuit group

number>]:[USE=<use of spe cgr>];

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
Notes : To use TDM resources, they must be attached to a VMGW. Use the JVC command to create a
new VMGW. Once the VMGW has been created, you can use the JVE command add a CGR to it.
If you add or remove the CGR with the JVE or JVF command and the VMGW has either registration
allowed on or registration status on, all circuits of the added or removed CGR must be in BA-US state
before the action is started. After adding the CGR with the JVE command, you can change the circuits’
state to WO-EX. You can also use the JVC and JVE commands at a later stage in the configuration if,
for example, other configurations need to be made prior to creating a VMGW and adding a CGR to it.

5.2 Set the interface type (RCM)

ZRCM:(NCGR=circuit group name | CGR=<circuit group

number>):INTER=<interface
type>;

Other Circuit Group Features can also be modified with ZRCM command, for example ECHO and DSP
Pool

ZRCM:CGR=<circuit group number>:ECHO=<Y/N>;

ZRCM:CGR=<circuit group number>: POOLNAME=<poolname>;

5.3 Change the state of the circuit group to WO-EX (CIM)

ZCIM:(NCGR=<circuit group name>...|CGR=<circuit group number>...):(WO|BA);

5.4 Change the state of the circuits to WO-EX (CIM)

ZCIM:CRCT=<circuit(s)>...:(WO|BA);

Example : Create Special Circuit Group with the VMGW Parameter in MGW Medan

1. Create a special circuit group (CGR) with the VMGW parameter.

ZRCC:TYPE=SPE,NCGR=NBWBTM1,CGR=400:USE=VMGW;

2. Attach the CGR to the Virtual Media Gateway

ZJVE:VMN= WNMD1V01:CGR=400::;

3. Set the interface type to Nb(TDM)-interface for TDM backbone

connection:

ZRCM:NCGR=NBWBTM1:INTER=O;

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
4. Modify CGR Pool

ZRCM:NCGR=NBWBTM1:POOLNAME= DEFVALUES;

5. Add TDM Circuits to CGR

ZRCA:NCGR=NBWBTM1:CRCT=264-1&&-31;

6. Change the CGR to WO-EX

ZCIM:CGR=400:WO;

7. Change the state of the circuits to WO-EX

ZCIM:CRCT=264-1&&-31:WO;

Example : Create Special Circuit Group with the VMGW Parameter in MGW Batam

1. Create a special circuit group (CGR) with the VMGW parameter.

ZRCC:TYPE=SPE,NCGR=NBWMDN1,CGR=500:USE=VMGW;

2. Attach the CGR to the Virtual Media Gateway

ZJVE:VMN= WNBT1V01:CGR=500::;

3. Set the interface type to Nb(TDM)-interface for TDM backbone

connection:

ZRCM:NCGR= NBWMDN1:INTER=O;

4. Modify CGR Pool

ZRCM:NCGR= NBWMDN1:POOLNAME= DEFVALUES;

5. Add TDM Circuits to CGR

ZRCA:NCGR= NBWMDN1:CRCT=179-1&&-31;

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
6. Change the CGR to WO-EX

ZCIM:CGR=500:WO;

7. Change the state of the circuits to WO-EX

ZCIM:CRCT=179-1&&-31:WO;

6. CONFIGURING USER PLANE ROUTING AND TOPOLOGY IN MSS MEDAN

When TDM backbone is used by between MGW’s that are controlled by single MSC Server, the new
type of Circuit Group called TDMC has to be created and this Circuit Group is dedicated to resources
between two MGW’s. TDMC cannot be used for Interconnection circuits toward MSC Server or to other
MGW’s which is controlled by other MSCi. At least two circuit groups have to be created for one
interconnection between MGWs. When the circuit group configuration is ready, external routes need to
be created into the MSC Server. These external routes needs to be attached into Topology Database
(MGW Interconnection). Finally the ICBNC phase of the User plane analysis has to be configured in
order to use BNC=TDM properly.

MGW selection can be optimised using the TDM borrowing functionality that is set with the
IC_CONF_OPT_IN_PHYS_MGW (053:0013) PRFILE parameter.

6.1 Create Circuit Group which leads to MGW

ZRCC:TYPE=TDMC,NCGR=<name of Circuit Group>,CGR=<Circuit Group

ID>::MGW=<name of MGW>,DMGW=<name of Destination MGW>;

Example :

ZRCC:TYPE=TDMC,NCGR=NBMDNBTM,CGR=400::MGW=WNMD1V01,DMGW=WNBT1
V01;

ZRCC:TYPE=TDMC,NCGR=NBBTMMDN,CGR=500::MGW=WNBT1V01,DMGW=WNMD1
V01;

6.2 Change the state of the circuit Group to WO

ZCRM:NCGR=<Circuit Group Name>:<state/WO>;

Example :

ZCRM:NCGR=NBMDNBTM:WO;

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
 ZCRM:NCGR=NBBTMMDN:WO;

6.3 Add Termination ID to TDMC circuit Groups

ZRCA:NCGR=<circuit group name>:TERMID=<circuit(s)>:DPCM=<number of PCM at the

destination MGW>;

Example :

ZRCA:NCGR=NBMDNBTM:TERMID=264-1&&-31:DPCM=180;

ZRCA:NCGR=NBBTMMDN:TERMID=180-1&&-31:DPCM=264;

6.4 Changing Working State of the Termination ID

ZCEC:TERMID=<circuit>:<state>;

Example :

ZCEC:TERMID=264-1&&-31:BA;

ZCEC:TERMID=180-1&&-31:BA;

ZCEC:TERMID=264-1&&-31:WO;

ZCEC:TERMID=180-1&&-31:WO;

6.5 Connecting TDMC Circuits to Route

6.5.1 Check the MGW_IDs values for both MGW. Use ZJGI command to check which MGW has the
lower mgw_id value in the database

6.5.2 Create the external route

ZRRC:EXT:ROU=<external route number>,NCGR=<circuit group>,OUTR=<outgoing

register signalling>,STP=<starting point of outgoing dialling>;

Example :

ZRRC:EXT:ROU=400,OUTR=OMCG0,NCCP=MAS,STP=1,NCGR=NBMDNBTM;

ZRRC:EXT:ROU=500,OUTR=OMCG0,NCCP=MAS,STP=1,NCGR=NBBTMMDN;

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
Notes : To avoid dual seizures, TDM resources between MGWs should always be reserved from the
same side and from the MGW that has the lower mgw_ID value in the MGW Data base. Only the CGR
with the lower mgw_id in the MGW ID Parameter should be attached to the route. This route will be
configured in Topology Database.

With the help of PDC 4558, it is not necessary to create CGR in every VMGWs. Only one CGR created
in each MGW towards other MGW with certain amounts of E1’s. Each CGR should be attached into first
VMGW in each physical MGW.

6.6 Create User Plane Analysis for TDM in MSS Medan and MGW Interconnection VMGW Medan
and VMGW Batam

6.6.1 First Create the User Plane Result for TDM Backbone in ICBNC

ZJUR:ICBNCSTO,ICBNC,STOP:;

ZJUR:ICBNCTDM,ICBNC,CONT:ICBNC=TDM;

6.6.2 Create user plane sub analysis for PSIGT in ICBNC Phase :

ZJUC:ICBNC1,START,ICBNC:PSIGT=MAS:RES=ICBNCTDM,DEFRES=ICBNCSTO:UNK
RES=ICBNCSTO:;

ZJUM:ICBNC1,ADD:VALUE=TRUNK,RES=ICBNCTDM;

6.6.3 Create MGW Interconnection between all VMGWs of MGW Medan to VMGWs of MGW Batam
using the router number created in step 6.5.2. The selection of route 1 or route 2 in JFT depend upon
which MGW has lower ID. Always use the route from lower MGW ID to higher MGW ID.

ZJFT:NMGW=<name of VMGW>:NMGW=<name of
VMGW>:BNCC=TDM:ROUTES=<route number>:ADD=Y;

Example :

ZJFT:NMGW=VNMD1V01:NMGW=WNBT1V01:BNCC=TDM:ROUTES=400:ADD=Y;

7. TESTING CALL SCENARIO FOR PHASE 1.

The objective target for this step will be focused on functionality testing of Nb over TDM interface. Since
we are using live MSS – MGW, we need to separate normal routing and Nb over TDM routing. For this

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
purpose, we will use selected subscribers number (which could be MSISDN test number) which are
roaming under coverage MGW Medan and MGW Batam. We will test voice call and video call for Mobile
to Mobile call between A subscriber in Medan and B subs in MGW Batam and vice versa. A-subs
number will be defined first and will be marked as different Original Dialing Class (ODC) during extended
pre-analysis stage. This ODC Flag will be analyzed later on during routing attribute analysis stage. If
routing criteria is match, then the call will go to digit analysis TREE 4 for MOC Tree Analysis and the
MSRN result will be sent to new TREE 51. If the routing criteria is not match, then the call will go to
default tree analysis TREE 2 and the MSRN result will be sent to TREE 50.

Within TREE 51, MSRN will be analyzed based on LBCU ID as identifier of originate MO calls. If the
LBCU ID is match with LBCU MGW Medan or MGW Batam the GSMEND procedure will be triggered to
start user plane analysis and paging for B subs.

Only selected subscriber will be routed to Nb over TDM interface. The rest of the calls will still go to
Gateway MSC in each corresponding area.

7.1 Create Extended Preanalysis Result in MSS Medan

ZCWR:ODC1,CONT:ODC=1,;
ZCWR:DUMMY;

7.2 Create Extended Preanalysis Subanalysis in MSS

ZCWC:CLIA,START,1:DIG=62816300115,NBR=CLI,TON=INT:RES=ODC1,DEFRES=DU
MMY:UNKRES=DUMMY:;

7.3 Add all MSISDN test numbers

ZCWM:CLIA,ADD:RES=ODC1,TON=INT,DIG=628556545526;

7.4 Change the state of Sub analysis from Test Side to Normal Side.

ZCWN:MTN,CLIA:;

7.5 Create EOS Attribut Final Result and Routing Attribut Final Result in MSS

ZRQK:TREE51,CMANAL:CORG=0,TREE=51,:;
ZRQK:TREE50,CMANAL:CORG=0,TREE=50,:;

ZRQL:TREE4:TREE=4,:;
ZRQL:DUMMY:;

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
7.6 Create EOS Attribut Subanalysis in MSS

ZRQC:EOS,NBTDM,START:ODC=1:RES=TREE51,DEFRES=TREE50:
UNKRES=TREE50:;

7.7 Create Routing Attribut Subanalysis in MSS

ZRQC:ROU,NBTDM1,START:ODC=1:RES=TREE4,DEFRES=DUMMY:
UNKRES=DUMMY::;

7.8 Change Subanalysis state from Test to Normal

ZRQN:EOS,TN,NBTDM:;

ZRQN:ROU,TN,NBTDM1:;

7.9 Create New NSDEST which lead to GSMEND

ZRPR:SPR=909,STP=1,NI=NA0,:

7.10 Create New NSDEST

ZRDE:NSDEST=NBHLRENQ:SPR=909,CT=SC,SP=0,:

7.11 Create New NDEST

ZRDE:NDEST= NBHLRENQ:NSDEST= NBHLRENQ:NCHA=FREECALL;

7.12 Create Digit Analysis in TREE 4

ZRDC:TREE=4,TON=NAT,DIG=81630:NDEST= NBHLRENQ:;

ZRDC:TREE=4,TON=NAT,DIG=85565:NDEST= NBHLRENQ:;

7.13 Create New Destination which will be used in TREE 51 Digit Analysis

ZRNC:SPR=1999:SAD=1,DIG=62,TON=INT,:TREE=SAME:;

ZRDE:NSDEST=AKHIR:SPR=1999,CT=SC,SP=0:;

7.14 Create NDEST for TREE 51

ZRDE:NDEST=AKHIR:NSDEST=AKHIR:NCHA=FREECALL:;

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
7.15 Create New Digit Analysis for MSRN MGW Medan and MSRN MGW Batam

ZRDC:TREE=51,TON=NAT,DIG= 81606110&&-9:NDEST=AKHIR;

ZRDC:TREE=51,TON=NAT,DIG= 81607715&&-9:NDEST=AKHIR;

ZRDC:TREE=51,TON=INT,DIG=6281606110&&-9:NDEST=OWNMSRN;

ZRDC:TREE=51,TON=INT,DIG=628167715&&-9:NDEST=OWNMSRN;

7.16 Modify Normal Preanalysis in MSS

ZRWN:MOC,3,62::::ESTP=1;

7.17 Modify Default preanalysis in MSS

ZRWN:MOC,2,0:::ESTP=1;

7.18 Modify EOS 1009 analysis in MSS

ZRXM:0:1009:EOSATTR;
ZRXM:1:1009:EOSATTR;
ZRXM:2:1009:EOSATTR;

7.19 In case of fallback :

ZRWN:MOC,3,62::::ESTP=0;
ZRWN:MOC,2,0:::ESTP=0;

ZRXM:0:1009:CMANAL,,,50,0,,,::
ZRXM:1:1009:CMANAL,,,50,0,,,::
ZRXM:2:1009:CMANAL,,,50,0,,,::

7.20 Make a test call for voice call and video call between coverage MGW Medan to coverage
MGW Batam or vice versa and on its own MGW coverage (A subs and B subs in it own MGW).

8. TESTING CALL SCENARIO FOR PHASE 2 – MIGRATION TO NB OVER TDM

Initially with the help of LBCU ID usage and LAC with MSRN division the calls from MGW
Medan to MGW Batam and vice versa is routed to Gateway MSC Siemens Medan and
Batam.

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
 Generally LAC with MSRN division here is explained as MSS controlling numbers of MGW
and having MSRN pool divided for those MGWs.

It is explained in the digit analysis in TREE 50 as below for call to MGW Medan.

81606110&&81606124 0 MSRNMGWMDN 1 N MSRNMDNGWBTM 0 CHARGECALL

1 MSRNMGWMDN 1 N SIELPGR2600 0 CHARGECALL

2 MSRNMGWMDN 1 N SIEPLBR2610 0 CHARGECALL

3 MSRNMGWMDN 1 N ADD62 0 CHARGECALL

Alternate 0 is used for call from MGW Batam to MGW Medan. Alternate 1 is used for call
from MGW Palembang to MGW Medan. And Alternate 3 is call within own MGW Medan
coverage.

Same situation for call to MGW Batam

81607715&&-9 0 MSRNMGWBTM 1 N MSRNBTMGWMDN 0 CHARGECALL

1 MSRNMGWBTM 1 N SIELPGR2600 0 CHARGECALL

2 MSRNMGWBTM 1 N SIEPLBR2610 0 CHARGECALL

3 MSRNMGWBTM 1 N ADD62 0 CHARGECALL

Alternate 0 is used for call from MGW Medan to MGW Batam. Alternate 1 is used for call
from MGW Palembang to MGW Batam. And alternate 3 is call within own MGW Batam
coverage.

It can be explained with the usage of LBCU ID. Under same MGW it is required to identify
the MGW where the calls are getting originated.

It is explained in the command output below.

RIL:NSDEST=MSRNMDNGWBTM,:;

MSCi MNMD1 2008-02-08 17:58:50

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
 NAME OF SUBDESTINATION: MSRNMDNGWBTM SDEST: 61

CT SP RC RT RNBR SRCL MNL

SC 1 APR ROU 1001 N 0

RRI:GSW:ROU=1001:;

MSCi MNMD1 2008-02-08 17:59:57

ROU TYPE OUTR STP TSG TMT SAT ATME DCME ECHO CONT TON SEQH ICR

1001 EXT O6PK1 1 - - N N N N - NOE Y N

UPDR LBCUID

- 1001

FCL

With the help LBCU id usage in MGW Parameter, MSS can recognize where the call is
originated from. In this case the call is coming from MGW Batam.
JGI:MODE=1:MGWID=6:;

MSCi MNMD1 2008-02-08 18:06:21

MGW DATA:

MGW ID..............................6

MGW NAME......................WNBT1V01

MGW ADDRESS...............10.201.76.2

PORT NUMBER.................8009

DOMAIN NAME................

ROUTE................................1001

MGW TYPE........................GENERAL

UNIT TYPE.........................SIGU

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
 UNIT INDEX.......................7

CTRL ADDRESS..................10.201.68.41

E.164 AESA...........................628160771000

LOCAL BCU-ID....................1001

REGISTRATION ALLOWANCE........ALLOWED

REGISTRATION STATUS..................REGISTERED

The objective call testing in this phase, is to migrate the traffic call under RNC Medan to RNC Batam and
vice versa with Nb interface over TDM.

The traffic calls from RNC Medan which is connected to MGW Medan to RNC Batam which is connected
to MGW Batam and vice versa now will be going through Nb over TDM interface MGW Medan – MGW
Batam.

Since there is one LAC in each MGW (which is used for each RNC Medan and Batam), we will choose
this A-LAC as main indicator to differentiate call via Nb interface and Call via Transit MSC.

All LAC under RNC Medan and RNC Batam will be marked with Original Dialling Class (ODC) during
extended pre analysis stage. This ODC Flag will be analyzed later on during routing attribute analysis
stage. If routing criteria is match, then the call will go to digit analysis TREE 4 for MOC Tree Analysis
and the MSRN result will be sent to new TREE 51. If the routing criteria is not match, then the call will
go to default tree analysis TREE 2 and the MSRN result will be sent to TREE 50.

Within TREE 51, MSRN will be analyzed based on LBCU ID as identifier of originate MO calls. If the
LBCU ID is match with LBCU MGW Medan or MGW Batam the GSMEND procedure will be triggered to
start user plane analysis and paging for B subs.

Only 3G Subscriber to 3G subscriber call under RNC Medan/ MGW Medan and RNC Batam/MGW
Batam will be routed via Nb over TDM interface. The routing for the rest of calls will not be changed and
still go via Siemens Transit MSC in each corresponding area.

The procedure is explained below. All these actions are executed in MSS.

8.1 Remove Extended Preanalysis from Normal and Default Pre analysis in MSS

ZRWN:MOC,3,62::::ESTP=0;
ZRWN:MOC,2,0:::ESTP=0;

ZRXM:0:1009:CMANAL,,,50,0,,,::
ZRXM:1:1009:CMANAL,,,50,0,,,::
ZRXM:2:1009:CMANAL,,,50,0,,,::

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
8.2 Change CLIA Extended Pre analysis Subanalysis to Test and Remove it in MSS.

ZCWN:MNT,CLIA:;

ZCWD:CLIA;

8.3 Create New Extended Preanalysis Subanalysis in MSS

ZCWC:LAC,START,1:LAC=5190:RES=ODC1,DEFRES=DUMMY:UNKRES=DUMMY;

LAC 5190 is for RNC Medan. Add LAC 5198 for RNC Batam

ZCWM:LAC,ADD:VALUE=5198,RES=ODC1:;

8.4 Change Extended Preanalysis Subanalysis stage to Normal

ZCWN:MTN,LAC:;

8.5 Create all digit analysis which is leading to HLR Enquiry in TREE 2 or TREE 200 in TREE 4
with new destination (= NBHLRENQ)

Example :

ZRDP:EXT=4,EXTON=NAT,EXD=81630:TREE=4,TON=NAT,DIG=81610;

ZRDP:EXT=4,EXTON=NAT,EXD=85510:TREE=4,TON=NAT,DIG=85565;

8.6 Modify Normal Preanalysis in MSS to execute Extended Preanalysis

ZRWN:MOC,3,62::::ESTP=1;

8.7 Modify Default preanalysis in MSS to executed Extended Preanalysis

ZRWN:MOC,2,0:::ESTP=1;

8.8 Modify EOS 1009 analysis in MSS

ZRXM:0:1009:EOSATTR;
ZRXM:1:1009:EOSATTR;
ZRXM:2:1009:EOSATTR;

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
8.9 In case of fallback :

ZRWN:MOC,3,62::::ESTP=0;
ZRWN:MOC,2,0:::ESTP=0;
ZRXM:0:1009:CMANAL,,,50,0,,,::
ZRXM:1:1009:CMANAL,,,50,0,,,::
ZRXM:2:1009:CMANAL,,,50,0,,,::

8.10 Make a test call for voice and video call from coverage RNC Medan to coverage RNC Batam
and vice versa and voice call and video call within own coverage (own coverage of RNC Medan
and RNC Batam) to verify that Nb interface over TDM is working.

9. REFERENCE

Integrating MGW in MSC Server system

C:\Temp\Integrating
MGW in MSC Server System.pdf

MSC Server Integration

C:\Temp\msc server
integraion.pdf

PDC4558/FN1566 Feature Activation

C:\USERS\
PDC4558.doc

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008
10. SYSTEM SECURITY

For security of the system, it is wisely recommended to make copy fall back in MSS and MGW before
doing the job of the integration. It is also wisely recommended to do the risk job during low traffic hour.

Erlang Bharata Revision 1

CMO APAC Care Area Core Stream ID 11/02/2008