MGCF Data Configuration

HUAWEI TECHNOLOGIES CO., LTD.

www.huawei.com

HUAWEI Confidential

Security Level:

UGC3200 Data Configuration

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 2

References

Data configuration documents shipped

with the UGC3200


After learning this course, you will be able to learn the

following information:

Overview and procedure of UGC3200 data

configuration

Configuration procedures of the hardware data,

basic data, interworking data, and common

features of the UGC3200


1.1. Overview of UGC3200 Data Overview of UGC3200 Data ConfigurationConfiguration

2. Configuration of the System Hardware Data

3. Configuration of the NE and Process Data

4. Configuration of the Public Data

5. Configuration of the Interworking Data

6. Configuration of the Service Data


1.1. Overview of UGC3200 Data Overview of UGC3200 Data

ConfigurationConfiguration

1.1 General Data Configuration

Procedure

1.2 Data Configuration

Relationship of the UGC3200


General Procedure of Data Configuration

Start

Configure the hardware data

Configure the NEs and modules

Configure the public data

Configure the interworking data

Configure the service data

End


General Procedure of Data Configuration

Hardware data: It refers to the rack data, subrack data, and board data.

Hardware data is the basis data of the UGC3200.

NE and module data: It refers to the data about association between

the hardware data and the NE logic data.

Public data: It refers to the basic data, such as the local office

information, database functions, and trunk data.

Interworking data: It refers to the basic data used for interworking

between the UGC3200 and other NEs. These NEs include the HLR and

SCP in the GSM network, the HLR and SCP in the CDMA network, and

the SCP and CCF in the fixed network.

Service data: It refers to the data of various services, such as the

customized ringback tone (CRBT), forwarding notification tone, and

number change.


1.1. Overview of UGC3200 Data Overview of UGC3200 Data

ConfigurationConfiguration

1.1 General Data Configuration

Procedure

1.2 Data Configuration

Relationship of the UGC3200


Data Configuration Relationship of the UGC3200

Child-parent relationship

To configure data B, data A must be configured first. This configuration relationship

is called child-parent relationship. The child object data can be configured only after

the parent object data is configured.

Reference relationship

During configuration of data B, specific parameters in data A must be referenced.

This configuration relationship is called reference relationship. The referencing

objects can be configured only after the referenced objects are configured.


1. Overview of UGC3200 Data Configuration

2.2. Configuration of the System Configuration of the System Hardware DataHardware Data







1.1 Equipment Numbering

1.2 Configuration of the

Hardware Data


Equipment Numbering

Extended Subrack 01

LAN Switch/Hard DiskArray/KVM/Dummy Panel

Basic Subrack 00

Power Distribution Frame

Extended Subrack 04

Dummy Panel

Extended Subrack 02

Extended Subrack 03

Dummy Panel

Integrated Cabinet 00 Service Cabinet 01


Equipment Numbering

Equipment numbering

Slot numbering

− All subracks of the UGC3200 are universal in terms of hardware.

The boards are inserted in the front and at the back of the

backplane.

− The slots for front boards are numbered from 0 to 13 from left to

right.

− The slots for back boards are numbered from right to left. The

numbers of back slots are mapped to those of front slots.

− There are two slots used to install the SMUs at the bottom of the

subrack. The slot on the left is numbered 14, and the slot on the

left is numbered 15.


Equipment Numbering

Rear

Front

Backplane



1.1 Equipment Numbering

1.2 Configuration of the

Hardware Data


Hardware Configuration — Network Type

Network type

SET NET: CASCADMODE=EXTERNALMODE;

Set the network mode used in the current environment.


Hardware Configuration — Rack

Rack configuration

Run ADD RACK to add a rack.

ADD RACK: RN=0, POSNUM=0, ROWNUM=0, COLNUM=0;

Run MOD RACK to modify parameters of the rack, for example, the

rack name, position number, row number, and column number.

Run RMV RACK to remove a rack.

You are advised to add racks sequentially from the smallest rack

number. Before removing a rack, you must remove the subrack

configuration related to the rack. Otherwise, the rack cannot be

removed.


Hardware Configuration — Subrack

Subrack configuration

Run ADD SUBRACK to add a subrack.

ADD SUBRACK: SRN=0, RN=0, PN=0, SBVER=T8260/T8261,

SRMUSN1=4, SRMUSN2=5, SWFBRDT=SWUA0,

Before running ADD BRD to add a board, you need to add the

board where the subrack management unit (SMU) is located first.


Hardware Configuration — Board Run ADD BRD to add a board.

ADD BRD: SRN=0, SN=4, METYPE=COMMON,

FBRDHTYP=UPB1, BBRDHTYP=USI7, APPTYPE=OMU;

ADD BRD: SRN=0, SN=5, METYPE=UGC, FBRDHTYP=UPB0,

BBRDHTYP=USI1, APPTYPE=UGMIU;

Configuration description

Before adding boards, you must add the related subrack first.

Update flag of operating system: If this parameter is set to Can

update operating system, the board automatically loads and

tailors the operating system from the OMU and the data from the

service database, and install the system locally after the board is

inserted into the subrack.


Questions

What are the numbering rules for the racks, subracks, and slots?

What data should be added when you configure the hardware data?


Summary

Equipment numbering rules

Hardware data configuration

SummarySummary




3.3. Configuration of the ME and Configuration of the ME and Process DataProcess Data





3.3. Configuration of the NE and Configuration of the NE and Process DataProcess Data

3.1 Basic Concepts

3.2 Relationship Between

Tables

3.3 Configuration Procedure

3.4 Configuration Example


Basic Concepts

Module: A module is also called a processing unit. It has some service functions.

The UGC3200 consists of the following types of modules:

Dispatch unit (DPU): It forwards IP packets and works in active/standby mode.

Broadband signaling unit (BSU): It terminates the TCP/SCTP connection and works in load-sharing mode.

Central database (CDB): It maintains the system data and works in active/standby mode.

Call control unit (CCU): It implements functions of the integrated tandem office, integrated gateway office, and international gateway for interworking between the FSX, MSX, and CSX. It also implements service functions of the MGCF logical ME. The CCU works in active/standby mode.

Media gateway control (MGC): It implements functions of the media gateway control and works in active/standby mode.


Basic Concepts Process group: A process group is a combination of different modules.

Process

GroupModule Description of the Process Group

CCU 1 x CCU + 1 x DEVImplements call control and works in

active/standby mode.

CDB 1 x CDB + 1 x DEVMaintains the system data and works in

active/standby mode.

BSU 1 x BSU + 1 x DEVTerminates the TCP/SCTP connection and

works in load-sharing mode.

DPU 1 x DPU + 1 x DEVForwards IP packets and works in active/standby

mode.

BSG 1 x DPU +1 x BSU + 1 x DEV Integrates functions of the DPU and BSU.

MGC 1 x MGC + 1 x DEVImplements functions of the media gateway

control and works in active/standby mode.

IFM 1 x IFM + 1 x DEVImplements the online charging function and

works in active/standby mode.


Basic Concepts

NE: The unified gateway controller (UGC) implements functions of the

integrated tandem office, integrated gateway office, and international

gateway for interworking between the FSX, MSX, and CSX. It also

implements service functions of the MGCF logical NE.

Entity:

The UGC3200 can serve as an MGCF and implements interworking

between the CS and IMS domains.



3.1 Basic Concepts

3.2 Relationship Between Tables





3.1 Basic Concepts





Loading the NE Package LOD PKG: FNM="UGC_SRV_ V200R006C02SPC200.tar";

Configuration description:

This command is used to load the new NE package to the system.

You must load the NE package before adding an NE.


Adding an ME

ADD ME: MEID=10, MENAME="UGC", METYPE=UGC,

MEVER="V200R008C03", MEVD="HUAWEI";


This command is used to add an ME to the system.

The system can be configured with multiple MEs, but the ID of each ME must be unique.



3.1 Basic Concepts




Configuration Example

//The following data is configured in the CGP MML command window.

SET NET: CASCADMODE=EXTERNALMODE;

ADD RACK: RN=0, POSNUM=0, ROWNUM=0, COLNUM=0;

ADD SUBRACK: SRN=0, RN=0, PN=0, SBVER=T8260/T8261,

SRMUSN1=4, SRMUSN2=5, SWFBRDT=SWUA0, SWBBRDT=SWIA0;

ADD BRD: SRN=0, SN=4, METYPE=COMMON, FBRDHTYP=UPB1,

BBRDHTYP=USI7, APPTYPE=OMU;

ADD BRD: SRN=0, SN=5, METYPE=UGC, FBRDHTYP=UPB0,

BBRDHTYP=USI1, APPTYPE=UGMIU;

ADD BRD: SRN=0, SN=8, METYPE=CSCF, FBRDHTYP=UPB0,

BBRDHTYP=USI1, APPTYPE=CSISU;

ADD ME: MEID=10, MENAME="ETSI", METYPE=UGC,

MEVER="V200R006C02SPC200", MEVD="HUAWEI";





4. Configuration of the Public Data4. Configuration of the Public Data




4.4. Configuration of the Public Configuration of the Public DataData

4.1 Basic Concepts




Basic Concepts

IP address of the local office: Configure the IP address of the UGC3200 for external

communication.

Database functions: Configure the service query capability of a CDB process of the

UGC3200, for example, the trunk line selection capability. When a UGC3200 has

multiple CDB processes, you can configure the service query capability of each CDB

process to implement load sharing of service query.

Local office information: Configure information such as the signaling point code (SPC),

area code, and country code of the UGC3200.

Mobile local office information: Configure information such as the MSC number, mobile

country code (MCC), mobile network code (MNC), and international number prefix of

the local office.

Call source: Configure information such as the route selection source code, failure

source code, and area code.

Trunk data: Configure the trunk data of the UGC3200. Trunk types supported by the

UGC3200 are ISUP, TUP, R2, PRA, SIP, and BICC.

Charging data: Configure the charging function of the UGC3200.


4.4. Configuration of the Public Configuration of the Public DataData

4.1 Basic Concepts




Configuring the IP Address Information of the Local Office

ADD IPADDR: IPNAME="0", DPUMID=1500, PORTID=BACK7, IPVER=IPV4, IP4="172.21.88.84",NETMASK="255.255.255.224",DEFAULTGW4="172.21.88.65", DETECT=ARP, RFC=OPEN, LFC=OPEN;


This command is used to configure the IP address of the IFM process and the

used network port number. The UGC3200 accesses the external network by

using this IP address.

Description of key parameters:

MID: It specifies the module number of the IFM process. If the UGC3200 has

multiple DPU processes, you can configure multiple external IP addresses to

enable communication with networks in different network segments.

PORTID: The structures of all service boards of the UGC3200 are the same.

The back board of each board has eight network ports. PORTID specifies the

network port that is bound with the IP address..


ADD CDBFUNC: CDBMN=1300, FUNC=TKAGT-1&CGAP-1&ECTCF-

1&TLDN-1&CCTF-1&TK-1;


This command is used to configure the service capability of the CDB

process.


CDBMN: It specifies the module number of the CDB. When the UGC3200 is

configured with multiple CDB processes, you can distribute the CDB query

capability to different CDB processes to achieve the loading sharing effect.

FUNC: It specifies the query capability of the CDB. Records can be queried

normally only after this capability is configured.

Configuring the CDB Functions


Configuring the Local Office Information SET OFI: OFN="UGC", LOT=CMPX, IN=YES, NN=YES, SN1=NAT, SN2=NATB, SN3=INT,

SN4=INTB, IPC="444", NPC="001122", NP2C="444", NNS=SP24, NN2S=SP14, SPF=YES, STP=YES, LAC="22", LNC=K'62, SIN=K'6288887777, ENI=NN, NONENI=NN;

Configuration description: This command is used to configure information such as the signaling point, area code, and

country code of the local office. Description of key parameters:

LOT: It specifies the type of the local office. The local office can be a national toll office or a mobile international toll office.

NN: It is the national active network valid flag, which indicates whether the signaling point of the local office is valid in the national active network. Besides this flag, there are international active network, national reserved network, and national reserved network valid flags. The parameter NN must be configured based on the unified planning of the local network.

SN1: It specifies the first search network. This parameter is used to set the network search sequence.

NPC: It specifies the signaling point code (SPC) of the local office in the national active network when the local office is valid in the national active network.

NNS: It specifies the length of the SPC of the local office in each signaling network. The SPC length varies according to the signaling network. In the national active network and international reserved network, the SPC length is generally 24 bits. In the national reserved network and international active network, the SPC length is generally 14 bits.

LAC: It specifies the area code of the local office. LNC: It specifies the country code of the local office.


Configuring the Mobile Local Office Information SET INOFFMSC: MSCN=K'6288888, MCC=K'510, MNC=K'10,

INNATIONPFX=K'00, NATIONPFX=K'0;


This command is used to configure the mobile local office information and

define information such as the MSC number of the local office in the PLMN

and the mobile country code.


MSCN: It specifies the MSC number of the local office.

MCC: It specifies the mobile country code of the local office.

MNC : It specifies the mobile network code of the local office.


Adding the Call Source Information ADD CALLSRC: CSCNAME="icscf_hw_sip", RSSN="icscf_hw_sip",

FSN="fsn";


RSSN: It specifies the name of the route selection source. It is used

for route analysis.

FSN: It specifies the name of the failure source. It is used for failure

processing.


Configuring the Trunk Data The UGC3200 supports the ISUP, PRA, R2, TUP, SIP, and BICC trunks.

The procedure for configuring the trunk data is as follows:

1. Configure the gateway data.

2. Configure the data of the signaling link between the local and peer

offices. (Optional)

3. Configure the office direction and route data.

4. Configure the trunk group data.

5. Configure the circuit data. (This step is mandatory for the narrowband

trunks, but is not required for broadband SIP/BICC trunks.)


Configuring the Trunk Data — ISUP

//Configure the data for interworking with the UMG. The H.248 links are established between the UGC3200 and the UMG to carry the SCTP signaling.

ADD MGW: MGWNAME="UMG1", TRNST=SCTP, CTRLMN=1600, MGWDESC="UMG1", BCUID=0, ENCT=NSUP;

ADD H248LNK: MGWNAME=“UMG1", TRNST=SCTP, LNKNAME=“UMG_UGC", SLOCIP1="154.104.3.1", SLOCPORT=2951, SRMTIP1="154.104.3.204", SRMTPORT=2961, QOSFLAG=TOS, ENWTCH=TRUE;


First, run ADD MGW to add an MGW. In the command, the parameter CTRLMN specifies the module number of the MGC process that controls the MGW. Then, configure the H.248 link data.

The H.248 links are established between the UGC3200 and the UMG to carry the SCTP signaling.

When configuring the H.248 links, note that the local port number and remote port number must be consistent with those configured on the UMG. In this example, the local IP address of the UGC3200 is 154.104.3.1 and the local port number is 2951. The IP address of the UMG is 154.104.3.204 and the port number is 2961.


Configuring the Trunk Data — ISUP//After configuration of the gateway data is complete, you need to configure the M3 links for interworking with the peer switch.

ADD M3LE: LENM="UGC", OPC=“444444", LET=AS;

ADD M3DE: DENM="NGN", LENM="UGC", NI=NAT, DPC="888888", DET=AS;

ADD M3LKS: LSNM="NGN", ADNM="NGN", WM=IPSP;

ADD M3LNK: MN=1400, LNKNM="NGN", LOCIP1="154.104.3.1", LOCPORT=2922, PEERIP1="154.112.0.10", PEERPORT=2922, CS=C, LSNM="NGN", SCTPPARA=FALSE, MONITOR=TRUE;

ADD M3RT: RTNM="NGN", DENM="NGN", LSNM="NGN";


OPC in the ADD M3LE command specifies the signaling point code of the UGC3200. In this example, the signaling point code of the UGC3200 is 444444.

DPC in the ADD M3DE command specifies the signaling point of the peer switch (NGN in this example) that interworks with the UGC3200. In this example, the signaling point code of the NGN is 888888.



LET in the ADD M3LE command must be set to AS.

DET in the ADD M3DE command must be set to AS.

WM in the ADD M3LKS command must be set to IPSP.

MN in the ADD M3LNK command specifies the module number of

the BSG process that controls the link. When running ADD M3LNK,

note that the local IP address and the port number must be

consistent with those configured on the peer side. In addition, the

setting of CS must be consistent with the setting on the peer side.

For example, if CS is set to C (client) for the UGC3200, CS must be

set to S (server) for the NGN.

After adding the M3 links, you need to run ADD M3RT to configure

the M3 routes.



//After configuration of the M3 link data is complete, the signaling links between the UGC3200 and the peer switch are established. Then, you need to configure the office direction and route data.

//Add the office direction data, where the ISUP trunk is used in the office direction, the local office type is MSC, and the signaling point code of the peer switch is 888888.

ADD OFC: ON="ISUP_NGN", OOFFICT=MSC, DOL=LOW, BOFCNO=0, OFCTYPE=COM, SIG=NONBICC/NONSIP, DPC1=“888888", ISEACM=TRUE;

//Add the subroute data. ADD SRT: SRN="ISUP_NGN", ON="ISUP_NGN";

//Add the route data. ADD RT: RN="ISUP_NGN", SR1N="ISUP_NGN";

//Add the route analysis data. ADD RTANA: RSN="ISUP_NGN", RSSN="UGC", RN="ISUP_NGN", ISUP=NOCHG; Configuration description:

SIG in the ADD OFC command is closely related to the trunk type used in the office direction. During configuration, you need to set SIG based on the trunk type.

When the UGC serves as an MGCF, SIG must be set to IMS in the IMS office direction. If SIG is set to IMS, you need to configure the RF charging data. Otherwise, calls cannot be connected.


Configuring the Trunk Data — SIP

//Configure the gateway information. ADD MGW: MGWNAME=“UMG2", TRNST=SCTP, CTRLMN=1600,

MGWDESC=“UMG2", BCUID=1234, ENCT=NSUP, VQECTRL=NSUP;//Configure the H.248 link. ADD H248LNK: MGWNAME=“UMG2", TRNST=SCTP, LNKNAME=“UMG_UGC",

SLOCIP1="154.104.3.1", SLOCPORT=2951, SRMTIP1="154.104.3.204", SRMTPORT=2951, QOSFLAG=TOS, ENWTCH=TRUE;

//Add the office direction. ADD OFC: ON="SIP_NGN", OOFFICT=NATT, DOL=SAME, BOFCNO=2,

OFCTYPE=COM, SIG=IMS, AN="0"; If the UGC3200 serves as an MGCF, SIG must be set to IMS. In addition, the

RF charging data must be configured. If the UGC3200 does not serve as an MGCF, but needs to interwork with the peer office through the SIP trunk, SIG must be set to NGN.

//Add the gateway in the office direction. The SIP trunk is carried over IP. It must be specified which gateway is used to establish the bearer. In the model without MGWs, this configuration is used to specify that the CNM does not control the bearer.

ADD OFCMGW: ON=“SIP_NGN”, MGWNAME=“UMG2”; -- Model with MGWs ADD OFCMGW: ON=“SIP_MSX”, MGWNAME=“CMN”, DESC=“NO MGW”; -- Model

without MGWs


Configuring the Trunk Data — SIP

//Configure the route and prefix.

Omitted.

//Configure the SIP protocol distribution capability.

SET SIPCFG: SOFTCTRLPARA=SVR7-1, MAXSRVPORT=5064;

SET DPA: MN=1400, PA=H248-1&MGCP-1&SIP-1;

MN: module number of the BSG process

//Configure the SIP trunk data. Pay attention to the settings of the local and remote port numbers. Generally, the local and remote port numbers are set to 5060.

ADD SIPTG: TGN="SIP_NGN", CSCN="UGC", SRTN="SIP_NGN", IMN=1500, LOCALIP="154.104.3.1", LPORT=5060, OSU="154.104.3.3:5060", PNET=NOIMS, CCUMODE=DIS;

//Specify the CCU process that handles the SIP trunk calls. (Optional)

MOD SIPTG: TGN="SIP_NGN", LOCALIP="154.104.3.1", CCUMODE=IND, CCU1=1001;


Basic Concepts

Number analysis

The number analysis data must be configured for all calls. As the UGC3200 supports all calls of the GSM, CDMA, and fixed networks, the number analysis data is complex. Through number analysis, the system can determine whether the call is a GSM network call, CDMA network call, or a transit call.

Number change

Carriers have raised diversified requirements on the incoming and outgoing numbers. The UGC3200 provides a full package of number change functions to meet various requirements of different carriers.

Customized ringback tone (CRBT)

When the UGC3200 serves as the gateway office of the GSM or CDMA network, it supports triggering of the CRBT service. The UGC3200 inherits existing features of the GSM and CDMA networks.

Common CRBT

The common CRBT service is similar to a tone playing function. Subscribers can use the service without configuring or subscribing to this service. To provide this service, carriers only need to configure the relevant data on the UGC3200.

Tone playing

Besides the IN tone playing function, the UGC3200 provides multiple tone playing functions to meet different requirements of customers.


Number AnalysisADD CNACLD: PFX=K'138, CSA=NTT, RSNAME="ISUP_NGN", MINL=4, MAXL=24,

ICLDTYPE=MSRH; CSA: It specifies the service attribute. For the UGC3200, CSA cannot be set to Local. ICLDTYPE: it specifies the type of the called number. The called number types

supported by the UGC3200 are MSISDN, PSTN, MSRN, IN, MDN, TLDN, and UNKNOWN. If ICLDTYPE is set to MSISDN, the UGC3200 obtains the MSRN from the GHLR. If ICLDTYPE is set to MDN, the UGC3200 obtains the TLDN from the CHLR. After obtaining the MSRN from the GHLR, ICLDTYPE must be set to MSRN. So far

as CSA is not set to Local and the correct RSNAME (route selection name) is configured, the UGC3200 can use the MSRN as a PSTN number and route the call to the terminating office.

After obtaining the TLDN from the CHLR, ICLDTYPE must be set to TLDN. So far as CSA is not set to Local and the correct RSNAME (route selection name) is configured, the UGC3200 can use the TLDN as a PSTN number and route the call to the terminating office. If the IPM is required to play tone, however, CSA of the TLDN must be set to Local and the ICLDTYPE must be set to TLDN.

When both CSTP (Service category) and CSA are set to Intelligent service, ICLDTYPE must be set to IN.


Number Analysis

ADD CNACLD: PFX=K'200, CSTP=IN, CSA=INSVR, MINL=3, MAXL=3,

ICLDTYPE=IN, INTYPE=FIN;

INTYPE: It specifies the network, whose IN service is triggered by the

IN service prefix.


Number Change

The UGC provides multiple number change functions. Frequently used

functions are as follows:

Caller discrimination

Incoming number pre-analysis

1. Incoming calling number associated processing

2. Incoming original called number associated processing

Call prefix processing

Outgoing number pre-processing

1. Outgoing calling number associated processing

2. Outgoing original called number associated processing


Number Change — Caller Discrimination

//During configuration of the trunk group, specify the discrimination group

number. In the following example, the discrimination group number is set to

2.

ADD N7TG: TGN="MSX_ISUP_UGC", MGWNAME="UMG", CT=ISUP,

SRN="MSX_ISUP_UGC", BTG=0, CSCNAME="MSX", CC=NO,

DISGRP=2, RELRED=NO;

//Add the number change data.

ADD DNC: DCN="DELETE_86", DCT=TYPE6, DCL=2;

// Add the caller number discrimination data, where DSP (Discrimination

group number) is set to 2.

ADD CLRDSG: DSP=2, CLI=K'86138, DAI=ALL, FUNC=ATT,

DN="DELETE_86";


Number Change — Incoming Number Pre-Processing Incoming number pre-processing is performed before the called number analysis. The calling number,

called number, and original called number can be changed. Incoming number pre-processing data is not merely used for trunk incoming calls. Here, incoming is

broadly defined as a processing before each number analysis, for example: Before number analysis performed after the roaming number is obtained from the MAP Before number analysis performed after the forwarded-to number is obtained from the MAP Before number analysis when the call is routed into the local office through trunk

Incoming number pre-processing also involves the ADD INCLRIDX and ADD INORICLDIDX commands.ADD INNUMPREPRO: CSCNAME="MSX", PFX=K'139, CIDN="DELETE_CLI_86", ODIDN="INVALID", CDN="DEFAULT", DDN="ADD_CLD_86", ODDN="DEFAULT";

PFX: It specifies the prefix of the called number. It is not the prefix configured in the CNACLD table. PFX supports fuzzy match.

CIDN: It specifies the caller number correlation processing name. It is used to reference ADD INCLRIDX.

ODIDN: It specifies the original called number correlation processing name . It is used to reference ADD INORICLDIDX.

CDN: It specifies the caller number change name. It is used to reference ADD DNC. DDN: It specifies the called number change name. It is used to reference ADD DNC. ODDN: It specifies the original called number change name. It is referenced by ADD DNC. In this command, the calling number is not matched. That is, regardless of the type of the calling

number, the number can be changed so far as the call source and the prefix of the called number are matched. If it is required that the number is changed only for calls originated by a specific type of caller, how should you configure the data?


Number Change — Incoming Number Pre-ProcessingThe following command is run to add the incoming caller number associated processing data.

ADD INCLRIDX: CIDN="DELETE_CLI_86", PFX=K'86138, CDN="DELETE_86",

DDN="INVALID", ODDN="DEFAULT";

CIDN: It specifies the caller number correlation processing name. It is referenced by ADD

INNUMPREPRO.

PFX: It specifies the prefix of the caller number. It supports fuzzy match.

CDN: It specifies the caller number change name. It is used to reference ADD DNC.

DDN: It specifies the called number change name. It is used to reference ADD DNC.

ODDN: It specifies the original called number change name. It is used to reference ADD

DNC.

In this command, the calling number is matched. This solves the problem that the calling

number cannot be matched during incoming number pre-analysis. In this way, the number

can be changed for calls originated by a specific type of callers.


Number Change — Incoming Number Pre-Processing

The following command is run to add the incoming original called number associated

processing data.

ADD INORICLDIDX: CIDN="ADD_ORGCLD_86", PFX=K'135, CDN="INVALID",

DDN="DEFAULT", ODDN="ADD_86";

CIDN: It specifies the original called number correlation processing name. It is

referenced by ADD INNUMPREPRO.

PFX: It specifies the prefix of the original called number. It supports fuzzy match.

CDN: It specifies the caller number change name. It is used to reference ADD DNC.

DDN: It specifies the called number change name. It is used to reference ADD DNC.

ODDN: It specifies the original called number change name. It is used to reference

ADD DNC.

In this command, the original called number is matched. This solves the problem that

the original called cannot be matched during incoming number pre-analysis. In this

way, the number can be changed after the original called numbers are discriminated

according to specific requirements.


Number Change — Incoming Number Pre-ProcessingQuestion: The incoming number pre-analysis data contains the number change indexes, including CDN (caller number change name), DDN (called number change name), and ODDN (original called number change name). The incoming caller number associated processing data and the incoming original called number associated processing data also contain CDN, DDN, and ODDN. If I configure all these parameters respectively in the incoming number pre-analysis data, incoming caller number associated processing data, and incoming original called number associated processing data, how does the UGC3200 process the data?Answer: During incoming number pre-processing, the number change priorities are listed as follows from high to low: (The calling number, called number, and original called number are independent of each other. Therefore, their priorities are the same.)1. Number change configured in the incoming original called number associated processing data2. Number change configured in the incoming caller number associated processing data3. Number change configured in the incoming number pre-analysis data

Note: In the incoming caller number associated processing data and the incoming original called number associated processing data, the default value of each number change index is DEFAULT. The UGC3200 treats DEFAULT as a valid value and does not perform number change on default records of ADD DNC. ADD INNUMPREPRO: CSCNAME="MSX", PFX=K'86138, CIDN="ADD_CLI_86", DDN="DELETE_86";ADD INCLRIDX: CIDN="ADD_CLI_86", PFX=K'135467, CDN="ADD_86", DDN="DEFAULT";Therefore, if the preceding configuration is available, DDN is DFAULT according to the number change priorities, that is, the called number is not changed. In this case, to make the value DELETE_86 of DDN effective, you need to run ADD INCLRIDX to set DDN to INVALID.


Number Change — Call Prefix Processing

ADD CNACLD: PFX=K'130, CSA=NTT, RSNAME="ISUP_CSX", MINL=4, MAXL=24, ICLDTYPE=GCT_TLDN, DNPREPARE=TRUE;

ADD PFXPRO: CSCNAME="UGC", PFX=K'130, CLDNCN="ADD_86", CLDNCN="DEFAULT“, STF=NSDT, PT=DONTPROC;

DNPREPARE: To enable call prefix processing during number analysis, this parameter must be set to TRUE.

PFX: It specifies the prefix of the called number. It supports maximum fuzzy match. PFX need not be the same as the prefix configured in the Call Prefix table. For example, the prefix configured in the Call Prefix table is 130, PFX in the Call Prefix Processing table can be set to 1301 or 1302. If DNPREPARE is set to TRUE in the Call Prefix table, the system queries the Call Prefix Processing table and matches numbers according to conditions such as the prefix. If a match is found, the system performs call prefix processing. If no match is found, the system does not perform call prefix processing and continues with the subsequent call flow.

CLINCN: It specifies the caller number change name. It is used to reference ADD DNC. CLDNCN: It specifies the called number change name. It is used to reference ADD DNC.


Number Change — Outgoing Number Pre-Processing After prefix analysis is complete and before the Setup message is sent to the callee, the system can

perform outgoing number pre-processing to change the calling number, called number, original call number, or redirected number.

Outgoing number pre-processing is performed only when the terminating side is a trunk. Outgoing number pre-processing also involves the ADD OUTCLRIDX and ADD OUTORICLDIDX

commands. Configuration and processing mechanism of outgoing number pre-processing are similar to those of

incoming number pre-processing, except for some minor differences. For details, see the description about incoming number pre-processing.

ADD OUTNUMPREPRO: Run this command to add the outgoing number pre-processing data. ADD OUTCLRIDX: Run this command to add the outgoing caller number associated processing

data. ADD OUTORICLDIDX: Run this command to add the outgoing original called number associated

processing data. During outgoing number pre-processing, the number change priorities are listed as follows from high

to low:1. Number normalization configured in the outgoing original called number associated processing

data2. Number normalization configured in the outgoing caller number associated processing data3. Number normalization configured in the outgoing number pre-analysis data4. Number change configured in the outgoing original called number associated processing data5. Number change configured in the outgoing caller number associated processing data6. Number change configured in the outgoing number pre-analysis data


Number Change

Question:

Specify the execution sequence of the following flows during a call:

Caller discrimination, incoming number pre-analysis, call prefix processing,

calling number analysis, and outgoing number pre-processing.

Answer:

The execution sequence is as follows:

1. Caller discrimination

2. Incoming number pre-analysis

3. Prefix analysis

4. Call prefix processing

5. Outgoing number pre-processing

Thank youwww.huawei.com

Documents

MGCF Data Configuration