¡ New Features of SoftX3000 V300R601C05¡¿AGCF Feature

AGCF Feature
Supported by SoftX3000 V3000R601C05 and later versions
www.huawei.com
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

Contents
 Introduction to AGCF
 AGCF Data Configuration
 AGCF Registration Process and Basic Call Flow
 AGCF Services
 AGCF Charging, Performance Measurement, Alarm and Signaling
trace
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 2

AGCF in IMS Network
Diameter
AS
HSS
SIP
Diameter
I-CSCF S-CSCF
OCS
Diameter
SIP SIP
SIP CCF
Diameter
AGCF
P-CSCF
H.248 AG SIP
AG
POTS POTS

AGCF Functions
 The AGCF originates registration requests to the IMS core for POTS
subscribers, thus connecting POTS subscribers to the IMS network.
 The POTS subscribers supported by the AGCF are H.248 subscribers
connected to the UA5000.
 Cooperating with other NEs in the IMS network, the AGCF provides PES
services, such as the call waiting, call forwarding, and three-party services.
 The AGCF provides bill information about AGCF subscribers to the CCF,
which adopts the Diameter protocol for interworking.

Interfaces Between AGCF and Peripheral NEs
IMS Core CCF
SIP Diameter
AGCF
MML
H.248
N2000 AG

AGCF Hardware Structure
B B S H S H U U
F F I S I S P P
Back boards
I I U C U C W W
I I I I I I R R
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
I I U U S S C C B B M M A U U
F F A A M M D D S S S S L P P
Front boards M M C C U U B B G G G G U W W
I I U U I I I I I I I I I R R
The UACU board implements the AGCF functions.

The service processing board (FCCU) of the SoftX3000 is not
required for the AGCF.
AGCF Software Structure
PID_FM
UACU
PID_AGENT
PID_USER PID_IMSBILL
PID_MGRA PID_MGC PID_DIAMRM

PID_SIP_APP
PID_H248 PID_DIAMCM
BSG PID_SIP_STK MSG

Difference Between AGCF and SoftX3000 in
Hardware and Software Installation
 In terms of hardware and software installation methods and cable
connections, no difference exists between the AGCF and the SoftX3000.
 The only difference is that the SoftX3000 uses the FCCU as the service
processing board, whereas the AGCF uses the UAUC. The FCCU and
UACU use the same hardware and differ from each other in terms of board
type, which is specified by running ADD BRD.

Contents
 AGCF Services
trace

Introduction to Data Configuration
The AGCF data consists of:
 Basic data
 Interworking data
 Subscriber data

Basic Data Configuration
The basic data of the AGCF consists of:

Equipment data
Protocol data
The following key parameters of the basic data will be referenced during the configuration
of other data:
Rack, subrack, and board (ADD SHF, ADD FRM, ADD BRD)
IP address of FE port (ADD FECFG)
IP routing data (ADD IPRT)
Database function (ADD CDBFUNC)
SIP protocol data (SET SIPLP, SET SIPCFG)
The configuration commands and parameters of the above basic data are
the same as those of the SoftX3000.

Interworking Data Configuration
The interworking data are used for interworking between the AGCF and
other IMS NEs, such as the I-CSCF, S-CSCF, and CCF. The following data
is added for the AGCF feature:
Home network data (ADD HNID)
Visited network data (ADD VNID)
Access network data (ADD ANI)
DNS data (ADD DNSRR)
Diameter local information (SET DIAMLOC)
Diameter peer device (ADD DIAMPEER)
Diameter link set (ADD DIAMLKS)
Diameter link (ADD DIAMLNK)
Phone context (ADD PHNCT)

Adding Home Network Data (Mandatory)
ADD HNID: NAME="hnid", HD="huawei.com";
Home network ID specifies the ID of the home network of a subscriber and

indicates the destination of the registration request. The Request-URI header field of
the registration request is filled with this parameter value. The home network name
specified here is converted to the IP address of the I-CSCF through DNS resolution.

Adding Visited Network Data (Mandatory)
ADD VNID: NAME="vnid", VNID="agcf.huawei.com";
Visited network ID specifies the ID of the visited network of a subscriber and

indicates the network on which the subscriber is located. The P-Visited-Network-ID
header field of the registration request is filled with this parameter value.

Adding Access Network Data (Mandatory)
ADD ANI: NAME="ani", ANI="GEN-ACCESS%3B%22location-

info%3DLINEIDTEST%22" ;
Access network info specifies the ID of the access network of a subscriber. It indicates the
information about the access network through which the subscriber accesses the IMS
network. The P-Access-Network-Info header field of the registration request and the INVITE
message is filled with this parameter value.

Adding DNS Data (Mandatory)
ADD DNSRR: DNS="huawei.com", IP="160.29.0.117";
DNS data configuration is used to configure the mapping between domain names
and IP addresses. The AGCF resolves two types of domain names, namely, domain
name of the home network and domain name of the S-CSCF. The former is used for
registration and the latter for call setup.

Setting Diameter Local Information (Mandatory)
SET DIAMLOC: HN="agcf.huawei.com", DN="huawei.com";
Host name uniquely identifies an AGCF entity on the network.

Setting a Diameter Peer Device (Mandatory)
ADD DIAMPEER: ID=8, DT=CCF, HN="ccf0.huawei.com", DN="huawei.com";
ADD DIAMPEER is used to configure the Diameter peer device, that is, the CCF.
Key parameters: Device type, Host name, and Domain name

Adding a Diameter Link Set (Mandatory)
ADD DIAMLKS: ID=8, PEERID=8, LSNAME="diam_links_1";
Key parameters: Peer device ID and Link selection mode (active/standby

or load-sharing)

Adding a Diameter Link (Mandatory)
ADD DIAMLNK: ID=0, MSGMID=13, LSX=8, LIP1="160.10.20.3",
PIP1="160.10.30.25";
Key parameters: MSG module number, Linkset ID, Protocol type, Local IP address1, and
Peer IP address1

Configuring Phone Context (Mandatory)
ADD PHNCT: PCN="shenzhen", PC="+86755";
Phone context refers to the phone-context parameter in the SIP protocol. In

a basic call, the phone-context parameter specifies the country code and area
code of the AGCF and is used by the upper NE for number normalization.

Subscriber Data Configuration
Subscriber data configuration consists of the configuration of the gateway

data, registration group data, and subscriber data.
Adding a gateway (ADD MGW)

Adding a registration group (ADD REGGRP)
Adding a subscriber (ADD ASBR)
ADD REGGRP and ADD ASBR are added for the AGCF feature.
A subscriber configured on the AGCF must be defined on the HSS.

Single Subscriber Registration & Group Registration
The AGCF supports two registration modes:

Single subscriber registration: When a gateway starts to provide services, the
AGCF sends a registration request on behalf of each subscriber connected to the
gateway.
Group registration: Multiple subscribers are placed in a registration group.
When a gateway starts to provide services, the AGCF sends a registration request
on behalf of the registration group. In this mode, an implicit registration set must
be configured on the HSS.
Compared with the single subscriber registration mode, less registration requests
are sent when the group registration mode is used. Thus, the impact on the bearer
network is minimized, especially when the number of subscribers is huge.

Adding a Registration Group
ADD REGGRP: RGN="reg1", EID="160.24.2.15:2944",

PRI="66680002@huawei.com",
TPUI="sip:66680002@huawei.com", HNID="hnid", NETID="vnid",
NETINFO="ani", PWD="******";
Only subscribers in a registration group need to be configured with the

above data. In other words, you need not configure a registration group data
for a subscriber adopting the single subscriber registration mode.
Key parameters: Registration group name, Equipment ID, Private user
ID, Temporary public user ID, Home network ID name, Visited
network ID name, Access network information name, and Password

Adding a Group Subscriber
ADD ASBR: PUI="sip:6680002@huawei.com",

PRI="6680002@huawei.com", REGTP=GROUP, RGN="reg1",
TID=K'2, HNID="hnid", NETID="vnid", NETINFO="ani",
PHNCON="shenzhen", DIGMAP=0, PWD="*****", SGN="scc",
DP=YES;
Only subscribers in a registration group need to be configured with the

above data.
Key parameters: Public user ID, Private user ID, Registration group
name, Termination ID, Home network ID name, Visited network ID
name, and Access network information name

Adding a Single Subscriber
ADD ASBR: PUI="sip:6680001@huawei.com",

PRI="6680001i@huawei.com", REGTP=SINGLE, MN=22,
EID="160.24.2.15:2944", TID=K'1, HNID="hnid", NETID="vnid",
NETINFO="ani", PHNCON="shenzhen", DIGMAP=0, PWD="******",
SGN="scc" , DP=YES, DR=YES;
Only subscribers adopting the single subscriber registration mode need to be

configured with the above data.
Key parameters: Public user ID, Private user ID, Equipment ID,
Termination ID, Home network ID name, Visited network ID name, and
Access network information name

Data Configuration Example
How to configure the AGCF in the left figure?
Hardware:
An AGCF with a rack, a subrack, over five service boards, over one
SMU boards, and corresponding back boards
Diameter A UA5000
AS
Diameter A router
Diameter HSS
SIP Multiple network cables and terminals
Diameter
Software:
I-CSCF S-CSCF
Network ID: GEN-ACCESS%3B%22location-
OCS info%3DLINEIDTEST%22
Diameter Public user ID of a single subscriber: sip:6680001@huawei.com
Public user ID of a registration group: sip:6680002@huawei.com
Public user ID of a group subscriber: sip:6680003@huawei.com
SIP SIP SIP Diameter
CCF
AGCF P-CSCF
NE IP Address Domain Name
H.248 UA/AG SIP I-CSCF 160.29.0.117 huawei.com

UA/AG
S-CSCF 160.29.0.118 scscf.huawei.com
MGC 160.24.2.1 agcf.huawei.com

POTS POTS
MG 160.24.2.15 -
CCF 160.24.2.25 ccf0.huawei.com

Data Configuration Example—Basic data
Add a rack.
ADD SHF: SHN=0, ZN=0, RN=0, CN=0;
Add a subrack.
ADD FRM: FN=0, SHN=0, PN=2;
Add boards. (Standby boards are not configured here. During deployment, configure their slot
numbers based on the actual conditions.)
ADD BRD: FN=0, SLN=0, LOC=FRONT, FRBT=IFMI, MN=132, ASS=255;
ADD BRD: FN=0, SLN=1, LOC=FRONT, FRBT=UACU, MN=22, ASS=255;
ADD BRD: FN=0, SLN=5, LOC=FRONT, FRBT=MSGI, MN=136, ASS=255;
ADD BRD: FN=0, SLN=3, LOC=FRONT, FRBT=BSGI, MN=137, ASS=255;
ADD BRD: FN=0, SLN=10, LOC=FRONT, FRBT=CDBI, MN=102, ASS=255;
ADD FECFG: MN=132, IP="160.24.2.1", MSK="255.255.0.0",
DGW="160.24.0.254",CONFIRM=Y;
ADD CDBFUNC: CDPM=102, FCF=LOC-1&TK-1&MGWR-1&DISP-1,CONFIRM=Y;

Data Configuration Example-Interworking data1
Add home network data.
ADD HNID: NAME="hnid", HD="huawei.com";
Add visited network data.
ADD VNID: NAME="vnid", VNID="agcf.huawei.com";
Add access network data.
ADD ANI: NAME="ani", ANI="GEN-ACCESS%3B%22location-info%3DLINEIDTEST%22";
Add a digitmap for H.248 subscribers.
ADD DMAP: PROTYPE=H248, DMAPIDX=0, PARTIDX=0, DMAP="888xxxx|666xxxx|668xxxx|[EF]xx[EF]|[EF].xx[E]x.F|F";
Add an SCC group.
ADD SCCGRP: SGN=“scc”, SDM=0;
Add a phone context.
ADD PHNCT: PCN="shenzhen", PC="+86755";
Add an H.248 gateway.
ADD MGW: EID="160.24.2.15:2944", GWTP=AG, MGCMODULENO=22, PTYPE=H248, LA="160.24.2.1", RA1="160.24.2.15",
ET=NO, SUPROOTPKG=NS;
Add a DNS route (used for registration).
ADD DNSRR: DNS=“huawei.com”, IP=“160.29.0.117”;)
Add a DNS route (used for call setup).
ADD DNSRR: DNS=“scscf.huawei.com”, IP=“160.29.0.118”;
Add an IP route.
ADD IPRT: MN=132, IP=“160.0.0.0”, IPM=“255.0.0.0”;
Set SIP global parameters.
SET SIPCFG: UST=SessionTimer;
Set a SIP local port.
SET SIPLP:;

Data Configuration Example-Interworking
data2
Set Diameter local information.
SET DIAMLOC: HN=“agcf.huawei.com”, DN=“huawei.com”;
Add a Diameter peer device.
ADD DIAMPEER: ID=8, DT=CCF, HN=“ccf0.huawei.com”, DN=“huawei.com”;
Add a Diameter link set.
ADD DIAMLKS: ID=8, PEERID=8;
Add a Diameter link.
ADD DIAMLNK: ID=0, MSGMID=136, PEERID=0, LIP1=“160.24.2.1”,
PIP1=“160.24.2.25”;

Data Configuration Example-Subscriber data
Add a registration group.

ADD REGGRP: RGN="reg1", EID="160.24.2.15:2944", PRI="66680002@huawei.com",
TPUI="sip:66680002@huawei.com", HNID="hnid", NETID="vnid", NETINFO="ani",
PWD="******";
Add a group subscriber.
ADD ASBR: PUI="sip:6680002@huawei.com", PRI="6680002@huawei.com",
REGTP=GROUP, RGN="reg1", TID=K'2, HNID="hnid", NETID="vnid",
NETINFO="ani", PHNCON="shenzhen", DIGMAP=0, PWD="*****", SGN="scc",
DP=YES;
Add a single subscriber.
ADD ASBR: PUI="sip:6680001@huawei.com", PRI="6680001i@huawei.com",
REGTP=SINGLE, MN=22, EID="160.24.2.15:2944", TID=K'1, HNID="hnid",
NETID="vnid", NETINFO="ani", PHNCON="shenzhen", DIGMAP=0, PWD="******",
SGN="scc" , DP=YES, DR=YES;

Contents
 AGCF Services
trace

AGCF Registration Process
Message flow
AG AGCF I-CSCF
SVC_CHG_REQ
SVC_CHG_REPLY
REGISTER
200

AGCF Registration Process
Description:
1. When an H.248 gateway connected to the AGCF starts to provide services, the
H.248 gateway sends an SVC_CHG_REQ to the AGCF.
2. Upon receipt of the SVC_CHG_REQ , the AGCF sends an
SVC_CHG_REPLY to the H.248 gateway.
3. The AGCF scans all the single subscribers and registration groups connected to
the H.248 gateway, and sends a REGISTER to the I-CSCF on behalf of each
single subscriber and each registration group.
4. The I-CSCF responds with a 200, indicating that the registration is successful.

AGCF Basic Call—Gateway Playing Ringback Tone
Message flow
AG_A AGCF-O S-CSCF-O AS-O I-CSCF-T S-CSCF-T AS-T AGCF-T AG_B
Notify/Reply
Offhook
Mod/Reply
Dial tone
Notify/Reply
Dial num
Add/Reply
Reserve T
D1: INVITE
SDP_A
D1: INVITE
SDP_A
D2: INVITE
SDP_A
D2: INVITE
SDP_A D2: INVITE
SDP_A D2: INVITE
SDP_A
D3: INVITE
SDP_A
D3: INVITE ADD/Reply
SDP_A Reserve T
D3:180 MOD/Reply
ring
D3: 180
D2: 180
D2: 180 D2: 180
D2: 180 Notify/Reply
D1: 180 offhook
D1: 180
D3: 200
Mod/reply SDP_A&B
Ring back D3: 200
SDP_A&B
D2: 200
D2: 200 SDP_A&B
D2: 200 SDP_A&B
SDP_A&B
D2: 200
SDP_A&B
D1: 200
D1: 200 SDP_A&B
Mod/reply SDP_A&B
SDP_A&B
D1: ACK D1: ACK
D2:ACK
D2: ACK D2: ACK
D3: ACK
D3: ACK
MOD/Reply
SDP_A&B
A and B start a conversation.

Description from the aspect of the caller:

1. After a subscriber picks up the phone, the H.248 gateway sends a NOTIFY to the AGCF on the
calling side. Upon receipt of the NOTIFY, the AGCF on the calling side sends a MOD_REQ to
instruct the H.248 gateway to play the dial tone, collect digits according to the digitmap, and
detect possible on-hook events.
2. The subscriber begins to dial digits. The H.248 gateway reports the digits to the AGCF on the
calling side, which then requests association establishment.
3. After successfully establishing the association, the H.248 gateway sends the caller SDP to the
AGCF on the calling side, which then sends an INVITE containing the caller SDP to the S-
CSCF.
4. Once the callee is alerted, the S-CSCF sends a 180 to the AGCF on the calling side. Upon
receipt of the 180, the AGCF on the calling side sends a message to instruct the H.248 gateway
to play the ringback tone to the caller.
5. After the callee picks up the phone, the S-CSCF sends a 200 containing the callee SDP to the
AGCF on the calling side. The AGCF on the calling side sends a MOD containing the callee
SDP to the H.248 gateway and responds with an ACK.

Description from the aspect of the callee:

1. Upon receipt of the INVITE from the S-CSCF, the AGCF on the called side
sends a request containing the caller SDP for association establishment to the
H.248 gateway on the called side.
2. Upon receipt of the response to the association establishment request, the
AGCF on the called side sends a MOD to the H.248 gateway on the called side
for announcement playing and sends a 180 to the S-CSCF.
3. Once the callee picks up the phone, the AGCF on the called side sends a 200
to the S-CSCF.

SDP negotiation process:
 The caller SDP negotiation is implemented through the exchange of INVITE

and 200 messages.
 The callee SDP negotiation is implemented through the exchange of INVITE
and 200 messages.

AGCF Basic Call—Network Playing Ringback Tone
Message flow
AG_A AGCF-O IMS Core caller IMS Core callee AGCF-T AG_B
Notify/Reply
offhook
Mod/Reply
Dial tone
Notify/Reply
Dial num
Add/Reply
Reserve T INVITE
SDP_A INVITE
SDP_A INVITE
SDP_A ADD/Reply
180 Reserve T
183 (p-early-media) PRACK MOD/Reply
183(p-early-media) SDP_MRF&A 200 ring
Mod/reply SDP_MRF&A
SDP_MRF&A PRACK
PRACK
200
200
180
180
PRACK
PRACK
200
200
Notify/Reply
200 offhook
UPDATE SDP_A&B
UPDATE SDP_A&B
SDP_A&B
200
SDP_A&B 200
SDP_A&B
Mod/reply
SDP_A&B 200
200
ACK
ACK
ACK
MOD/Reply
SDP_A&B
A and B start a conversation.

AGCF Basic Call—Network Playing Ringback Tone
SDP negotiation process:
 The ringback tone is played by the MRS at the request of the AS on the called
side.
 The negotiation of the SDP used for ringback tone playing is implemented
through the exchange of INVITE and 183 messages.
 The caller SDP negotiation is implemented through the exchange of UPDATE
and 200 messages.
 The callee SDP negotiation is implemented through the exchange of INVITE
and 200 messages.

Contents
 AGCF Services
trace

Characteristics of AGCF Services
 Cooperating with other NEs on the IMS network for service provision
The AGCF must cooperate with other NEs on the IMS network for service provision.
 Customizing service flow
The AGCF supports customizing the name and flow of a service.
This feature is the Switching Order Command (SOC) feature required by FT.
 Supporting loose-coupling services
The IMS services, especially the hook flash services, can be implemented in tight
coupling mode or loose coupling mode. Currently, the AGCF supports only services in
loose coupling mode.

Basic Concepts of SOC
 Action: Logically, a service can be divided into multiple actions. These actions are
sequenced together to from a service flow. For example, the call waiting service
consists of the following actions: hearing the call waiting announcement, requesting
command codes such as 1, 2 and 3, placing a session on hold, playing the call hold
announcement, connecting the waiting party, switching between two calls, and
releasing the waiting party.
 Leg state: Leg state indicates the overall state of all sessions. For example, a session is
active whereas a session is placed on hold, or only one session is active. The leg state
changes with the service flow.
 Event: Events are operations performed by subscribers, such as hook flash, on-hook,
and receipt of command codes. A service flow is event-driven.

Basic Concepts of SOC
 Service state: With other conditions, the service state is used to control the processing
of the SOC logic. By default, the service state of a service is set to IDLE. The
subsequent service states can be customized but must form a closed loop. In other
words, the service should return to the IDLE state after a normal or exceptional service
flow.
 SOC logic: SOC logic specifies the output service state and output behavior of a
service after an event is received in a certain service state and leg state. Take the call
waiting service for example. When its service state is wait-soc-num and leg state is one
active one waiting, the output service state should be IDLE and output behavior should
be placing the active party on hold and connecting the waiting party, after command
code 2 is received. Multiple closed-loop SOC logic data records form a specific service
flow.

AGCF Service Configuration
Procedure:
1. Add the service action (ADD SOCACT), such as requesting the SOC number,
requesting the initial number, or connecting the waiting party.
2. Add a service (ADD SOCCFG).
3. Add the SOC logic (ADD SOCLOGIC).
4. Add a service right (ADD SRVRGT).

Adding the Service Action
ADD SOCACT: SI="connect waiting party", AI=CWP;
Service action provides options such as Request SOC number, Request

initial number, and Connect waiting party.

Adding a Service
ADD SOCCFG: SN="China CW", SP=1;
Specify Service name and Service PRI as desired.

Adding the SOC Logic
ADD SOCLOGIC: SN="China CW", SS="wait-soc-num", LS=LAW,
EVT=S1, OSS="idle", ACT1="release active party",
ACT2="connect waiting party";

Adding a Service Right
ADD SRVRGT: IMPU="sip:6680001@huawei.com", SN="China

CW";
ADD SRVRGT is used to assign a service right to a subscriber.

Call Waiting (An AGCF Service Example)
User experience:
When A and B are engaged in a call, C calls A. After hearing the prompt tone, A
presses the hook switch and dials 2 to answer the call from C. B is placed on
hold and hears the music. (A must have the call waiting service right.)

Service configuration:
1. Run ADD SOCACT to add the service action.
Set Service action to Start call waiting, Request SOC number, Hold active
party, and Connect waiting party.
2. Run ADD SOCCFG to add a service.
Specify Service name and Service PRI.
3. Run ADD SOCLOGIC to add the service logic.
 For the receipt of a session during the conversation, set Output action to Start
call waiting.
 For the receipt of a hook flash message, set Output action to Request SOC
number.
 For the receipt of an SOC number, 2 for example, set Output action to Hold
active party, and Connect waiting party.

Service flow
S-CSCF AGCF AG-A
A and B are in conversation. (ID1)
C calls A. INVITE
(ID2, no SDP)
Start call waiting
MOD/REPLY
182 Play CW announcement

NOTIFY/REPLY Press the
hook switch
Send SOC digitmap
and dial tone MOD/REPLY (digitmap, DT)
Dial SOC
NOTIFY/REPLY
SOC_2
P1: Place the active party on hold
and connect the waiting party
INVITE (ID1, sendonly)
L1
200 (ID1, receiveonly)
ACK (ID1)
200 (ID2, SDP_A)
ACK (ID2, SDP_B)

MOD/REPLY
A talks with C. B is placed on

hold.

Contents
 AGCF Services
trace

AGCF Charging Flow
The AGCF starts charging after AGCF S-CSCF CCF
a 200 in response to the INVITE

INVITE is received and stops
200 (to INVITE)
charging when the call is
released. An intermittent bill is ACR[Start]
generated every 240 seconds.
ACA
All the bills are stored in the
bill pool and sent to the CCF Conversation
by the AGCF when the
ACR[Interim]
Diameter link is in normal
state. ACA
……
Bye
ACR[Stop]
ACA

AGCF Performance Measurement
The AGCF provides four performance measurement units:
 AGCF User Originating Traffic

 AGCF User Terminating Traffic
 MGW Out Traffic
 MGW Terminating Traffic

AGCF New Alarms
Alarm ID Description Message Contents
Indicates a long conversation.

• Conversation start time
The subscriber may hang up,
967 • Conversation duration
but the related resources are
• Caller and callee numbers
not released.
• Cause value
4900 Indicates a registration failure.
• Subscriber number
• Call time
Indicates that an emergency • Caller and callee numbers
4904
call is originated. • Gateway and port number of the
caller
Indicates that an emergency • Call time

4905
call is terminated. • Caller and callee numbers

Fault Identification Methods
Command query
• Checking a gateway (LST/DSP MGW)
• Deactivating or activating a gateway (DEA/ACT MGW)
• Checking a subscriber (LST ASBR, DSP USR)
• Manually registering or deregistering a subscriber (MNT USR)
• Checking data consistency
Signaling trace
• H.248 or SIP message tracing
• Internal interface tracing
The trace type PUI is added for the AGCF feature and must be set to the public ID of a subscriber.
Log display
• DeviceAlarm: displaying certain errors and alarms
• Serial port display
The fault identification methods of the AGCF are similar to those of the SoftX3000.

Thank You
www.huawei.com
www.huawei.com
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

¡ New Features of SoftX3000 V300R601C05¡¿AGCF Feature

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

¡ New Features of SoftX3000 V300R601C05¡¿AGCF Feature

Uploaded by

Copyright:

Available Formats

AGCF Feature

Supported by SoftX3000 V3000R601C05 and later versions

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 2

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 3

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 4

IMS Core CCF

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 5

The UACU board implements the AGCF functions.

PID_MGRA PID_MGC PID_DIAMRM

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 7

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 8

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 9

The AGCF data consists of:

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 10

The basic data of the AGCF consists of:

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 11

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 12

ADD HNID: NAME="hnid", HD="huawei.com";

Home network ID specifies the ID of the home network of a subscriber and

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 13

ADD VNID: NAME="vnid", VNID="agcf.huawei.com";

Visited network ID specifies the ID of the visited network of a subscriber and

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 14

ADD ANI: NAME="ani", ANI="GEN-ACCESS%3B%22location-

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 15

ADD DNSRR: DNS="huawei.com", IP="160.29.0.117";

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 16

SET DIAMLOC: HN="agcf.huawei.com", DN="huawei.com";

Host name uniquely identifies an AGCF entity on the network.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 17

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 18

ADD DIAMLKS: ID=8, PEERID=8, LSNAME="diam_links_1";

Key parameters: Peer device ID and Link selection mode (active/standby

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 19

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 20

ADD PHNCT: PCN="shenzhen", PC="+86755";

Phone context refers to the phone-context parameter in the SIP protocol. In

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 21

Subscriber data configuration consists of the configuration of the gateway

Adding a gateway (ADD MGW)

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 22

The AGCF supports two registration modes:

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 23

ADD REGGRP: RGN="reg1", EID="160.24.2.15:2944",

Only subscribers in a registration group need to be configured with the

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 24

ADD ASBR: PUI="sip:6680002@huawei.com",

Only subscribers in a registration group need to be configured with the

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 25

ADD ASBR: PUI="sip:6680001@huawei.com",

Only subscribers adopting the single subscriber registration mode need to be

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 26

H.248 UA/AG SIP I-CSCF 160.29.0.117 huawei.com

MGC 160.24.2.1 agcf.huawei.com

CCF 160.24.2.25 ccf0.huawei.com

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 27

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 28

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 29

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 30

Add a registration group.

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 31