Scribd
Upload
134 views

Configuration Example Between MSC and HLR

This document provides an example configuration for setting up signaling between an MSOFTX3000 and an HLR using MTP networking mode. It involves configuring two MTP links and SCCP signaling data on the MSOFTX3000 side to allow successful SCCP connection between the devices. Scripts are provided to add MTP signaling data like data point codes and links, as well as SCCP data like signaling points, gateway translation groups and gateway triggers for functions like location update and routing to the correct HLR.

Uploaded by

sinansafaa
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
134 views

Configuration Example Between MSC and HLR

This document provides an example configuration for setting up signaling between an MSOFTX3000 and an HLR using MTP networking mode. It involves configuring two MTP links and SCCP signaling data on the MSOFTX3000 side to allow successful SCCP connection between the devices. Scripts are provided to add MTP signaling data like data point codes and links, as well as SCCP data like signaling points, gateway translation groups and gateway triggers for functions like location update and routing to the correct HLR.

Uploaded by

sinansafaa
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Configuration example between MSC and HLR:

2.

c. Add an SCCP GT group.

ADD SCCPGTG: GTGNM=GT group name, CFGMD=Configure mode,


SERVNM=Server name;

d. Add an SCCP GT.

ADD SCCPGT: GTNM=GT name, NUMPLAN=Numbering plan, ADDR=GT


address information, RESULTT=Translation result type, SPC=SPC,
GTGNM=GT group name;

NOTE:

To realize the location update of mobile subscribers, you must configure the IMSI
GT. When subscribers originate location update, the VLR searches for the HLR
based on the HLR GT, which is obtained based on the IMSI. When the SCCP
translates the GT, the correct result can be obtained only when the record that
matches both the GT group and the GT is found.

e. Add an SCCP GT.

ADD SCCPGT: GTNM=GT name, NUMPLAN=Numbering plan, ADDR=GT


address information, RESULTT=Translation result type, SPC=SPC,
GTGNM=GT group name;

NOTE:

To realize the location update of mobile subscribers, you must configure the
HLR-NUMBER GT. The HLR-NUMBER GT helps the VLR identify the HLR to
which the Insert_Subscriber_Rsp message should be returned. When the SCCP
translates the GT, the correct result can be obtained only when the record that
matches both the GT group and the GT is found.

f. Add an SCCP GT.

ADD SCCPGT: GTNM=GT name", ADDREXP=Address nature indicator,


ADDR=GT address information, RESULTT=Translation result type,
SPC=SPC, GTGNM=GT group name;

NOTE:
When a subscriber is called, you need to configure an ordinary GT (MSIDSN
GT). When obtaining the routing information, the MSC searches for the HLR
based on the HLR GT that is obtained based on the MSISDN of the called
subscriber. When the SCCP translates the GT, the correct result can be obtained
only when the record that matches both the GT group and the GT is found.

Example

Introduction

An example is provided to explain how to configure the data for interworking between the
MSOFTX3000 and the HLR when the MSOFTX3000 connects to the HLR in MTP networking
mode.

In this example, you are required to configure data on the MSOFTX3000 side to meet the
following requirements:

 Two MTP links are set up between the MSOFTX3000 and the HLR.
 The SCCP connection can be set up successfully between the MSOFTX3000 and the
HLR.

Scripts

//Configuring the MTP Signaling Data


ADD N7DSP: DPNM="dpc_name1_0", NI=NAT, DPC="110055", OPC="001122",
STPF=FALSE, ADJF=TRUE;
ADD N7LKS: LSNM="lks_name1", ASPNM="dpc_name1_0";
ADD N7RT: DPNM="dpc_name1", LSNM="lks_name1", RTNM="rt_name1";
ADD N7LNK: MN=22, LNKNM="lnk_name1_0", LNKTYPE=TDM0, E1=0, TS=1,
LSNM="lks_name1", SLC=0;
ADD N7LNK: MN=23, LNKNM="lnk_name1_1", LNKTYPE=TDM0, E1=0, TS=1,
LSNM="lks_name1", SLC=1;

//Configuring the SCCP Signaling Data


ADD SCCPDSP: DPNM="dpc_name1_0", NI=NAT, DPC="110055", OPC="001122";
ADD SCCPSSN: SSNNM="name1-HLR", NI=NAT, SSN= HLR, SPC="110055", OPC="001122";
ADD SCCPGTG: GTGNM="LOCAL", CFGMD=ALL, SERVNM="LOCAL";
ADD SCCPGT: GTNM="HLR-IMSIGT", NUMPLAN=ISDNMOV, ADDR=K'86139, RESULTT=LSPC2,
SPC="110055", GTGNM="LOCAL";
ADD SCCPGT: GTNM="HLR-NUMBER", NUMPLAN=ISDN, ADDR=K'8613907550000,
RESULTT=LSPC2, SPC="110055", GTGNM="LOCAL";
ADD SCCPGT: GTNM="HLR-MSIDSN", ADDREXP=INTER, ADDR=K'861390755,
RESULTT=LSPC2, SPC="110055", GTGNM="LOCAL";

You might also like