¡¾UGC3200 C03¡¿MGCF Data Configuration-20091020-A-1.0

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

Equipment numbering

Rack numbering

− The UGC3200 can be configured with 20 cabinets (racks). During

data configuration, these racks are numbered from 0 to 19.

− The integrated rack is permanently set to 0. The remaining racks

are numbered according to the order of the racks.


Equipment Numbering Equipment numbering

Subrack numbering (including logical numbers and physical numbers)

− The logical numbers of subracks ranges from 0 to 19.

− The integrated rack can be installed with up to two OSTA

subracks, whose physical numbers are 0 and 1.

− The service rack can be installed with up to three OSTA subracks,

whose physical numbers are 0, 1, and 2.

Rules for assigning logical numbers of subracks

− Subracks in the same rack are numbered sequentially according

to the installation position (from bottom to up).

− Subracks in different racks are numbered sequentially according

to the rack numbers (from small to large).


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="ETSI", METYPE=UGC,

MEVER="V200R006C02SPC200", 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

In the CGP MML command window, add an ME, a subrack, and boards.


Configuration ExampleConfigure the processes, process group, and service data for the ME.



//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";


Questions

How is a process defined? What are the functions of a process?

Where should you configure the NE and process data?

In which window should you run the MML commands for adding an ME, a

subrack, or a board? In which window should you run the MML commands

for adding a process group and a process?





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.1 Basic Concepts




Configuring the IP Address Information of the Local Office

ADD IPADDR: IPNAME="ETSI", DPUMID=1500, PORTID=BACK7, IPVER=IPV4, IP4="154.104.8.152", NETMASK="255.255.0.0", DEFAULTGW4="154.104.0.1", ARPDETECT=NEIGH, 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="ETSI", LOT=CMPX, NN=YES, SN1=NAT, NPC="654321", NNS=SP24,

LAC="755", LNC=K'86, SIN=K'654321, 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'861360001, MCC=K‘460, MNC=K'00,

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=" MSX1", RSSN=" MSX1", FSN=" MSX1";


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.



//After the configuration of the gateway, link, office direction, and route data is complete, you need to configure the trunk group data and the circuit data.

//Add the ISUP trunk group data, where the SPC of the UGC3200 is 444444 and the SPC of the peer switch is 888888.

ADD N7TG: TGN="ISUP_NGN", MGWNAME=“UMG1", CT=ISUP, SRN="ISUP_NGN", BTG=1, SOPC=“444444", SDPC=“888888", CSCNAME="UGC", CC=NO, RELRED=NO;

//Add the ISUP trunk group circuits.

ADD N7TKC: MN=1000, TGN="ISUP_NGN", SCIC=0, ECIC=31, TID=1152, SCF=TRUE;


The settings of SCIC and ECIC in the ADD N7TKC command must be the same as those on the peer switch. If SCIC is set to 0 and ECIC to 31 on the UGC3200, SCIC must also be set to 0 and ECIC to 31 on the peer switch. In addition, the value of TID must be the same as the value of TID of the TDMIU on the UMG.

MN in the ADD N7TKC command specifies the module number of the CCU process.


Configuring the Trunk Data — TUP

//Configuration of the TUP trunk data is similar to configuration of the ISUP trunk data. The same configuration is not detailed.

Configure the data for interworking with the UMG. This step is the same as that in the procedure for configuring the ISUP trunk data.

Configure the M3 link data. This step is the same as that in the procedure for configuring the ISUP trunk data.

Configure the office direction and route data. This step is the same as that in the procedure for configuring the ISUP trunk data.

Configure the TUP trunk data.

ADD N7TG: TGN="TUP_NGN", MGWNAME=“UMG1", CT=TUP,

SRN="TUP_NGN", BTG=2, SOPC=“444444", SDPC=“888888",

CSCNAME="UGC", CC=NO;

ADD N7TKC: MN=1000, TGN="TUP_NGN", SCIC=32, ECIC=63,

TID=1184, SCF=TRUE;


Configuring the Trunk Data — R2//When configuring the R2 trunk data, you need not configure the M3 link data. After the configuration of the gateway, H.248 link, office direction, and route data is complete, you also need to configure the following data. (Configuration of the gateway, H.248 link, office direction, and route data is the same as that in the case of ISUP trunk, and therefore omitted here.)

//Add the R2 trunk group data.

ADD CASTG: TGN="R2_NGN", MGWNAME=“UMG1", G=INOUT, SRN="R2_NGN", BTG=0, CSCNAME="UGC", ICN="STANDARD", OCN="STANDARD";

//Add the R2 trunk circuit data.

ADD CASTKC: MN=1000, TGN="R2_NGN", STID=1248, SPCMSN=0, ETID=1279;


STID specifies the start circuit ID and ETID specifies the end circuit ID. The settings of STID and ETID must be the same as those of the TDMIU on the UMG.

SPCMSN specifies the start E1/T1 serial number. The UGC3200 automatically calculates the CIC based on the values of STID, ETID, and SPCMSN.


Configuring the Trunk Data — PRA

Configuration of the PRA trunk data is special, and therefore is introduced in detail.

//Configure the gateway and H.248 link data.

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

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

//Configure the MGW as the embedded signaling gateway.

ADD ESG: SGNM="PRA_UMG", MGNM=“UMG1";

//Configure the IUA signaling data, where LSNM will be referenced by PRALNK.

ADD IUALKS: LSNM="PRA_UMG", SGNM="PRA_UMG";

ADD IUALNK: MN=1400, LNKNM="PRA_UMG", LSNM="PRA_UMG", LOCPORT=3033, LOCIP1="154.104.3.1", PEERPORT=3033, PEERIP1="154.104.3.204", SCTPPARA=TRUE, QOS=TOS, MONITOR=TRUE;


Configuring the Trunk Data — PRA// Configure the PRA link data. LSNM specifies the name of the IUA link set. BINIFID is one

of the parameters used for interworking between the UGC3200 and the embedded signaling gateway that supports the IUA protocol. BINIFID uniquely identifies the PRA link in the D-channel signaling messages of all PRA subscribers carried by the IUA link set. The UGC3200 supports both the integer-type and text-type interface IDs. In practice, the integer-type interface ID is used preferentially. Description of TID is as follows: TID specifies the E1 slot that will be occupied by the RPA link in the PRA trunk group. In the case of T1 transmission, any timeslot of the T1 circuit can be configured. In the case of E1 transmission, it is recommended that timeslot 16 be configured. In either of the T1 or E1 transmission mode, the signaling circuit number must be set to

the logical circuit number. (For details, see the command description of ADD PRATKC. The value of TID in the ADD PRALNK command is a value between STID and ETID

specified in the ADD PRATKC command. Generally, TID is equal to STID+16. After configuration, this timeslot is used for carry signaling instead of media stream.

ADD PRALNK: PLNAME="PRA_UMG", MN=1000, MGWNAME=“UMG1", TID=1232, LSNM="PRA_UMG", BINIFID=17, SIGT=NET;


Configuring the Trunk Data — PRAConfigure the office direction and route data. (Omitted) Configure the route data. (Omitted)

//Add the number segment for PRA subscribers. ADD DNSEG: P=0, SDN=K'32000000, EDN=K'32000099;

//Add the transmission attributes and call attributes of ISDN subscribers, including the transmission capability, transmission rate, maximum number of B channels, and call forwarding notification mode. Generally, these parameters are set to the default values.

ADD ISDNDAT: ISDNN="PRA";

//Add a PRA subscriber, whose number is within the number segment defined by ADD DNSEG.

ADD PRA: D="32000000", RSN="PRA_NGN", ISDNN="PRA", MN=1000, P=0, CSCNAME="UGC";

//Add the PRA trunk group information, where CDEF (default caller number) is set to the same value of D. The value of D must be set by ADD PRA in advance.

ADD PRATG: TGN="PRA_NGN", MGWNAME=“UMG1", SRN="PRA_NGN", PLNAME="PRA_NGN", CDEF=K'32000000, BTG=13, CSCNAME="UGC";

//Add a PRA circuit. ADD PRATKC: TGN="PRA_NGN", STID=1216, SPCMSN=0, ETID=1247;


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;


Configuring the Trunk Data — BICC

Configuration of the BICC trunk is slightly different from configuration of the SIP trunk. To configure the BICC trunk, you need not add the office direction MGW data and SIP configuration data. The configuration procedure is as follows:

Configure the gateway and H.248 link data. (Omitted) Configure the office direction data. (Omitted) Configure the route data. (Omitted) Add the BICC trunk configuration.

ADD BICCTG: TGN=“BICC_MSX”, MGWNAME=“UMG2”, SRN=“BICC_MSX”, BTG=5, RELRED=NO; // Model with MGWs

ADD BICCTG: TGN=“BICC_MSX”, MGWNAME=“CMN”, SRN=“BICC_MSX”, BTG=5, RELRED=NO; //Model without MGWs. The MGW name is set to CMN. In addition, the MGW named CMN need not be configured.

Add a BICC CIC module. Add a BICC CIC in a certain office direction and configure the BICC CIC on the specified module. When an inter-office call is originated, an unused BICC CIC is selected to identify this call. ADD BICCCICMDU: ON="BICC_MSX", MN=1000, SCIC=1000, ECIC=1100;

Add the BICC SCTP link data. The BICC SCTP link belongs to a specified office direction and is used to carry the BICC signaling. CLNTSVR specifies whether the local office acts as the client or a server. If the local office acts as a client, the peer office must act as a server. If the local office acts as a server, the peer office must act as a client. ADD BICCSCTPLNK: LNKNAME="BICC_MSX", ON="BICC_MSX", LOCIP1="154.104.3.1",

LOCPORT=2911, PEERIP1="154.104.3.3", PEERPORT=2911, CLNTSVR=SERVER, QOS=TOS, QUALITYCHK=NO;


Configuring the Trunk Data — Special Configuration

During trunk selection, a software parameter is available to determine whether

to allow the same-level office alternative routing. Same-level office alternative

routing means the incoming and outgoing trunks are the same trunk. In

practice, to prevent loopback calls, same-level office alternative routing is

generally disabled.

P75 Bit0

Bit 0 of P75 determines whether to allow a trunk call in which the incoming and

outgoing office directions are the same, that is, when a call is routed from the

peer office to the local office through a trunk, whether it is allowed to route the

call to the peer office through the same trunk.

= 0: No

=1: Yes

The default value is 0.


Configuring the Charging Data

Configuring the AP port that is used for interworking with the

iGWB.

Configure the trunk group CDR control data.

Configure the global CDR control data.

Configure the office direction type.

Configure the time zone information.

Configure the CDR number change rules.


Configuring the Charging Data — AP Port

When the UGC3200 serves as a switching office, it must support the charging function of

the iGWB. In this case, you need to configure the AP port information for interworking

with the iGWB.

ADD AP: MN=1000, APMN=1701, APIP1="172.16.129.1", APPORT1=9901;


MN: It specifies the module number of the CCU process. Each CCU can interwork

with the iGWB independently.

APMN: It specifies the AP module number.

APIP1: It specifies the IP address of the active AP module of the iGWB. It is the IP

address of the BASE1 plane.

APPORT1: It specifies the port number of the active AP module of the iGWB.

APIP2 : It specifies the IP address of the standby AP module of the iGWB. It is the

IP address of the BASE2 plane.

APPORT2 : It specifies the port number of the standby AP module of the iGWB.

If there is only one iGWB, configure only APIP1 and APPORT1. You need not

configure APIP2 and APPORT2.


Configuring the Charging Data — CDR Control of the Trunk GroupWhen the UGC3200 serves as a switching office, it can function as a tandem office or a

gateway office, but cannot process services for subscribers. Therefore, the CDR

generation unit of the UGC3200 is designed as a trunk. That is, each trunk can be

configured with its own CDR generation rules independently.

For example, for ISUP trunk group 1 from the MSX to the UGC3200, only the GW

(gateway) CDR and ATTEMPT (call attempt) CDR are generated. For SIP trunk group 2

coming from the UGC3200 to the CSX, only the gateway office CDRs are generated. ADD TKBLCTRL: TGN="MSX_ISUP1_UGC", BCF=GWI-1&ATTEMP-1; ADD TKBLCTRL: TGN=“UGC_ISUP2_CSX", BCF=GWO-1; Description of key parameters:

BCF: It specifies the type of CDR to be generated. When the UGC3200 is

applied, the GW CDR and ATTEMPT CDR are two types of CDRs that account

for the largest proportion of generated CDRs. Therefore, for each trunk, only the

scripts for configuring the GW CDR and ATTEMPT CDR for incoming and

outgoing trunk groups are provided.

By default, the GW CDR is selected for incoming and outgoing trunk groups, and

the ATTEMPT CDR is not selected.


Configuring the Charging Data — Global CDR ControlBesides the GWI, GWO, and ATTEMPT CDRs, the UGC3200 also supports other types of CDRs, such as the CFW (call forwarding), ROAM (roaming), and TRANSIT CDRs. The number of these CDRs, however, is not large. Therefore, the global control mode is adopted for these CDRs. Global CDR control enables configuration of the maximum call duration, alarm threshold of the CDR pool, CDR pool protection, call barring upon outflow of the CDR pool, and size of the CDR pool.

MOD GBILLCTRL: BCF=CFW-1&ROAM-1&TRANSIT-1&ATTEMP-1&SS_ACT-1&FIXED_IN-1&GWO-1&GWI-1, MCT=36000, OAV=50, RAV=30, PTCT=TRUE, BPS=400;

Description of key parameters: BCF: It specifies the type of CDR that can be generated by the UGC3200. Note that the GWO/GWI/ATTEMP

CDR types are in AND relationship with the GWO/GWI/ATTEMP CDR types configured by running ADD TKBLCTRL. The UGC3200 generates GWO/GWI/ATTEMP CDRs only when these CDRs are configured in both MOD GBILLCTRL and ADD TKBLCTRL. Among all the CDR types, CFW, TRANSIT, IN MO, GWO, GWI, and CAMEL LEG CDRs are selected by default, and other types of CDRs are not selected by default.

MCT: It specifies the maximum call duration. If the duration of a call exceeds this value, the UGC3200 releases the call.

PTCT: It specifies whether to enable the global call barring (excepts the emergency call) when the CDR pool is full.

BPS: It specifies the size of the CDR pool. Carriers can predict the size of the CDR pool based on the actual service requirements, and configure this parameter to maximize the memory utilization rate. This method is especially useful when the UGC3200 serves as an MGCF. For example, when the UGC3200 serves as an MGCF, the UGC3200 needs to generate only the RF CDRs, and the common iGWB CDRs are not needed. Therefore, you can set the CDR pool of the iGWB to a smaller value. Note that you must restart the CCU process after re-configuring the CDR pool size.


Configuring the Charging Data — Office Direction TypeDepending on whether the UGC3200 needs to settle charges in a specific direction, the office direction types of the UGC3200 can be set to home network or foreign network. For calls originated or connected by the home network, the UGC3200 generates the TRANSIT CDRs to record the brief information about the current transit call. For calls originated or connected by the foreign network, the UGC3200 generates the GW CDRs to settle charges with the foreign network.

ADD BILLCTRL: OFFICENAME="MSX", OOFFICT=HOMENET, GNO=0; Description of key parameters:

OOFFICT: It specifies the office direction type of the peer office. It can be set to home network or foreign network.

GNO: It specifies the charging control group number. When the UGC functions as an integrated gateway, the network topology could be rather complex. Simply defining the MO office direction as the home network and MT office direction as the foreign network cannot meet the requirements of carriers in terms of GW and TRANSIT CDRs. Therefore, the charging control group number is defined so that you can run SET OFCBLCTRL to forcibly control generation of the GW CDR and TRNASIT CDR for a call.

SET OFCBLCTRL: SRG=0, DRG=10, BILLT=GWI-1&GWO-1; Description of key parameters:

SRG: It specifies the MO charging control group number. DRG: It specifies the MT charging control group number. This command is used to forcibly control generation of the GW CDR and TRNASIT CDR for a call no matter

whether the call is originated by the home or foreign network. The control priority of this command is the highest. For example, if OOFFICT is set to home network by running ADD BILLCTRL, but generation of the GWI CDRs is enabled by running SET OFCBLCTRL, the CDR that is finally generated is the GWI CDR.

It is recommended not to run SET OFCBLCTRL unless necessary.


Configuring the Charging Data — Time Zone Information

The UGC3200 supports multiple-time-zone charging. When CDRs are generated at the end of a call, the UGC3200 adjusts the conversation time in the CDRs based on the time zone information configured for the call sources of the caller and callee and the time zone information of the UGC3200.

//In the CGP MML command window, run the following command to set the time zone information of the UGC3200.

SET TZ: TZONE=E0930, DST=NO;

//In the MML command window of the service NE, run the following command to set the time zone information.

ADD TZDST: TZDSTNAME="EAST8", TIMEZONEFLAG=YES, TIMEZONE=GMT-0800, DSTFLAG=NO;


TZDSTNAME: It specifies the name of the time zone. It is referenced by the call source.

DSTFLAG: It is the daylight saving time flag. It this flag is set to TRUE, the start time of daylight saving time and the time offset must be configured.

//Configure the time zone index during configuration of the call source.

ADD CALLSRC: CSCNAME="MSX", RSSN="MSX", FSN="MSX", TZNAME="EAST8";


Configuring the Charging Data — CDR Number Change Rules

Carriers can change the numbers in the CDRs by using the number

change rules to meet some special requirements. The ADD BILLPROC

command affects only the CDRs, but not the numbers in the outgoing

signaling.

ADD BILLPROC: BLLT=GWI, DNT=CLD, PFX=K'138, NCN="ADD_86";


BLLT: It specifies the type of CDR, in which the number should be

changed.

DNT: It specifies the type of number to be changed.

PFX: It specifies the prefix of the number to be changed. This

parameter supports fuzzy match.



4.1 Basic Concepts




Configuring the Trunk Data — Example of ISUP Trunk ConfigurationScenario Description The UGC3200 interworks with the NGN through ISUP. The ISUP trunks are carried over M3UA. Information related to the UGC3200 is as follows: The IP address is 154.104.3.1. The signaling point

code of the local office is 320030. The number of the port that is used to control the H.248 links of the UMG is 2951. The H.248 links are carried over SCTP. The port number of the M3 signaling link is 2922. The UGC3200 acts as the client of the M3 signaling link.

Information related to the NGN is as follows: The IP address is 154.112.0.10. The signaling point code is 888888. The port number of the M3 signaling link is 2923. The NGN acts as the server of the M3 signaling link.

Information related to the UMG is as follows: The IP address of the virtual gateway is 154.104.3.204. The port number of the H.248 link is 2961.


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

BCUID=0, ENCT=NSUP;

//Configure the H.248 link, which is used to control the UMG. ADD H248LNK: MGWNAME=“UMG_NGN", TRNST=SCTP, LNKNAME=“UMG_NGN",



Configuring the Trunk Data — Example of ISUP Trunk Configuration

//Add a local entity. The local entity is the UGC3200. The signaling point code is 320030.

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

//Add a destination entity. The destination entity is the NGN. The signaling point code is 888888.

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

//Add a link set. Note that WM (work mode ) must be set to IPSP.

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

//Add an M3 link. Pay attention to the settings of the IP address, port number, and work mode (client/server). In this example, the IP address of the UGC3200 is 154.104.3.1 and the port number is 2922. The IP address of the NGN is 154.112.0.10 and the port number is 2923. The UGC3200 acts as the client of the M3 link, whereas the NGN acts as the server.

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

//Add an M3 route.

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


Configuring the Trunk Data — Example of ISUP Trunk Configuration

//Add an office direction, where DPC is 888888 (the signaling point code of the NGN). ADD OFC: ON="ISUP_NGN", OOFFICT=MSC, DOL=LOW, BOFCNO=0,

OFCTYPE=COM, SIG=NONBICC/NONSIP, DPC1=“888888", ISEACM=TRUE;

//Add the subroute and route information. ADD SRT: SRN="ISUP_NGN", ON="ISUP_NGN"; 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;

//Add the ISUP trunk data. ADD N7TG: TGN="ISUP_NGN", MGWNAME=“UMG_UGC", CT=ISUP,

SRN="ISUP_NGN", BTG=1, SOPC="320030", SDPC=“888888", CSCNAME="UGC", CC=NO, RELRED=NO;

//Add an ISUP circuit, where SCIC and ECIC must be consistent with the CIC on the NGN and TID must consistent with the TID configured on the UMG. The CIC is transferred through signaling. Therefore, CIC is a logical concept and the CIC settings must be consistent between two switching devices. The TID is transferred through the media stream. Therefore, the TID must be negotiated between the gateway control (UGC3200 or other softswitches) and the gateway (UMG). TID is a physical concept. It is the ID of the timeslot and therefore must be mapped to the timeslot of the E1.

ADD N7TKC: MN=1000, TGN="ISUP_NGN", SCIC=0, ECIC=31, TID=1152, SCF=TRUE;


Configuring the Trunk Data — Example of PRA Trunk Configuration

//Configure the gateway and H.248 link. The IP address of the UGC3200 is 154.104.3.1 and the port number is 2952. The virtual gateway IP address of the UMG is 154.104.3.204 and the port number is 2962.

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

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

//Configure the MGW as the embedded signaling gateway.

ADD ESG: SGNM="PRA_UMG", MGNM=“UMG1";

//Configure the IUA signaling data, where LSNM is referenced by PRALNK. The port number of the UGC3200 is 3033, and the port number of the peer UMG is 3034.

ADD IUALKS: LSNM="PRA_UMG", SGNM="PRA_UMG";

ADD IUALNK: MN=1400, LNKNM="PRA_UMG", LSNM="PRA_UMG", LOCPORT=3033, LOCIP1="154.104.3.1", PEERPORT=3034, PEERIP1="154.104.3.204", SCTPPARA=TRUE, QOS=TOS, MONITOR=TRUE;



//Configure the PRA link data. Assume that the TID of the E1 on the UMG is 1216

and the 16th timeslot is selected to carry the signaling. BINIFID is set to 17. In

addition, BINIFID is set to 17 on the UMG by running ADD Q921LNK.

ADD PRALNK: PLNAME="PRA_UMG", MN=1000, MGWNAME=“UMG1",

TID=1232, LSNM="PRA_UMG", BINIFID=17, SIGT=NET;

Configure the office direction and route data. (Omitted)

//Add the number segment for PRA subscribers.

ADD DNSEG: P=0, SDN=K'32000000, EDN=K'32000099;

//Add the transmission attributes and call attributes of ISDN subscribers, including

the transmission capability, transmission rate, maximum number of B channels,

and call forwarding notification mode. Generally, these parameters are set to

the default values.

ADD ISDNDAT: ISDNN="PRA";



//Add a PRA subscriber, whose number is within the number segment defined by

ADD DNSEG.

ADD PRA: D="32000001", RSN="PRA_NGN", ISDNN="PRA", MN=1000, P=0,

CSCNAME="UGC";

//Add the PRA trunk group information, where CDEF (default caller number) is set

to the same value of D. The value of D must be set by ADD PRA in advance.

ADD PRATG: TGN="PRA_NGN", MGWNAME=“UMG1", SRN="PRA_NGN",

PLNAME="PRA_NGN", CDEF=K'32000001, BTG=13, CSCNAME="UGC";

//Add a PRA circuit. The values of STID and ETID must be consistent with the value

of TID configured on the UMG.

ADD PRATKC: TGN="PRA_NGN", STID=1216, SPCMSN=0, ETID=1247;


Configuring the Trunk Data — Example of SIP Trunk Configuration

Scenario Description

The UGC3200 interworks with the NGN through SIP trunks. The IP address of the UGC3200 is 154.104.3.1. The IP address of the NGN is 154.112.0.10. As the SIP of the UGC3200 can control the UMG, the IP address of the UMG is 154.104.3.204. The port number of the H.248 link of the UMG is 2961, and the port number of the H.248 link of the UGC3200 is 2951.


//Add 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",


//Add the office direction. Pay attention to the setting of SIG. In this example, the UGC3200 serves as a switch to interwork with the NGN. The UGC3200 does not serve as an MGCF. Therefore, SIG is set to NGN. If the UGC3200 serves as an MGCF to interwork with the IMS, SIG must be set to IMS.

ADD OFC: ON="SIP_NGN", OOFFICT=NATT, DOL=SAME, BOFCNO=2, OFCTYPE=COM, SIG=NGN, AN="0";


Configuring the Trunk Data — Example of SIP Trunk Configuration

//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

Or, ADD OFCMGW: ON=“SIP_MSX”, MGWNAME=“CMN”, DESC=“NO MGW”; -- Model

without MGWs

//Configure the route and prefix. (Omitted)

//Configure the SIP protocol distribution capability. Assume that the module number of the BSG process is 1400.

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

//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;


Configuring the Trunk Data — Example of BICC Trunk Configuration

Configuration of the BICC trunk is slightly different from configuration of the SIP trunk. To configure the BICC trunk, you need not add the office direction MGW data and SIP configuration data. The configuration procedure is as follows:

Add the BICC trunk configuration. ADD BICCTG: TGN=“BICC_MSX”, MGWNAME=“UMG2”, SRN=“BICC_MSX”, BTG=5,

RELRED=NO; // Model with MGWs ADD BICCTG: TGN=“BICC_MSX”, MGWNAME=“CMN”, SRN=“BICC_MSX”, BTG=5,

RELRED=NO; //Model without MGWs. The MGW name is set to CMN. In addition, the MGW named CMN need not be configured.

Add a BICC CIC module. Add a BICC CIC in a certain office direction and configure the BICC CIC on the specified module. When an inter-office call is originated, an unused BICC CIC is selected to identify this call. ADD BICCCICMDU: ON="BICC_MSX", MN=1000, SCIC=1000, ECIC=1100;

Add the BICC SCTP link data. The BICC SCTP link belongs to a specified office direction and is used to carry the BICC signaling. CLNTSVR specifies whether the local office acts as the client or a server. If the local office acts as a client, the peer office must act as a server. If the local office acts as a server, the peer office must act as a client. ADD BICCSCTPLNK: LNKNAME="BICC_MSX", ON="BICC_MSX",

LOCIP1="154.104.3.1", LOCPORT=2911, PEERIP1="154.104.3.3", PEERPORT=2911, CLNTSVR=SERVER, QOS=TOS, QUALITYCHK=NO;


Configuring the Charging Data — Configuration ExampleScenario Description1) The module number of the CCU process of the UGC3200 is 1000. The IP address used for the communication

between the UGC3200 and the iGWB is 172.16.129.1 and the port number is 9901. The standby IP address is 172.17.129.1, and the standby port number is 9901. The AP module number is 1701.

2) The UGC3200 serves as the integrated gateway office of the CDMA and fixed networks. It relays calls routed from the CDMA and fixed networks. The UGC3200 needs to meet the following CDR-specific requirements:

Generating TRANSIT CDRs for calls between CDMA subscribers and for calls between fixed network subscribers Generating GWO CDRs for calls between the CDMA network and the fixed network Supporting both the GWI and GWO CDRs Generating ATTEMPT CDRs for failed calls Supporting the CFW CDRs because the UGC3200 serves as the gateway office and may trigger the call forwarding

service of the CDMA networkThe UGC3200 is not required to support other types of CDRs.

3) The CDR pool overload alarm is generated when the available size of the CDR pool is smaller than 50% of the total size. The CDR pool overload recovery alarm is generated when the available size of the CDR pool exceeds 70% of the total size.

Configuration Example//Configure the AP port information for interworking with the iGWB. ADD AP: MN=1000, APMN=1701, APIP1="172.16.129.1", APPORT1=9901, APIP2="172.17.129.1", APPORT2=9901; //Enable the UGC3200 to support the GWI, GWO, TRANSIT, ATTEMPT, and CFW CDRs. Set the CDR pool alarm

thresholds. ADD TKBLCTRL: TGN="CSX_IN", BCF=GWI-1&GWO-1&ATTEMP-1; ADD TKBLCTRL: TGN="CSX_OUT", BCF=GWI-1&GWO-1&ATTEMP-1; ADD TKBLCTRL: TGN=“NGN_IN", BCF=GWI-1&GWO-1&ATTEMP-1; ADD TKBLCTRL: TGN=“NGN_OUT", BCF=GWI-1&GWO-1&ATTEMP-1; MOD GBILLCTRL: BCF=CFW-1&TRANSIT-1&ATTEMP-1&GWO-1&GWI-1, OAV=50, RAV=70;


Configuring the Charging Data — Configuration Example

//Set the CSX office direction type to home network and the charging control group

number to 0.

ADD BILLCTRL: OFFICENAME="CSX", OOFFICT=HOMENET, GNO=0;

//Set the NGN office direction type to home network and the charging control group

number to 1.

ADD BILLCTRL: OFFICENAME=“NGN", OOFFICT=HOMENET, GNO=1;

// Configure the office direction charging control table so that the TRANSIT CDRs

are generated for calls between CSX subscribers and for calls between NGN

subscribers, and GW CDRs for calls between the CSX and the NGN.

SET OFCBLCTRL: SRG=0, DRG=0, BILLT=GWI-0&GWO-0&TRANSIT-1;





Summary

Configuration flow and

procedure of the public data

SummarySummary






5.5. Configuration of the Interworking DataConfiguration of the Interworking Data



5.5. Configuration of the Configuration of the Interworking DataInterworking Data

5.1 Basic Concepts




Basic Concepts Tandem office

When the UGC3200 serves as a tandem office, it does not need to query the MSRN. It only relays calls to the terminating office.

Gateway officeWhen the UGC3200 serves as a gateway office, it may need to query the MSRN and the subscription data of the caller and callee and send the MSRN to the terminating office for call connection. In addition, the UGC3200 may trigger the IN services. The UGC3200 needs to interwork with the HLR and SCP in the GSM network, the HLR and SCP in the CDMA network, and the SCP in the fixed network.

MGCF When the UGC3200 serves as an MGCF, it must be connected to the CS and IMS domains. In addition, it

must support RF charging and interwork with the CCF. Charging Collection Function (CCF)

The CCF is located between the IMS entities and the charging center. It implements the offline charging function. The UGC3200 does not have the CCF function. The CCF functions are as follows: The CCF collects the charging information from various IMS entities (such as the MGCF, SCSCF, and AS)

through the Rf interface by using the Diameter protocol. The CCF converts the format of the charging information, generates the Charging Data Record (CDR)

based on the charging information, and then submits the CDRs to the charging center. When the charging center is busy, the CCF buffers the CDRs.

Integrated gatewayWhen the UGC3200 serves as an integrated gateway office, the UGC3200 must support interworking with the HLR and SCP in the GSM network, the HLR and SCP in the CDMA network, and the SCP in the fixed network. When the UGC3200 and the MGCF are integrated, the UGC3200 must also interwork with the CCF.


Basic Concepts Global title (GT)

The GT is generally a dialed number, for example, an international telephone number, or a national telephone number. It is used when the originating node does not know the network address of the terminating node. As the MTP cannot route the call based on the GT, the SCCP must first translate the GT of the callee into the DPC, DPC+SSN, or DPC+GT, and then send the translation result to the MTP. In addition, the SCCP must notify the next-hop signaling point of the numbering scheme of the GT. In a word, the function of the GT is to translate the number into the signaling point, based on which the target device is found.

Rules for configuring the GT data

The GT data is mainly used in the signaling flow during location update, call proceeding, and inter-office handover of MSs/UEs. As the UGC3200 does not serve as an end office, the GT data does not involve the location update of MSs/UEs.

Generally, the translation result type is configured as “DPC+GT” for the signaling transferred by the STP; the translation result type is configured as “DPC” for the signaling sent through direct links.

The signaling from the local office to the MSC/HLR that is located in the same province or in another province is generally transferred by the STP through the “DPC+GT” addressing.


5. Configuration of the 5. Configuration of the Interworking DataInterworking Data

5.1 Basic Concepts




Configuring the M3 Signaling Link

When the UGC3200 interworks with the HLR and SCP in the GSM and CDMA networks, the M3 link must be configured first. The configuration method is the same. The following takes the HLR in the GSM network as an example.

//Add a local entity. OPC specifies the local SPC, that is, the SPC of the UGC3200.

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

//Add a destination entity. DPC specifies the destination SPC, that is, the SPC of the HLR or SCP. When the UGC3200 interworks with another device through M3 links, DPC is set to the SPC of the peer device.

ADD M3DE: DENM=“GHLR", LENM="UGC_GHLR", DPC="111111", DET=AS;

//Add a link set.

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

//Add an M3 link.

ADD M3LNK: LNKNM="GHLR", LOCIP1="154.104.2.6", LOCPORT=2912, PEERIP1="164.137.64.26", PEERPORT=2912, CS=C, LSNM="GHLR";

//Add a route.

ADD M3RT: RTNM="GHLR", DENM=“GHLR", LSNM="GHLR";


Configuring the SCCP Layer Data Between the UGC3200 and the HLR in the GSM Network

//Add an SCCP DSP from the UGC3200 to the HLR. The SPC of the HLR is 111111. Note that DPNM (DSP name) in ADD SCCPDSP is different from DENM (destination entity name) defined in ADD M3DE . These two parameters are not referenced by each other.

ADD SCCPDSP: DPNM=“G_HLR", NI=NAT, DPC="111111", OPC="444444";

//Add an SCCP subsystem of the HLR. ADD SCCPSSN: SSNNM=“GHLR_HLR", NI=NAT, SSN=HLR, SPC="111111",

OPC="444444";

//Add an SCCPGT group. ADD SCCPGTG: GTGNM="LOCAL", CFGMD=ALL, SERVNM="LOCAL";

//Add the SCCP GT data. When a subscriber serves as a callee, an ordinary GT (MSIDSN GT) must be configured. In the Send-Route-Information (SRI) flow, the GT of the HLR is obtained based on the MSISDN of the callee. Based on the obtained GT, the related HLR is found.

ADD SCCPGT: GTNM=“GHLR_NUMBER”, GTI=GT4, NUMPLAN=LSPC2, ADDR=K‘861390755, RESULTT=LSPC2, SPC=“111111”, GTGNM=“UGC”;

//When the local office analyzes the MSRN obtained from the GHLR, it needs to query the configured MSC GT of the local office. The MSC GT of the local office is configured in the INOFFMSC table. For details about the configuration, see the description about SET INOFFMSC.


Configuring the SCCP Layer Data Between the UGC3200 and the HLR in the CDMA Network

//Add an SCCP DSP from the UGC3200 to the HLR. The SPC of the HLR is 222222. ADD SCCPDSP: DPNM=“C_HLR", NI=NAT, DPC=“222222", OPC="444444";// Add an SCCP subsystem of the HLR. ADD SCCPSSN: SSNNM=“CHLR_HLR", NI=NAT, SSN=HLR, SPC=“222222",

OPC="444444"; ADD SCCPSSN: SSNNM="CHLR_SCMG", NI=NAT, SSN=SCMG, SPC="222222",

OPC="444444";// Add an SCCPGT group. ADD SCCPGTG: GTGNM="LOCAL", CFGMD=ALL, SERVNM="LOCAL";//Add the SCCP GT data. When a subscriber serves as a callee, an ordinary GT (MDN GT) must

be configured. In the Send-Route-Information (SRI) flow, the GT of the HLR is obtained based on the MDN of the callee. Based on the obtained GT, the related HLR is found.

ADD SCCPGT: GTNM=“CHLR_NUMBER”, GTI=GT4, NUMPLAN=LSPC2, ADDR=K‘8613301, RESULTT=LSPC2, SPC=“222222”, GTGNM=“UGC”;

//When the local office performs the second number analysis, it needs to query the SIN GT of the local office. When a subscriber is called, the MSC sends an SRI request to the home HLR of the callee. The HLR then obtains the TLDN from the VLR serving the callee. After the HLR obtains the TLDN, it sends a message to the MSC. The callee address in this message contains the SIN GT of the HLR. The MSC checks whether the SIN GT is the SIN GT of the local office. If the SIN GT is the SIN GT of the local office, the MSC initiates paging. Assume that the SIN of the HLR is 4600309131300000.

ADD SCCPGT: GTNM=“CHLR_SIN", GTI=GT4, NUMPLAN=LAND, ADDR=K'4600309131300000, RESULTT=LSPC2, SPC=“222222", GTGNM=“LOCAL";


Configuring the SCCP Layer Data Between the UGC3200 and the SCP in the GSM Network

//Add an SCCP DSP from the UGC3200 to the SCP in the GSM network. The SPC of the SCP is 333333.

ADD SCCPDSP: DPNM=“GHLR", NI=NAT, DPC=“333333";// Add an SCCP subsystem. ADD SCCPSSN: SSNNM=“GSCP_CAP", NI=NAT, SSN=CAP, SPC=“333333",

OPC=“444444"; ADD SCCPSSN: SSNNM=“GSCP_SCMG", NI=NAT, SSN=SCMG,

SPC=“333333", OPC=“444444"; ADD SCCPSSN: SSNNM=“GSCP_GSMSCF", NI=NAT, SSN=GSMSCF,

SPC=“333333", OPC=“444444"; SCMG: It specifies the SCCP management subsystem. CAP: It specifies the CAMEL application part. GSMSCF: It specifies the GSM service control center.

// Add an SCCPGT group. ADD SCCPGTG: GTGNM="LOCAL", CFGMD=ALL, SERVNM="LOCAL";//Add the SCCP GT data, where ADDR (GT address) is 861390755 and RESULTT

(translation result type) is SPC. ADD SCCPGT: GTNM=“GSCP", GTI=GT4, NUMPLAN=ISDN,

ADDR=K'861390755, RESULTT=LSPC2, SPC=“333333", GTGNM=“UGC";


Configuring the SCCP Layer Data Between the UGC3200 and the SCP in the CDMA Network

//Add an SCCP DSP from the UGC3200 to the SCP in the CDMA network. The

SPC of the SCP is 100100.

ADD SCCPDSP: DPNM=“CHLR", NI=NAT, DPC=“100100";

// Add an SCCP subsystem.

ADD SCCPSSN: SSNNM=“CSCP_SCMG", NI=NAT, SSN=SCMG,

SPC=“100100", OPC=“444444";

ADD SCCPSSN: SSNNM=“CSCP_CSCP", NI=NAT, SSN=CSCP,

SPC=“100100", OPC=“444444";

// Add an SCCPGT group.

ADD SCCPGTG: GTGNM="LOCAL", CFGMD=ALL, SERVNM="LOCAL";

//Add the GT translation data of the SCP SIN.

ADD SCCPGT: GTNM=“CSCP", GTI=GT4, ADDR=K'460030912343000,

NUMPLAN=LAND, RESULTT=LSPC2, SPC="100100", GTGNM="LOCAL";


Configuring the SCCP Layer Data Between the UGC3200 and the SCP in the Fixed Network

//Add an SCCP DSP from the UGC3200 to the SCP in the fixed network. The SPC of the SCP is 100011 .

ADD SCCPDSP: DPNM=“FSCP", NI=NAT, DPC="100011";

// Add an SCCP subsystem.

ADD SCCPSSN: SSNNM=“FSCP_INAP", NI=NAT, SSN=INAP, SPC="100011", OPC=“444444";

ADD SCCPSSN: SSNNM=“FSCP_SCMG", NI=NAT, SSN=SCMG, SPC="100011", OPC=“444444";

//Configure the SCP address information.

ADD SCPINFO: SCP=“FSCP_INAP", INVER=INAP_CH, RT=DPC, DPC="100011";

// Configure the SSP address information. The SSP is the UGC3200.

ADD SSPINFO: SCP="FSCP", RT=DPC, OPC=“444444";


MGCF Scenario

When the UGC3200 serves as an MGCF and interworks with the CS and IMS domains, the UGC3200 must support the RF charging. Therefore, the UGC3200 must interwork with the CCF.

Data configuration on the UGC3200 is as follows: //Modify the local device data.

MOD DMLOC: HN="UGC.HUAWEI.COM"; //Add the peer CCF data.

ADD DMDEV: UGCID=0, DEVID=0, DEVTP=CCF, DN="CCF", HN="LSIG.HUAWEI.COM", RN="HUAWEI.COM"; //Add a link set.

ADD DMLKS: DEVID=0, LKSID=0, LKSN="UGC.HUAWEI.COM"; //Add a link

ADD DMLNK: DEVID=0, LKSID=0, LNKID=0, LNKN="UGC.HUAWEI.COM", MID=1400, IPTP=IPV4, LIP41="191.139.6.100", LPORT=3866, PIP41="154.28.113.100", PPORT=13868; //Modify the size of the RF CDR pool. The unit is M. After modifying the data

of the RF CDR pool, you must restart the CCU process.

MOD RFPARAM: PLSZ=200;


5.5. Configuration of the Configuration of the Interworking DataInterworking Data

5.1 Basic Concepts




Example of Data Configuration for Interworking Between the UGC3200 and SCP/HLR

The following attachment provides a script that can be automatically

installed in the development environment. It contains the configuration data

used for interworking between the UGC3200 and the SCP/HLR in the GSM

or CDMA network and for interworking between the UGC3200 and the

SCP in the fixed network.


Summary

Configuration flow and procedure

of the interworking data

SummarySummary







6.6. Configuration of the Service DataConfiguration of the Service Data


6.6. Configuration of the Service Configuration of the Service

DataData

6.1 Basic Concepts


and Example


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.


6. Configuration of the Service 6. Configuration of the Service

DataData

6.1 Basic Concepts


and Example


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


CRBT

The UGC3200 supports the CRBT service in the GSM and CDMA

networks.

The CRBT service in the GSM network supports the CRBT of the

original MSX.

The CRBT service in the CDMA network is designed based on the

CRBT triggered in GMSC SS_CODE mode in the GSM network. It

supports only the serial CRBT mode. In addition, the CRBT number

must be AIP + called number.


CRBT — CRBT Triggered in GMSC SS_CODE Mode in the GSM Network

Scenario: Assume that subscriber A (13313121201) of the CDMA network calls subscriber B (15912343301) of the GSM network. Subscriber B has subscribed to the CRBT service that is triggered by the HLR based on the SS-CODE. The trigger value is 24. The roaming number of subscribe B is 861378004442. The CRBT access code is 666888. The CRBT number is in the AIP+MSISDN+MSRN format. The trigger mode is TOAIP (Route to ring back tone service center). Assume that the trunk from the UGC3200 to other offices and the connections between the GHLR and the AIP have been configured.

Add the call prefix data, where Prefix is 159, Service attribute is MNTT (PLMN national toll MSC), and Called number type is MS (MSISDN). When subscriber A calls subscriber B, the subscription information and roaming number of subscriber B can be obtained from the GHLR.

ADD CNACLD: PFX=K'159, CSA=MNTT, RSNAME="ISUP_MSX", MINL=4, MAXL=24, ICLDTYPE=MS; After the UGC3200 sends the number of subscriber B to the GHLR, the GHLR sends the SS_CODE and

MSRN through the MP_CC_ROUTING_DATA message to the UGC3200. To trigger the CRBT service properly, add the color ring service configuration data on the UGC3200, where Called number format is MSISDNMSRN (AIP+MSISDN+MSRN), and Ring back processing type is TOAIP (Route to ring back tone service center). ADD RBTCTRL: CRST=SPEECH, CRTT=GSSCODE, CRTV=24, CRPT=TOAIP, AIPAC=K'666888, CLDFMT=MSISDNMSRN, ORGCLDFMT=OCLDUNUSED;

To send the MSRN to the VMSC in the GSM network for call connection, the called number type of the MSRN prefix must be set to MSRN and the service attribute must be set to NTT (National toll) or MITT (PLMN international toll MSC). In addition, the called number type of the CRBT number prefix must be set to PSTN and the call must be routed to the AIP.ADD CNACLD: PFX=K'86137, CSA=MITT, RSNAME="ISUP_MSX", MINL=4, MAXL=24, ICLDTYPE=MSRH;ADD CNACLD: PFX=K'666888, CSA=NTT, RSNAME="SIP_AIP", MINL=4, MAXL=24, ICLDTYPE=PS;The CRBT service in the GSM network can be triggered in multiple modes. Descriptions of these trigger modes are omitted. Configuration of all these trigger modes is related to ADD RBTCRTL. For details about other trigger modes, see the documents delivered with the UGC3200 product.


CRBT — GMSC CRBT Trigger Mode of the CDMA NetworkThe GMSC CRBT trigger mode of the CDMA network is different from the CRBT trigger mode of the GSM network. To trigger the CRBT service in the CDMA network, the CHLR or CSCP must send CFIE (CRBT indication flag) and ROUTDGTS (CRBT access code) to the UGC3200. In the CDMA network, the RBTCRTL table need not be configured. In addition, the number sent to the AIP supports only one format: AIP + called number. Assume that subscriber A (15912343301) of the CDMA network calls subscriber B (13313121201) of the GSM network. Subscriber B has subscribed to the CRBT service on the HLR. The CRBT access code is 666999. The roaming number of subscriber B is 861308004442.

Add the call prefix data, where Prefix is 133, Service attribute is MNTT (PLMN national toll MSC), and Called number type is MDN. When subscriber A calls subscriber B, the subscription information and roaming number of subscriber B can be obtained from the CHLR.ADD CNACLD: PFX=K'133, CSA=MNTT, RSNAME="ISUP_CSX", MINL=4, MAXL=24, ICLDTYPE=GCT_MDN;

After the UGC3200 sends the number of subscriber B to the CHLR, the CHLR sends CFIE, ROUTDGTS, and TLDN to the UGC3200 through the MP_CC_LOCREQ_RSP message. On the UGC3200, you only need to configure the prefix sent to the AIP and the prefix sent to the VMSC in the CDMA network.ADD CNACLD: PFX=K'86130, CSA=NTT, RSNAME="ISUP_CSX", MINL=4, MAXL=24, ICLDTYPE=TLDN;ADD CNACLD: PFX=K'666888, CSA=NTT, RSNAME="SIP_AIP", MINL=4, MAXL=24, ICLDTYPE=PS;


Common CRBT

The common CRBT is a feature migrated from the fixed network. Some

carriers require that the MT CRBT service be implemented with the limited

investment. In this case, the common CRBT is a good choice.

The common CRBT is similar to a tone playing function. The customized

ringback tone replaces the normal ringback tone through call prefix

processing and is played to the caller. The customized ringback tone

played is determined by the carrier. Subscribers cannot choose the tone.

The common CRBT is played by the gateway.

The common CRBT aims to replace the normal ringback tone of the callee.

When the tone should be played at the callee side, the UGC3200 does not

trigger the common CRBT service.

The common CRBT can be implemented regardless of the network type.

The common CRBT is implemented through call prefix processing.


Common CRBT

ADD CNACLD: PFX=K'86130, CSA=MNTT, RSNAME="SIP_CSX",

MINL=4, MAXL=24, ICLDTYPE=GCT_TLDN, DNPREPARE=TRUE;

ADD PFXPRO: CSCNAME="UGC", PFX=K'86130, STF=NSDT,

PT=DONTPROC, COMMONCRBT=YES,

COMMONCRBTTONE=TID29;

During call prefix analysis, DNPREPARE (DN processing flag) is set to

TRUE.

During call prefix processing, COMMONCRBT is set to TRUE,

indicating that the common CRBT should be triggered.

COMMONCRBTTONE (Common CRBT tone type) is also set.

COMMONCRBTTONE can be set to any value within the value range.


Tone Playing

Besides the IN tone playing in the GSM and CDMA network, the UGC3200 also supports playing the ANNLIST tone in the CDMA network, playing the forwarding notification tone to the caller upon call forwarding, playing the call prefix processing tone, and playing the failure tone.

Playing the forwarding notification tone

ADD REDRCTANA: PFX=K'138, RT=CDMA_CFNA, PTMOD=PRWTH_TN, PT=DONTPROC;

RT: It specifies the forwarding type. It contains information about the network where call forwarding occurs and the specific type of call forwarding.

PTMOD: it specifies the tone playing mode. The values are NST_TN (Not play tone) PRWTH_TN (Play tones while connecting calls), and PRAFT_TN (Connect calls after playing tones).

PT: It specifies the processing type. In the case of tone playing upon call forwarding, PT must be set to DONTPROC.

Playing the call prefix processing tone

ADD PFXPRO: CSCNAME="UGC", PFX=K'138, STF=SDT, TT=TID7, PT=DONTPROC; Playing the failure tone

ADD CFPRO: FCC=CV13, FSNAME="UGC", PT=SIG, TT=TID5;

FSNAME: It specifies the failure source name. It corresponds to the failure source name defined in ADD CALLSRC.

Thank youwww.huawei.com

Documents

¡¾UGC3200 C03¡¿MGCF Data Configuration-20091020-A-1.0