01-07 Configuring Trunk Data

U-SYS SoftX3000 Operation Manual – Interworking Data Configuration Contents

Issue 03 (2006-12-20) Huawei Technologies Proprietary i

Contents

7 Configuring Trunk Data...........................................................................................................7-1 7.1 Related Concepts...........................................................................................................................................7-4

7.1.1 SIP Trunk .............................................................................................................................................7-4 7.1.2 H.323 Trunk .........................................................................................................................................7-5 7.1.3 No. 7 Trunk ..........................................................................................................................................7-8 7.1.4 R2 Trunk ..............................................................................................................................................7-9 7.1.5 PRA Trunk .........................................................................................................................................7-12 7.1.6 AT0 Trunk ..........................................................................................................................................7-14 7.1.7 V5 Trunk ............................................................................................................................................7-15

7.2 Configuring SIP Trunk Data........................................................................................................................7-16 7.2.1 Overview............................................................................................................................................7-16 7.2.2 Adding SIP Trunk Group ...................................................................................................................7-18 7.2.1 Adding IP Address Pair of SIP Trunk Group......................................................................................7-27

7.3 Configuring H.323 Trunk Data ...................................................................................................................7-29 7.3.1 Overview............................................................................................................................................7-29 7.3.2 Adding Virtual IP List (Optional).......................................................................................................7-31 7.3.3 Adding H.323 Trunk Group ...............................................................................................................7-32

7.4 Configuring No. 7 Trunk Data ....................................................................................................................7-39 7.4.1 Overview............................................................................................................................................7-39 7.4.2 Adding No. 7 Trunk Group ................................................................................................................7-42 7.4.3 Adding No. 7 Trunk Circuit ...............................................................................................................7-60 7.4.4 Adding Carrier Access Code (Optional) ............................................................................................7-62 7.4.5 Adding Carrier Selection Code (Optional).........................................................................................7-64 7.4.6 Adding Originating Network ID (Optional).......................................................................................7-65 7.4.7 Adding PCM Port (Optional) .............................................................................................................7-65

7.5 Configuring R2 Trunk Data.........................................................................................................................7-67 7.5.1 Overview............................................................................................................................................7-67 7.5.2 Adding R2 Incoming Caller Category Conversion (Optional)...........................................................7-71 7.5.3 Adding R2 Outgoing Caller Category Conversion (Optional) ...........................................................7-72 7.5.4 Adding CAS Signaling Configuration ...............................................................................................7-73 7.5.5 Adding R2 Trunk Group ....................................................................................................................7-75 7.5.6 Adding R2 Trunk Circuit....................................................................................................................7-91

Contents U-SYS SoftX3000

Operation Manual – Interworking Data Configuration

ii Huawei Technologies Proprietary Issue 03 (2006-12-20)

7.5.7 Adding R2 Trunk Group Caller Number Segment (Optional) ...........................................................7-92 7.6 Configuring PRA Trunk Data......................................................................................................................7-93

7.6.1 Overview............................................................................................................................................7-93 7.6.2 Adding PRA Trunk Group..................................................................................................................7-96 7.6.3 Adding PCM Port (Optional) ...........................................................................................................7-103 7.6.4 Adding PRA Trunk Circuit...............................................................................................................7-104

7.7 Configuring AT0 Trunk Data.....................................................................................................................7-105 7.7.1 Overview..........................................................................................................................................7-105 7.7.2 Adding AT0 Trunk Group ................................................................................................................7-107 7.7.3 Adding AT0 Trunk Circuit................................................................................................................7-115

7.8 Configuring V5 Trunk Data ......................................................................................................................7-116 7.8.1 Overview..........................................................................................................................................7-116 7.8.2 Adding V5 Trunk Group ..................................................................................................................7-118 7.8.3 Adding V5 Trunk Circuit .................................................................................................................7-119

7.9 Configuring Trunk Group Bearer Data......................................................................................................7-121 7.9.1 Overview..........................................................................................................................................7-121 7.9.2 Adding TOS Changing Index (Optional) .........................................................................................7-123 7.9.3 Adding Trunk Group Bearer ............................................................................................................7-125 7.9.4 Adding Trunk Group Bearer Index ..................................................................................................7-127

7.10 Other Commands ....................................................................................................................................7-128 7.10.1 Adding Trunk Group Append Configuration .................................................................................7-128 7.10.2 Adding Caller Category Transform Index......................................................................................7-132 7.10.3 Adding Internal Caller Category Transform...................................................................................7-133 7.10.4 Adding Protocol Cause Value Convert...........................................................................................7-134 7.10.5 Adding Release Cause Value Convert............................................................................................7-135

U-SYS SoftX3000 Operation Manual – Interworking Data Configuration Figures

Issue 03 (2006-12-20) Huawei Technologies Proprietary iii

Figures

Figure 7-1 Data configuration procedure ...........................................................................................................7-3

Figure 7-2 H.323 plain trunk ..............................................................................................................................7-6

Figure 7-3 H.323 GW trunk ...............................................................................................................................7-7

Figure 7-4 H.323 GK trunk ................................................................................................................................7-7

Figure 7-5 H.323 outer GK trunk .......................................................................................................................7-8

Figure 7-6 AT0 trunk networking .....................................................................................................................7-15

Figure 7-7 Parameter referencing relation of the No. 7 trunk data...................................................................7-41

Figure 7-8 Parameter referencing relation of the R2 trunk data .......................................................................7-70

Figure 7-9 Parameter referencing relation of the PRA trunk data ....................................................................7-95

Figure 7-10 Parameter referencing relation of the AT0 trunk data .................................................................7-107

Figure 7-11 Parameter referencing relation of the V5 trunk data ...................................................................7-118

Figure 7-12 Parameter referencing relation of the trunk group bearer data....................................................7-123

Figure 7-13 Bit structure of TOS....................................................................................................................7-124

Tables U-SYS SoftX3000


iv Huawei Technologies Proprietary Issue 03 (2006-12-20)

Tables

Table 7-1 Examples of SIP URL ........................................................................................................................7-5

Table 7-2 Details of the forward signaling and the backward signaling.............................................................7-9

Table 7-3 Meanings of the signaling combinations ..........................................................................................7-10

Table 7-4 Analysis of the work mode of the PRA trunk group.........................................................................7-13

Table 7-5 Parameter referencing relation between the SIP trunk data and other data.......................................7-16

Table 7-6 Preparations for configuring the SIP trunk data................................................................................7-17

Table 7-7 Steps for configuring the SIP trunk data...........................................................................................7-17

Table 7-8 Parameter referencing relation between H.323 trunk data and other................................................7-29

Table 7-9 Preparations for configuring the H.323 trunk data ...........................................................................7-30

Table 7-10 Steps for configuring the H.323 trunk data.....................................................................................7-30

Table 7-11 Parameter referencing relation between the No. 7 trunk data and other data..................................7-39

Table 7-12 Preparations for configuring the No. 7 trunk data ..........................................................................7-40

Table 7-13 Steps for configuring the No. 7 trunk data......................................................................................7-41

Table 7-14 Applications of the parameter .........................................................................................................7-50

Table 7-15 Details of two code sending modes ................................................................................................7-51

Table 7-16 Details of IRI and ORI....................................................................................................................7-54

Table 7-17 Details of tables ..............................................................................................................................7-55

Table 7-18 Different operations based on different conditions.........................................................................7-57

Table 7-19 Parameter referencing relation between the R2 trunk data and other .............................................7-67

Table 7-20 Preparations for configuring the R2 trunk data...............................................................................7-68

Table 7-21 Steps for configuring the R2 trunk data..........................................................................................7-69

Table 7-22 Certain common channel associated signaling types......................................................................7-74

Table 7-23 Parameter referencing relation between the PRA trunk data and other data...................................7-94

Table 7-24 Preparations for configuring the PRA trunk data............................................................................7-94

Table 7-25 Steps for configuring the PRA trunk data .......................................................................................7-95

Table 7-26 Parameter referencing relation between the AT0 trunk data and other .........................................7-106

U-SYS SoftX3000 Operation Manual – Interworking Data Configuration Tables

Issue 03 (2006-12-20) Huawei Technologies Proprietary v

Table 7-27 Preparations for configuring the AT0 trunk data...........................................................................7-106

Table 7-28 Steps for configuring the AT0 trunk data......................................................................................7-106

Table 7-29 Parameter referencing relation between the V5 trunk data and other ...........................................7-117

Table 7-30 Preparations for configuring the V5 trunk data ............................................................................7-117

Table 7-31 Steps for configuring the V5 trunk data........................................................................................7-117

Table 7-32 Parameter referencing relation between the trunk group bearer data and other............................7-121

Table 7-33 Steps for configuring the trunk group bearer data ........................................................................7-122

U-SYS SoftX3000 Operation Manual – Interworking Data Configuration 7 Configuring Trunk Data

Issue 03 (2006-12-20) Huawei Technologies Proprietary 7-1

7 Configuring Trunk Data

About This Chapter

The following table lists the contents of this chapter.

Section Describes

7.1 Related Concepts The related concepts in trunk data configuration.

7.2 Configuring SIP Trunk Data How to configure the SIP trunk data.

7.3 Configuring H.323 Trunk Data

How to configure the H.323 trunk data.

7.4 Configuring No. 7 Trunk Data How to configure the No. 7 trunk data.

7.5 Configuring R2 Trunk Data How to configure the R2 trunk data.

7.6 Configuring PRA Trunk Data How to configure the PRA trunk data.

7.7 Configuring AT0 Trunk Data How to configure the AT0 trunk data.

7.8 Configuring V5 Trunk Data How to configure the V5 trunk data.

7.9 Configuring Trunk Group Bearer Data

How to configure the trunk group data.

7.10 Other Commands How to configure the other trunk data.

7 Configuring Trunk Data U-SYS SoftX3000


7-2 Huawei Technologies Proprietary Issue 03 (2006-12-20)

Before configuring the trunk data, ensure that the following data is configured:

Equipment data Local office data Charging data MGW data Protocol data Signaling data Routing data

See Figure 7-1.



Figure 7-1 Data configuration procedure

Start

Equipment data

Office data

Charging data

MGW data

MRS data

Protocol data

Signaling data

Routing data

End

Number analysis data

Subscriber data

Centrex data

Call barring data

IN service data

Comprehensiveapplication data

Other application data

Basic data

Interworkingdata

Trunk data

Service data

Applicationdata

Other service data

Except the V5 trunk data, the other trunk data must be configured after the corresponding signaling data is configured. The parameter V5 trunk group number defined in the V5 trunk data will be referenced in V5 interface data. Therefore, the V5 interface data must be configured after the V5UA data and the V5 trunk data are configured.




7.1 Related Concepts 7.1.1 SIP Trunk

Basic Concept As a kind of packet trunk, Session Initiation Protocol (SIP) trunk is different from the physical channel defined in the circuit trunk. It is a logical channel for interworking authentication and call addressing between the local office and the peer office.

SIP URL SIP adopts Uniform Resource Locators (URL) for addressing. According to the URI rule prescribed in RFC2396, SIP URL defines the syntax. The user name field can be a telephone number. This is to support IP telephone gateway addressing and to interwork IP network and PSTN. SIP identifies terminal users using the WWW technology.

For the general structure of SIP URL, see the following:

SIP: user name: password @ host: port; transmission parameters; user parameters; method

parameters; TTL parameters; server address parameters? Header name = header value

SIP: It indicates that SIP is used to communicate with the specific end system. User name: It can be composed of any characters. Generally, it can be phone number or

user name as in E-mail address. Currently, the SoftX3000 treats telephone numbers as user names.

Host: It can be the domain name of the host or the IPv4 address. Port: It indicates the number of the port to which the message is sent. The default value is

5060, that is, the public SIP port number. Password: It can be placed in the SIP URL. For safety purposes, it is not recommended to

do so. Transmission parameters: It indicates whether TCP or UDP is used for transmission. By

default, it is UDP. User parameters: The SIP URL allows the host to be an IP telephone gateway. In this case,

a user name can be a common telephone number. BNF syntax fails to distinguish telephone numbers from user names, so the field "user parameters" is added after the domain name. This field has two options: IP and phone. When it is set to Phone, it indicates that the user name is a telephone number and the corresponding end system is an IP telephone gateway.

Method parameters: It indicates the methods or options used. TTL parameters: It indicates the lifespan of a UDP multi-cast data packet. It is available

only when the transmission parameters field is set to UDP and server address parameters is set to Multi-cast address.

Server address parameters: It indicates the address of the server communicating with a specific user. It covers the address in the host field and is set to Multi-cast address usually.

Transmission parameters, TTL parameters, server address parameters, and method parameters are all URL parameters that can be used only in the Contact field (described in the later part).

Table 7-1 lists several examples of SIP URL.



Table 7-1 Examples of SIP URL

SIP URL Example Meaning

Sip; [email protected]; "55500200" is the user name. "191.169.1.112" is the IP address of the IP telephone gateway.

Sip; [email protected]:5061; User=phone;

"55500200" is the user name. "127.0.0.1" is the IP address of the host. "5061" is the port number of the host. "User parameters" is "phone", indicating that the user name is a telephone number.

Sip: [email protected]; method=REGISTER;

"Alice" is the user name. "registrar.com" is the domain name of the host. "Method parameters" is "Register".

SIP-T SIP-T is based on the SIP and enables the extension mechanism to implement the interworking between SIP network and PSTN. The features are described as follows:

Encapsulation The SIP message body carries Integrated Services Digital Network (ISDN) User Part (ISUP) message, that is, the SIP message can transparently transmit ISUP message.

Mapping It includes: − Mapping between ISUP messages and SIP messages − Mapping between ISUP parameters and SIP header fields The mapping between ISUP messages and SIP messages is briefed as follows: − IAM = INVITE − ACM = 180 RINGING − ANM = 200 OK − REL = BYE − RLC = 200 OK

7.1.2 H.323 Trunk

Basic Concept As a kind of packet trunk, H.323 trunk is different from the physical channel defined in the circuit trunk. Instead, it is a logical channel for the following items between the SoftX3000 and GW, gatekeeper (GK), and outer GK in the H.323 network:

Access authentication Address resolution Route selection




Charging

The SoftX3000 can be interconnected with softswitch, GK, outer GK, and GW in the H.323 network. Therefore, the status of the SoftX3000 in the H.323 network varies with different networking applications.

For networking, the SoftX3000 classifies H.323 trunks as five types:

Plain trunk GW trunk GK trunk Outer GK trunk Virtual trunk

You must correctly configure the type of the H.323 trunk. Or else, the interconnection between the SoftX3000 and the peer H.323 device fails.

H.323 Plain Trunk H.323 plain trunk applies to the application that the local office and the peer office are softswitches. It provides the following functions between the local office and the peer office:

Interworking authentication Call addressing

Figure 7-2 shows the typical network.

Figure 7-2 H.323 plain trunk

Network/Backbone

SoftX3000

IP MAN/backbonenetwork

Other softswitch

H.323trunk

H.323trunk

H.323 GW Trunk In the traditional H.323 network, if the SoftX3000 serves as a GK and the opposite device serves as a GW such as A8010 Expert, the trunk from the SoftX3000 to the peer office must be H.323 GW trunk. The H.323 GW trunk provides the following functions at the SoftX3000 side:

Access authentication Address resolution Route selection Charging of the H.323 GW

Figure 7-3 shows the typical networking.



Figure 7-3 H.323 GW trunk

SoftX3000 (GK)

Network/Backbone

PSTN officein city A

H.323 network

IP MAN/backbonenetwork

H.323 GW

H.323 trunk

H.323 GW

H.323 trunk

PSTN officein city B

H.323 GK Trunk In the legacy H.323 network, if the SoftX3000 serves as a GK and the opposite device serves as an upper-layer GK in the H.323 network (or a GK in other H.323 network), the trunk from the SoftX3000 to the peer office must be H.323 GK trunk. The H.323 GK trunk provides the following functions between the SoftX3000 and the upper GK:

Address resolution Route selection

Figure 7-4 shows the typical networking.

Figure 7-4 H.323 GK trunk

SoftX3000 (GK)

H.323 trunk

Lower GK

Backbonenetwork

H.323 terminal

H.323network

H.323network

H.323 GWH.323 GW H.323 GW

Upper GK

H.323 trunk

Backbonenetwork

H.323network

H.323network




H.323 Outer GK Trunk The SoftX3000 can serve as a GW in the H.323 network, and the opposite device is an outer GK. In this case, the trunk from the local office to the peer office must be H.323 outer GK trunk. The H.323 outer GK trunk is used for access authentication between the SoftX3000 and its upper GK. Figure 7-5 shows the typical networking.

Figure 7-5 H.323 outer GK trunk

SoftX3000 (GW)

SIP phone

IP networkIP MAN in city A

H.323 trunk Outer GK

A8010 Export(GW)

PSTN exchangein city B

AMG TMG

H.323 phone

H.323 trunk

H.323 Virtual Trunk H.323 virtual trunk is applicable to the situation in which the local office functions as a GK and the peer office functions as a GW controlled by another GK (supporting RAS but not Q.931). With the H.323 GK trunk, it is used for the charging and the authentication of only incoming calls.

7.1.3 No. 7 Trunk

Basic Concept No. 7 trunk is a kind of circuit trunk and adopts SS7 as the inter-office signaling. The TUP and the ISUP in the SS7 can be used to control the inter-office trunk circuits. Therefore, No. 7 trunks can be classified as TUP trunk and ISUP trunk.

CIC The Circuit Identification Code (CIC) is one of the important parameters used for interworking with No. 7 trunk. It identifies a unique trunk circuit between two signaling points. The CIC exists only in the Telephone User Part (TUP) and ISUP messages. It contains 12 bits. In this case, one office direction can have a maximum of 212 (212 = 4096) trunk circuits.

Between the two offices using SS7 for interconnection, the CIC of the same trunk circuit must be consistent. Or else, there may be exceptions, such as one way audio.



Master/Slave In the bi-directional trunk group, the ITU-T prescribes that each of the two interconnected offices can control half of the trunk circuits. This is to prevent the two offices occupying the same trunk circuit at the same time. The office with larger signaling code controls the circuits with even CICs, and the office with smaller signaling code controls the circuits with odd CICs.

Based on this principle, while selecting outgoing trunk, each office will first occupy the trunk circuits controlled by itself. When the circuits controlled by an office are all busy, the office tries to occupy the trunk circuits controlled by the other office. If the two offices try to occupy the same trunk circuit at the same time, the office abandons the circuit and tries to occupy the next one.

7.1.4 R2 Trunk

Basic Concept R2 trunk is a kind of circuit trunk and adopts R2 as the inter-office signaling. R2 trunk refers to the trunk using the R2 signaling as the inter-office signaling. The R2 signaling is a kind of Channel Associated Signaling (CAS). Therefore, when you configure the R2 trunk data, certain R2 signaling parameters have to be set.

The R2 signaling is defined in the ITU-T Recommendations Q.400 to Q.490, but it is implemented differently in different countries or areas. There is a variety of R2 signaling versions in the world. Some versions, such as Russia CAS, are greatly different from the standard R2 signaling. This chapter describes certain basic concepts related to the standard R2 signaling.

Register Signaling The R2 register signaling adopts the Multi-Frequency Control (MFC) signaling.

For the forward signaling, two from six frequencies are combined. The range of the frequencies is 1380 Hz to 1980 Hz. The frequency difference is 120 Hz.

For the backward signaling, two from six frequencies are combined. The range of the frequencies is 1140 Hz to 540 Hz. The frequency difference is 120 Hz.

For the details of the two signaling, see Table 7-2.

Table 7-2 Details of the forward signaling and the backward signaling

Name Category Function

Forward groups I Connection signaling Forward signaling

Forward groups II Caller category signaling

Backward group A Acknowledgement and control signaling to the forward group I

Backward signaling

Backward group B Callee state signaling

The forward group I and the backward group A are a pair of mutual control signaling. The forward group II and the backward group B are another combination of mutual control signaling.




Table 7-3 lists the meanings of the combinations of signaling.

Table 7-3 Meanings of the signaling combinations

Forward Signaling Backward Signaling Signaling No.

Connection Signaling Group I

Caller Category Signaling Group II (Answering A3 and A5 Signaling)

Acknowledgement and Control Signaling Group A (Answering Group I Signaling)

Callee State Signaling Group B

1 Digit 1 Ordinary subscriber A1: Send the next digit (n+1)

B1: Ready to trace the malicious caller

2 Digit 2 Preferred subscriber

A2: Send the previous digit (n-1)

B2: Subscriber transfer

3 Digit 3 Maintenance device A3: To the group B signaling

B3: The callee is busy

4 Digit 4 (Reserved) services A4: Congestion B4: Congestion

5 Digit 5 Operator A5: Send the caller category

B5: Unallocated number

6 Digit 6 Data transmission A6: Set up the voice channel (charge)

B6: The callee is idle (charge)

7 Digit 7 Ordinary subscriber A7: Send the previous two digits (n-2)

B7: The callee is idle (no charge)

8 Digit 8 Data transmission A8: Send the previous three digits (n-3)

B8: The callee is suspended temporarily

9 Digit 9 Preferred subscriber A9: (Reserved)

10 Digit 0 Operator services A10: (Reserved)

11 Calling manual operator

Coin subscriber A11: Send the start digit of the international number

(Reserved)



Forward Signaling Backward Signaling Signaling No.

Connection Signaling Group I

Caller Category Signaling Group II (Answering A3 and A5 Signaling)

Acknowledgement and Control Signaling Group A (Answering Group I Signaling)

Callee State Signaling Group B

12 Rejecting the signaling A’s request

A12: Send the start digit of the national number

13 Calling maintenance device

A13: Check the sending of the start digit of the international number

14 Inserting echo suppresser

A14: Whether the echo suppresser is needed

15 Sending completed

(Reserved)

(Reserved)

NOTE Signaling 1–6 are for national services. Signaling 7–11 are for international services.

Transmission Modes CAS is transmitted over multiple segments of routes in two modes:

End-to-end transmission The procedure of the end-to-end transmission is as follows:

1. The originating office sends to the first transfer office a called number that has sufficient digits for routing.

2. The first transfer office judges the route and connects the mapping incoming trunk circuit to an outgoing trunk circuit. At this time, the call from the originating office is connected to the next transfer office.

3. The originating office sends to the second transfer office a called number that has sufficient digits for routing.

4. The second transfer office judges the route and connects the corresponding incoming trunk circuit to an outgoing trunk circuit. At this time, the call from the originating office is connected to a third transfer office, or the terminating office. The following operations can be deduced in the same way. With this transmission mode, the call is connected rapidly and the register is used efficiently. The same register signaling mode of the exchanges, however, must be used through the multiple segments of routes.




Segment-by-segment transfer Each transfer office must have received all called number digits from the previous exchange before it transfers the called number to the next transfer office, or the terminating office. With this transmission mode, the requirements for the line are low and different register signaling modes of the exchanges can be used through the multiple segments of routes. The call is connected slowly. For the register signaling, the R2 signaling system of the SoftX3000 provides both transmission modes. You can select one according to the quality of the line: the segment-by-segment transfer mode is suitable for low-quality line and the end-to-end transmission mode for high-quality line. For the line signaling, only the segment-by-segment transfer mode can be selected.

Control Modes A control mode is a method of controlling the sending of the signaling.

Non mutual control mode (pulse mode) The originating office keeps sending one or a group of expected pulse signals to the terminating office despite the reception of the correct signals at the terminating office. This mode requires simple devices, but the reliability of the transmission is very poor.

Half mutual control mode Whenever sending one or a group of pulse signals to the terminating office, the originating office waits for the positive acknowledgement signal before sending the next signal.

Full mutual control mode The originating office keeps sending forward signals until it receives the acknowledgement signal returned by the terminating office. The terminating office keeps sending acknowledgement signals until the originating office stops sending forward signals. The forward and backward signals are all continuous, so this mode is also called "continuous mutual control mode".

The R2 signaling system of the SoftX3000 employs the full mutual control mode. It provides, however, the non mutual control mode and the half mutual control mode.

7.1.5 PRA Trunk

Basic Concept In an extensive sense, Primary Rate Access (PRA) trunk is a kind of circuit trunk. It is a PRA digital subscriber line, that is, 30B+D 2 Mbit/s subscriber line. PRA trunk uses DSS1 as its control signaling. DSS1 is designed based on the model of network side and subscriber side. Thus, the system manages and controls a PRA trunk as a subscriber (PRA subscriber).

Multi-PCM System Normally, one PRA link controls only one PCM system, that is, 32 trunk circuits. When PRA link resource is not enough, you can use one PRA link to control four PCM systems at most.

In the SoftX3000, the system manages attributes of the PRA trunk group by controlling those of the PRA subscriber mapping the PRA trunk group. The attributes include:

Call-in authority



Call-out authority Charging Route selection

In this case, before you configure the PRA trunk data, configure the PRA subscriber data correctly.

Work Mode of PRA Trunk Group PRA trunk group works in two modes:

Trunk mode Subscriber mode

Trunk mode means that the SoftX3000 manages authority, charging analysis, and call restrictions of a call based on the call and charging attributes of the PRA trunk group when the call is started from the PRA trunk group. At this time, for an incoming trunk group call, the SoftX3000 generates a trunk bill instead of a subscriber bill.

Subscriber mode means that the SoftX3000 manages authority, charging analysis, and call restrictions of a call based on the call and charging attributes of the PRA subscriber when the call is started from the PRA trunk group. At this time, for an incoming trunk group call, the SoftX3000 generates a subscriber bill instead of a trunk bill.

When a call is started from the PRA trunk group, the SoftX3000 has different criteria for judging the work mode of the PRA trunk group for outgoing and incoming calls. For an outgoing call, the SoftX3000 judges the work mode of the PRA trunk group by the call attribute of the called prefix, which is static. For an incoming call, the SoftX3000 judges the work mode of the PRA trunk group by the calling number sent by the peer office, which is dynamic. For details, see Table 7-4.

Table 7-4 Analysis of the work mode of the PRA trunk group

Call Type Analysis Process

Outgoing call When the SoftX3000 originates a call through the PRA trunk group, the SoftX3000 searches the local number analysis table (set with ADD CNACLD) for the call attribute of the prefix of the called number. If the call attribute is intra-office call (that is, local office call), the PRA trunk group works in subscriber mode for the call. If the call attribute is out-office call (that is, local call), the PRA trunk group works in trunk mode for the call.




Call Type Analysis Process

Incoming call 1. When the peer office originates a call to the SoftX3000 through the PRA trunk, the SoftX3000 first judges whether the incoming call signaling contains the calling number or not. If not, the SoftX3000 proceeds with step (2). If yes, the SoftX3000 carries out steps (3) and (4).

2. If the incoming call signaling does not contain the calling number, the SoftX3000 judges the default calling number (set with ADD PRATG) of the PRA trunk group as follows: If the default calling number is an invalid PRA subscriber number, the PRA works in trunk mode for the call. Otherwise, the PRA works in subscriber mode for the call.

3. If the incoming call signaling contains the calling number, the SoftX3000 checks the validity of the calling number, that is, the SoftX3000 searches the local PRA subscriber data table to check whether there is the same PRA subscriber number as the calling number. If the calling number is invalid, that is, if the caller is not a PRA subscriber of the local office, the PRA works in trunk mode for the call. If the calling number is valid, the SoftX3000 proceeds with step (4).

4. If the calling number is valid, the SoftX3000 continues to judge whether or not the corresponding PRA subscriber number belongs to the same call source as the PRA trunk group. If not, the PRA works in trunk mode for the call. If yes, it works in subscriber mode for the call.

7.1.6 AT0 Trunk

Basic Concept In the extensive sense, AT0 trunk is a circuit trunk, but it is actually an analog subscriber line for Direct-Dial-In (DDI) functions of PBX. When AT0 trunk is used in networking, the SoftX3000 interacts with the peer PBX through the common analog subscriber line signaling. Figure 7-6 shows the typical networking.



Figure 7-6 AT0 trunk networking

SoftX3000

IP MAN

Analog subscriber line(AT0 trunk)

AMG/IAD

PBX

Inserted with theCDI

Inserted with theanalog subscriber

board

Purpose of AT0 Trunk DDI means that a subscriber can directly dial the number of a PBX subscriber from the PSTN side (the SoftX3000 side) instead of using dual-stage dialing.

In Figure 7-6, PBX occupies the number resources of PSTN. AT0 trunk can support only single-directional calls, that is, calls from the PSTN side (the SoftX3000 side) to the PBX side.

7.1.7 V5 Trunk

Basic Concept In the extensive sense, V5 trunk is a circuit trunk, but it is actually a 2.048-Mbit/s link at a V5 interface. V5 trunk is located between a local exchange and the access network. V5 trunk adopts V5.1/V5.2 as the call control protocol. Thus, one V5 trunk group can be configured with at most 16 E1s.

V5 Link ID V5 link ID is one of the concepts in the V5 protocol. One V5.2 interface can support up to 16 2.048-Mbit/s links. Thus, V5.2 protocol uses two parameters, V5 link ID and V5 time slot number, to identify a unique V5 time slot over multiple 2.048-Mbit/s links.

V5 link ID An 8-bit field, it identifies a specific 2.048-Mbit/s link among the 2.048-Mbit/s links composing the V5.2 interface. This specific link contains the V5 time slot selected to be bearer channel. The V5 link ID must be determined by the negotiation between the Local Exchange/Office (LE) side and Access Network (AN) side, and it must be consistent with that in the data configuration.

V5 time slot number




A 5-bit field, it identifies the V5 time slot that is to be used or being used as bearer channel. The V5 time slot number is controlled and assigned by the Bearer Channel Connection (BCC) protocol.

MG E1 ID MG E1 ID is one of the concepts in the V5UA protocol. One V5UA link set can bear the protocol messages of multiple V5.2 interfaces. One V5.2 interface can support multiple 2.048-Mbit/s links. Therefore, you must map the V5 link ID of the V5.2 interface to the MG E1 ID in the V5UA link set. This is to ensure that a 2.048-Mbit/s link can be identified among the messages in the same V5UA link set.

7.2 Configuring SIP Trunk Data 7.2.1 Overview

Configuration Relation The SIP trunk data configures interconnection information between the SoftX3000 and other softswitch or SIP application server, such as SIP-URL and SIP-T. Before configuring the SIP trunk data, you must configure the following data:

Equipment data Local office data Charging data Protocol data Routing data

For details, see Figure 7-1.

During the configuration, certain parameters defined in the local office data, charging data and routing data are referenced in the SIP trunk data. Besides, the parameter Network management source code defined in the SIP trunk data is referenced when the network management data is configured. Table 7-5 shows the details.

Table 7-5 Parameter referencing relation between the SIP trunk data and other data

Input Parameter Output Parameter

Name Defined in Name Referenced in

Call source code Basic call data Network management source code

Network management data

Charging source code Charging data - -

Outgoing trunk charging source code

Charging data - -

Subroute number Routing data - -





Caller number discrimination group number (optional)

Call barring data - -

Preparations Before configuring the SIP trunk data, prepare as specified in Table 7-6.

Table 7-6 Preparations for configuring the SIP trunk data

SN Item Remark

1 IP address of the peer office For interworking with other SoftSwitch or SIP application server

2 SIP port number of the peer office For interworking with other SoftSwitch or SIP application server

3 Whether SIP-T is supported For interworking with other SoftSwitch or SIP application server

Configuration Steps Table 7-7 lists the general steps for configuring the SIP trunk data.

Table 7-7 Steps for configuring the SIP trunk data

Step Description Command

1 Add an SIP trunk group. ADD SIPTG

2 Add IP address pair of the SIP trunk group. ADD SIPIPPAIR

Parameter Referencing Relation During the configuration, the key parameters of the data tables are not referenced mutually.




7.2.2 Adding SIP Trunk Group

Related Commands

Command Function

ADD SIPTG To add an SIP trunk group

RMV SIPTG To remove an SIP trunk group

MOD SIPTG To modify an SIP trunk group

LST SIPTG To list SIP trunk groups

Notes of Configuration Before adding an SIP trunk group, run the commands to obtain the following parameters defined by the system:

Parameter Command

Call source LST CALLSRC

Subroute number LST SRT

Charging source code LST CHGGRP, LST CHGIDX


LST CLRDSN

Parameter Description

This section introduces only the parameters related to SIP trunk group. For the other parameters, see online help or section 7.1.3 "No. 7 Trunk."

Trunk group number

It identifies a unique trunk group. The options are:

SIP trunk group H.323 trunk group No. 7 trunk group R2 trunk group PRA trunk group AT0 trunk group V5 group

Assign its value globally. The value ranges from 0 to 65534.

Call source code



It defines the call source to which the trunk group belongs. This parameter must be defined by ADD CALLSRC before being used here.

Sub-route number

It defines the subroute to which the trunk group belongs. This parameter must be defined by ADD SRT before being used here.

Trunk group name

It identifies a trunk group with a string of characters.

Call-in authority

It defines the call-in authority of the trunk group, such as:

Intra-office Local Local toll National toll International toll Intra-office national toll (in multi-zone-code application) Intra-office international toll (in multi-country-code application) Intra-office local toll

The system enables all call-in authority of the trunk group by default.

Call-out authority

It defines the call-out authority of the trunk group, such as:


The system enables all call-out authority of the trunk group by default.

For SIP or H.323 incoming trunk, the SoftX3000 cannot control the authority for national or international toll incoming calls due to signaling restrictions. It can, however, control the authority for such calls through SIP-T incoming trunk.

Charging source code

It is one of the charging attributes of the trunk group. Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of incoming trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being used here.

For details about charging, see chapter 4 "Configuring Charging Data" in the U-SYS SoftX3000 SoftSwitch System Operation Manual – Basic Data Configuration.





It is one of the charging attributes of the trunk group. Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of outgoing trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being used here.

For details about charging, see chapter 4 "Configuring Charging Data" in the U-SYS SoftX3000 Operation Manual – Basic Data Configuration.

EC capability

It is one of the parameters used for interworking with the peer office. It controls the SIP trunk to enable the EC function. The default option is YES, indicating that the EC function is enabled.

IFMI module number

It defines the module number of the IFMI dispatching SIP trunk protocol messages at the SoftX3000 side. The value range is from 132 to 211. This parameter must be defined by ADD BRD before being used here.

Remote URI

It is one of the parameters used for interworking with other softswitch or SIP application server. It defines the IP address and SIP port number of the opposite device. The format is xxx.xxx.xxx.xxx:port, where, xxx.xxx.xxx.xxx is the IP address and port is the port number (the default value is 5060). For example, the SIP-URI of an office is 191.169.150.80:5060.

Use heartbeat

It defines whether the SoftX3000 periodically sends heartbeat signals to the SIP device in the peer office. The default setting is NO, indicating that the SoftX3000 does not send heartbeat signals. In the following applications, the parameter must be set to YES:

This SIP trunk interconnects two assistant softswitches in the dual homing networking. It is required to improve the call completion rate and to prevent the SIP trunk from being

suspended at the occurrence of network interruption.

Minimum heartbeat timer length in minutes

It defines the minimum duration of the timer that controls the sending of heartbeat signals in the SoftX3000. It is valid only when the SoftX3000 sends heartbeat signals. The value range is from 1 to 60. The unit is minute. The default value is 1.

Maximum heartbeat timer length in minutes

It defines the maximum duration of the timer that controls the sending of heartbeat signals in the SoftX3000. It is valid only when the SoftX3000 sends heartbeat signals. The value range is from 1 to 60. The unit is minute. The default value is 5.

Software parameter of service control

It is the additional service flag used to set whether a SIP trunk supports certain special services or applications. There are 16 options for this parameter. Currently, only eight options are used, and the others are reserved. The meanings of the used options are as follows:

Redirection enable It indicates whether the SoftX3000 supports the function of call redirection of SIP trunks. It is Not support by default. Suppose that the SoftX3000 initiates INVITE request to the peer office through outgoing SIP trunks. The SoftX3000 receives call redirection response message 300, 301, 302, or 305 returned by the peer office. The called subscriber is in the



local office. If the option is selected, the SoftX3000 initiates a call to the new address to complete the connection. If not, the SoftX3000 releases the call.

Disable default caller number It is valid only for incoming trunks. By default, it is not selected. When the message of incoming SIP trunk does not contain calling number information such as anonymous card call, the SoftX3000 uses the default calling number of the trunk group as the calling number of this call. If the option is selected, the SoftX3000 does not use the default calling number of the trunk group as the calling number of this call. That is, the call has no calling number.

To header Use Tel-URI It is valid only for outgoing trunks. When it is selected, the sip messages over the trunk use Tel-URI for ReqestUri and To header fields. If it is not selected, the trunk uses Sip-URI.

From header Use Tel-URI It is valid only for outgoing trunks. When it is selected, the sip messages over the trunk uses Tel-URI for From or P-Asserted-Identity header fields. If it is not selected, the trunk uses Sip-URI.

WAC service The parameter works with ISUP software parameter P9. If both software parameters are selected, the call is an intra-group Centrex call. The trunk sends caller short number, group number, and group name to the peer office.

No ringback tone from peer office SIP-T check for transfer case

It is valid only for transit calls. Suppose a transit network is like "A–B–C", in which the SoftX3000 is transit office B. A and B are interconnected through SIP-T trunk, and B and C through SIP-T/ISUP trunk. If you select this option, the SoftX3000 checks the SIP-T version at A and B. If SIP-T versions at A and B are consistent, the SoftX3000 transits SIP-T body (that is, ISUP message body) directly when transferring ISUP signaling from A to C. If SIP-T versions at A and B are inconsistent, the SoftX3000 encodes or decodes SIP-T body when transferring ISUP signaling from A to C. If you do not select this option (default value), the SoftX3000 encodes or decodes SIP-T body when transferring ISUP signaling from A to C.

Used for adding address type The address attribute is contained.

Support Q1912.5 For an incoming ISUP call routed out through SIP, if this option is selected, the SIP trunk does not send the ACM message to the ISUP trunk if the 183 message that the SIP trunk receives does not contain ISUP Body. Instead, the SIP trunk establishes a media channel based on the 183 message. If this option is not selected, the SIP trunk sends the ACM message to the ISUP trunk. Moreover, when the SIP trunk adopts the pure SIP protocol, this option controls the conversion between the internal cause value and the SIP status code. If this option is selected, the conversion is based on Q1912.5. If this option is not selected, the conversion is based on RFC3398. By default, this option is not selected.

Stop call restriction

When the total number of calls (which can be queried with DSP TGCALL) decreases to a value less than the quantity defined in this parameter, the system auto stops the enabled call restriction. Its value range is from 0 to 65535.

The value of stop call restriction must be smaller than or equal to that of maximum caller number restriction. For example, if the parameter stop call restriction is set to 1800 and




maximum caller number restriction is set to 2000, the system auto starts call restriction when the total number of incoming and outgoing calls on one SIP trunk group exceeds 2000, and auto stops call restriction when the total number of calls falls back to a value less than 1800 (≤ 1799).

Maximum caller number restriction

It defines the maximum number of calls allowed on one SIP trunk group. That is, when the total number (which can be queried with DSP TGCALL) of incoming and outgoing calls on the SIP trunk group exceeds the quantity defined in this parameter, the system auto starts call restriction. The system auto stops call restriction when the total number of calls falls back to a value less than Stop call restriction defined by this command. Its value range is from 0 to 65535. The default value is 65535, indicating that the system does not start call restriction.

Time delay value

It is the maximum transmission delay that can be tolerated by the circuits of a trunk group. The value ranges from 0 to 1023, in unit of second. When the transmission delay of the call circuits is greater than the maximum value, it is necessary to install echo canceller. The parameter is used when satellite circuits are connected. In other cases, it is set to 0.

Software parameter of signaling control

It is the additional signaling flag used to set whether a SIP trunk supports certain special signaling modes. There are 16 options for this parameter. Currently, 10 options are used, and the others are reserved. The meanings of the used options are as follows:

Calling party number with ST If it is selected, an ST signal is added at the end of the calling number.

Called party number with ST If it is selected, an ST signal is added at the end of the called number.

Connected party number with ST If it is selected, an ST signal is added at the end of the connected number.

Generic number with ST If it is selected, an ST signal is added at the end of the generic number.

Original called party number with ST If it is selected, an ST signal is added at the end of the original called number.

Redirecting number with ST If it is selected, an ST signal is added at the end of the redirecting number. The redirecting number is the forwardly sent information that represents the last redirecting number.

Redirection number with ST If it is selected, an ST signal is added at the end of the redirection number. The redirection number is the backwardly sent information indicating that the call must reselect route-to-number or forward-transfer number.

Intercept COT Suppose that a networking of tandem offices is in the format of "A→B→C". No. 7 trunk is the only inter-office trunk. A SoftX3000 is in tandem office B. Suppose that A calls C through sending an IAM to B. If A, in the IAM, requests to check the continuity of circuits from A to B, tandem office B forwards the IAM to C only after receiving the COT message (indicating that the continuity check is successful) sent by A. If the option is selected, office B does not need to wait for the COT message sent by A. Office B forwards the IAM to C immediately after receiving it from A.

Peer office no ringback tone



It is valid only for outgoing trunks. If it is selected, the caller, (no matter whether the caller is in the local office, hears the ringback tone sent by the local office when the local office initiates calls to the peer office. That is, the peer office is regarded to have no capability of sending the ringback tone by default. The option is mainly used in Russia.

Anonymous card auth by SX3000 If it is selected, the SoftX3000, through INAP messages, transfers the card number and password information sent by the SIP software terminal to the U-NICA for authentication (the mode used in R002). If it is not selected (system default), the SoftX3000, through SIP trunks, transfers the card number and password sent by the SIP software terminal to the U-NICA for authentication.

ISUP transmit mask

It transforms the ISUP message encapsulated by the SIP-T trunk on the transmission direction to adapt to the ISUP signaling used by the peer office. You must configure the parameter according to the ISUP signaling script provided by Huawei.

ISUP receive mask

It transforms the ISUP message encapsulated by the SIP-T trunk on the receiving direction to adapt to the ISUP signaling used by the peer office. You must configure the parameter according to the ISUP signaling script provided by Huawei.

Outgoing trunk type

It is valid only for outgoing trunks. When the local office initiates a call to the peer SoftSwitch through SIP trunks, the parameter specifies whether the local office sends the pure SIP, SIP-T, or SIP-I message to the peer SoftSwitch. The meanings of the options are as follows:

Use pure SIP trunk It indicates that the local office sends the pure SIP messages to the peer SoftSwitch in all cases.

Use SIP-T when caller is ISUP It indicates that the local office sends the SIP-T messages to the peer SoftSwitch only when the caller is an ISUP incoming trunk. In other cases, the local office sends the pure SIP messages to the peer SoftSwitch.

Use SIP-T when caller is not SIP/H.323 It indicates that the local office sends the SIP-T messages to the peer SoftSwitch only when the caller is not a SIP or an H.323 subscriber. When the caller is a SIP or an H.323 subscriber, the local office sends the pure SIP messages to the peer SoftSwitch.

Always use SIP-T It indicates that the local office sends the SIP-T messages to the peer SoftSwitch in all cases.

Use SIP-I when caller is ISUP It indicates that the local office sends the SIP-I messages to the peer SoftSwitch only when the caller is an ISUP incoming trunk. In other cases, the local office sends the pure SIP messages to the peer SoftSwitch.

Use SIP-I when caller is not SIP/H.323 It indicates that the local office sends the SIP-I messages to the peer SoftSwitch only when the caller is not a SIP or an H.323 subscriber. When the caller is a SIP or an H.323 subscriber, the local office sends the pure SIP messages to the peer SoftSwitch.

Always use SIP-I




It indicates that the local office sends the SIP-I messages to the peer SoftSwitch in all cases.

Incoming trunk type

It is valid only for incoming trunks. When the peer SoftSwitch initiates a call to the local office through SIP trunks, the local office can judge whether the received incoming signaling is carried in a pure SIP, SIP-T, or SIP-I message. The local office must judge the terminal type at the called side to determine whether to send a SIP, SIP-T, or SIP-I message to the peer SoftSwitch. The meanings of the options are as follows:

Use pure SIP trunk It indicates that the local office sends the pure SIP messages to the peer SoftSwitch in all cases.

Use SIP-T when callee is ISUP It indicates that the local office sends the SIP-T messages only when the callee side is outgoing ISUP trunk. In other cases, the local office sends the pure SIP messages to the peer SoftSwitch.

Use SIP-T when callee is not SIP/H.323 It indicates that the local office sends the SIP-T messages to the peer SoftSwitch only when the callee is not a SIP or an H.323 subscriber. When the callee is a SIP or an H.323 subscriber, the local office sends the pure SIP messages to the peer SoftSwitch.

Always use SIP-T It indicates that the local office sends the SIP-T messages to the peer SoftSwitch in all cases.

Use SIP-I when callee is ISUP It indicates that the local office sends the SIP-T messages only when the callee side is outgoing ISUP trunk. In other cases, the local office sends the pure SIP messages to the peer SoftSwitch.

Use SIP-I when callee is not SIP/H.323 It indicates that the local office sends the SIP-T messages to the peer SoftSwitch only when the callee is not a SIP or an H.323 subscriber. When the callee is a SIP or an H.323 subscriber, the local office sends the pure SIP messages to the peer SoftSwitch.

Always use SIP-I It indicates that the local office sends the SIP-I messages to the peer SoftSwitch in all cases.

Privacy level

It indicates what information related to the caller in the incoming or outgoing SIP/SIP-T message must be shielded by the SoftX3000 to provide privacy services such as CLIR and RIO for the caller. The meanings of the options are as follows:

User It indicates that the security service of the user level is used, that is, the user information in the header field of the SIP message is shielded.

Header It indicates that the security service of the header field level is used, that is, the header field of the SIP message is shielded.

ID



It indicates that the security service of the ID level is used. If the message includes field of P-Asserted-ID header (inter-office transmission), the local office obtains caller information from field of P-Asserted-ID. If the message includes field of P-Preferred-ID header (caller terminal transmission), the local office obtains caller information from field of P-Preferred-ID. In other cases, the local office shields the caller information fully.

Unreliable The peer end is an untrusted entity, and the caller information is fully shielded.

If services such as CLIR and RIO are to be implemented, select ID.

Release call

It indicates whether the SoftX3000 supports batch releasing of all calls on the trunk group when it cannot detect the heartbeat signal periodically sent by the peer SIP device (SIP trunk may be faulty). It is supported by default. For example, 50 calls can be released per second.

If the batch releasing of calls is enabled, the system does not send many BYE messages when SIP trunk is faulty. Therefore, in the case of heavy traffic, the overload of system resources such as memory usage and CPU usage does not happen.

Incoming reserved circuit

It is valid only when the trunk group is bi-directional. It sets the minimum number of circuits in the trunk group that are reserved for incoming calls. That is, when the number of idle circuits in the trunk group reduces to the minimum number, the SoftX3000 allows only incoming calls to occupy trunks. Its value range is from 0 to 65535. By default, it is set to 65535, indicating that there is no reserved circuit.

Video supported

It defines whether the SIP trunk supports video services. It is Yes by default.

Audio codec prefer, Video codec prefer

They define the codec modes of the audio and the video media stream preferred by the multimedia terminal controlled by the SoftX3000 during call connection.

When the MGWs are controlled by the SoftX3000 during a call, the SoftX3000 controls through signaling the MGWs at the caller and the callee side to directly use these two parameters for connecting media streams if the SoftX3000 finds that the codec modes supported by the caller and the callee have intersection and the intersection contains the audio/video codec prefer defined here.

You can set codec prefer data in the following tables:

Subscriber data table (with ADD VSBR or ADD MSBR) Trunk data table (with ADD N7TG or ADD SIPTG) Called number analysis table (with ADD CNACLD) Calling number discrimination table (with ADD CLRDSN)

If a call involves more than two codec prefer modes, the SoftX3000 chooses one according to the following principles:

The audio/video codec prefer defined in the calling number discrimination table enjoys the highest priority, and that in the called number analysis table enjoys the second.

If a call does not involve the audio/video codec prefer defined in either the calling number discrimination table or the called number analysis table, the SoftX3000, based on the principle of "caller and subscriber first", selects a codec mode. For example,




− In an intra-office call, if the codec prefer of the caller is different from that of the callee, the codec prefer of the caller is valid.

− In an intra-office outgoing call, if the codec prefer of the caller is different from that of the outgoing trunk group, the codec prefer of the caller is valid.

− In a transit call, if the codec prefer of the local incoming trunk group is different from that of the local outgoing trunk group, the codec prefer of the local incoming trunk group is valid.

− In an incoming terminated call, if the codec prefer of the local incoming trunk group is different from that of the local callee, the codec prefer of the local callee is valid.

Call heart beat flag

It is one of the parameters for the SoftX3000 to interwork with the peer SIP device, such as the U-NICA of Huawei. It defines the policy of the SoftX3000 on the call heart beat signal. It has the following options:

No heart beat This option indicates the SoftX3000 does not start the transmission and detection mechanisms of the call heart beat signal.

Local heart beat This option means that the SoftX3000 sends the message Options to the peer SIP device periodically when a call is originated through the SIP trunk group. After receiving the message, the peer SIP device returns a 200 acknowledgement to the SoftX3000 to denote the consistency of the call states at both sides. If the peer SIP device returns a 481 acknowledgement to the SoftX3000 or makes no response, it means that the peer SIP device has released the call or an error occurs in the call. At this time, the SoftX3000 releases the call at once.

Remote heart beat This option means that the SoftX3000 detects the message Options sent by the peer SIP device periodically when a call is originated through the SIP trunk group. If the SoftX3000 receives this message within the defined duration, it returns a 200 acknowledgement to the peer SIP device. If not, it releases the call at once.

Call heart beat period in minutes

It is valid only when the call heart beat signal is started. It defines the following two duration:

Duration for the local office to regularly send the Options messages to the peer SIP device Duration for the local office to regularly detect the Options messages received from the

peer SIP device

Its value range is from1 to 60, in unit of minute. By default, it is 6.

2833 encryption flag

It is one of the parameters for the SoftX3000 to interwork with the peer SIP device. It indicates if HNC1 encryption algorithm of RFC2833 is supported in the SIP trunk group direction by the local SoftX3000 and the peer SIP device. By default, it is set to No.

If the local SoftX3000 and the peer SIP device support RFC2833 and its HNC1 encryption algorithm, set this parameter to Yes. This is to ensure the reliable transfer of DTMF signals in the IP network.

For details, see chapter 2 "Configuring MGW Data."

2833 encryption key



It is valid only when the parameter 2833 encryption flag is set to Yes. It is one of the parameters for the SoftX3000 to interwork with the peer SIP device. It defines the RFC2833 shared secret key between the SoftX3000 and the SIP device. It is a string of 8 to 16 characters.

SIP-T version

It is one of the parameters for the SoftX3000 to interwork with the peer SIP device. It sets the international or national specification to which the SIP-T protocol used by the SIP trunk group conforms, such as ITU-T, ANSI, ETSI, China, Russia, or Brazil. You must select the correct protocol. Or else, inter-office signaling cooperation fails.

Connect satellite circuit

It defines if the SIP trunk is carried over satellite circuits. You must set it as needed. In normal cases, set it to No.

Enhanced Attribute

If you set it to Yes, the enhanced attributes are displayed.

Default caller number

This parameter is available only for incoming trunks. If Caller number provision mode of the trunk group is Default number and no caller number is contained in the call signaling message sent by the peer office when it originates a call through the incoming trunk, the local office uses the default caller number.

Select FCCU mode

It specifies which mode the MSGI adopts to dispatch a SIP trunk call to the specified FFCU for processing when the SoftX3000 interworks with other devices through the SIP or SIP-T trunk. There are two dispatch modes, distribute mode and specify mode. The default value is Distribute. When Select FCCU mode is set to Distribute, the MSGI selects the FCCUs one after another. In this case, all calls are equally dispatched to all FCCUs for processing. When Select FCCU mode is set to Specify, the calls are dispatched to the specified FCCU for processing. A maximum of eight FCCUs can be specified.

Note that the parameter is null by default in MOD SIPTG.

FCCU module number

It is valid only when Select FCCU mode is set to Specify. A maximum of eight FCCUs can be designated to process the SIP message dispatched from the MSGI.

7.2.1 Adding IP Address Pair of SIP Trunk Group

Related Commands

Command Function

ADD SIPIPPAIR To add an IP address pair of a SIP trunk group

MOD SIPIPPAIR To modify an IP address pair of a SIP trunk group

LST SIPIPPAIR To lists IP address pairs of a SIP trunk group




Notes of Configuration Before adding an IP address pair of a SIP trunk group, run the commands to obtain the following parameters defined by the system:

Parameter Command

Trunk group number LST SIPTG

IFMI module number LST BRD

Parameter Description Trunk group number

It specifies a unique SIP trunk group configured.

IFMI module number

It specifies the module number of the IFMI that dispatches the SIP protocol message at the SoftX3000 side. The value range is from 132 to 211. The parameter must be defined by ADD BRD before being used here.

Local server port

It specifies the SIP protocol port number of the local office. The default value is 5060.

Remote URI 1

It is one of the interconnection parameter between the SoftX3000 and other softswitches or SIP APSs. It specifies the IP address and SIP protocol port number of the peer devices, and the format is xxx.xxx. xxx.xxx:port. Here, xxx.xxx. xxx.xxx is the IP address and port is the port number (the default value 5060). For example, the URI of an office is 191.169.150.80:5060.

Master/Slave type

It specifies whether the remote URI is in active or standby mode. The options are:

Master: It indicates the SIP trunk data belongs to the local office and is valid.

Slave: It indicates the SIP trunk data belongs to the assistant office and is valid only when the dual-homing status of the local office is ACTIVE.

Whether config DH sip ip pair

It specifies whether to configure the IP address of dual-homing SIP self-loop trunk. If it is required to set the remote URI of the dual-homing self-loop trunk, the parameter must be set to Yes.

DH Remote URI

In the dual-homing networking, the first URI is the remote URI of an ordinary SIP trunk. The second URI is the URI of the SIP self-loop trunk of the local office dual homing. The IP address of the second URI should be the IP address of the IFM in the local office.



7.3 Configuring H.323 Trunk Data 7.3.1 Overview

Configuration Relation The H.323 trunk data configures interconnection information between the SoftX3000 and other softswitch and between the SoftX3000 and GK or GW in the traditional H.323 network, such as:

IP address of other softswitch IP address of GK Alias of GW CALL port number RAS port number

Before the H.323 trunk data is configured, the following data must be configured:

Equipment data Local office data Charging data Protocol data Routing data


During the configuration, the H.323 trunk data reference certain parameters defined in:

Local office data Charging data Routing data Call barring data

The parameter Network management source code defined in the H.323 trunk data will be referenced when the network management data is configured. Table 7-8 lists the details.

Table 7-8 Parameter referencing relation between H.323 trunk data and other



Call source code Basic Call Data Network management source code




Charging data - -









Call barring group (optional)


Preparations Before configuring the H.323 trunk data, prepare as specified in Table 7-9.

Table 7-9 Preparations for configuring the H.323 trunk data

SN Item Remark

1 Position of the SoftX3000 in H.323 network

To determine the type of the H.323 trunk at the SoftX3000 side

2 IP address of SoftSwitch or GK

For interworking with other SoftSwitch or GK

3 CALL port number For interworking with other SoftSwitch

4 RAS port number For interworking with GK

5 GK entity type For interworking with GK

6 GK ID For interworking with GK

Configuration Steps Table 7-10 lists the general steps for configuring the H.323 trunk data.

Table 7-10 Steps for configuring the H.323 trunk data


1 Add an H.323 virtual IP list. ADD IPLIST

2 Add an H.323 trunk group. ADD H323TG

Parameter Referencing Relation During the configuration, the key parameters of the data tables are not referenced mutually.



7.3.2 Adding Virtual IP List (Optional)

Related Commands

Command Function

ADD IPLIST To add a virtual IP list

RMV IPLIST To remove a virtual IP list

MOD IPLIST To modify a virtual IP list

LST IPLIST To list virtual IP lists

Notes of Configuration This step is optional.

In certain countries or regions, carriers may have already fully developed an H.323 network. When you connect such an H.323 network to an NGN, the carriers require that one or multiple H.323 entities (such as GK or GW) in the H.323 network access the SoftX3000 as a trunk group. Thus, the SoftX3000 can authenticate and charge the incoming calls originated by these H.323 entities. Therefore, you must run ADD IPLIST to configure a list of IP addresses for virtual H.323 trunks.

Parameter Description IP list number

It defines a list of IP addresses in the SoftX3000. It will be referenced in ADD H323TG. Here are the configuration guidelines:

An IP address list contains multiple IP addresses. An IP address is included only in one IP address list.

The IP address list authenticates the incoming calls from a virtual H.323 trunk. When a virtual H.323 incoming trunk initiates a call, and the IP address of the peer H.323 entity is included in the IP address list defined in the office, the authentication succeeds. Or else, the authentication fails and the SoftX3000 rejects the call.

IP address

It defines a specific IP address in the IP address list. The IP address is the one of an H.323 entity interconnected with the local office through the virtual H.323 trunk.

Mask

It is used with the IP address to determine a network segment. Set it by the following principles:

To define a specific IP address in the IP address list, set this parameter to 255.255.255.255. To define a specific IP address segment in the IP address list, set this parameter based on

the actual situation. For example, if the IP address is 150.1.1.1 and the mask is 255.255.255.240, the corresponding IP address segment is 150.1.1.0–150.1.1.15.




7.3.3 Adding H.323 Trunk Group

Related Commands

Command Function

ADD H323TG To add an H.323 trunk group

RMV H323TG To remove an H.323 trunk group

MOD H323TG To modify an H.323 trunk group

LST H323TG To list H.323 trunk groups

Notes of Configuration Before adding H.323 trunk group, run the commands to obtain the following parameters defined by the system:

Parameter Command





LST CLRDSN

Call barring group number (optional) LST GRPAC

Module number of FCCU (optional) LST BRD


This section introduces only the parameters related to H.323 trunk group. For the other parameters, see online help or section 7.4.2 "Adding No. 7 Trunk Group."

Trunk group number


SIP trunk group H.323 trunk group No. 7 trunk group R2 trunk group PRA trunk group AT0 trunk group V5 trunk group



Trunk groups are uniformly numbered in the network. The value ranges from 0 to 65534.

Call source code


Sub-route number


Group direction

It defines the call connection direction of the H.323 trunk group. The default option is Bi-directional trunk. The parameter options are described as follows:

Incoming trunk It indicates that only the incoming calls from the peer office are processed.

Outgoing trunk It indicates that only the outgoing calls to the peer office are processed by default. If the controlling software parameter is modified, the incoming calls from the peer office can also be processed.

Bi-directional trunk It indicates that the calls from and to the peer office are processed.

Trunk group name


H323 trunk type

It is one of the parameters used for the SoftX3000 to interwork with the peer office. It defines the type of the H.323 trunk at the SoftX3000 side. The parameter options are described as follows:

H323 peer trunk It is applicable to the case that the local office and peer office are SoftSwitch.

H323 GW trunk It is applicable to the case that the local office is a GK and the peer office is a GW in the same H.323 network.

H323 GK trunk It is applicable to the case that the local office and the peer office are GKs.

H323 outer GK trunk It is applicable to the case that the local office is a GW and the peer office is a GK in the same H.323 network.

H323 virtual trunk It is applicable to the case that the local office is a GK and the peer office is a GW under the control of other GK (supporting RAS protocol, but not supporting the Q.931 protocol). It is usually used with H.323 GK trunk only for incoming calls. The purpose is to charge and to authenticate the incoming calls from the GW.

Trunk IP address




It is one of the parameters used for interworking with other SoftSwitch or GK. It defines the IP address of the peer office (SoftSwitch or GK). This parameter is valid only when the H323 trunk type is set to H323 peer trunk, H323 GK trunk, or H.323 outer trunk.

CALL trunk port number

It is one of the parameters used for the SoftX3000 to interwork with other SoftSwitch. It defines the number of the TCP port processing the call signaling in the peer office (SoftSwitch). The default value is 1720. This parameter is valid only when H323 trunk type is set to H323 Plain Trunk.

RAS trunk port number

It is one of the parameters used for the SoftX3000 to interwork with GK. It defines the number of the UDP port processing the RAS signaling in the peer office (GK). The default value is 1719. This parameter is valid only when H323 trunk type is set to H323 GK trunk or H323 outer GK trunk.

FCCU module number

It defines the module number of the FCCU processing the call signaling of the H.323 trunk. This parameter is valid only when H323 trunk type is set to H323 GW Trunk. It must be defined by ADD BRD before being here.

Gateway alias

It is one of the parameters used for the SoftX3000 to interwork with GW. It defines the alias of the GW (such as the A8010 Expert) connected to the local office (GK). This parameter is valid only when H323 trunk type is set to H323 GW Trunk.

Entity name

When the type of trunk is H323 Outer GK Trunk, it is valid to describe an outer GK.

Entity type

It is one of the parameters used for the SoftX3000 to interwork with GK. It defines the entity type of the peer office (GK). This parameter is valid only when H323 trunk type is set to H323 Outer GK Trunk.

Primary GK It indicates that the SoftX3000 first registers with this GK during initialization.

Alternate It indicates that the SoftX3000 registers with this GK if it fails to register with the primary GK.

Gatekeeper ID

It is one of the parameters used for the SoftX30000 to interwork with GK. It defines the alias of the peer office (GK). This parameter is valid only when H323 trunk type is set to H323 Outer GK Trunk.

Support gatekeeper release

It defines whether the peer office (GK) can control the local office to release the calls. This parameter is valid only when H323 trunk type is set to H323 Outer GK Trunk. The default option is YES, indicating that the GK can control the local office to release the calls.

Manufacturer code



It defines the code of the upper GK interconnected with the SoftX3000. It is valid only when H323 trunk type is set to H323 GK trunk.

Incoming trunk TOS

It defines the TOS conversion index used by the incoming H.323 trunk. It is valid only when H323 trunk type is set to H323 GK trunk. The parameter must be defined by ADD TOSC before being used here.

Outgoing trunk TOS

It defines the TOS conversion index used by the outgoing H.323 trunk. It is valid only when H323 trunk type is set to H323 GK trunk. The parameter must be defined by ADD TOSC before being used here.

Send tech-prefix flag

It is one of the parameters for the SoftX3000 to interwork with other softswitches or GKs. It is valid only when the trunk is an H.323 trunk of peer type, GK type, or outer-GK type. When the SoftX3000 sends H.323 messages to the peer office through the H.323 trunk group, this parameter defines whether the SoftX3000 inserts the parameter tech-prefix before the called number, and sends them to the peer office through an H.323 message. By default, it is set to No.

In VoIP networking of the H.323 network, if the peer softswitch or GK must authenticate H.323 calls originated by the local SoftX3000, you must set this parameter to Yes and set the parameter tech-prefix. At this time, when the local SoftX3000 originates a call, it sends "tech-prefix+called number" to the peer office through H.323 signaling.

Tech-prefix

It is one of the parameters for the SoftX3000 to interwork with other softswitches and GKs. Set this parameter only in the following two cases:

When the SoftX3000 must send "tech-prefix" to the peer office on the outgoing trunk When the SoftX3000 must authenticate "tech-prefix" from the peer office on the incoming

trunk

Set this parameter by the following principles:

It consists of only digits and # and it must be ended with #. Its maximum length is 6 characters, such as 123# and 12345#.

The SoftX3000 authenticates "tech-prefix" sent by the peer office on the incoming trunk as follows:

1. Upon receiving the H.323 message from the peer office, the SoftX3000 reads the parameter "tech-prefix" in the called number field, that is, the number before #.

2. The SoftX3000 compares the "tech-prefix" read from the H.323 message with that set on the incoming trunk group.

If they are the same, the authentication succeeds, and the SoftX3000 deletes "tech-prefix" from the called number field, and then analyzes the remaining called number.

If they are different, the authentication fails, and the SoftX3000 releases the call.

IP list number

It is available only when H323 trunk type is set to Virtual H.323 trunk. When the peer H.323 entity (GK or GW) originates a call to the local office through the H.323 incoming trunk, this parameter indicates the IP addresses from which the calls can be connected by the SoftX3000.




The value ranges from 0 to 6553. If you enter a valid value for this parameter, this value must be defined by ADD H323TG before being referenced here.





Stop call restriction

When the total number of calls (which can be queried with DSP TGCALL) is less than the quantity defined in this parameter, the system auto stops the enabled call restriction. Its value range is from 0 to 65535.

The value of stop call restriction must be smaller than or equal to that of maximum caller number restriction. For example, if the parameter stop call restriction is set to 1800 and maximum caller number restriction is set to 2000, the system auto starts call restriction when the total number of incoming and outgoing calls on one H.323 trunk group exceeds 2000, and auto stops call restriction when the total number of calls falls back to a value less than 1800 (≤ 1799).

Maximum caller number restriction

It defines the maximum number of calls allowed on one H.323 trunk group. That is, when the total number (which can be queried with DSP TGCALL) of incoming and outgoing calls on the H.323 trunk group exceeds the quantity defined in this parameter, the system auto starts call restriction. The system auto stops call restriction when the total number of calls falls back to a value less than Stop call restriction defined by this command. Its value range is from 0 to 65535. The default value is 65535, indicating that the system does not start call restriction.

Enhanced attribute


EC capability

It is one of the parameters used for the SoftX3000 to interwork with the peer office. It controls the SIP trunk to enable the EC function. The default option is YES, indicating that the EC function is enabled.

Video supported

It indicates whether one H.323 trunk can bear video transmission. It is SUPPORT by default.

Audio codec prefer, Video codec prefer

They define the codec modes of audio and video media streams preferred by the multimedia terminal controlled by the SoftX3000 during call connection.

When the MGWs are controlled by the SoftX3000 during a call, the SoftX3000 controls through signaling the MGWs of at the caller and the callee side to directly use these two parameters for connecting media streams if the SoftX3000 finds that the codec modes



supported by the caller and the callee have intersection and the intersection contains the audio/video codec prefer defined here.

You can set codec prefer data in the following tables:

Subscriber data table (with ADD VSBR or ADD MSBR) Trunk data table (with ADD N7TG or ADD SIPTG) Called number analysis table (with ADD CNACLD) Calling number discrimination table (with ADD CLRDSN)

If a call involves more than two codec prefer modes, the SoftX3000 chooses one by the following principles:

The audio/video codec prefer defined in the calling number discrimination table enjoys the highest priority, and that in the called number analysis table enjoys the second.

If a call does not involve the audio/video codec prefer defined in either the calling number discrimination table or the called number analysis table, the SoftX3000, based on the principle of "caller and subscriber first", selects a codec mode. For example, − In an intra-office call, if the codec prefer of the caller is different from that of the callee,

the codec prefer of the caller is valid. − In an intra-office outgoing call, if the codec prefer of the caller is different from that of

the outgoing trunk group, the codec prefer of the caller is valid. − In a transit call, if the codec prefer of the local incoming trunk group is different from

that of the local outgoing trunk group, the codec prefer of the local incoming trunk group is valid.


H245 route supported

It controls whether the SoftX3000 forwards the H.245 route message sent by the H.323 equipment when the caller and callee are H.323 equipment, and at least one of them uses normal start work mode. The default option is No.

If it is set to No, a direct route exists between the H.323 equipment at the caller and the callee side. That is, the equipment at the caller and the callee side exchanges H.245 route messages directly. No H.245 messages between the caller and callee are forwarded by the SoftX3000. Therefore, the SoftX3000 cannot obtain information such as media channel attribute and provide related data on bills.

If it is set to Yes, GK route is used between the H.323 equipment at the caller and the callee side. That is, the equipment at the caller and the callee side exchanges H.245 route messages through GK (the SoftX3000).

2833 encryption flag

It is one of the parameters for the SoftX3000 to interwork with the peer H.323 device. It indicates if HNC1 encryption algorithm of RFC2833 is supported in the SIP trunk group direction by the local SoftX3000 and the peer H.323 device. By default, it is set to No.

If the local SoftX3000 and the peer H.323 device support RFC2833 and its HNC1 encryption algorithm, set this parameter to Yes. This is to ensure the reliable transfer of DTMF signals in the IP network.

For details, see chapter 2 "Configuring MGW Data."

2833 encryption key




It is valid only when the parameter 2833 encryption flag is set to Yes. It is one of the parameters for the SoftX3000 to interwork with the peer H.323 device. It defines the RFC2833 shared secret key between the SoftX3000 and the H.323 device. It is a string of 8 to 16 characters.

Call-in authority




For the SIP incoming trunk and H.323 incoming trunk, the SoftX3000 cannot control the national incoming toll call or international incoming toll call because of the restriction of signaling. This is not so for the SIP-T incoming trunk.

Call-out authority





This parameter is available only to incoming trunks. If Caller number provision mode of the trunk group is Default number and no caller number is contained in the call signaling message sent by the peer office when it originates a call through the incoming trunk, the local office uses the default caller number.



7.4 Configuring No. 7 Trunk Data 7.4.1 Overview

Configuration Relation The No. 7 trunk data configures the No. 7 trunk related information used for interconnection between the SoftX3000 and PSTN switch, such as:

Signaling type of No. 7 trunk circuit Circuit identification code

The No. 7 trunk data must be configured after the following data is configured:

Equipment data Local office data Charging data Media gateway data Signaling data Routing data


During the configuration, the No. 7 trunk data reference certain parameters defined in:

Local office data Charging data Media gateway data Routing data

The parameter Network management source code defined in the No. 7 trunk data will be referenced when the network management data is configured. Table 7-11 lists the details.

Table 7-11 Parameter referencing relation between the No. 7 trunk data and other data



Call source code Local office data Network management source code




Charging data - -

Equipment ID of trunk media gateway (TMG)

Media gateway data - -









Call barring group number (optional)


Configuration Preparations Before configuring the No. 7 trunk data, prepare as specified in Table 7-12.

Table 7-12 Preparations for configuring the No. 7 trunk data

SN Item Remark

1 Originating signaling Point Code (OPC) of the signaling in No. 7 trunk group

For interworking with PSTN switch

2 Destination signaling Point Code (DPC) of the signaling in No. 7 trunk group


3 Group direction of No. 7 trunk group, including outgoing trunk, incoming trunk or bi-directional trunk


4 Signaling type of No. 7 trunk group, including TUP and ISUP


5 Circuit selection mode of No. 7 trunk group Correctly planned to avoid that a circuit is occupied by two offices at the same time

6 Range of circuit numbers for No. 7 trunk circuits

These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA, and R2 trunk circuits. The corresponding physical numbers assigned at the TMG are specified in the start circuit termination identifier parameter.

7 Termination identifier of circuit number For interworking with TMG

8 Start CIC For interworking with PSTN switch

Configuration Steps Table 7-13 lists the general steps for configuring the No. 7 trunk data.



Table 7-13 Steps for configuring the No. 7 trunk data


1 Add a No. 7 trunk group. ADD N7TG

2 Add a No. 7 trunk circuit. ADD N7TKC

3 Add a carrier access code. (Optional) ADD CAC

4 Add a carrier selection code. (Optional) ADD CSC

5 Add an originating network ID. (Optional) ADD ONID

6 Add a PCM port. (Optional) ADD PCMPORT

Parameter Referencing Relation Figure 7-7 shows the referencing relation between the key parameters used when the No. 7 trunk data is configured.

Figure 7-7 Parameter referencing relation of the No. 7 trunk data

Trunk group number

ADD N7TG

Equipment ID

Group direction

FCCU module number

ADD N7TKC

Trunk group number

Start circuit number




7.4.2 Adding No. 7 Trunk Group

Related Commands

Command Function

ADD N7TG To add a No. 7 trunk group

RMV TG To remove a No. 7 trunk group

MOD N7TG To modify a No. 7 trunk group

LST TG To list No. 7 trunk groups

Notes of Configuration Before adding a No. 7 trunk group, run the commands to obtain the following parameters defined by the system:

Parameter Command




Caller number discrimination group number (optional) LST CLRDSN


Equipment ID of the TMG LST MGW




Assign its value globally. The value ranges is from 0 to 65534.



Equipment ID

It defines the equipment ID of the TMG (such as the TMG8010 or UMG8900) providing No. 7 trunk circuits. This parameter must be defined by ADD MGW before being used here.

Group direction

It defines the call connection direction of the No. 7 trunk group. The default option is Bi-directional trunk. The parameter options are described as follows:

Incoming trunk It indicates that the local office processes only the incoming calls from the peer office.

Outgoing trunk It indicates that the local office processes only the outgoing calls to the peer office.

Bi-directional trunk It indicates that the local office processes the calls from and to the peer office.

Sub-route number


OPC

It is one of the parameters used for the SoftX3000 to interwork with the peer office. It defines the OPC of the No. 7 trunk group. The default code is the signaling point code of the local office in the national network defined in SET OFI. If it is required to use signaling point code in other signaling network, such as international network, you must specify it separately.

Due to the limitation of the SS7 CIC length (12 bits), two offices can enable up to 4096 No. 7 trunk circuits in the case of using a single signaling point code. If it is necessary to enable more trunk circuits, multi-signaling-point-code is required in either the local office or the peer office. If the multi-signaling-point-code is used in the local office, this parameter must be defined by ADD OFI before being used here.

DPC

It is one of the parameters used for interworking with the peer office. It defines the DPC of the No. 7 trunk group. The system uses DPC1 defined in ADD OFC by default.

Due to the limitation of the SS7 CIC length (12 bits), two offices can enable up to 4096 No. 7 trunk circuits in the case of using single signaling point code. If it is necessary to enable more trunk circuits, multi-signaling-point-code is required in either the local office or the peer office. If the multi-signaling-point-code is used in the peer office, this parameter must be defined by ADD OFC before being used here.

Trunk group name


Call source code


Circuit type

It defines the signaling type used by the No. 7 trunk group, including ISUP and TUP. The default type is ISUP.




Circuit selection mode

It defines the policy for selecting the trunk circuits in a trunk group. The default mode is Master/slave. The options are as follows:

Minimum The system always selects a trunk circuit with the minimum number. The preferential selection of the trunk circuits can be realized through this mode.

Maximum The system always selects a trunk circuit with the maximum number. The preferential selection of the trunk circuits can be realized through this mode.

Cyclic The system selects a circuit from the next one to the last selected circuit number each time. If the last selected number is the maximum one, the next one is the minimum number.

FIFO For all the circuits of the trunk group, the system selects a circuit according to the "first in, first out" principle. That is, the circuit released first is selected first.

Master/slave For the circuits controlled by the local office, the system selects a circuit according to the "first in, first out" principle. For the circuits not controlled by the local office, the system selects a circuit according to the "first in, last out" principle. That is, the circuit released first is selected last.

Random The system selects a trunk circuit randomly. This mode is seldom used.

User side allocation The system selects a circuit according to the instruction from the user side.

If the No. 7 trunk group is a bi-directional one, it is recommended to set Circuit selection mode to Master/slave. This is to prevent two offices occupying the same circuit at the same time.


It identifies whether the No. 7 trunk is carried over a satellite circuit. Set it based on the actual conditions. Generally, it is set to NO.

International call

It indicates whether the local office sets the bit national/international call indicator of the forward call indicator parameter to 1 in the Initial Address Message (IAM) sent to a lower national office or a peer international office when the SoftX3000 connects international incoming or outgoing calls. The value 1 means that the call is processed as an international call.

The default value is No, indicating that the local office does not process the international calls on the No. 7 trunk group. This feature is mainly used in Hong Kong.

Number incomplete

It defines whether the SoftX3000 sets the bit caller number incomplete indicator of the parameter caller number in the IAM to 1. The value 1 indicates that the caller number is incomplete.

The default value is No, indicating that the local office does not process the IAM. This feature is mainly used in Hong Kong.

Call-in authority




Intra-office Local Local toll National toll International toll Intra-office national toll (in multi-zone-code application) intra-office international toll (in multi-country-code application) Intra-office local toll

Call-out authority



DOD2

It is valid only for outgoing trunks. With the software parameters "TUP operation reserved parameter 3 (P10) and "TUP operation reserved parameter 4 (P11)", it controls the preset value of the caller category in the IAM/Initial Address Message with Information (IAI) sent by the local office.

If it is set to Yes and bit 2 of the TUP operation reserved parameter 4 is set to 0, the preset value of the caller category in the IAM/IAI is "bit 13–8" of the TUP operation reserved parameter 3.

CLIR flag

It is used to manually set the value of the CLIP flag in the IAM or Initial Address Message with Information (IAI) of the incoming call signaling or outgoing call signaling, that is, the original value of CLIP in the call signaling is invalid.

Nothing select It is the default option, indicating that the original value of "CLIP flag" in the call signaling need not be changed.

Incoming CLIR It indicates the CLIP flag bit in IAM or IAI in the incoming call signaling is set to 1.

Outgoing no CLIR It indicates the CLIP flag bit in IAM or IAI in the outgoing call signaling is set to 0.

Send initial tone

It is valid only for incoming trunks. With the software parameters "TUP operation reserved parameter 3 (P10)" and "TUP operation reserved parameter 4 (P11)", it controls the preset value of the caller category in the IAM/IAI received by the local office.




If it is set to Yes and bit 2 of the TUP operation reserved parameter 4 is set to 0, the preset value of the caller category in the IAM/IAI is bits 7–0 of the TUP operation reserved parameter 3.

Send exceptional tone

It controls the local office to send exceptional tone to the peer office through the Address Complete Message (ACM) when the call through the incoming trunk fails. It is valid only for incoming trunks.

If the parameter is set to NO, the local office sends Release (REL) message to the peer office when the call fails. In this case, the call is released and the peer office sends busy tone to the caller.

If the parameter is set to YES, the local office sends ACM to the peer office when the call fails. In this case, the call is held temporarily and the local office sends exceptional tone to the caller through the incoming trunk. If the caller hangs up or the timer times out, the call is released.







Use opposite pulse

It is used for the inter-office trunk cooperation in the instant charging. When it is set to Yes, its meanings for outgoing trunk and incoming trunk are different.

Outgoing trunk When there is an outgoing call from the trunk group, the local office must receive the charging pulse in the signaling sent back from the peer office. The peer office must cooperate to send the charging pulse to the local office through signaling.

Incoming trunk When there is an incoming call to the trunk group, the local office must send charging pulse to the peer office through signaling. The peer office must cooperate to receive the charging pulse sent from the local office through signaling.

CAMA

It is valid only for incoming trunks. It sets whether the local office performs centralized accounting operations on the incoming trunk. If the value is YES, the local office adopts the centralized accounting mode for the incoming trunk. In this case, when the peer office originates a call through the incoming trunk, the local office requests the calling number on initiative through signaling if the signaling from the originating office does not carry the calling number.



Can request caller number

It sets whether to request caller number. It is valid only for incoming trunks. When the Whether request caller number parameter is set to YES, this parameter is used to ask the local office to request caller number from the peer office if the incoming call signaling through the trunk does not contain caller number. The default option is YES, indicating that the local office can request caller number on initiative. If this feature affects connection or connection time, the option can be set to NO.

Connect without valid caller number

It sets whether the local office gets a call through if the incoming call signaling through the trunk does not contain caller number or the contained number is invalid. It is valid only for incoming trunks. The default option is YES.

Caller number provision mode

When the peer office originates a call through the incoming trunk, this parameter indicates how the local office obtains the calling number from the incoming trunk if the call signaling from the peer office contains no calling number. It is valid only for incoming trunks.

Trunk line ID It indicates that the calling number is an ID of a trunk circuit.

Default number It indicates that the calling number is the default one pre-defined in this command.

If the peer office sends the calling number in the incoming call signaling, the local office uses it and this parameter is invalid.


If Caller number provision mode of the trunk group is Default number and no caller number is contained in the call signaling message sent by the peer office when it originates a call through the incoming trunk, the local office uses the default caller number. The parameter is valid only for incoming trunks.

Call barring group number

It defines the call barring group to which the trunk group belongs. The parameter configuration principle is described as follows:

If the value is not specified or is set to 65535, it indicates that the inter-group call barring function is not enabled.

If the black/white list barring is used, the preset three call barring groups can be referenced directly, that is, black list 60001, white list 60002 and ordinary call barring group 65534.

If other call barring groups are expected, this parameter must be defined by SET GRPAC before being used here.

During the number analysis process of inter-group call barring authentication, the SoftX3000 authenticates twice the caller, called prefix, and the callee. The inter-group call barring authentication procedure is as follows:

1. When a local subscriber or incoming trunk initiates a call, the SoftX3000 authenticates the call barring group number of the caller or incoming trunk (caller barring group number), by comparing with the call barring group of the called prefix (called barring group number, configured by ADD CLDGRP, 65534 by default). If the authentication succeeds, the SoftX3000 proceeds with subsequent procedures. Or else, the SoftX3000 rejects the call.




2. When the call passes the first inter-group call barring authentication, the SoftX3000 authenticates the call barring group number of the caller or incoming trunk (caller barring group number) and that of the callee or outgoing trunk (called barring group). If the authentication succeeds, the SoftX3000 proceeds with subsequent procedures. Or else, the SoftX3000 rejects the call.

Upper seizure threshold

It defines the maximum seizure duration of a trunk circuit. If a trunk circuit is seized for a time longer than this threshold, the system checks the circuit status and generates an alarm. Its value range is from 0 to 65535, in unit of second. The value 0 or 65535 indicates that the threshold is invalid.

Lower seizure threshold

It defines the minimum seizure duration of a trunk circuit. If a trunk circuit is seized for a time shorter than this threshold, the system counts one over-short seizure. If the number of over-short seizures is bigger than the value of the lower 8 bits in the TUP operation reserved parameter 1, the system generates an alarm. Its value range is from 0 to 65535, in unit of second. The value 0 or 65535 indicates that the threshold is invalid.

Continuity check

It is valid only for outgoing trunks. When the local office originates a call through the trunk group, this parameter sets whether the local office checks continuity in the trunk group direction. Its value range is 0 to 100, in unit of %. By default, it is set to 0, indicating that the local office never checks continuity on initiative. If it is set to 100, the local office checks continuity for every outgoing call. If it is set to 50, the local office checks the continuity of 50% of all outgoing calls. It is the same in other cases.

Time delay value

It sets the maximum transmission delay allowed by the circuits of a trunk group. Its value range is from 0 to 1023, in unit of second. If the transmission delay of a call through the circuit segments is larger than the maximum transmission delay allowed by the system, it is required to configure echo canceller. This parameter is generally used for the case of connecting satellite circuits. In other cases, it is set to 0.

Group message timeout to single

When the local office cannot receive the acknowledgment messages from the peer office for the sent group messages, this parameter sets whether the local office forwards the related signaling message, that is, to send RSC message instead of GRS message. Generally, it is set to NO.

Transmission capability

It is one of the route selection conditions. It defines the service types that the route can bear, such as voice service, digital service, and video service. Generally, it is set to All.

Transmission mode

It defines the transmission rates that the trunk group can provide, including packet mode, 64 kbit/s, 128 kbit/s, and 1920 kbit/s. If there is no special requirement, set it to Multiple rate.

CIC change type

It is mainly used for the self-loop test of the two No. 7 trunk groups (outgoing trunk E1 and incoming trunk E1) with the same office direction in the local office. The configuration principle is described as follows:



When the self-loop test is not enabled, you must set this parameter to No change. Or else, the trunk interconnection fails.

When the self-loop test is enabled, if the CIC change type of the outgoing trunk group is set to Increase, CIC change type of the incoming trunk group must be set to Decrease, and conversely the same.

CIC change value

It sets the CIC change value. The self-loop test is performed between two E1s, the CIC change value must be a multiple of 32. This parameter is valid only when CIC change is necessary.

Availability

It is valid only when the trunk group selection mode of a subroute is set to Cyclic. It defines the times that a trunk group can be selected in the corresponding subroute. Its value range is from 0 to 255. By default, it is set to 255, indicating the parameter is invalid.

In a subroute, every time the system selects the trunk group, the available times of the trunk group is decreased by 1. When the available times become 0, the system cannot select the trunk group. If the available times of all trunk groups in the corresponding subroute become 0, those times are assigned with new values. This parameter is designed to distribute the traffic over all trunk groups of the subroute according to the expected principle, that is, the carrier can use this parameter to control the selected ratio of each trunk group of a subroute.


It sets whether an ISUP trunk supports certain special services or applications. There are 16 options for this parameter. Currently, only seven options are used, and the others are reserved. The meanings of the options are as follows:

Wide area network Centrex service It is used with bit 4 of the parameter "ISUP operation reserved parameter 9 (P26)". If you select this option and bit 4 of the "ISUP operation reserved parameter 9" is 0, the local office sends a short number contained in the IAM to the peer office in the WAN Centrex service.

Blocked ISUP circuit cannot be reset If you do not select this option and the circuit is blocked at the peer office currently, the circuit is idle after reset. If you select this option (mainly applicable to Hong Kong), the blocked circuit is still blocked after reset. At this time, you can only use the unblocking command to release the blocked circuit.

Use default caller number in incoming call It is used with bit 12 of the parameter "ISUP operation reserved parameter 9 (P26)". If you select this option and bit 12 of the "ISUP operation reserved parameter 9" is 0, the local office masks the real caller number sent by the peer office and uses the default caller number in this command when the peer office originates a call through the incoming trunk to the local office.

Send default caller number in outgoing call It is used with bit 13 of the parameter "ISUP operation reserved parameter 9 (P26)". If you select this option and bit 13 of the "ISUP operation reserved parameter 9" is 0, the local office masks the real caller number and uses the default caller number in this command when the local office originates a call through the outgoing trunk to the peer office.

Send ringback tone for HK It is valid only for incoming trunks. If you select this option, the local office, no matter whether it is a terminating office, sends the ringback tone to the peer office when the peer




office originates a call through the incoming trunk. This feature is mainly applicable to Hong Kong.

Peer office no ringback tone It is valid for outgoing trunks in transit calls. If you select this option, the local office (transit office) sends the ringback tone to the caller. If you do not select this option, the terminating office sends the ringback tone to the caller. Note that when the terminating office needs to send the special signal tone, such as failure announcement, to the caller, this parameter is invalid.

IDR/IDS flag It indicates whether the No. 7 trunk group uses IDR/IDS signaling flow when implementing the MCID service. If the option is selected (mainly used in Russia), IDR/IDS signaling flow is to be used. If not, INR/INF signaling flow is to be used.

Network management source code

It defines the network management attributes of a trunk group. It is valid only for incoming trunks. It will be referenced when the network management data is configured.

Idle circuits for weak call restriction

It is used with the "NM trunk reserved control" instruction for call restriction. It must be more than those for forced call restriction. Table 7-14 lists the applications of the parameter.

Table 7-14 Applications of the parameter

Type When… Then…

No call restriction Actual idle circuits of the controlled trunk group ≥ idle circuits for weak call restriction

NM trunk reserved control function is disabled, that is, the system does not start call restriction.

Weak call restriction

Idle circuits for forced call restriction ≤ actual idle circuits of the controlled trunk group < idle circuits for weak call restriction

System carries out call restriction by percentage of weak call restriction.

Forced call restriction

Actual idle circuits of the controlled trunk group < idle circuits for forced call restriction

System carries out call restriction by percentage of forced call restriction.

Idle circuits for forced call restriction

It is used with the "NM trunk reserved control" instruction for call restriction. Idle circuits for weak call restriction must be more than those for forced call restriction.

Bar forwarded call

It sets whether to bar the forwarded calls unconditionally. The default option is NO, indicating no barring. If the value is set YES, the system bars all the calls forwarded through the trunk group.

Default connect

If querying caller number discrimination group failed, it sets whether to connect the call. The default option is YES, indicating that the call is connected.



Whether request caller number

If the incoming call signaling through the trunk does not contain caller number, it defines whether the local office requests caller number from the peer office on initiative. It is valid only for incoming trunks. The default option is NO, indicating that the local office does not request caller number on initiative.

Request original called number

It sets whether to request the original called number. It is valid only for incoming trunks. In a forwarded call (the call redirection indicator is 1), if the incoming call signaling through the trunk does not contain the original called number, this parameter tells the local office whether to request the original called number from the peer office. The default option is NO, indicating that the local office does not request the original called number on initiative.

It should be noted that if the incoming trunk needs to conduct caller number discrimination, the system discriminates only the original called number in the forwarded call instead of the caller number. If the peer office does not send the original called number on initiative, the following cases occur:

For the TUP trunk, the original called number can be obtained when this parameter is set to YES.

For the ISUP trunk, the local office can get only the false number even when this parameter is set to YES.

Therefore, for the ISUP trunk, if it is required to discriminate the original called number in the forwarded call, the peer office must send the original called number on initiative.

Connect without valid original called number

It is valid only for incoming trunks. It sets whether the local office connects a call if the incoming call signaling through the trunk does not contain the original called number or the contained number is invalid in a forwarded call (the call redirection indicator in the signaling message is 1). The default option is YES.

Overlap send called number

It defines whether a trunk group supports overlap code sending mode. The SoftX3000 supports the two code sending modes as show in Table 7-15.

Table 7-15 Details of two code sending modes

Code Sending Mode

When… Then…

Overlap code sending

System receives enough digits of the called number for judging the route.

It sends them to the peer office through the signaling IAM or IAI.

It sends the remaining digits of the called number one by one through SAO or SAM.

Group code sending

System collects all the digits of the called number.

It sends them to the peer office through one signaling message.




Code Sending Mode

When… Then…

NOTE SAO = Subsequent Address Message with One signal SAM = Subsequent Address Message

The overlap code sending mode features fast connection but occupies a plenty of CPU resources. The group code sending mode occupies a few of CPU resources, but the connection is slow, which may affect the quality of the telecom services. The default mode is overlap code sending. When the SoftX3000 interconnects with a switch complying with ANSI through the No. 7 trunk group, you must set this parameter to No.

Software parameter of signaling control

It defines whether ISUP trunk supports certain special signaling modes. The meanings of the options are as follows:

Calling party number with ST If this option is selected, ST signal is added at the end of a calling number.

Called party number with ST If this option is selected, ST signal is added at the end of a called number.

Connected party number with ST If this option is selected, ST signal is added at the end of a connected number.

Generic number with ST If this option is selected, ST signal is added at the end of a generic number.

Original called party number with ST If this option is selected, ST signal is added at the end of an original called number.

Redirecting number with ST If this option is selected, ST signal is added at the end of a redirecting number. The redirecting number is the information sent forward and indicates the number to which a call is sent at last.

Redirection number with ST If this option is selected, ST signal is added at the end of a redirection number. The redirection number is the information sent backwardly and indicates the number to which a call is forwarded.

Intercept COT Suppose the networking is "A→B→C", only No. 7 trunks are used between offices, and the SoftX3000 functions as transit office B. By default, when office A calls office C, it sends an IAM to office B. If office A requests continuity check to the circuit between office A and office B through the IAM, transit office B transfers the IAM to office C only after receiving the Continuity (COT) message from office A indicating successful continuity check. If this option is selected, it indicates that the local office (transit office B) transfers the IAM to office C immediately after receiving it from office A, without waiting for the COT message from office A.

Reserved signaling 8 It is reserved.

Send original called number



If you select this option, the called number in the IAM sent by the local office to the peer office is the same as the original called number when a call is forwarded. If you do not select this option (default value), the called number in the IAM sent by the local office to the peer office is different from the original called number when a call is forwarded.

Not support hold request indicator If you select this option, the local office cannot include "hold request indicator" in the INR message sent to the peer office.

Not support calling party is category request indicator If you select this option, the local office cannot include "calling party’s category request indicator" in the INR message sent to the peer office.

Not support charge information requested indicator If you select this option, the local office cannot include "charge information requested indicator" in the INR message sent to the peer office.

Not support calling number request indicator If you select this option, the local office cannot include "calling number request indicator" in the INR message sent to the peer office.

Not support malicious number request indicator If you select this option, the local office cannot include "malicious number request indicator" in the INR message sent to the peer office.

Charge number with ST If you select this option, ST signal is added at the end of a charge number.

Extended overlap send called number

It sets whether a No. 7 trunk group supports extended overlap code sending mode, that is, whether the trunk group can send the remained digits of the called number to the peer office through an SAM.

It is different from the overlap code sending mode. In the overlap code sending mode, the remained digits of the called number can be sent to the peer office in one or several SAOs/SAMs. In the extended overlap code sending mode, only the remained digits are sent to the peer office in one SAM.

Disconnection procedure

In ISUP trunk, when the circuit release mode is "Calling party release" or "Called party release", this parameter controls which message the slave party resident office sends to the peer office if the slave party (not controlling the release) hangs up while the master party (controlling the release) hangs on. The peer office does not release the call after receiving the message. There are different specifications in different countries. For example, this message in China is Suspend (SUS).

Inter-gateway circuit flag

It defines whether the SoftX3000 flags the circuits in a trunk group as inter-gateway circuits (IGC). The default value is No. If it is set to Yes, all circuits in the trunk group are flagged as IGC, which means that the ISUP signaling in the trunk group direction supports the Incoming Route Identifier (IRI) in the IAM and the Outgoing Route Identifier (ORI) in the ACM. For details of IRI and ORI, see Table 7-16.




Table 7-16 Details of IRI and ORI

Name Description Function Remark

IRI Additional parameter in the IAM with the "(incoming) trunk group identifier" field

Charging Routing

After the terminating office receives the IAM with IRI from the local office, it can judge the incoming trunk group of the local office through which the call is transferred.

ORI Additional parameter in the ACM with the "message indicator" field and the "(outgoing) trunk group identifier" field

Charging After the terminating office receives the ACM with ORI from the local office, it can judge the route or outgoing trunk group of the local office through which the call is transferred.

This feature is applicable to Singapore. The two fields "message indicator" and "trunk group identifier" in the IRI/ORI are defined in Route ID message indicator and Route ID trunk group ID in this command.

Route ID message indicator

It defines the message indicator field in the ORI of the ACM. It is available only when Inter-gateway circuit flag is set to Yes. The options are:

National route Transit route Terminating route Spare route

Route ID trunk group ID

It is valid only when Inter-gateway circuit flag is set to Yes. Set this parameter by the following principles:

For outgoing trunks, it defines the trunk group identifier field in the IRI of the IAM, that is, it defines the incoming trunk group of the local office through which a call is connected.

For incoming trunks, it defines the trunk group identifier field in the ORI of the ACM, that is, it defines the outgoing trunk group of the local office through which a call is connected.

Trunk group identifier is a trunk group ID identified by two offices interworking through IGC. It is different from the trunk group number defined in the SoftX3000 in functions.

EC use mode

It defines how the SoftX3000 distributes EC parameter to the TMG. The default setting is Always send EC. When the TMG has the echo cancellation function, the parameter options are described as follows:

Always send EC For incoming trunks or outgoing trunks, despite the value of the EC indicator carried in the IAM or the ACM/CON sent by the peer office, the SoftX3000 always sends EC=ON to the TMG.

Never send EC



For the incoming trunk or the outgoing trunk, despite the value of the EC indicator carried in the IAM or the ACM/CON sent by the peer office, the SoftX3000 always sends "EC=OFF" to the TMG.

Send EC if needed For incoming trunks, if the value of the EC indicator carried in the IAM sent by the peer office is NO, the SoftX3000 sends EC=ON to the TMG. If the value of the EC indicator in the IAM is YES, the SoftX3000 sends EC=OFF to the TMG. For outgoing trunks, if the value of the EC indicator in the ACM/CON sent by the peer office is NO, the SoftX3000 sends EC=ON to the TMG. If the value of the EC indicator in the ACM/CON is YES, the SoftX3000 sends EC=OFF to the TMG.

Send EC if mandatory For incoming trunks, only when the value of the EC indicator carried in the IAM sent by the peer office is NO and the delay is bigger than that defined in this command, the SoftX3000 sends EC=ON to the TMG. In other cases, the SoftX3000 sends EC=OFF to the TMG. For outgoing trunks, the SoftX3000 always sends EC=OFF to the TMG. If the TMG has no echo cancellation function, the SoftX3000 always sends EC=OFF to the TMG.

Support EC in hairpin call

It sets whether the TMG supports EC for hairpin call. If the option is No, it indicates that the SoftX3000 does not send EC parameter to the TMG. Only when the TMG is the UMG8900, the parameter is set to YES.

NOA attribute

You can set Transparent called NOA, Cast called NOA, Called NOA, Cast caller NOA and Caller NOA only when this parameter is set to TRUE.

Codec prefer

It defines the codec mode preferred by MGW (instructed by the SoftX3000 during call control process) for the RTP audio media streams in the trunk group direction. Set this parameter by the following principles:

Codec prefer defined here has already been defined in Codec list in ADD MGW. Or else, it is invalid.

If the option is set to None (the default option), the codec prefer is determined by the sequence of the codec list of the TMG in the MGW data table, that is, the first codec mode that can be queried with LST MGW.

You can specify a specific codec mode.

When all MGWs in a call process are controlled by the SoftX3000, and the SoftX3000 finds intersections, covering Codec prefer, between the codec of the caller and the callee, the SoftX3000 controls the MGWs at the caller and callee sides to directly use Codec prefer for stream connections.

You can configure Codec prefer in the tables listed in Table 7-17.

Table 7-17 Details of tables

Table Configured by

User data table ADD VSBR




Table Configured by

Trunk data table ADD N7TG

Called number analysis table ADD CNACLD

Caller number discrimination table ADD CLRDSN

When a call has two or more codec preferences, the SoftX3000 selects one according to the following principles:

Codec prefer in the caller number discrimination table takes the highest priority, and then the called number analysis table.

When the call does not involve Codec prefer in neither the caller number discrimination table nor the called number analysis table, the SoftX3000, according to the principle of "caller and subscriber prior to callee and trunk", selects a codec during call connection. For example, − In an intra-office call, if the codec prefer of the caller is different from that of the callee,

the codec prefer of the caller is valid. − In an outgoing call, if the codec prefer of the caller is different from that of the outgoing

trunk group, the codec prefer of the caller is valid. − In a transit call, if the codec prefer of the local incoming trunk group is different from



Transparent called NOA

It determines whether the local office, when it functions as a transit office, forwards the address nature of a called number carried in an incoming office signaling message, such as IAM, transparently. The default value is No, indicating that the local office does not send the address nature of the called number transparently. This parameter is used with the parameters Cast called NOA and Called NOA in this command.

If this parameter is set to Yes, the local office transparently transmits the address nature of the called number carried in the incoming signaling message in any cases.

If this parameter and Cast called NOA are set to No, the local office transparently transmits the address nature of the called number carried in the incoming signaling message.

If this parameter is set to No and Cast called NOA is set to Yes, the local office transmits the address nature of the called number specified in this command.

Cast called NOA

It determines whether the local office re-sets the called NOA parameter in an outgoing signaling message, such as IAM. The default value is No, indicating that the local office does not re-set the called NOA. If it is set to Yes,

For outgoing calls made by local subscribers, the local office always transmits the called NOA defined in this command in an outgoing signaling message.

For outgoing calls forwarded by the local office, when Transparent called NOA is set to Yes, the local office transparently transmits the called NOA carried in the incoming signaling message.



For outgoing calls forwarded by the local office, when Transparent called NOA is set to No, the local office transmits the called NOA defined this command in an outgoing signaling message.

Called NOA

It is used to manually set the parameter called NOA in an outgoing signaling message, such as IAM. It is available only when Cast called NOA is set to Yes. The default value is Unknown1(national use).

Cast caller NOA

It determines whether the local office re-sets the caller NOA parameter in an outgoing signaling message, such as IAM. The default value is No, indicating that the local office does not re-set the caller NOA. If it is set to Yes, the local office always transmits the called NOA defined in this command in an outgoing signaling message.

Caller NOA

It is used to manually set the parameter caller NOA in an outgoing signaling message, such as IAM. It is available only when Cast caller NOA is set to Yes. The default value is Unknown1(national use).

HOP counter flag

It indicates whether the system starts the HOP counter function on the No. 7 trunk group. The default option is No.

It is one of the parameters in forward IAMs. It controls the maximum number of segments of ISUP circuits that can be connected in one call. This is to minimize the occurrence of route selection loop because of errors in the network routing. If the parameter is set to Yes, the operations vary under different conditions. Table 7-18 lists the details.

Table 7-18 Different operations based on different conditions

If the local office is a (an)…

Then…

Originating office in a call It should carry the HOP counter parameter when sending IAM message forward.

Initial value of the HOP counter parameter is defined by HOP counter value in this command.

If the HOP counter is not 0, the local office fills the value of the HOP counter parameter minus 1 in the IAM message and forwards it to the subsequent office.

Tandem office in a call, and the received IAM message includes the HOP counter parameter

If the HOP counter is 0, the local office returns the REL message (the cause value is #25, which indicates switching route error) to the originating office to release the call.

Terminating office of a call

No operation is performed to the HOP counter parameter in the received IAM message.

HOP counter value




It defines the initial value of the HOP counter parameter when the local office sends (not forwards) an IAM message forward. It is valid only when HOP counter flag is set to Yes.

National Variant

It indicates the type of the SS7 applied by the No. 7 trunk group. By default, it is ITU-T. If the SoftX3000 interconnects with the switch complying with ANSI specifications through the No. 7 trunk group, you must select ANSI. At this time, the No. 7 trunk group cannot use the overlap code sending mode.

When it is set to UK, the Presentation number parameter is valid. In this case, the number displayed on the callee's phone set is the real number of the PBX subscriber and the number charged is the PRA trunk number.

To use the Philippine TUP service, set the parameter to Philippine. At the same time, set the country code to 63 when you run ADD ACODE and ADD LDNSET to set the area code and the local DN set.

To use the operator break-in service of the Thailand TOT, set the parameter to Thailand. The SoftSwitch functioning as an end or a tandem office interconnects with the console through the ISUP trunk.

MPM type

During the process of CRG charging, if the local office functions as a tandem office in a call and the charging signaling message received by the local office from the charging office does not specify the MPM type, the parameter specifies the MPM type used in the charging signaling message forwarded by the local office to the charging office.

Timer group index

It is reserved.

Reserved circuit number for priority user

It defines the number of circuits in a trunk group reserved for subscribers and calls with higher priority. When the number of idle circuits in the trunk group is equal to or less than the number defined here, the system allocates trunks only for the new calls originated by the subscribers with higher priority or those with priority (defined in SET PFXPRI). Its value range is from 0 to 9999. The default value is 0, indicating no reserved circuits.

Reserved circuit number for incoming call

It is valid only when the trunk group is bi-directional. It defines the minimum number of circuits in the trunk group reserved for incoming calls. When the number of idle circuits in the trunk group is reduced to the number defined here, the system allocates trunks only for incoming calls. Its value range is from 0 to 65535. The default value is 0, indicating no reserved circuits.

ISUP mask

It indicates whether to enable the following parameters:

ISUP transmit mask ISUP receive mask ISUP compatibility tx mask ISUP compatibility rx mask

ISUP transmit mask



It converts the ISUP messages sent by the local office in the trunk group direction. This is to adapt to the ISUP signaling used by the peer office. Set the parameter based on the ISUP signaling adaptation script offered by Huawei.

ISUP receive mask

It converts the ISUP messages received by the local office in the trunk group direction. This is to adapt to the ISUP signaling used by the peer office. Set the parameter based on the ISUP signaling adaptation script offered by Huawei.

ISUP compatibility tx mask

It carries out parameter adaptation compatibility on the ISUP messages sent by the local office in the trunk group direction. This is to adapt to the ISUP signaling used by the peer office. Set the parameter based on the ISUP signaling adaptation script offered by Huawei.

ISUP compatibility rx mask

It carries out parameter adaptation compatibility on the ISUP messages received by the local office in the trunk group direction. This is to adapt to the ISUP signaling used by the peer office. Set the parameter based on the ISUP signaling adaptation script offered by Huawei.

Enhanced Attribute

If you set it to TRUE, the enhanced attributes are displayed.

Enhanced Voice Attribute

It defines the functions that optimize the voice. It can be:

Acoustic echo compression Noise compensation Enhanced voice service Automatic gain control

Based on the requirements, you can select one or more of them.

Maximum Simultaneous Call

It defines the maximum number of simultaneous calls through the trunk group. Its range is from 0 to 65535. If it is set to 65535, there is no limit for the number of simultaneous calls.

To display the numbers of different types of ongoing calls through a specified trunk group, run DSP TG.

Maximum Simultaneous Incoming Call

It defines the maximum number of simultaneous incoming calls through the trunk group. Its range is from 0 to 65535. If it is set to 65535, there is no limit for the number of simultaneous incoming calls.


Maximum Simultaneous Outgoing Call

It defines the maximum number of simultaneous outgoing calls through the trunk group. Its range is from 0 to 65535. If it is set to 65535, there is no limit for the number of simultaneous outgoing calls.





When Maximum Simultaneous Call, Maximum Simultaneous Incoming Call, and Maximum Simultaneous Outgoing Call are all set at the same time:

If the number of outgoing calls through the trunk group exceeds Maximum Simultaneous Outgoing Call, the subsequent outgoing call attempts fail.

If the number of incoming calls through the trunk group exceeds Maximum Simultaneous Incoming Call, the subsequent incoming call attempts fail.

If the total number of incoming and outgoing calls through the trunk group exceeds Maximum Simultaneous Call, the subsequent incoming or outgoing call attempts fail.

Emergency calls are not restricted. The system, however, counts them.

7.4.3 Adding No. 7 Trunk Circuit

Related Commands

Command Function

ADD N7TKC Add a No. 7 trunk circuit

RMV TKC Remove a No. 7 trunk circuit

MOD N7TKC Modify a No. 7 trunk circuit

LST TKC List No. 7 trunk circuits

Parameter Description FCCU module number

It defines the module number of the FCCU processing the No. 7 trunk calls. This parameter must be defined by ADD BRD before being used here.

The FCCU module number defined here must be the same as that defined in ADD MGW for adding the TG. Or else, the TG circuits cannot work normally.

Trunk group number

It defines the No. 7 trunk group to which the No. 7 trunk circuit to be added belongs. This parameter must be defined by ADD N7TG before being used here.

Start circuit number, End circuit number

They specify the range of the E1 circuit numbers for the No. 7 trunk circuits inside the SoftX3000. The value ranges from 0 to 9999. The configuration principles of these parameters are as follows:

These are unified logical numbers assigned in a particular FCCU module to E1 trunk circuits regarding No. 7, PRA, R2 and V5 inside the SoftX3000. The corresponding physical numbers at the TMG are specified in the start circuit termination identifier parameter of the command.

Up to 320 trunk circuits can be added in one execution of this command. To add more, run the command again.



The absolute value of the difference between the start circuit number and the start circuit termination identifier (a decimal value after converted from a binary value) must be a multiple of 32, such as 0, 32, 64, and 96.

Start CIC

It is one of the parameters used for the SoftX3000 to interwork with the peer office. It defines the CIC corresponding to the start circuit number. The CIC is an important parameter used for the interconnection of No. 7 trunk circuit. The CIC must be determined and kept consistent through the negotiation between the local office and peer office. If they are inconsistent, single pass of trunk circuits may occur.

Controlling flag of start circuit

It is one of the parameters used for the SoftX3000 to interwork with the peer office. It identifies the mode of the local office to control the start circuit when the circuit selection mode of the trunk group is "Master/slave". After the controlling mode of the start circuit is specified, the controlling modes of the other circuits in the trunk group are specified. Suppose that the controlling mode of the start circuit is Master, the controlling modes of the following circuits are Slave, Master, Slave, Master and so on.

According to the ITU-T recommendations, the office with larger signaling point code is responsible for controlling the circuits with even CICs and the office with smaller signaling point code for the circuits with odd CICs. This is to avoid that a circuit is occupied by two offices at the same time. It should be noted that this parameter is unavailable if the trunk group is a single-direction one.

Circuit state

It sets the initial state of a trunk circuit. Generally, the default value Available is used. When adding several circuits continuously, set it to Unavailable if a circuit of the TMG is used as a signaling timeslot.

Start circuit termination ID

It defines the identifier of the start circuit timeslot of a specified batch of trunk circuits in the resident trunk media gateway. Set this parameter by the following principles:

The value of this parameter can only be digits. When Termination ID mode is Limited, the absolute value of the difference between the

start circuit number and the start circuit termination ID (a decimal value converted from a binary code) must be a multiple of 32, such as, 0, 32, 64, or 96.

Termination ID mode

It defines whether the absolute value of the difference between the start circuit number and the start circuit termination ID (a decimal value converted from a binary code) must be a multiple of 32. By default, it is set to Limited.

Circuit engineering number

It is one of the parameters for the SoftX3000 to interwork with the peer office. It defines the start engineering number of the circuits in an ISUP trunk group complying with ANSI specifications. It is used in messages of the ANSI ISUP such as CVT and CVR.




7.4.4 Adding Carrier Access Code (Optional)

Related Commands

Command Function

ADD CAC To add a carrier access code

RMV CAC To remove a carrier access code

MOD CAC To modify a carrier access code

LST CAC To list carrier access codes


When the local office interconnects with another office through ISUP trunk, the SoftX3000, by default, does not authenticate the CAC in the IAM by default if the peer office sends an IAM containing CAC to the local office. Only after you run ADD CAC to add authentication information for the ISUP incoming trunk, the SoftX3000 authenticates the CAC for the call originated by the ISUP incoming trunk.


It instructs the SoftX3000 to authenticate the CAC of the calls initiated by the ISUP incoming trunk by specifying the number of the incoming trunk. The parameter must be defined by ADD N7TG before being used here.

CAC source code

It is one of the parameters for the SoftX3000 to interwork with the peer office. When the local office needs to authenticate the CAC in the IAM received from the peer office, this parameter defines the field in the IAM from which the local office reads the CAC parameter. The options are as follows:

By callee number The local office reads CAC from the called number field in the IAM, such as, Argentine ISUP signaling.

By CAC IE The local office reads the CAC from the CAC information unit of the IAM, such as, Germany ISUP signaling.

CAC discriminate

It is one of the parameters for the SoftX3000 to interwork with the peer office. It defines whether the local office should authenticate the CAC in the IAM received from the peer office. Here are the descriptions of options:

No discriminate



It means the local office does not authenticate the CAC in the IAM. That is, the local office defaults the calls originated by the peer office through the ISUP trunk as legal calls.

No discriminate send It means the local office does not authenticate the CAC in the IAM. That is, the local office defaults the calls originated by the peer office through the ISUP trunk as legal calls. In this mode, the SoftX3000 must transfer the parameter CAC number to the call processing software for further processing, such as sending CAC during a transit call, or writing the CAC in a trunk bill.

Discriminate It means the local office authenticates the CAC in the IAM. − If the CAC source code is read from the called number field of the IAM, see CAC

number for the CAC authentication process of the local office. − If the CAC source code is read from the CAC information unit of the IAM, see ADD

CSC for the CAC authentication process of the local office. − If the CAC is contained in the called number and this parameter is set to No

discriminate or No discriminate send, the SoftX3000 defaults that the called number field of the IAM from the peer office does not contain the CAC. At this time, the peer office should not be able to send the CAC to the local office. If this parameter is set to Discriminate, the peer office must send the CAC to the local office, but the local office deletes the CAC in the called number after the discrimination for the subsequent call connection.

CAC send

It is valid only when the CAC source code is read from the called number field of the IAM. When the local office needs to originate a call through the ISUP trunk, it defines whether the local office sends the CAC to the peer office through the IAM. For different calls, the SoftX3000 sends different CACs.

For an outgoing call originated by a local subscriber, the SoftX3000 sends the CAC defined in SET OFI.

For an outgoing call (transit call) originated by an ISUP incoming trunk of the local office, the SoftX3000 sends the CAC carried by the ISUP incoming trunk. If the ISUP incoming trunk does not carry the CAC or the parameter CAC discriminate is set to No discriminate, the SoftX3000 sends the CAC defined in SET OFI.

CAC number

It is one of the parameters for the SoftX3000 to interwork with the peer office. It is valid only when the CAC source code is read from the called number field of the IAM and the carrier needs to authenticate the CAC in the IAM. It defines the carrier selection code for incoming calls allowed by the local office.

If the peer office originates a call to the local office through the ISUP incoming trunk, CAC authentication succeeds only when the CAC in the called number field of the IAM is the same as that defined in this parameter. Or else, the local office rejects the call. After CAC authentication succeeds, the SoftX3000 must transfer the CAC received from the peer office to the call processing software for processing, such as, sending CAC during a transit call, or writing the CAC in a trunk bill.




7.4.5 Adding Carrier Selection Code (Optional)

Related Commands

Command Function

ADD CSC To add a carrier selection code

RMV CSC To remove a carrier selection code

LST CSC To list carrier selection codes

Notes of Configuration This step is optional and only used for CAC authentication in Germany mode.

The carrier access code is used when a gateway office authenticates a pre-selected call. That is, you can set this parameter only when the local office serves as a gateway office.

When the local office receives a call from the peer gateway office, and its ISUP trunk group is configured with authentication information by using ADD CAC, the SoftX3000 starts CAC authentication for the calls from the ISUP incoming trunk. The basic authentication procedure is as follows:

1. After receiving the IAM containing Carrier selection code from the peer office, the local office judges whether or not the carrier selection code in the IAM is the same as the Local office CAC in the local office information table (which can be configured with SET OFI). If yes, the authentication succeeds, and the local office deletes the parameter Carrier selection code in the IAM when transferring the message to the lower-level office. If not, the local office carries out step 2.

2. The local office judges whether or not the carrier selection code table (which can be configured with ADD CSC) contains the carrier selection code in the IAM. If yes, the authentication succeeds, and the local office transparently transfers the IAM to the lower-level office. If not, the local office rejects the call.

Parameter Description Carrier selection code

It defines the carrier selection code to be configured, ranging from 0 to 9 and A to E with a maximum length of six characters. The parameter is used when the local office is a gateway office. It must authenticate the pre-selected call initiated by the ISUP incoming trunk, that is, the local office should authenticate the carrier selection code in the IAM sent by the peer office. The parameter must be allocated uniformly by the telecom department on nation-wide basis.



7.4.6 Adding Originating Network ID (Optional)

Related Commands

Command Function

ADD ONID To add an originating network ID

RMV ONID To remove an originating network ID

LST ONID To list originating network IDs

Notes of Configuration This step is optional and only used for CAC authentication in Germany mode.

The original network ID is used by the peer office to authenticate a pre-selected call. The basic authentication procedure is as follows:

When a local caller uses the pre-selection service, the local office (that is, originating office) sends an IAM containing this parameter in the local office information table (which can be set with SET OFI) through the outgoing trunk. During the call connection process, this parameter is transmitted transparently to the terminating office.

Upon receiving the IAM, the terminating office judges whether or not the originating network identifier table (which can be set with ADD ONID) contains this parameter in the IAM. If yes, the authentication succeeds, and the terminating office connects the call. If not, the terminating office releases the call (the release cause value is 21).

By default, the SoftX3000 does not authenticate the ONID for calls of pre-selected routes. When you set the bit 7 of call internal parameter 8 (P155) to 0, the SoftX3000 authenticates the ONID of the calls from the ISUP incoming trunk.

Parameter Description Originating network ID

It defines the ID of the originating network that the local office allows to connect, ranging from 0 to 9 and A to E with a maximum length of six characters. The parameter is used when the local office is an end office. It must authenticate the pre-selected call initiated by the ISUP incoming trunk, that is, the local office should authenticate the originating network ID in the IAM sent by the peer office. It is one of the important parameters for the interconnection between two offices. It must be consistent at the two offices.

7.4.7 Adding PCM Port (Optional)

Related Commands

Command Function

ADD PCMPORT To add a PCM port

RMV PCMPORT To remove a PCM port




Command Function

MOD PCMPORT To modify a PCM port

LST PCMPORT To list PCM ports


For ISUP/TUP circuits: By default, the PCM type is E1, and the PCM codec mode is A law when you run ADD N7TKC to add a No. 7 trunk circuit. For networking in countries such as the USA and Japan, the PCM type is T1, and the PCM codec mode is μ law generally. In this case, you must run ADD PCMPORT to add a PCM port.

For PRA circuits: By default, one PRA signaling link can control only one Pulse Code Modulation (PCM) system. Correspondingly, you can add up to 32 PRA trunk circuits by using ADD PRATKC. When the PRA link resources are not enough, you must run ADD PCMPORT to add PCM ports if one PRA link is required to control multiple PCM systems (up to four E1s).


It defines the module number of the FCCU processing the trunk calls. This parameter must be defined by ADD BRD before being used here.


Port number

It defines the logical number in the FCCU for timeslot 0 of the PCM port. It must be a multiple of 32.

One PRA link can control up to four PCM ports. Therefore, you must pay attention to this limitation when running the command.

Device type

It defines the device type of the PCM port. It can be PRA, ISUP or TUP.

PRA link number

It defines the PRA link bearing the call signaling at the PCM port. It is valid only when Device type is PRA. This parameter must be defined by ADD PRALNK before being used here.

PCM port interface identification

It is one of the parameters used for the SoftX3000 to interwork with the PRA device. It defines the interface identification of the PCM port to be added. It is valid only when Device type is PRA. This parameter at the SoftX3000 side must be consistent with that at the PRA device side. Or else, the interconnection may fail.

PCM type

It defines the physical interface of the trunk circuit, E1 or T1. The default value is E1.



PCM companding law

It defines the voice codec mode supported by the PCM port, that is, whether A law or μ law is used in the PCM compression algorithm.

7.5 Configuring R2 Trunk Data 7.5.1 Overview

Configuration Relation The R2 trunk data defines the R2 trunk related information at the SoftX3000 side, such as:

Charging Call barring Interconnection

To configure the R2 trunk data, ensure that the following data is configured:

Equipment data Local office data Charging data MGW data Signaling data Routing data


During the configuration, the R2 trunk data will reference certain parameters defined in the following data:

Local office data Charging data MGW data Routing data

The network management data will reference the network management source code defined in the R2 trunk data. Table 7-19 shows the details.

Table 7-19 Parameter referencing relation between the R2 trunk data and other


Parameter Defined in Parameter Referenced in

Call source code Local office data Network management source code









Charging data - -

Equipment ID of the TMG

MGW data - -




Call barring group number (optional)


Preparations Before configuring the R2 trunk data, prepare as specified in Table 7-20.

Table 7-20 Preparations for configuring the R2 trunk data

SN Item Remark

1 Group direction of R2 trunk group, including outgoing trunk, incoming trunk or bi-directional trunk

It is one of the interconnection parameters between the SoftX3000 and PBX devices.

2 Cooperation of caller number The R2 signaling is transmitted with low efficiency. Therefore, you must consider the requirements of connection speed, charging, and caller number display for the transmission of caller numbers when you are interconnecting the SoftX3000 to PBX devices.

3 Numbering range of R2 trunk circuits

These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA, and R2 trunk circuits. The corresponding physical numbers at the TMG are specified in the start circuit termination identifier parameter.

4 Termination ID of circuit number It is one of the interconnection parameters between the SoftX3000 and TMG.

Configuration Steps Table 7-21 lists the general steps for configuring the R2 trunk data.



Table 7-21 Steps for configuring the R2 trunk data


1 Add R2 incoming caller category conversion. (Optional) ADD CATICVT

2 Add R2 outgoing caller category conversion. (Optional) ADD CATOCVT

3 Add a R2 trunk group. ADD N1TG

4 Add a R2 trunk circuit. ADD N1TKC

5 Add CAS signaling configuration. ADD CASCFG

6 Add a R2 trunk group caller number segment. (Optional) ADD TKDNSEG

Parameter Referencing Relation Figure 7-8 shows the referencing relation between the key parameters used when the R2 trunk data is configured.




Figure 7-8 Parameter referencing relation of the R2 trunk data

Incoming convert index

ADD CATICVT

Standard caller calling category

Inner caller calling category

Outgoing convert index

ADD CATOCVT

Standard caller calling category

Inner caller calling category

Trunk group number

ADD N1TG

Equipment ID

Group direction

ADD N1TKC

Trunk group number


Incoming trunk group number

ADD N1TDM

Outgoing trunk group number

Tandem mode

Incoming cat convert index

Outgoing cat convert index

FCCU module number



7.5.2 Adding R2 Incoming Caller Category Conversion (Optional)

Related Commands

Command Function

ADD CATICVT To add R2 incoming caller category conversion

RMV CATICVT To remove R2 incoming caller category conversion

MOD CATICVT To modify R2 incoming caller category conversion

LST CATICVT To list R2 incoming caller category conversion


Different countries or regions may define different quantity and code of caller categories. To enable the SoftX3000 adaptive to the R2 signaling in different countries and regions, Huawei provides a separate R2 signaling adaptation script. The script contains the definition data about caller category conversion on R2 trunk group during equipment commissioning.

Parameter Description Incoming conversion index

It defines a caller category conversion index of incoming trunk. The index is unique inside the SoftX3000. The value range is from 0 to 7.

Several incoming trunk caller category transform records can be configured for one incoming conversion index. When you add incoming trunk caller category transform data, one incoming conversion index can be used in several ADD CATICVT commands.

Standard caller category

It defines the code of the caller category that is sent by the peer office to the SoftX3000 through the incoming R2 trunk. This code must be consistent with that of the peer office. The value range is from1 to 15.

Internal caller category

It defines the caller category code that is defined inside the SoftX3000 and corresponds to the standard caller category of the incoming R2 trunk. The value range is from 0 to 254.

For the conversion relation between the internal caller category and the standard caller category, see the R2 signaling adaptation script provided by Huawei.




7.5.3 Adding R2 Outgoing Caller Category Conversion (Optional)

Related Commands

Command Function

ADD CATOCVT To add R2 outgoing caller category conversion

RMV CATOCVT To remove R2 outgoing caller category conversion

MOD CATOCVT To modify R2 outgoing caller category conversion

LST CATOCVT To list R2 outgoing caller category conversion


Different countries or regions may define different quantity and code of caller categories. To enable the SoftX3000 adaptive to the R2 signaling in different countries and regions, Huawei provides a separate R2 signaling adaptation script. The script contains the definition data about caller category conversion on R2 trunk group during system commissioning.

Parameter Description Outgoing conversion index

It defines a caller category conversion index of outgoing trunk. The index is unique inside the SoftX3000. The value range is from 0 to 7.

Several outgoing trunk caller category transform records can be configured for one outgoing conversion index. When you add outgoing trunk caller category transform data, one outgoing conversion index can be used in several ADD CATOCVT commands.

Internal caller category

It defines the caller category code that is defined inside the SoftX3000 and corresponds to the standard caller category of the outgoing R2 trunk. The value range is from 0 to 254.

For the conversion relation between the internal caller category and the standard caller category, see the R2 signaling adaptation script provided by Huawei.

Standard caller category

It defines the code of the caller category that is sent by the SoftX3000 to the peer office through the outgoing R2 trunk. This code must be consistent with that of the peer office. The value range is from 1 to 15.



7.5.4 Adding CAS Signaling Configuration

Related Commands

Command Function

ADD CASCFG To add CAS signaling configuration

RMV CASCFG To remove CAS signaling configuration

MOD CASCFG To modify CAS signaling configuration

LST CASCFG To list CAS signaling configuration

Notes of Configuration Different countries or regions may have defined the specifications of CAS different from the standard ones in ITU-T. Before configuring R2 trunk data, run ADD CASCFG to add CAS signaling configuration for the SoftX3000, with the following purpose:

To adapt to the CAS specifications of the countries or regions To ensure the normal interoperation of inter-office signaling

Parameter Description CAS signaling name

It identifies a CAS signaling uniquely in the SoftX3000. It is a character string with a maximum length of 16 characters.

Signaling type

It defines the specification to which the CAS signaling conforms, such as:

R2 signaling R1 signaling No. 5 signaling China No. 1 signaling Russia CAS signaling

You must select the correct signaling type. Or else, the inter-office signaling cooperation is abnormal. Table 7-22 lists certain common channel associated signaling types.




Table 7-22 Certain common channel associated signaling types

Name Component Description

R2 signaling Inter-office line signaling

Inter-office register signaling

It is a channel-associated signaling system. It adopts the multi-frequency mutual control mode.

Line signaling is transmitted in multiframes to indicate the connection states.

Register signaling controls the automatic connection of circuits.

China No.1 signaling

Digital line signaling Multi-frequency mutual-control register signaling

It is a sub-set of R2 signaling only used in domestic networks in China.

Line signaling adopts the mode of transfer segment by segment.

Register signaling adopts multi-frequency coding mode of selecting 2 from 6, and forward signaling includes forward group I and forward group II, and backward signaling includes backward group A and backward group B.

No.5 signaling

Double-frequency line signaling

Multi-frequency pulse register signaling

It is a sub-set of R2 signaling only used in international network.

Line signaling adopts the mode of transfer segment by segment. Except for forward transfer signaling, the other signaling types are mutual-controlled.

Register signaling adopts multi-frequency coding mode of selecting 2 from 6, and there is only forward signal.

All register signaling types start with KP signal and end with ST signal.

In China No.1 signaling,

Forward group I is connection signaling and forward group II is caller category signaling. Backward group A is the acknowledgment and control signaling of forward group I.

Backward group B is the called subscriber state signaling. Forward group I and backward group A are mutually controlled. Forward group II and backward group B are mutually controlled.

Line signal

It defines the type of the line signal.

Register signal

It defines the type of the register signal.

Line signal conversion index



It defines the conversion operation that must be performed when the local office converts the line signal (the local office receives incoming line signal). It is reserved at present.

Line command conversion index

It defines the conversion operation that must be performed when the local office converts the line signal (the local office sends outgoing line signal). It is reserved at present.

RSD signal conversion index

It defines the conversion operation that must be performed when the local office converts the RSD signal (the local office receives incoming line signal). It is reserved at present.

RSD command conversion index

It defines the conversion operation that must be performed when the local office converts the RSD signal (the local office sends outgoing line signal). It is reserved at present.

Circuit type

It defines the type of the circuit that bears the CAS signaling.

PTS mode

It defines the use mode of pulse signal.

Send FAS

It defines whether the SoftX3000 sends the FAS signal. The default value is No.

Send EOS

It defines whether the SoftX3000 sends the EOS signal. The default value is No.

Send RLG

It defines whether the SoftX3000 sends the RLG signal. The default value is No.

Send MCT

It defines whether the SoftX3000 sends the MCT signal. The default value is No.

Send congestion

It defines whether the SoftX3000 sends the congestion signal. The default value is No.

7.5.5 Adding R2 Trunk Group

Related Commands

Command Function

ADD N1TG To add a R2 trunk group

RMV TG To remove a R2 trunk group

MOD N1TG To modify a R2 trunk group

LST TG To list R2 trunk groups




Notes of Configuration Before adding an R2 trunk group, run the commands to obtain the following parameters defined by the system:

Parameter Command





LST CLRDSN







Equipment ID

It defines the equipment ID of the TMG (such as the TMG8010 or UMG8900) providing R2 trunk circuits. This parameter must be defined by ADD MGW before being used here.

Group direction

It defines the call connection direction of the R2 trunk group. The default option is bi-directional trunk. The parameter options are described as follows:




Sub-route number



It defines the subroute to which the trunk group belongs. This parameter is defined by ADD SRT before being used here.

CAS signal name

It defines which type of CAS signal the trunk group uses. The parameter must be defined by ADD CASCFG before being used here.

Trunk group name


Call source code



It defines the trunk circuit selection policy of the trunk group. The default mode is Cyclic. The meanings of the options are

Minimum The system always selects a trunk circuit from the minimum number. The preferential selection of the trunk circuits can be realized through this mode.

Maximum The system always selects a trunk circuit from the maximum number. The preferential selection of the trunk circuits can be realized through this mode.

Recycle The system selects a circuit from the next one to the last selected circuit number each time. If the last selected number is the maximum one, the next one is the minimum number.



User side allocation The system selects a circuit according to the instruction from the user side.

Reserved circuit

It defines the number of circuits in a trunk group reserved for subscribers or calls with higher priority. It can only be set with MOD N1TG. When the number of idle circuits in the trunk group is equal to or less than the number defined here, the system allocates trunks only for the new calls originated by the subscribers with higher priority or the calls with priority (defined in SET PFXPRI). Its value range is from 0 to 1023. The default value is 0, indicating no reserved circuits.


It identifies whether the R2 trunk is carried over the satellite circuits. Set it based on the actual conditions. Generally, it is set to NO.

EC attribute

If you set it to Yes, the echo cancellation attributes are displayed.




Time attribute

If you set it to Yes, the time attributes are displayed.

Enhanced attribute


EC support

It defines whether the local office starts the echo suppress function to the incoming trunk group circuits or the outgoing trunk group circuits. By default, the system does not start the echo suppress function. The setting of this parameter must be consistent with that of the peer office. In other words, to successfully complete call connection through the R2 trunk, both exchanges must provide the echo suppress function. This premise must be satisfied first. Or else, the connection may fail. The parameter options are described as follows:

No EC support It indicates the system does not start the echo suppress function to the R2 trunk circuits.

EC support for outgoing call It indicates the system starts the echo suppress function only for the outgoing R2 trunk circuits. In this case, the corresponding incoming trunk circuits of the peer office must support the echo suppress function.

EC support for incoming call It indicates the system starts the echo suppress function only for the incoming R2 trunk circuits. In this case, the corresponding outgoing trunk circuits of the peer office must support the echo suppress function.

Bi-directional EC support It indicates the system starts the echo suppress function for outgoing and incoming R2 trunk circuits. In this case, the corresponding incoming and outgoing trunk circuits of the peer office must support the echo suppress function.

When the R2 trunk is carried over the satellite circuits, this parameter is set to bi-directional echo suppress.

Call-in authority




Call-out authority


Intra-office



Local Local toll National toll International toll Intra-office national toll (in multi-zone-code application) Intra-office international toll (in multi-country-code application) Intra-office local toll


DOD2

It is valid for outgoing trunks to control whether the local callers can hear the secondary dial tone sent by the peer office after seizing the outgoing trunk. For the AT0 outgoing trunk group, you can set this parameter to YES. In other cases, set this parameter to NO.

Send initial tone

It is valid only for incoming trunks and only when the register signaling adopts MFP, Pulse, and DTMF. It controls the local office to send the initial signal tone to the peer office during the transition. This feature is used for the transit office with R2 trunks. The connection speed of R2 trunks is slow. Therefore, the caller listens to nothing for a long time before connected to the callee, which seriously affects the quality of service. If the transit office enables the initial tone function, it sends the specified signal tone, such as music, to the caller in the connection process after the call gets to the transit office. After successful connection, the destination office plays ring-back tone to the caller. This satisfies subscribers in a greater degree.

Initial tone type

It defines the type of the initial tone. It is valid only when Send initial tone is set to YES.


It controls the local office to send exceptional tone to the peer office through a B7 signal when the call through the incoming trunk fails. It is valid only for incoming trunks.

If this parameter is set to NO, the local office sends a B3 signal to the peer office after the call fails. In this case, the call is released and the peer office sends the busy tone to the caller.

If the parameter is set to YES, the local office sends a B7 signal to the peer office when the call fails. In this case, the call is held temporarily and the local office sends the exceptional tone to the caller through the incoming trunk. If the caller hangs up or the timer times out, the call is released.

Exceptional tone type

It defines the type of the exceptional tone. It is valid only when Send exceptional tone is set to YES.


It is one of the charging attributes of the trunk group. Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of incoming trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being referenced here.






It is one of the charging attributes of the trunk group. Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of outgoing trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being referenced here.


Use opposite pulse

It is used for the inter-office trunk cooperation in the immediate charging. When it is set to YES, its meanings for outgoing trunk and incoming trunk are different.

Outgoing trunk When there is an outgoing call from the trunk group, the local office must receive the charging pulse sent back from the peer office, and the peer office must cooperate to send the charging pulse to the local office.

Incoming trunk When there is an incoming call to the trunk group, the local office must send charging pulse to the peer office, and the peer office must cooperate to receive the charging pulse sent from the local office.

CAMA

It is valid only for incoming trunks. It sets whether the local office performs the centralized charging on the incoming trunks. If it is set to YES, the local office performs the centralized charging on the incoming trunks. In this case, when the peer office originates a call through an incoming trunk and the call signaling does not carry the caller number, the local office requests the caller number through signaling.


It is valid only for incoming trunks. When the Whether request caller number parameter is set to YES, this parameter defines whether the local office can request the caller number from the peer office if the incoming call signaling through the trunk contains no caller number. The default option is YES, indicating that the local office can request the caller number on initiative. If this feature affects call completion rate or connection time, you can set it to NO.

Connect without or with invalid caller number

It is valid only for incoming trunks. If the incoming call signaling through the trunk does not carry a caller number or the carried caller number is invalid, this parameter indicates the local office whether to connect the call, that is, whether the call is not rejected. By default, it is set to YES.

Minimum caller number length

It is valid only for incoming trunks. When the Whether request caller number parameter is set to YES, it defines the minimum number length of the caller number if the incoming call signaling through the trunk carries the caller number. If the actual length of the caller number is less than the defined minimum number length, the local office does not connect the call, that is, the local office rejects the call. By default, the minimum number length of the caller number is seven digits.







If the peer office sends the calling number in the incoming call signaling, the local office uses the calling number and this parameter is invalid.


It is valid only for incoming trunks. If Caller number provision mode of the trunk group is Default number and no caller number is contained in the call signaling message sent by the peer office when it originates a call through the incoming trunk, the local office uses the default caller number.



If the value is not specified or specified with 65535, it indicates that the call barring function is not enabled.

If the black/white list barring is used, the three preset call barring groups can be referenced directly, that is black list 60001, white list 60002, and ordinary call barring group 65534.


During the number analysis process of inter-group call barring authentication, the SoftX3000 authenticates twice the caller, called prefix, and the callee. The inter-group call barring authentication procedure is as follows:



Signaling link number

It is reserved.

Upper seizure threshold

It defines the maximum occupancy time length of the trunk circuit. If the time that the trunk circuit is occupied exceeds the threshold, the system checks the circuit status and generates alarm. Its value range is from 0 to 65535, in unit of second. The value 0 or 65535 indicates that the threshold is invalid.

Lower seizure threshold




It defines the minimum occupancy time length of the trunk circuit. If the time that the trunk circuit is occupied is lower than the threshold, the system counts once. If the number of times is larger than the value presented by the lower 8 bits in TUP operation reserve parameter 1, the system generates alarm. Its value range is from 0 to 65535, in unit of second. The value 0 or 65535 indicates that the threshold is invalid.

Request caller number

If the incoming call signaling through the trunk does not contain caller number, it defines whether the local office requests caller number from the peer office on initiative. It is valid only for incoming trunks. The default option is NO, indicating that the local office does not request caller number on initiative.

Request caller number position

It is valid only for incoming trunks. When the Whether request caller number parameter is set to YES, it defines the digit from which the peer office sends the caller number as requested by the local office.

ANI request count

It is valid only for incoming trunks and applicable only to the R1.5 signaling. When the local office fails to request the caller number from the peer office, it defines the maximum number of request attempts. By default, it is 3 times.

Request caller category

If the incoming call signaling through the trunk does not contain the call category, it defines whether the local office requests the call category from the peer office on initiative. It is valid only for incoming trunks. The default option is NO, indicating that the local office does not request the call category on initiative.

Request caller category position

It is valid only for incoming trunks. When the Request call category parameter is set to YES, it defines the digit from which the peer office sends the call category as requested by the local office.

Receive caller number

It is valid only for incoming trunks. It specifies whether the local office continues to receive the caller number sent by the peer office after the local office has received the call category. The default option is YES, indicating that the local office continues to receive the caller number from the peer office. If this parameter is set to NO, the local office receives only the call category from the peer office. The local office does not receive the caller number.

The setting of this parameter must be consistent at both offices. If the peer office is defined not to send the caller number but the local office defined to receive the caller number, the local office considers the caller number sent by the peer office as the called number.

Send caller number

It is valid only for outgoing trunks. It specifies whether the local office continues to send the caller number to the peer office after the local office has sent the call category to the terminating office. The default option is YES, indicating that the local office continues to send the caller number to the peer office. If this parameter is set to NO, the local office sends only the call category to the peer office. The local office does not send the caller number.

The setting of this parameter must be consistent at both offices. If the local office is defined not to send the caller number but the peer office defined to receive the caller number, the peer office considers the caller number sent by the local office as the called number.



Send caller category

It is valid only for outgoing trunks. It specifies whether the local office sends the call category to the peer office. The default option is NO, indicating that the local office does not send the call category to the peer office.

The setting of this parameter must be consistent at both offices. If the local office is defined not to send the call category, the local office cannot respond correctly when the peer office requests the call category from the local office.

Request HES

It is valid only for incoming trunks. If the incoming call signaling through the trunk does not contain the echo suppress signal, this parameter defines whether the local office requests the echo suppress signal from the peer office on initiative. The default option is NO, indicating that the local office does not request the echo suppress signal from the peer office on initiative. If this parameter is set to YES, the Echo suppress parameter in this command must be set correctly.

Request circuit type

It is valid only for incoming trunks. If the incoming call signaling through the trunk does not contain the circuit type signal, this parameter defines whether the local office requests the circuit type signal from the peer office on initiative. The default option is NO, indicating that the local office does not request the circuit type signal from the peer office on initiative.

Waiting seizure ACK time

It is valid only for outgoing trunks. After the local office seizes a trunk circuit and sends the seizure signal (line signaling) to the peer office, it defines the maximum time for waiting for the seizure acknowledgement that is returned by the peer office. The value range is from 0 to 5, and the unit is second. The default value is 3.

For the line signaling mode requiring the seizure acknowledgement signal, if the local office does not receive a seizure acknowledgement signal from the peer office after the expiration, the call fails.

For the line signaling mode not requiring the seizure acknowledgement signal, if the local office does not receive a seizure acknowledgement signal from the peer office after the expiration, the local office auto enters the seizure acknowledged state.

Number interval duration

It defines the inter-digit time interval when an incoming R2 trunk sends a number to an outgoing R2 trunk. The value range is from 0 to 60, and the unit is second. The default value is 50.

Waiting caller category time

It is valid only for incoming trunks. After the local office sends an A5 signal to the peer office, it defines the maximum time for waiting for the call category signal that is returned by the peer office. The value range is from 0 to 60, and the unit is second. The default value is 50.

Waiting callee state time

It is valid only for outgoing trunks. After the local office sends all signals to the peer office, it defines the maximum time for waiting for the callee state signal that is returned by the peer office. The value range is from 0 to 60, and the unit is second. The default value is 10.

Ringing duration




It is valid only for incoming trunks. When an originating subscriber calls a local office subscriber through an incoming trunk, the local office simultaneously sends the ringing tone to the callee and the ringback tone to the originating office if the callee is idle. It defines the maximum time the local office monitors the ringing at the callee. The value range is from 0 to 65535, and the unit is second. The default value is 240.

Listening to ringback tone time

It is valid only for outgoing trunks. It defines the maximum duration during which a local caller (or an incoming trunk) can hear the ringback tone. The value range is from 0 to 65535, and the unit is second. The default value is 240.

The time when the local caller enters the state of hearing the ringback tone is not the time when the terminating office starts sending the ringback tone to the local office, but the time after one timer duration when all digits of the called number are sent. The timer duration is defined in the parameter Listening to ringback tone delay in this command.

Number send delay

It is valid only for outgoing trunks. It specifies the duration between the time when the local office receives the outgoing trunk circuit seizure acknowledgement message returned by the peer office and the time when the local office sends the first digit. The value range is from 0 to 10, and the unit is second. The default value is 1.

If the time when the local office starts to seize the outgoing trunk circuit is counted, the delay for the local office to send the first digit to the peer office is "Waiting seizure ACK time" + "Number send delay".

Listening to ringback tone delay

It is valid only for outgoing trunks. When the register signaling through the outgoing trunk adopts the non MFC mode, it defines the delay the ringback tone is auto played to the local office subscriber (or the incoming trunk) if the length of the called number sent from the local office to the terminating office is less than the minimum number length defined at the terminating office. The value range is from 0 to 30, and the unit is second. The default value is 5.

If the register signaling through the outgoing trunk adopts the MFC mode, this parameter is invalid. Whether to play the ringback tone to the caller depends on the register signal or the line signal that is sent by the terminating office.

Automatic answer time

It is valid only for outgoing trunks. After the ringback tone is played to the local subscriber (through the incoming trunk), it defines the monitoring duration after the local subscriber auto enters the conversation state (suppose the callee has picked up the phone). The value range is from 0 to 30, and the unit is second. The default value is 6.

Ringback tone send delay

It is valid only for incoming trunks. It specifies the time gap between the sending of the KB signal from the local office to the originating office and the sending of the ringback tone. The value range is from 0 to 5, and the unit is second. The default value is 0.

Priority

It defines the routing priority for the R2 trunk group. A trunk group with currently the highest priority is selected first. A trunk group will be selected to convey traffic only after there are absolutely no available trunk circuits with a higher priority. The greater the value is, the lower the priority is. The value 0 indicates the highest priority.



Availability

It is valid only when the trunk group selection mode of a subroute is set to Cyclic. It defines the times that a trunk group can be selected in the corresponding subroute. Its value range is from 0 to 255. By default, it is set to 255, indicating invalid.

In a subroute, every time the system selects the trunk group, the available times of the trunk group is decreased by 1. When the available times become 0, the system cannot select the trunk group. If the available times of all trunk groups in the corresponding subroute become 0, those times are assigned with new values. This parameter is designed to distribute the traffic over all trunk groups of the subroute according to the expected principle, that is, the carrier can use this parameter to control the selected ratio of each trunk group of a subroute.


It sets whether R2 trunks support certain special services or applications. There are 16 options for this parameter. Currently, only seven options are used, and the others are reserved. The meanings of the options are as follows:

Wide area network Centrex service It is used with bit 4 of the parameter "ISUP operation reserved parameter 9 (P26)". If you select this option and bit 4 of the "ISUP operation reserved parameter 9" is 0, the local office sends a short number to the peer office in the WAN Centrex service.

Set caller type as operator It is available only for incoming trunks. If you select this option, the local office sets the caller category to Operator forcedly no matter whether the peer office sends the caller category through the incoming trunk and no matter what the value of the caller category is.

Trunk send ringback tone It is valid only for incoming trunks. If you select this option, when a call originated by the peer office to the local office through the incoming trunk is connected successfully, the local office sends the ringback tone to the peer office no matter whether the local office is the terminating office or not. This feature is applicable to Hong Kong.

Trunk is Brunei It is valid only for incoming trunks. When the peer office calls a subscriber of the local office through an incoming trunk, and if the subscriber line is faulty or the subscriber number is inexistent, the local office returns an R2 signaling message indicating subscriber line fault or number inexistence to the peer office if you do not select this option. If you select this option, the local office returns an R2 signaling message indicating congestion to the peer office. When the SoftX3000 is used in Brunei, you can determine whether to select.

No answer if free It is available only for incoming trunks. If you select this option, the local office returns to the originating office the response signal with a delay of two seconds when the local callees are idle. If you do not select this option, the local office returns the response signal to the originating office at once.

A6 signaling special release It is available only for outgoing trunks. If you select this option, after the local office originates a call, the local office can display its outgoing trunk circuits as idle without receiving the backward release monitor signal from the terminating office when the caller or callee hangs up. If you do not select this option, the local office can display its outgoing trunk circuits as idle only after receiving the backward release monitor signal from the terminating office.

Trunk group caller number segment




It indicates whether the SoftX3000 judges the validity of the caller number sent by the peer office through the incoming trunk. It verifies whether the caller number sent by the peer office is in the number segment defined by ADD TKDNSEG. If the number is in the number segment defined by ADD TKDNSEG, the caller number is valid. Or else, it is invalid. The parameter is valid only for incoming trunks. When you select this option, the local office judges the validity of the caller number sent by the peer office. If the caller number is valid, the local office uses the original caller number in charging, and displays it on the callee's telephone. If the caller number is invalid, the local office uses the default caller number of the trunk group in charging, and displays it on the callee's telephone. When you leave the option unselected, the local office does not judge the validity of the caller number sent by the peer office. In this case, the caller number sent by the peer office is always charged and displayed on the phone set of the callee.

Send calling party number but presentation restricted

It is valid only for incoming R2 calls routed out through the ISUP trunks. If it is selected, the calling number PI of an outgoing ISUP call cannot be displayed. If it is unselected, the calling number PI of an outgoing ISUP call can be displayed.

Send A9 signal

It is valid only for incoming trunks. It defines whether the local office sends A9 signal to the originating office. A9 signal is the reserved signal in the standard R2 signaling. The SoftX3000 defines it as follows: In the auto toll telephone network, A9 signal is used to restrict the toll calls of common subscribers. This is to ensure the calling priority of the subscribers with higher authority and the toll operators.

This parameter is applicable only to the channel associated signaling TB85_No1 or TB93_No1 in the China railway dedicated network.

International call

It is valid only for outgoing trunks. It defines whether the outgoing trunk transits international calls. The default option is NO.

If this parameter is set to YES, the outgoing trunk transits international calls. In this case, when the terminating office sends an A5 signal to the local office to request the call category, the local office returns the group II signaling, the signal of which ranges from 7 to 11.

If this parameter is set to NO, the outgoing trunk transits national calls. In this case, when the terminating office sends an A5 signal to the local office to request the call category, the local office returns the group II signaling, the signal of which ranges from 1 to 6.

Number incomplete

When the local office connects the R2 incoming trunk with the ISUP outgoing trunk, it defines whether the SoftX3000 sets the bit "caller number incomplete indicator" in the message sent by the R2 incoming trunk to the call processing software to 1. The value 1 indicates that the caller number is incomplete. It is available only for incoming trunks.

Name valid

It is valid only for incoming trunks. It defines whether the parameter Trunk group name in the message sent by the R2 incoming trunk to the call processing software is valid. The parameter Trunk group name is the one defined in this command and it is equivalent to caller name.

Operator call barring



It is valid only for outgoing trunks. It specifies whether the subscriber whose call category is operator has the permission to seize the outgoing trunk. The default option is NO, indicating that the operator can seize the outgoing trunk.

First backward code

It is valid only for incoming trunks and is applicable only to the R1.5 signaling. When the register signaling adopts the MFS mode, it defines the first backward signal returned by the local office. It may be B1, B2, or B3. The default option is B2. To receive all of the called number, set this parameter to B1 or B2. To receive part of the called number, set this parameter to B2.

Reset flag

It is valid only for incoming trunks and is applicable only to the R1.5 signaling. When the originating office calls a local office subscriber through the incoming trunk, it defines whether the local office sends the ringing tone to the local office subscriber as requested by the originating office. The default option is YES. If the incoming trunk connects only toll calls, set this parameter and the receive ringing signal parameter to YES. In other cases, set this parameter to NO.

Send ringing signal

It is valid only for outgoing trunks and is applicable only to the R1.5 signaling. When the local office calls a terminating office subscriber through the outgoing trunk, this parameter controls whether the local office sends the ringing signal to the terminating office as requested by the local office. The default option is NO. If the outgoing trunk connects only outgoing toll calls, this parameter is set to YES. In other cases, this parameter is set to NO.

Receive ringing signal

It is valid only for incoming trunks and applicable only to the R1.5 signaling. When the originating office calls a local office subscriber through the incoming trunk, it defines whether the local office receives the ringing signal from the originating office. The default option is NO. If the incoming trunk connects only incoming toll calls, this parameter is set to YES, and the reset flag parameter must be set to YES. In other cases, this parameter is set to NO.

Response to B6

It is valid only for outgoing trunks and is applicable only to the R1.5 signaling. When the register signaling adopts the MFS mode and the local office receives the B6 signal from the terminating office, it defines the operations for the local office to perform.

Reattempt: re-attempt to connect the call Resend: re-send the called number Disconnect: disconnect the call (In other words, the call fails.)

Trunk name

It identifies a trunk with a string of characters.

Block the blocker

It is valid only for outgoing trunks. It defines whether an R2 trunk group supports the block the blocker service. That is, when a call originated by the local office seizes the R2 outgoing trunk, the system rejects the call if it judges that there is no caller number in the call. This feature is applicable only to Hong Kong. By default, it is set to FALSE.




EC signaling flag

It defines whether the local office starts the echo suppress function based on the echo suppress signal sent by the originating office or the echo suppress data configured at the local office. The default option is YES.

EC use mode

It defines the mode in which the local office starts the echo suppress function to the R2 trunk circuits. The default option is No internal EC support. The setting of this parameter must be consistent with that of the peer office. In other words, to successfully complete call connection through R2 trunk, both exchanges must provide the echo suppress function. This premise must be satisfied first. Otherwise, the connection may fail. The parameter options are described as follows:

No internal EC support It indicates the system does not start the echo suppress function to the R2 trunk circuits.

EC support for outgoing call It indicates the system starts the echo suppress function only to the outgoing R2 trunk circuits. In this case, the corresponding incoming trunk circuits of the peer office must support the echo suppress function.

EC support for incoming call It indicates the system starts the echo suppress function only to the incoming R2 trunk circuits. In this case, the corresponding outgoing trunk circuits of the peer office must support the echo suppress function.

Bi-directional EC support It indicates the system starts the echo suppress function to outgoing and incoming R2 trunk circuits. In this case, the corresponding incoming and outgoing trunk circuits of the peer office must support the echo suppress function.

External EC support Use an external echo suppress device that is interconnected between the exchange and the transmission device.

When the R2 trunk is carried over the satellite circuits, this parameter is set to bi-directional echo suppress.

Forward office EC

It is valid only for incoming trunks. It specifies the mode in which the originating office starts the echo suppress function to the R2 trunk circuits. The default option is unknown.

For the meanings of the parameter options, see Using EC mode.

Backward office EC

It is valid only for outgoing trunks. It specifies the mode in which the terminating office starts the echo suppress function to the R2 trunk circuits. The default option is Unknown.

For the meanings of the parameter options, see Using EC mode.

Connect without EC

The local office has started the echo suppress function to the R2 trunk circuits. When the related echo suppress device becomes faulty during the call, it defines whether the local office continues the call. The default option is YES.

EC index



It defines the EC data to be used in this command. This parameter must be defined by ADD ECPARA before being used here.

Default connect

If querying caller number discrimination group failed (that is, the queried record is not found), it sets whether to connect the call. The default option is TRUE, indicating that the call is connected.

Whether request caller number for CCB

If the incoming call signaling through the trunk does not contain caller number, it defines whether the local office requests caller number from the peer office on initiative. It is available only for incoming trunks. The default option is FALSE, indicating that the local office does not request caller number on initiative.

Send MPM message

It is valid only for incoming trunks, and is used for inter-office trunk cooperation during the immediate charging process. The default option is YES, indicating that the local office sends charging pulse to the peer office through signaling, and the peer office cooperates to receive the charging pulse sent from the local office through signaling.

Waiting PTS time

It is reserved.

Codec prefer

It defines the codec mode used by the RTP audio media streams of the TMG in the trunk group direction. Set this parameter by the following principles:

The codec prefer defined here must be defined in codec list in ADD MGW. Otherwise, it is invalid.


You can specify a specific codec mode. Codec prefer is the first mode in the codec list that is supported by the MGWs of the caller and the callee. If the codec list contains the codec prefer of the caller, callee, incoming trunk group, and outgoing trunk group at the same time, the SoftX3000, according to the principle of "caller and subscriber prior to callee and trunk", queues a codec mode in the first position of the list during call connection. For example, − In an intra-office call, if the codec prefer of the caller is different from that of the callee,




− In an incoming trunk terminated call, if the codec prefer of the local incoming trunk group is different from that of the local callee, the codec prefer of the local callee is valid.

Incoming caller category conversion index




It defines the caller category conversion index to be used by the incoming R2 trunk group. This parameter must be defined by ADD CATICVT before being used here.

Outgoing caller category conversion index

It defines the caller category conversion index to be used by the outgoing R2 trunk group. This parameter must be defined by ADD CATOCVT before being used here.


It defines whether to overlap send called number. By default, it is set to YES.

Enhanced voice attribute





It defines the maximum number of simultaneous calls through the trunk group. Its range is from 0 to 65535. If you set it to 65535, there is no limit for the number of simultaneous calls.



It defines the maximum number of simultaneous incoming calls through the trunk group. Its range is from 0 to 65535. If you set it to 65535, there is no limit for the number of simultaneous incoming calls.



It defines the maximum number of simultaneous outgoing calls through the trunk group. Its range is from 0 to 65535. If you set it to 65535, there is no limit for the number of simultaneous outgoing calls.


When Maximum Simultaneous Call, Maximum Simultaneous Incoming Call, and Maximum Simultaneous Outgoing Call are all set at the same time,






7.5.6 Adding R2 Trunk Circuit

Related Commands

Command Function

ADD N1TKC To add a R2 trunk circuit

RMV TKC To remove a R2 trunk circuit

MOD N1TKC To modify a R2 trunk circuit

LST TKC To list R2 trunk circuits


It defines the module number of the FCCU processing the R2 trunk calls. This parameter must be defined by ADD BRD before being used here.


Trunk group number

It defines the R2 trunk group to which the R2 trunk circuits to be added belongs. This parameter must be defined by ADD N1TG before being used here.


They specify the E1 numbering range of the R2 trunk circuits in the SoftX3000. The value ranges from 0 to 6399. Set this parameter by the following principles:

These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA, R2, and V5 E1 trunk circuits in an FCCU module. The corresponding physical numbers at the TMG are specified in the Start circuit termination ID parameter in this command.

Up to 320 trunk circuits can be added in one execution of this command. If you want to add more than 320 trunk circuits, run the command again.

The absolute value of the difference between the start circuit number and the start circuit termination ID (a decimal value after converted from a binary value) must be a multiple of 32, such as 0, 32, 64, and 96.

Circuit state

It defines the initial state of the trunk circuits. The meanings of the parameter options are as follows:

Unavailable The trunk circuits specified in this command are not used. In this case, the state of the trunk circuits is displayed as uninstalled.

Available The trunk circuits specified in this command are used as the inter-office trunk to interconnect the exchange devices like PBX.




Resource The trunk circuits specified in this command are used as the ordinary E1 circuits to interconnect the voice card of the voice mailing system.

Usually, this parameter is set to the default value, available.

Fill the engineer number

It defines whether to number, at the local office, the R2 trunk circuits to be added here. This number is used for maintaining the R2 trunk circuits conveniently, such as blocking, unblocking, and resetting R2 trunk circuits. This is not an interconnection parameter between the exchanges. If this parameter is set to YES, the circuits in the same R2 trunk group must be numbered with different engineering numbers.

Start engineer number

It is valid only when Fill the engineer number is set to YES. It defines the start number for the batch of the trunk circuits in the resident R2 trunk group.


It defines the identifier of the start circuit timeslot of a specified batch of trunk circuits in the resident trunk media gateway. Set this parameter by the following principles:

The value of this parameter can only be digits. The absolute value of the difference between the start circuit number and the start circuit

termination ID (a decimal value converted from a binary code) must be a multiple of 32, such as 0, 32, 64, or 96.

7.5.7 Adding R2 Trunk Group Caller Number Segment (Optional)

Related Commands

Command Function

ADD TKDNSEG To add a trunk group caller number segment

RMV TKDNSEG To remove a trunk group caller number segment

LST TKDNSEG To list trunk group caller number segments


By default, when the peer office initiates a call through an R2 incoming trunk to the local office, the local office does not judge the validity of the caller number sent by the peer office. Instead, it charges the caller number and displays it on the callee's telephone.

It may be necessary to precisely charge the call initiated through R2 incoming trunks for accurately distributing call charges to caller numbers during bill sorting. In addition, to prevent charge disputes caused by a wrong caller number from the peer office, the local office must judge the validity of the received caller number. The local office should judge whether or not the caller number is in the number segment defined by ADD TKDNSEG. If yes, the number is valid. If not, it is invalid.



Note the following:

To ensure the judging process, run MOD N1TG, and select Trunk group caller number segment (for the R2 incoming trunk group) in Software parameter of service control. Then the local office judges the validity of the caller number sent by the peer office. If the caller number is valid, the local office uses the original caller number in charging, and displays it on the callee's telephone. If it is invalid, the local office uses the default caller number of the trunk group in charging, and displays it on the callee's telephone.

If you also configure the calling number discrimination function for the R2 incoming trunk group with ADD TGDSG, calling number discrimination is prior to calling number validity judgment. That is, the SoftX3000 firsts discriminate the calling number sent by the peer office, and then judges the validity.


It defines the R2 incoming trunk group for which a caller number segment is to be configured. The parameter must be defined by ADD N1TG before being used here. You can configure only one caller number segment for each trunk group.

Start caller number, End caller number

The two parameters define the range of a trunk group caller number segment. Set this parameter by the following principles:

Trunk group caller number segment is independent data. The number type defined by it can be subscriber or national number in the maximum length of 16 digits.

If the calling number sent by the peer office is a subscriber number, the number type defined by the trunk group caller number segment must be subscriber number.

If the calling number sent by the peer office is a national number, the number type defined by the trunk group caller number segment must be national number. The national number should be in the format of "0 + national toll area code + subscriber number".

7.6 Configuring PRA Trunk Data 7.6.1 Overview

Configuration Relation The PRA trunk data configures interconnection information between the SoftX3000 and PBX, NAS, or other PRA device. The interconnection information includes:

Start E1 number End E1 number Default caller number

The PRA trunk data must be configured after the following data is configured:

Equipment data Local office data Charging data




Signaling data Routing data


During the configuration, the PRA trunk data reference certain parameters defined in:

Local office data Charging data Routing data

Table 7-23 lists the details.

Table 7-23 Parameter referencing relation between the PRA trunk data and other data



Call source code Local office data PRA trunk group number

PRA subscriber data


PRA link ID Signaling data - -



Preparations Before configuring the PRA trunk data, prepare as specified in Table 7-24.

Table 7-24 Preparations for configuring the PRA trunk data

SN Item Remark

1 Start E1 number and end E1 number of the PRA trunk group

These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA, and R2 trunk circuits. The corresponding physical numbers at the TMG are specified in the start circuit termination identifier parameter.

2 Termination identifier of circuit number

For interworking with TMG

Configuration Steps Table 7-25 lists the general steps for configuring the PRA trunk data.



Table 7-25 Steps for configuring the PRA trunk data


1 Add a PRA trunk group. ADD PRATG

2 Add a PCM port. (Optional) ADD PCMPORT

3 Add a PRA trunk circuit. ADD PRATKC

Parameter Referencing Relation Figure 7-9 shows the referencing relation between the key parameters used when the PRA trunk data is configured.

Figure 7-9 Parameter referencing relation of the PRA trunk data

Trunk group number

ADD PRATG

Equipment ID

Sub-route number

FCCU module number

ADD PRATKC

Trunk group number





7.6.2 Adding PRA Trunk Group

Related Commands

Command Function

ADD PRATG To add a PRA trunk group

RMV TG To remove a PRA trunk group

MOD PRATG To modify a PRA trunk group

LST TG To list PRA trunk groups

Notes of Configuration Before adding PRA trunk group, run the commands to obtain the following parameters defined by the system:

Parameter Command





LST CLRDSN



It identifies a unique trunk group, which can be:



Equipment ID

It defines the equipment ID of the TMG (such as the TMG8010 or UMG8900) providing PRA trunk circuits. This parameter must be defined by ADD MGW before being used here.



Sub-route number

It defines the subroute to which the trunk group belongs. This parameter must be defined ADD SRT before being used here.

Signaling link number

It defines the PRA signaling link used by the PRA trunk group. This parameter must be defined by ADD PRALNK before being used here.


It defines the default caller number used by the PRA trunk group. You can enter any telephone number, such as 88888888.

It is used with the parameter Caller number provision mode. If Caller number provision mode of the trunk group is Default number and no caller number is contained in the call signaling message sent by the peer office when it originates a call through the incoming trunk, the local office uses the default caller number.

Trunk group name


Group direction

It defines the call connection direction of the PRA trunk group. The default option is Bi-directional trunk. The parameter options are described as follows:




Call source code


Circuit type

It is reserved. The options include only PRA currently.


It defines the trunk circuit selection policy of the trunk group. The default mode is Cyclic. The meanings of the options are as follows:

Minimum The system always selects a trunk circuit from the minimum number. The preferential selection of the trunk circuits can be realized through this mode.

Maximum The system always selects a trunk circuit from the maximum number. The preferential selection of the trunk circuits can be realized through this mode.

Recycle




The system selects a circuit from the next one to the last selected circuit number each time. If the last selected number is the maximum one, the next one is the minimum number.



User side allocation The system selects a trunk circuit based on the command at the user side.


It is valid for incoming and outgoing trunks. Set the parameter by the following principles:

For incoming trunks, when a subscriber of the peer office originates a call through the incoming trunk, this parameter defines the mode how the local office obtains the caller number from the incoming trunk if the call signaling contains no caller number. If this parameter is set to Trunk line ID, the caller number is the trunk circuit number. If this parameter is set to Default number, the caller number is the default one defined in this command.

For incoming trunks, when a subscriber of the peer office originates a call through the incoming trunk and the incoming office signaling from the peer office contains the caller number, the local office uses this caller number for the call. The setting is invalid here.

For outgoing trunks, when a local subscriber originates a call through the outgoing trunk and this parameter is set to Trunk line ID, the called number dialed by the local subscriber must be a PRA subscriber number defined by the local office. Or else, the system rejects the call. If this parameter is set to Default number, the system connects the call.

When the PBX accesses the SoftX3000 through the PRA trunk and occupies the subscriber number resources of the local office, you can set the parameter Caller number provision mode of the corresponding PRA outgoing trunk to Trunk line ID. This is to prevent the PBX from using unauthorized PSTN numbers.

Enhanced attribute

If you set it to YES, the enhanced attributes are displayed.


It identifies whether the PRA trunk is carried over a satellite circuit. Set it based on the actual conditions. Generally, it is set to NO.

Call-in authority

It is valid only when the PRA trunk group works in trunk mode. It defines the call-in authority of the PRA trunk group, such as:

Intra-office Local Local toll National toll International toll Intra-office national toll (in multi-zone-code application) Intra-office international toll (in multi-country-code application)



Intra-office local toll


Call-out authority

It is valid only when the PRA trunk group works in trunk mode. It defines the call-out authority of the PRA trunk group, such as:



Send initial tone

It is valid only for incoming trunks. It specifies whether the local office sends the busy tone to the peer office for failed incoming trunk calls. By default, it is set to NO.

If it is set to NO, the local office sends to the peer office the Disconnect message without the Send busy tone flag when a call fails. At this time, the call is released and the peer office sends the busy tone to the caller.

If it is set to YES, the local office sends to the peer office the Disconnect message with the Send busy tone flag when a call fails. At this time, the call is held temporarily and the local office sends the busy tone to the caller through the incoming trunk. After the caller hangs up or the timer times out, the call is released.

Initial tone type

It is reserved.


It is valid only for incoming trunks. It controls whether the local office sends the exceptional tone to the peer office through the Alerting message when the call through the incoming trunk fails.

If the parameter is set to NO, the local office sends the Disconnect message to the peer office when the call fails. In this case, the call is released and the peer office sends busy tone to the caller.

If the parameter is set to YES, the local office sends the Alerting message to the peer office when the call fails. In this case, the call is held temporarily and the local office sends the exceptional tone to the caller through the incoming trunk. The type of the exceptional tone is determined by the call processing software based on the failure cause code. After the caller hangs up or the timer times out, the call is released.

Exceptional tone type

It is reserved.





It is valid only when the PRA trunk group works in trunk mode. It is one of the charging attributes of the trunk group (incoming trunk charging). Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of incoming trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being used here.



It is valid only when the PRA trunk group works in trunk mode. It is one of the charging attributes of the trunk group (outgoing trunk charging). Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of outgoing trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being used here.


Use opposite pulse

It is used for the inter-office trunk cooperation in the instant charging. When it is set to YES, its meanings for outgoing trunk and incoming trunk are different.

Outgoing trunk: When there is an outgoing call from the trunk group, the local office must receive the charging pulse in the signaling sent back from the peer office, and the peer office must cooperate to send the charging pulse to the local office through signaling.

Incoming trunk: When there is an incoming call to the trunk group, the local office must send charging pulse to the peer office through signaling, and the peer office must cooperate to receive the charging pulse sent from the local office through signaling.

CAMA

It is valid only for incoming trunks. It sets whether the local office performs centralized charging operations on the incoming trunk. When the peer office originates a call through the incoming trunk, the local office requests the calling number on initiative through signaling if the signaling from the originating office does not carry the calling number.


It sets whether to request caller number. It is valid only for incoming trunks. When the Whether request caller number parameter is set to YES, this parameter is used to ask the local office to request caller number from the peer office if the incoming call signaling through the trunk does not contain caller number. The default option is YES, indicating that the local office can request caller number on initiative. If this feature affects connection or connection time, it can be set to NO.


It sets whether the local office connects a call if the incoming call signaling through the trunk does not contain caller number or the contained number is invalid. It is valid only for incoming trunks. By default, it is set to YES.

Default connect

If querying caller number discrimination group failed (that is, the queried record is not found), it sets whether to connect the call. The default option is YES, indicating that the call is connected.




If the incoming call signaling through the trunk does not contain caller number, it defines whether the local office requests caller number from the peer office on initiative. It is available only for incoming trunks. The default option is NO, indicating that the local office does not request caller number on initiative.

Codec prefer

It defines the codec mode used by the RTP audio media streams of the TMG in the trunk group direction. Set this parameter by the following principles:

The codec prefer defined here must be defined in Codec list in ADD MGW. Or else, it is invalid.


You can specify a specific codec mode. Codec prefer is the first mode in the codec list that is supported by the MGWs of the caller and the callee. If the codec list contains the codec prefer of the caller, callee, incoming trunk group, and outgoing trunk group at the same time, the SoftX3000, according to the principle of "caller and subscriber prior to callee and trunk", queues a codec mode in the first position of the list during call connection. For example, − In an intra-office call, if the codec prefer of the caller is different from that of the callee,






It sets whether PRA trunks support certain special services or applications. There are 16 options for this parameter. Currently, five options are used, and the others are reserved. The meanings of the options are as follows:

Wide area network Centrex service It is used with bit 4 of the parameter "ISUP operation reserved parameter 9 (P26)". If you select this option and bit 4 of the "ISUP operation reserved parameter 9" is 0, the local office sends a short number contained in the IAM to the peer office in the WAN Centrex service.

Progress send tone It is valid only for outgoing trunks. If you select this option, when the local office originates a call to the peer office through the outgoing trunk, the local office sends to the caller resident office the Alerting message with the "Send ringback tone" flag if receiving the Progress message with the progress indicator as 1 or 8 from the peer office. At this time, the caller hears the ringback tone sent by the terminating office. If the local office receives the Progress message with the progress indicator as other values from the peer office, it sends to the caller resident office the Alerting message without the "Send ringback tone" flag. At this time, the caller hears the ringback tone sent by the resident office. If the peer




office connects the call slowly, the ringback tone can be sent to the caller faster through the setting of this parameter.

Audio to speech out trunk The transmission capability of outgoing trunks is degraded from audio to speech. This option is available only to outgoing trunks. If you select this option, when the local office originates a call to the peer office through the outgoing trunk, the local office sends a Setup message, in which the transmission capability field is set to "speech" forcedly to the peer office. That is, when the local office originates a call, it demands the peer office to degrade the transmission capability from 3.1-kHz audio to speech. By default, the system does not degrade the transmission capability.

Audio to speech in trunk The transmission capability of incoming trunks is degraded from audio to speech. This option is available only to incoming trunks. If you select this option, when the peer office originates a call to the local office through the incoming trunk, the local office forcedly degrades the transmission capability from 3.1-kHz audio to speech no matter what transmission capability field is set in the Setup message sent by the peer office. By default, the system does not degrade the transmission capability. If the degradation by the local office leads to no intersection of the transmission capabilities between the calling and called terminals, the calls cannot be connected. Therefore, be careful when setting this parameter.

Send calling party number but presentation restricted It is valid only for outgoing trunks. If you select this option, when the local office originates a call to the peer office through the outgoing trunk, the local office sends to the peer office a Setup message with calling number presentation indicator set to presentation restricted and containing the caller number if it detects that the caller has the CLIR authority. If you do not select this option (default value), the field calling number presentation indicator is still presentation restricted but no caller number is contained in the Setup message.


It defines whether a trunk group supports overlap code sending mode. The SoftX3000 supports the following two code sending modes:

Overlap code sending When the system receives enough digits of the called number for judging the route, it sends them to the peer office through an IAM or IAI, and then sends the remaining digits of the called number one by one through SAOs or SAMs.

Group code sending After the system collects all the digits of the called number, it sends them to the peer office through one signaling message.

The overlap code sending mode features fast connection but occupies plenty of CPU resources. The group code sending mode occupies a few CPU resources, but the connection is slow, which may affect the quality of the telecom services. The default mode is overlap code sending. When the SoftX3000 interconnects with a switch complying with ANSI through the No. 7 trunk group, you must set this parameter to NO.



Acoustic echo compression Noise compensation



Enhanced voice service Automatic gain control

You can select one or more of them based on the requirements.














7.6.3 Adding PCM Port (Optional)

Related Commands

Command Function

ADD PCMPORT To add a PCM port

MOD PCMPORT To remove a PCM port

RMV PCMPORT To modify a PCM port

LST PCMPORT To list PCM ports





For ISUP/TUP circuits By default, the PCM type is E1, and the PCM codec mode is A law when you run ADD N7TKC to add a No. 7 trunk circuit. For networking in countries such as the USA and Japan, the PCM type is T1, and the PCM codec mode is μ law generally. In this case, you must run ADD PCMPORT to add a PCM port.

For PRA circuits By default, one PRA signaling link can control only one Pulse Code Modulation (PCM) system. Correspondingly, you can add up to 32 PRA trunk circuits when running ADD PRATKC. When the PRA link resources are not enough, you must run ADD PCMPORT to add a PCM port if one PRA link is required to control multiple PCM systems (a maximum of four E1s).

Parameter Description For details, see section 7.4.7 "Adding PCM Port (Optional)."

7.6.4 Adding PRA Trunk Circuit

Related Commands

Command Function

ADD PRATKC To add a PRA trunk circuit

RMV TKC To remove a PRA trunk circuit

MOD PRATKC To modify a PRA trunk circuit

LST TKC To list PRA trunk circuits


It defines the module number of the FCCU processing the PRA calls. This parameter must be defined by ADD BRD before being used here.


Trunk group number

It defines the PRA trunk group to which the PRA trunk circuit to be added belongs. This parameter must be defined by ADD PRATG before being used here.

Start circuit, End circuit

They specify the range of the E1 circuit numbers for the PRA trunk circuits inside the SoftX3000. The value ranges from 0 to 9999. The configuration principles of these parameters are as follows:



These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA, R2, and V5 trunk circuits. The corresponding physical numbers at the TMG are specified in the Start circuit termination identifier parameter of the command.

The absolute value of the difference between the start circuit number and the start circuit termination identifier (a decimal value after converted from a binary value) must be a multiple of 32, such as 0, 32, 64, and 96.

If you does not run ADD PCMPORT to add PCM port, the system regards that the PRA link control only one PCM system by default, that is, only 32 PRA trunk circuits can be added once.

If you have run ADD PCMPORT to add n (1 ñ n ñ 4) PCM ports for a PRA link, a maximum of n*32 PRA trunk circuit can be added once.


It is one of the parameters used for the SoftX3000 to interwork with the AMG. It defines the number of the physical port of the AMG (UMG8900) corresponding to time slot 0 of the start PRA trunk E1. Set this parameter by the following principles:



Circuit state

It sets the initial state of a trunk circuit. Generally, the default value Available is used. When adding several circuits continuously, set it to Unavailable if a circuit of the TMG is used as a signaling timeslot.

7.7 Configuring AT0 Trunk Data 7.7.1 Overview

Configuration Relation The AT0 trunk data defines the AT0 trunk information at the SoftX3000 side, such as charging, call barring, and interconnection. To configure the AT0 trunk data, make sure that the following data is configured:

Equipment data Local office data Charging data MGW data Routing data


During the configuration, the AT0 trunk data will reference certain parameters defined in the local office data, charging data, MGW data, and routing data. Table 7-26 shows the details.




Table 7-26 Parameter referencing relation between the AT0 trunk data and other



Call source code Local office data - -



Charging data - -

Equipment ID of the TMG

MGW data - -


Preparations Before configuring the AT0 trunk data, prepare as specified in Table 7-27.

Table 7-27 Preparations for configuring the AT0 trunk data

SN Item Remark

1 Numbering range of AT0 trunk circuits

These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA, and AT0 trunk circuits. The corresponding physical numbers at the TMG are specified in the start circuit termination identifier parameter.

2 Termination ID of circuit number

It is one of the interconnection parameters between the SoftX3000 and the TMG.

Configuration Steps Table 7-28 lists the general steps for configuring the AT0 trunk data.

Table 7-28 Steps for configuring the AT0 trunk data


1 Add an AT0 trunk group. ADD AT0TG

2 Add an AT0 trunk circuit. ADD AT0TKC

Parameter Referencing Relation Figure 7-10 shows the referencing relation between the key parameters used when the AT0 trunk data is configured.



Figure 7-10 Parameter referencing relation of the AT0 trunk data

Trunk group number

ADD AT0TG

Equipment ID

Sub-route number

FCCU module number

ADD AT0TKC

Trunk group number


7.7.2 Adding AT0 Trunk Group

Related Commands

Command Function

ADD AT0TG To add a AT0 trunk group

RMV TG To remove a AT0 trunk group

MOD AT0TG To modify a AT0 trunk group

LST TG To list AT0 trunk groups

Notes of Configuration Before adding an AT0 trunk group, run the commands to obtain the following parameters defined by the system:

Parameter Command





Parameter Command




This section introduces only the parameters closely related to AT0 trunk group. For the other parameters, see online help or section 7.5.5 "Adding R2 Trunk Group."

Trunk group number




Group direction

It defines the call connection direction of the AT0 trunk group. For the AT0 trunk group, set this parameter to outgoing trunk, which indicates that the AT0 trunk group processes only the outgoing calls to the peer office.

Equipment ID

It defines the equipment ID of the access media gateway (such as the UMG8900 or AMG5000) providing AT0 trunk circuits. This parameter must be defined by ADD MGW before being used here.

Sub-route number


Trunk group name


Call source code



It defines the trunk circuit selection policy of the trunk group. For the AT0 trunk group, select Minimum. Or else, the connection fails.



Call-in authority




Call-out authority




DOD2

It is valid for outgoing trunks to control whether the local callers can hear the secondary dial tone sent by the peer office after seizing the outgoing trunk. If AT0 trunk is used for PBX DDI networking, set the parameter to NO.


It is one of the charging attributes of the (incoming) trunk group. Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of incoming trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being used here.



It is one of the charging attributes of the (outgoing) trunk group. Its value range is from 0 to 255. The value 254 is the wildcard that cannot be used for trunk charging. The value 255 indicates no charging of outgoing trunks. This parameter must be defined by ADD CHGIDX or ADD CHGGRP before being used here.





Waiting seizure ACK time

It is valid only for outgoing trunks. After the local office seizes a trunk circuit and sends the seizure signal (line signaling) to the peer office, it defines the maximum time for waiting for the seizure acknowledgement signal (dial tone) that is returned by the peer office. The value range is from 0 to 10, and the unit is second. The default value is 5.

If the local office receives no seizure acknowledgment signal after waiting timeout, it auto enters the seizure acknowledgment state.

Ringing duration

It is valid only for incoming trunks. When an originating subscriber calls a local office subscriber through an incoming trunk, the local office simultaneously sends the ringing tone to the callee and the ringback tone to the originating office if the callee is idle. It defines the maximum time during which the local office monitors the ringing at the callee. The value range is from 0 to 65535, and the unit is second. The default value is 240.

Back tone time

It is valid only for outgoing trunks and only when the parameter Polarity check in this command is set to YES. It defines the maximum duration during which a local caller (or an incoming trunk) can hear the ringback tone. The value range is from 0 to 90, and the unit is second. The default value is 30.

If the local office detects the polarity reversal signal on the trunk when the caller (or the incoming trunk) hears the ringback tone, it regards this time point as the start time for charging. If the caller hears the ringback tone until timeout, the local office auto releases the call.

The time when the local caller enters the state of hearing the ringback tone is not the time when the terminating office starts sending the ringback tone to the local office, but the time after one timer duration when all digits of the called number are sent. The timer duration is defined in the parameter Listening to ringback tone delay in this command.

Number send delay

It is valid only for outgoing trunks. It specifies the duration between the time when the local office receives the outgoing trunk circuit seizure acknowledgement message returned by the peer office and the time when the local office sends the first digit. The value range is from 0 to 10, and the unit is second. The default value is 1.

If the time when the local office starts to seize the outgoing trunk circuit is counted, the delay for the local office to send the first digit to the peer office is "Waiting seizure ACK time" + "Number send delay".

Automatic answer time

It is valid only for outgoing trunks and only when the parameter Polarity check in this command is set to NO. After the ringback tone is played to the local subscriber (through the incoming trunk), it defines the monitoring duration after the local subscriber auto enters the conversation state (suppose the callee has picked up the phone). The value range is from 0 to 30, and the unit is second. The default value is 6.

If the peer PBX does not provide the polarity reversal function on subscriber boards, the local office cannot judge the answer time of an AT0 outgoing trunk call according to the off-hook of the callee. After this parameter is set, the local office takes the "Alerting signal send delay + Automatic answer time" after all digits of the called number are sent as the charging start time by default, no matter whether the callee picks up the phone or when the callee picks up the phone.



Polarity check

It defines whether the local office detects the polarity reversal signal sent by the peer PBX after an outgoing trunk of the local office seized. It is available only for outgoing trunks. The default value is YES.

If the local office detects no polarity reversal signal on the trunk within the specified timer duration, the call fails. The timer length is defined in the parameter Alerting signal send delay in this command.

Alerting signal send delay

It defines the delay for a local caller (or an incoming trunk) to hear the ringback tone after the local office sends all digits of the called number through the outgoing trunk. It is available only to outgoing trunks. The value range is from 0 to 30, and the unit is second. The default value is 5.



Overlap code sending: When the system receives enough digits of the called number for judging the route, it sends them to the peer office through an IAM or IAI, and then sends the remaining digits of the called number one by one through SAOs or SAMs.

Group code sending: After the system collects all the digits of the called number, it sends them to the peer office through one signaling message.

The overlap code sending mode features fast connection but occupies plenty of CPU resources. The group code sending mode occupies a few CPU resources, but the connection is slow, which may affect the quality of the telecom services. The default mode is overlap code sending. When the SoftX3000 interconnects with a switch complying with ANSI through the No. 7 trunk group, you must set this parameter to NO.





EC attribute

If you set it to Yes, the echo cancellation attributes are displayed.

EC signaling flag

It defines whether the local office starts the echo suppress function according to the echo suppress signal sent by the originating office or the echo suppress data configured at the local office. The default option is YES.

EC use mode

It defines the mode in which the local office starts the echo suppress function to the AT0 trunk circuits. The default option is No internal EC support. The setting of this parameter must be consistent with that of the peer office. In other words, to successfully complete call connection




through AT0 trunk, both exchanges must provide the echo suppress function. This premise must be satisfied first. Otherwise, the connection may fail. The parameter options are described as follows:

No internal EC support It indicates the system does not start the echo suppress function to the AT0 trunk circuits.

EC support for outgoing call It indicates the system starts the echo suppress function only to the outgoing AT0 trunk circuits. In this case, the corresponding incoming trunk circuits of the peer office must support the echo suppress function.

EC support for incoming call It indicates the system starts the echo suppress function only to the incoming AT0 trunk circuits. In this case, the corresponding outgoing trunk circuits of the peer office must support the echo suppress function.

Bi-directional EC support It indicates the system starts the echo suppress function to both outgoing and incoming AT0 trunk circuits. In this case, the corresponding incoming and outgoing trunk circuits of the peer office must support the echo suppress function.

External EC support It indicates the system uses an external echo suppress device that is interconnected between the exchange and the transmission device.

When the AT0 trunk is carried over the satellite circuits, this parameter is set to Bi-directional echo suppress.

Forward office EC

It is valid only for incoming trunks. It specifies the mode in which the originating office starts the echo suppress function to the AT0 trunk circuits. The default option is Unknown.

For the meanings of the options, see the description of Using EC mode.

Backward office EC

It is valid only for outgoing trunks. It specifies the mode in which the terminating office starts the echo suppress function to the AT0 trunk circuits. The default option is Unknown.

For the meanings of the options, see the description of Using EC mode.

Connect without EC

The local office has started the echo suppress function to the AT0 trunk circuits. When the related echo suppress device becomes faulty during the call, it defines whether the local office continues the call. The default option is YES.

EC index

It defines the EC data to be used in this command. This parameter must be defined by ADD ECPARA before being used here.

Enhanced attribute


CAMA

It is valid only for incoming trunks. It sets whether the local office performs centralized accounting operations on the incoming trunk. If the value is YES, the local office adopts the



centralized accounting mode for the incoming trunk. In this case, when the peer office originates a call through the incoming trunk, the local office requests the calling number on initiative through signaling if the signaling from the originating office does not carry the calling number.


It sets whether to request caller number. It is valid only for incoming trunks. When the Whether request caller number parameter is set to YES, this parameter is used to ask the local office to request caller number from the peer office if the incoming call signaling through the trunk does not contain caller number. The default option is YES, indicating that the local office can request caller number on initiative. If this feature affects connection or connection time, the option can be set to NO.


It sets whether the local office gets a call through if the incoming call signaling through the trunk does not contain caller number or the contained number is invalid. It is valid only for incoming trunks. The default option is YES.

Minimum caller number length

It is valid only for incoming trunks. When the Whether request caller number parameter is set to YES, it defines the minimum number length of the caller number if the incoming call signaling through the trunk carries the caller number. If the actual length of the caller number is less than the defined minimum number length, the local office does not connect the call, that is, the local office rejects the call. By default, the minimum number length of the caller number is seven digits.





If the peer office sends the calling number in the incoming call signaling, the local office uses it and this parameter is invalid.


It is valid only for incoming trunks. If Caller number provision mode of the trunk group is Default number and no caller number is contained in the call signaling message sent by the peer office when it originates a call through the incoming trunk, the local office uses the default caller number.



If the value is not specified or specified with 65535, it indicates that the call barring function is not enabled.

If the black/white list barring is used, the three preset call barring groups can be referenced directly, that is black list 60001, white list 60002, and ordinary call barring group 65534.





During the number analysis process of inter-group call barring authentication, the SoftX3000 should authenticate twice the caller, called prefix, and the callee. The inter-group call barring authentication procedure is as follows:



Priority

It defines the routing priority for the AT0 trunk group. A trunk group with currently the highest priority is selected first. A trunk group will be selected to convey traffic only after there are absolutely no available trunk circuits with a higher priority than it. The greater the value is, the lower the priority is. The value 0 indicates the highest priority.

Availability

It is valid only when the trunk group selection mode of a subroute is set to Cyclic. It defines the times that a trunk group can be selected in the corresponding subroute. Its value range is from 0 to 255. By default, it is set to 255, indicating invalid.

In a subroute, every time the system selects the trunk group, the available times of the trunk group is decreased by 1. When the available times become 0, the system cannot select the trunk group. If the available times of all trunk groups in the corresponding subroute become 0, those times is assigned with new values. This parameter is designed to distribute the traffic over all trunk groups of the subroute according to the expected principle, that is, the carrier can use this parameter to control the selected ratio of each trunk group of a subroute.

Default connect

If querying caller number discrimination group failed (that is, the queried record is not found), it sets whether to connect the call. The default option is TRUE, indicating that the call is connected.


If the incoming call signaling through the trunk does not contain caller number, it defines whether the local office requests caller number from the peer office on initiative. It is valid only for incoming trunks. The default option is FALSE, indicating that the local office does not request caller number on initiative.
















7.7.3 Adding AT0 Trunk Circuit

Related Commands

Command Function

ADD AT0TKC To add a AT0 trunk circuit

RMV TKC To remove a AT0 trunk circuit

MOD AT0TKC To modify a AT0 trunk circuit

LST TKC To list AT0 trunk circuits


It defines the module number of the FCCU processing the AT0 trunk calls. This parameter must be defined by ADD BRD before being used here.


Trunk group number

It defines the AT0 trunk group to which the AT0 trunk circuits to be added belongs. This parameter must be defined by ADD AT0TG before being used here.





They specify the E1 numbering range of the AT0 trunk circuits in the SoftX3000. The value ranges from 0 to 6399. Set this parameter by the following principles:

These are unified logical numbers assigned inside the SoftX3000 to No. 7, PRA, R2, V5, and AT0 E1 trunk circuits in an FCCU module. The corresponding physical numbers at the TMG are specified in the start circuit termination ID parameter in this command.

A maximum of 32 trunk circuits can be added in one execution of this command. If you want to add more than 32 trunk circuits, run the command several times.

Circuit state

It defines the initial state of trunk circuits. Generally, the default value Available is used.


It defines the start circuit timeslot number of a batch of trunk circuits in the resident AMG (UMG8900 or AMG5000). Set this parameter by the following principles:



7.8 Configuring V5 Trunk Data 7.8.1 Overview

Configuration Relation The V5 trunk data configures the E1 information of the SoftX3000 for interconnecting with such V5 devices as access network devices and base station controller. The E1 information includes:

Start E1 number End E1 number V5 link ID

The V5 trunk data must be configured after the following data is configured:

Equipment data MGW data V5UA data


During the configuration, certain parameters defined in the equipment data, MGW data and V5UA data will be referenced in the V5 trunk data. Certain parameters defined in the V5 trunk data will be referenced when the V5 interface data is configured. Table 7-29 lists the details.



Table 7-29 Parameter referencing relation between the V5 trunk data and other



Equipment ID of the media gateway

MGW Data V5 trunk group number

V5 interface data

Module number of FCCU Equipment data - -

V5UA link set index V5UA data - -

Preparations Before configuring the V5 trunk data, prepare as specified in Table 7-30.

Table 7-30 Preparations for configuring the V5 trunk data

SN Item Remark

1 Start E1 number and end E1 number of V5 trunk group

The internal E1 numbers of the SoftX3000

2 V5 link IDs of E1s in V5 trunk group For interworking with V5 access network device

3 Terminal ID of the MGW corresponding to the start E1 of V5 trunk group

For interworking with access media gateway

4 MGW E1 link IDs of V5 trunk group For interworking with access media gateway

Configuration Steps Table 7-31 lists the general steps for configuring the V5 trunk data.

Table 7-31 Steps for configuring the V5 trunk data


1 Add a V5 trunk group. ADD V5TG

2 Add a V5 trunk circuit. ADD V5TKC

Parameter Referencing Relation Figure 7-11 shows the referencing relation between the key parameters used when the V5 trunk data is configured.




Figure 7-11 Parameter referencing relation of the V5 trunk data

Trunk group number

ADD V5TG

Equipment ID

FCCU module number

ADD V5TKC

Start E1 number

End E1 number

Trunk group number

7.8.2 Adding V5 Trunk Group

Related Commands

Command Function

ADD V5TG To add a V5 trunk group

RMV V5TG To remove a V5 trunk group

MOD V5TG To modify a V5 trunk group

LST V5TG To list V5 trunk groups



SIP trunk group H.323 trunk group No. 7 trunk group R2 trunk group PRA trunk group



AT0 trunk group V5 trunk group


Equipment ID

It defines the equipment ID of the AMG (such as UMG8900) providing V5 trunk circuits. This parameter must be defined by ADD MGW before being used here.

Trunk group name















7.8.3 Adding V5 Trunk Circuit

Related Commands

Command Function

ADD V5TKC To add a V5 trunk circuit

RMV V5TKC To remove a V5 trunk circuit




Command Function

MOD V5TKC To modify a V5 trunk circuit

LST V5TKC To list V5 trunk circuits


It defines the module number of the FCCU processing the V5 calls. This parameter must be defined by ADD BRD before being used here.

The FCCU module number defined here must be the same as that defined in ADD MGW for adding the UMG. Or else, the UMG circuits cannot work normally.

Start E1 number, End E1 number

They are used to specify the E1 number range of the V5 trunk circuits in the SoftX3000. The value ranges from 0 to 311. The configuration principles for these two parameters are described as follows:

This range of E1 numbers includes the unified logical numbers assigned in a particular FCCU module to E1 trunk circuits regarding No. 7, PRA, R2, and V5 inside the SoftX3000. The corresponding physical numbers at the access media gateway are specified in the start MG E1 link ID parameter in this command.

For V5.1 interface, the end E1 number must be equal to the start E1 number, that is, only one E1 can be configured.

For V5.2 interface, the difference between the end E1 number and the start E1 number must be less than or equal to 15, that is, a maximum of 16 E1s can be configured.

Trunk group number

It defines the V5 trunk group to which the V5 trunk circuit to be added belongs. This parameter must be defined by ADD V5TG before being used here.

Start E1 link ID

It is one of the parameters used for the SoftX3000 to interwork with the V5 access network device. It identifies a unique 2.048 Mbit/s link in the corresponding V5 interface. In the same V5 trunk group, the E1 link IDs must not be repeated.

V5UA linkset number

It defines the V5UA link set bearing the physical C channels of the corresponding V5 interface. This parameter must be defined by ADD V5UALKS before being used here.

Start MG termination ID

It is one of the parameters used for the SoftX3000 to interwork with the AMG. It defines the circuit terminal ID of time slot 0 of the start E1 for the V5 trunk circuit at the AMG (UMG8900) side. Set this parameter by the following principles:





Start MG E1 link ID

It is one of the parameters used for interworking with the AMG. It defines the E1 link ID at the AMG side corresponding to the start E1 of the V5 trunk group. In the same access media gateway, the E1 link IDs must not be repeated.

Equipment ID

It defines the equipment ID of the media gateway (UMG8900) to which the V5 trunk circuit configured in ADD V5TKC belongs. This parameter must be defined by ADD MGW before being used here. The parameter configuration principle is described as follows:

When the active and standby links of a V5 interface are provided by a media gateway, that is, the V5 interface is homed to one UMG8900, you must not specify the parameter.

Suppose that the active and standby links of a V5 interface are provided by two media gateways, that is, the V5 interface is homed to two UMG8900s controlled by the same SoftX3000. If the V5 trunk circuit configured in ADD V5TKC belongs to the UMG8900 specified by using ADD V5TG, you must not specify the parameter. Or else, set the parameter to the equipment ID of another UMG8900.

The parameter backs up the V5 interface in equipment level. That is, the V5 interface of a V5 access network equipment can be homed to two UMG8900s controlled by the same SoftX3000. In normal cases, the two UMG8900s bear all calls of subscribers of the V5 access network in load sharing mode. When one UMG8900 is faulty, the other can bear all calls of subscribers of the V5 access network.

7.9 Configuring Trunk Group Bearer Data 7.9.1 Overview

Configuration Relation The trunk group bearer data configures information related to outgoing trunk calls (that is, outgoing calls). The information includes:

Trunk occupancy point Caller number change Called number change

During the configuration, certain parameters defined in the number analysis data and trunk group data will be referenced in the trunk group bearer data. Table 7-32 lists the details.

Table 7-32 Parameter referencing relation between the trunk group bearer data and other



Trunk group number Trunk data - -

Number change index Number analysis data - -




Configuration Steps Table 7-33 lists the general steps for configuring the trunk group bearer data.

Table 7-33 Steps for configuring the trunk group bearer data


1 Add a TOS changing index. (Optional) ADD TOSC

2 Add trunk group bearer. ADD TGLD

3 Add a trunk group bearer index. ADD TGLDIDX

Parameter Referencing Relation Figure 7-12 shows the referencing relation between the key parameters used when the trunk group bearer data is configured.



Figure 7-12 Parameter referencing relation of the trunk group bearer data

Bearer index

ADD TGLD

Trunk occupy point

Trunk group number

ADD TGLDIDX

Call source code

Call prefix

Caller TOS change index

Callee TOS change index

Bearer index

TOS changing index

ADD TOSC

TOS changing type

TOS value after changing

7.9.2 Adding TOS Changing Index (Optional)

Related Commands

Command Function

ADD TOSC To add a TOS changing index

RMV TOSC To remove a TOS changing index

MOD TOSC To modify a TOS changing index




Command Function

LST TOSC To list TOS changing indexes


Type of Service (TOS) is an 8-bit field in the header of the IP packet. TOS controls the router to transfer the IP packet. Figure 7-13 shows its bit structure.

Figure 7-13 Bit structure of TOS

ReservedTOS sub-fieldPriority sub-field

7 6 5 4 3 2 1 0

In Figure 7-13, the priority sub-field occupies three bits and is not used currently. The TOS sub-field occupies four bits:

Bit 4 represents the minimum delay. Bit 3 represents the maximum throughput. Bit 2 represents the highest reliability. Bit 1 represents the minimum charge.

Among the four bits, only one bit can be set to 1 at one time. If the four bits are all set to 0, it means common service. The reserved bits must be set to 0.

In actual application, TOS controls the router of the gateway office to route the outgoing traffic. For example, the pure audio traffic is routed to the dedicated VoIP network to ensure Quality of Service (QoS), and the video traffic is routed to the Internet. To set traffic routing control, you must run ADD TOSC to add the TOS changing index.

Parameter Description TOS changing index

It defines a TOS changing index uniquely in the SoftX3000. Its value range is from 0 to 255.

TOS changing type

It defines the type of the TOS change. The options are:

Not need to change TOS value It indicates that the SoftX3000 neither modifies the TOS field in the IP packet, nor notifies the GW, terminal, or NAT device with a signaling message to modify the TOS field in the media stream packet.

Need to change TOS value



It indicates that the SoftX3000 not only modifies the TOS field in the IP packet, but also notifies the GW, terminal, or NAT device with a signaling message to modify the TOS field in the media stream packet.

TOS value after changing

It is one of the parameters for the SoftX3000 to interwork with the router of the gateway office. It defines the TOS field in a specified IP packet manually. The parameter is valid only when there is a need to change the TOS value. It is a decimal value, ranging from 0 to 255. Generally, bigger TOS value indicates higher service level. If it is set to 255, it indicates no change.

The carrier must plan the relation between various services and TOS values in advance. The related GW, terminal, NAT, and router must support the identification of the TOS field in the IP packet. Or else, the TOS traffic routing function cannot be implemented.

7.9.3 Adding Trunk Group Bearer

Related Commands

Command Function

ADD TGLD To add trunk group bearer

RMV TGLD To remove trunk group bearer

MOD TGLD To modify trunk group bearer

LST TGLD To list trunk group bearer

Parameter Description Bearer index

It identifies a piece of trunk group bearer data uniquely in the SoftX3000. If you bind Trunk group bearer index with a trunk group by using ADD TGLD or ADD TGLDIDX, the trunk group can implement number change, TOS change, and other special services through trunk group bearer.

Trunk seizure point

It defines the minimum length of the called number that causes the local office to occupy the outgoing trunk. The length here refers to the length after number change.

During the trunk number analysis, the system judges whether the called number complies with the number length prescribed by Minimal number length in the call prefix data. If not, the system continues to wait for the called number. If yes, the system judges whether the called number complies with the number length prescribed by Trunk occupy point in the trunk bearer data. When the called number complies with the number length prescribed by Trunk occupy point, the system begins occupying the outgoing trunk.

Caller sending change index

It defines the index for calling number change before the local office sends the calling number through the outgoing trunk. This parameter must be defined by ADD DNC before being used here.

Callee sending change index




It defines the index for called number change before the local office sends the called number through the outgoing trunk. This parameter must be defined by ADD DNC before being used here.

Caller TOS change index

It defines the change of the TOS field of the IP packet made by the local office when there is an incoming call. It is available only for incoming trunks. It must be defined by ADD TOSC before being used here.

Callee TOS change index

It defines the change of the TOS field of the IP packet made by the local office when there is an outgoing call. It is available only for outgoing trunks. It must be defined by ADD TOSC before being used here.

If the original TOS value in the incoming signaling message is inconsistent with that after callee TOS change, or the TOS value after caller TOS change is inconsistent with that after callee TOS change, the system uses the TOS value with higher priority for the call.

Direct national route

It defines whether the local office forcibly sets the "national/international call indicator" bit to 1 (that is, process the call as an international call) when the SoftX3000 transits an incoming or outgoing international call. The bit is in the "forward call indicator" field in the IAM message sent from the local office to a lower national office or the peer international office.

The default option is NO, indicating that the local office does not process the international call on the trunk group according to the above description.

Echo suppress

It defines whether the local office enables the echo suppress function on the incoming trunk direction. The default option is NO, indicating that the echo suppress function is disabled.

Send caller number

It defines whether the local office sends the caller number to the peer office. It is valid only for outgoing trunks. The default option is NO, indicating that the local office does not send the caller number to the peer office.

DOD2

It controls whether the local caller can hear the secondary dial tone sent by the peer office after seizing the outgoing trunk. It is valid only for outgoing trunks. The default option is NO.

DOD2 position

It defines the duration between the time when a local caller seizes the outgoing trunk and the time when the caller hears the secondary dial tone sent by the peer office. It is valid only when DOD2 is set to YES. The value of the parameter ranges from 0 to 15, in the unit of second. The default value is 1.

Delay ring back position

It defines how long the local office delays to send an Alerting message to the peer office after the peer office initiates a call through an incoming trunk, and the call is connected successfully. It is valid only for incoming trunks. The value of the parameter ranges form 0 to 15, in the unit of second. The default value is 7.

FAS



It defines whether the local office can receive the FAS signal sent by the peer office. It is valid only for incoming trunks. The default option is NO.



Overlap code sending When the system receives enough digits of the called number for judging the route, it sends them to the peer office through an IAM or IAI, and then sends the remained digits of the called number one by one through SAOs or SAMs.

Group code sending After the system collects all the digits of the called number, it sends them to the peer office through one signaling message.

The overlap code sending mode features fast connection but occupies more CPU resources. The group code sending mode occupies fewer CPU resources, but the connection is slow, which may affect the quality of the telecom services. The default mode is overlap code sending. When the SoftX3000 interconnects with a switch complying with ANSI through the No. 7 trunk group, you must set this parameter to NO.

Extend overlap send called number

It sets whether a No. 7 trunk group supports extended overlap code sending mode, that is, whether the trunk group can send the remained digits of the called number to the peer office through an SAM.

The extended overlap code sending mode is different from the overlap code sending mode. In the overlap code sending mode, the remained digits of the called number can be sent to the peer office in one or several SAOs/SAMs. The extended overlap code sending mode allows only the remained digits to be sent to the peer office in one SAM.

7.9.4 Adding Trunk Group Bearer Index

Related Commands

Command Function

ADD TGLDIDX To add a trunk group bearer index

RMV TGLDIDX To remove a trunk group bearer index

MOD TGLDIDX To modify a trunk group bearer index

LST TGLDIDX To list trunk group bearer indexes


It defines the number of the outgoing trunk group to which the trunk group bearer index is to be added. This parameter must be defined by ADD SIPTG, ADD H323TG, or ADD N7TG before being used here.




Call source code

It is one of the match conditions for trunk group bearer data. When a call seizes the outgoing trunk group, it defines the call source code of the calling number that matches the trunk group bearer data. The value range is from 0 to 65535. The wildcard 65534 represents all call source codes. This parameter must be defined by ADD CALLSRC before being used here.

When the call processing software analyzes the trunk group bearer, if the call source code of several trunk group bearer indexes matches the current call in the system, the wildcard 65534 has the lowest priority, that is, the system matches the other call source codes as prior.

Call prefix

It is one of the match conditions for trunk group bearer data. When a call seizes the outgoing trunk group, it defines the prefix of the called number that matches the trunk group bearer data. It is the first several digits of the called number. "eeeeeeee" is the wildcard, indicating all prefixes.

When the call processing software analyzes the trunk group bearer, if the call prefix of several trunk group bearer indexes matches the current call in the system, the wildcard eeeeeeee has the lowest priority, that is, the system matches the other call prefixes as prior.

Local DN set

It is one of the match conditions for trunk group bearer data. When a call seizes the outgoing trunk group, it defines the local DN set of the call prefix that matches the trunk group bearer data. It must be defined by ADD LDNSET before being used here.

Bearer index

It defines the trunk group bearer index used by the trunk group. This parameter must be defined by ADD TGLD before being used here.

7.10 Other Commands 7.10.1 Adding Trunk Group Append Configuration

Related Commands

Command Function

ADD TGAP To add trunk group append configuration

RMV TGAP To remove trunk group append configuration

MOD TGAP To modify trunk group append configuration

LST TGAP To list trunk group append configuration

Notes of Configuration The command ADD TGAP is used to add trunk group append configuration data such as:

Convert cause value



Convert protocol cause value Charging complaint Incomplete call watch Allow divert UC analysis flag AOC99 flag


It defines the number of the trunk group to which append configuration data of the trunk group is to be added. This parameter must be defined by ADD SIPTG, ADD H323TG, ADD N7TG, ADD N1TG, and ADD PRATG before being used here.

Convert cause value

It defines whether the SoftX3000 converts the release cause value generated and transmitted in the SoftX3000 software into that transmitted between offices in the trunk group direction. The default value is NO. If you set it to YES, you must correctly set the release cause value conversion data with ADD TKRCC.

Convert protocol cause value

It is valid only for SIP trunks. It defines whether the SoftX3000 converts the protocol cause value generated and transmitted in the SoftX3000 software into that transmitted between offices in the trunk group direction. The default value is NO. If you set it to YES, you must correctly set the protocol cause value conversion data with ADD TKPCC.

Charging complaint

It is one of the charging attributes of the trunk group. It sets whether to generate a complaint ticket when the trunk group is charged. The default value is NO, indicating that the system does not generate a complaint ticket. If it is set to YES, complaint tickets are generated for incoming and outgoing trunk calls.

Incomplete call watch

It defines whether the system records the failed calls on one trunk group, that is, whether the system generates watch bills for failed calls. The options are:

No watch It is the default value, indicating that the system does not record the failed calls occurred on the trunk group.

Watch caller It indicates that the system records only the failed calls occurred on the incoming trunk group.

Watch callee It indicates that the system records only the failed calls occurred on the outgoing trunk group.

Watch both It indicates that the system records all failed calls occurred on the trunk group.




UC analysis flag

In UC service, UC subscribers can bind the numbers of non-local subscribers as original binding numbers. The bound numbers of non-local subscribers can be fixed numbers or mobile numbers. The parameter specifies whether the system immediately triggers caller UC service when there is an incoming call on the trunk group, and the calling number of the incoming call fully matches an original binding number in the system. It is valid only for incoming trunks. The default option is NO.

AOC99 flag

It defines if the SoftX3000 sends or receives AOC99 charging information in the ISUP signaling messages on the No. 7 trunk group. It is NO by default. If the charging manner (which can be set with ADD CHGANA) of the charging source code of the trunk group or the outgoing trunk charging source code is Send AOC99 charging information, Receive AOC99 charging information, or Transfer AOC99 charging information, you must set this parameter to YES.

Carrier selection flag

It defines whether the SoftX3000 needs to contain carrier selection code in the IAM sent through the No. 7 outgoing trunk group. It is valid for No. 7 outgoing trunk groups only. It is NO by default.

When the local office serves as an originating office and you have set carrier selection code for a preselection access code with ADD PRECODE, you must set this parameter to YES. At this time, when the local office originates a call associated with preselection, it contains the parameter carrier access code in the forward IAM on the outgoing ISUP trunk.

AOC99 national regulation

It indicates the nation identification code contained in the AOC99 charging information sent by the SoftX3000 through the No. 7 trunk group. It is valid only for outgoing trunks. It ranges from 0 to 65535. It is a fixed code.

AOC99 network

It indicates the network identification code (also called carrier identification code) contained in the AOC99 charging information sent by the SoftX3000 through the No. 7 trunk group. It ranges from 0 to 65535. It is allocated country-wide by the telecom department.

AOC99 node identification

It indicates the node identification code (also called office identification code) contained in the AOC99 charging information sent by the SoftX3000 through the No. 7 trunk group. It ranges from 0 to 65535. It is allocated country-wide by the telecom department.

Generate CDR

When an incoming terminated call or a transit call happens on the trunk group, this parameter defines if the SoftX3000 generates a trunk group CDR. The default value is YES. Set the parameter by the following principles:

For an incoming terminated call, if you set this parameter to YES for the incoming trunk group, the SoftX3000 generates a trunk group CDR. Or else, no CDR is generated.

For an outgoing call, no matter what value of this parameter you set for the outgoing trunk group is, the SoftX3000 generates no CDR.

For a transit call, if you set this parameter to YES for either the related incoming or outgoing trunk group, the SoftX3000 generates a trunk group CDR. It does not generate a CDR only when you set this parameter to NO for the related incoming and outgoing trunk groups.



Owned status

It defines the owing fee status of the trunk group. The parameter values are listed as follows:

Normal It means that the trunk group has the call-in and call-out authority, and is marked as a normal subscriber.

Owing fee in call-out It means that the trunk group has the call-in authority, but is restricted to call out except for making emergency calls such as fire and police emergency calls.

Owing fee in call-in It means that the trunk group can call out, but its call-in authority is restricted.

Owing fee in call-out and call-in It means that the call-in and call-out authority of the trunk group is restricted except for outgoing emergency calls.

Owing fee but have right It means that the trunk group has the call-in and call-out authority, but is marked as an owing fee subscriber.

Emergency calls and console calls are not restricted.

Caller discrimination failure function

It defines the processing after the caller number discrimination on the trunk group fails. The parameter values are listed as follows:

No Change It means that no processing is made after the caller number discrimination on the trunk group fails.

Reject call It means that the call processing software rejects all calls from the caller number.

Change caller It means that the call processing software modifies the attributes of the caller number in the incoming trunk call. The attributes include: − Call source code − Charging source code − Barring group number − Caller category

Caller number change index

It decides whether to change the caller number. It is valid only when the Caller discrimination failure function parameter is set to Change caller. It must be defined by ADD DNC before being referenced here.

If you set it to 0, it indicates the caller number is not changed.

Caller category

It redefines the caller category of the caller number. It is valid only when the Caller discrimination failure function parameter is set to Change caller.

Call source code




It redefines the call source code used by the caller number. It is valid only when the Caller discrimination failure function parameter is set to Change caller. It must be defined in ADD CALLSRC before being referenced here. If you set it to 65535, it indicates the call source code is not changed.


It redefines the charging source code used by the caller number. It is valid only when the Caller discrimination failure function parameter is set to Change caller. It must be defined in ADD CHGIDX or ADD CHGGRP before being referenced here. If you set it to 255, it indicates the charging source code is not changed.

Barring group number

It redefines the call barring group number used by the caller number. It is valid only when the Caller discrimination failure function parameter is set to Change caller.

If you set it to 65535, it indicates the call barring group number is not changed. If you use the black and white list function, you can directly reference the three preset call

barring group numbers: 60001 for black list, 60002 for white list, and 65534 for call barring group.

If you set it to any other value, the value must be defined in SET GRPAC before being referenced here.

7.10.2 Adding Caller Category Transform Index

Related Commands

Command Function

ADD CATRNS To add a caller category transform index

RMV CATRNS To remove a caller category transform index

MOD CATRNS To modify a caller category transform index

LST CATRNS To list caller category transform indexes

Notes of Configuration When the SoftX3000 interconnects with the switching equipment of other manufactures through ISUP trunk, the caller category transmitted through signaling messages between two offices may not meet the requirements of each other. This is because differences may exist in definition and usage of caller category in different countries or by different equipment manufacturers. In this case, you can run ADD CATRNS and ADD ICATRNS at the SoftX3000 side to add the conversion relation between caller categories to make them of both offices matched.

Parameter Description Call source code

It defines the call source whose caller category transform index is to be configured. This parameter must be defined by ADD CALLSRC before being used here.



Trunk group number

It defines the number of the trunk group whose caller category transform index is to be configured. This parameter must be defined by ADD SIPTG, ADD N7TG, or ADD N1TG before being used here.

Transform index

It identifies a transform index uniquely for the specified incoming trunk group of a call source in the SoftX3000. That is, you can use only one transform index for the call source code and trunk group number defined in this command.

Although the value of this parameter is of enumeration type, it has no special meanings and is used to set up the indexing relation with the internal caller category transform index table (defined in ADD ICATRNS). There are 11 options for this parameter. In other words, it ranges from 0 to 10.

7.10.3 Adding Internal Caller Category Transform

Related Commands

Command Function

ADD ICATRNS To add internal caller category transform

RMV ICATRNS To remove internal caller category transform

MOD ICATRNS To modify internal caller category transform

LST ICATRNS To list internal caller category transform

Notes of Configuration When the SoftX3000 interconnects with the switching equipment of other manufactures through ISUP trunk, the caller category transmitted through signaling messages between two offices may not meet the requirements of each other. This is because differences may exist in definition and usage of caller category in different countries or by different equipment manufacturers. In this case, you can run ADD CATRNS and ADD ICATRNS at the SoftX3000 side to add the conversion relation between caller categories to make them of both offices matched.

Parameter Description Transform index

It identifies a transform index uniquely for an internal caller category in the SoftX3000. Although the value of this parameter is of enumeration type, it has no special meanings. There are 11 options for this parameter. In other words, it ranges from 0 to 10.

Caller inner calling category

It defines the caller category before change, that is, the caller category received by the local office from the incoming signaling messages, such as ISUP messages. Its value range is from 0 to 255. It must be negotiated and kept consistent with that of the peer office.

New inner calling category




It defines the caller category in the SoftX3000 after change, that is, the new caller category transformed from the one received by the local office from the incoming signaling messages, such as ISUP messages. Its value range from is 0 to 255. Before setting this parameter, consult Huawei technical engineers.

7.10.4 Adding Protocol Cause Value Convert

Related Commands

Command Function

ADD TKPCC To add protocol cause value convert

RMV TKPCC To remove protocol cause value convert

MOD TKPCC To modify protocol cause value convert

LST TKPCC To list protocol cause value convert

Notes of Configuration When the SoftX3000 interconnects with the switch of other manufactures through ISUP trunk, the protocol cause value transmitted through signaling messages between two offices may not meet the requirements of each other. This is because differences may exist in definition and usage of the protocol cause value in different countries or by different manufacturers. In this case, you can run ADD TKPCC at the SoftX3000 side to add the conversion relation between protocol cause values to make them of both offices matched.

Parameter Description Convert type

It defines the conversion direction of protocol cause values, that is, to convert the internal protocol cause value to the external protocol cause value, or conversely.

Protocol type

It defines the protocol whose cause value needs to be converted. Currently, the SoftX3000 supports converting the cause value of SIP.

Protocol cause

It defines the external protocol cause value for conversion. Its value range is from 300 to 699. It must be negotiated and kept consistent with that of the peer office.

Internal cause

It defines the internal protocol cause value for conversion. Its value range is from 0 to 255. Consult Huawei technical engineers for how to set this parameter.



7.10.5 Adding Release Cause Value Convert

Related Commands

Command Function

ADD TKRCC To add release cause value convert

RMV TKRCC To remove release cause value convert

MOD TKRCC To modify release cause value convert

LST TKRCC To list release cause value convert

Notes of Configuration Suppose a transit network is networked as "A–B–C", and the SoftX3000 acts as transit office B. If the signaling between A and B defines the release cause value differently from that between B and C, the SoftX3000 must convert the release cause values of A and C when transferring the signaling between A and C. Otherwise, it is possible that the release cause values that are transmitted by the SoftX3000 cannot meet the requirements of A and C. In this case, you can add the conversion relation between release cause values at the SoftX3000 to make them matched by using ADD TKPCC.

Parameter Description Old cause value

It defines the release cause value before conversion, that is, the release cause value received by the local office from the originating office through incoming signaling, such as ISUP signaling. Its value range is from 0 to 65535. It should be negotiated and kept consistent with that of the peer office.

Caller trunk group number

It defines the incoming trunk group through which the inter-office signaling including the release cause value before conversion is transmitted to the local office. It must be defined by ADD SIPTG, ADD N7TG, or ADD N1TG before being used here. The value 65534 is a wildcard, indicating all incoming trunk groups.

Callee trunk group number

It defines the outgoing trunk group through which the inter-office signaling including the release cause value after conversion is transmitted by the local office to the terminating office. It must be defined by ADD SIPTG, ADD N7TG, or ADD N1TG before being used here. The value 65534 is a wildcard, indicating all outgoing trunk groups.

Local DN set

It defines the local DN set to which the call prefix whose release cause value is to be converted belongs. It must be defined in ADD LDNSET before being used here.

Call prefix

It defines the call prefix whose release cause value is to be converted. That is, when the SoftX3000 analyzes the called number in the incoming signaling, it converts the release cause




value only if the called number can match the call prefix defined here. This parameter must be defined in ADD CNACLD before being used here. *65534# is the wildcard, indicating all call prefixes.

New cause value

It defines the release cause value after conversion, that is, the release cause value sent by the local office to the terminating office through outgoing signaling, such as ISUP signaling. Its value range is from 0 to 65535. It should be negotiated and kept consistent with that of the peer office.

01-07 Configuring Trunk Data

Documents

Transcript of 01-07 Configuring Trunk Data