07 - MSOFTX3000 SBC SIP Introduce - 201306 V2 1

MSOFTX3000 & SBC
SIP Configuration Introducution
201306 Turkey AVEA

Updated in 201306
HUAWEI TECHNOLOGIES CO., LTD.

Contents
1. Network layout for SIP Overview

2. Interconnection with other operators
3. SIP configuration on MSFTX3000
4. SIP configuration on SBC
5. Routine maintenance
6. Others
Network layout of SIP Overview
BICC
SIP/SCTP
SIP/UDP
VMSC GMSC PLMN/PSTN
RTP SBC
 SIP is over SCTP inner AVEA network
 SIP is over UDP for interconnecting with PLMN/PSTN
 Both of GMSC and SBC can support SIP-I.
 SBC can translate SIP/SCTP to SIP/UDP
 But, SBC cannot support translate the SIP-I to SIP which means both of GMSC and PSTN have to use the
same SIP protocol.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Contents

6. Others
Interconnection with other operators
SCTP heart-beat
SIP Option
VMSC SIP3 Load- SBC 01 Load- SIP1

sharing sharing
PLMN/PSTN
GMSC SIP2
SIP4
SBC 02
GMSC
 At each main site there are 2 SBCs which work at load-sharing mode
 Thus for PLMN/PSTN it need create 2 SIP trunks at load-sharing mode too.
 Same for GMSC, 2 SIP trunks at load-sharing mode
 The SIP is over SCTP between GMSC and SBC, because SCTP can detect the link status so there is no
need to start the SIP option heart-beat.
 The SIP is over UDP between SBC and PLMN/PSTN, the SIP option heart-beat is recommended.

Istanbul
1
2
SBC 01
GMSC TT 01 SBC 03 TT
3 SBC 02
Ankara
SBC 04
GMSC TT 02 SBC 06
SBC 05
 At each main site there are 2 SBCs which work at load-sharing mode, there is no interconnection between
these 2 SBCs.
 AVEA SBC can take the TT SBC as the softswitch
 Considering about the redundancy, one SBC may need to interworking with 2 softswitchs, and because
GMSC use SIP/SCTP to connect with SBC, so every PSTN/PLMN office need 4 signaling IPs in one
SBC. As the original IP plan one SBC only have 28 IPs, in the future is most probably need new IPs.
 We suggest the route is:

SIP-TT-ROUTE: SRT1=1, 50%, SRT2=2, 50%, SRT3=3, 50%, SRT4=4, 50%,

Istanbul
SBC 01
GMSC TT 01 SBC 03 TT
SBC 02
Ankara
SBC 04
TT 02 SBC 06
SBC 05
WHY not use the dual-homing function in SBC?
Because when SBC detect the master TT softswitch is not reachable it will swap to the slave TT softswitch
without releasing the call. So, if the TT softswitch (actually is the TT SBC) does not support the dual-homing
then the call will be lost in the TT side, but not be released in AVEA side.

Contents

6. Others
SIP configuration on MSFTX3000
Set Min & Max local port Optional, MSC can automatically set it
(MOD SIPCFG)
Specify the local port of the BSG Optional, MSC can automatically set the BSG local port to
(SET SIPLP) realize load-sharing
Add SIP Office Direction

(ADD OFC)
Add MGW for the SIP OFC One SIP OFC can add 2 OFCMGW: MGW and CMN
(ADD OFCMGW)
Add sub-route for the SIP OFC

(ADD SRT)
Add route for the SIP OFC

(ADD RT)
Add route analysis Add prefix analysis

(ADD RTANA) (ADD RTANA)
 Signal bearer type: UDP, TCP or SCTP

Add SIP trunks  Support SIP-I
(ADD SIPTG)  ISUP version
 Heart-beat
Add SIP SCTP links Add SIP TCP links

(ADD SIPSCTPLNK) (ADD SIPSCTPLNK)
END

Contents

6. Others
SE2600 Function– Proxy
 Proxy ：
 Softswitch A configures IP1 of SBC as the peer interworking address;
Softswitch B configures IP2 of SBC as the peer interworking address.
 I-SBC acts as B2BUA and forwards the packets to Softswitch based on the
map group.
SBC forwards message to Softswitch A:

IP2->IP1->Softswitch A IP
SBC forwards message to Softswitch B:
Softswitch A IP1->IP2->Softswitch B IP
Softswitch B
Core Network B
Core Network A IP bearer IP bearer
SE2600
IP1- Connect to Core Network A IP2- Connect to Core Network B

I-SBC Basic Data Configuration
There are five steps in the basic configuration:
Define the physical interface in LPU board and the

Configure interface Logic interface in SPU board
Set the IP address and route for

Configure IP core network side A and side B.
address and route
Set the operating mode of the SBC, including the
signaling dispatching unit, service processing unit,
Configure and protocols supported by the SBC in this
Functional entities
application scenario.
Create a mapping group aims to bind the

signaling address mapping and the media
Configure Interworking
Gateway mapping group stream address mapping.
I-SBC need two groups at least.
Configure Set the Well-known Ports between the SBC
Well-known Ports and Softswitch

I-SBC Basic Data Configuration Step 1
 Configuration Commands list:
 Configure the interface
Command Function View

Physical interface configuration
interface { ethernet | Configure ethernet interface System view
gigabitethernet } interface-number
interface eth-trunk trunk-id Configure the trunk System view
[.subnumber ]
workmode { backup | loadbalance } Configure the work mode for the trunk Eth-trunk interface
eth-trunk trunk-id Set the physical belong to a certain Ethernet interface

trunk
Logical interface configuration
interface { Signal-if | Media-if | set the logical interface for signaling and System view
Combined-if } slot-id/cpu-id/vcpu-id the media

Interface Data Configuration of the SPU
 Logical interface
 The logical interfaces are provided by the
SPU. Two types of interfaces are available: SBC
signal-if and media-if, which are used to LPU LPU SPU SPU SPU SPU
Processing unit 0 Processing unit 1

Processing unit0 Processing unit 1
forward signaling packets and media signal-if 5/0/1
packets respectively.
media-if 5/0/1
 Each SPU has 2 processing units, for
example, 3/0 and 3/1.
 Every processing unit support a
maximum of 96 logical interface.
 Every processing unit support a
maximum of 64 signaling interfaces, for
example, Signal-if3/0/41.
 Every processing unit supports a
maximum of 32 media interfaces, for 1 2 3 4 5 6
example, Meida-if3/0/0.
 Different PLMN/PSTN need to use
different Signal-if and Media-if
 Note: Logical interfaces need to be
configured in slots 3, 5, and 7 only,
A processing unit is a multi-core processor, each

SPU has 2 processing units, and the entire system
contains a maximum of 12 processing units.

 Configure the IP address and IP route ( static )

IP address configuration
ip address ip-address { mask | Configure IP address interface view
mask-length } [ sub ]
IP route configuration
interface { Signal-if | Media-if | set the logical interface for signaling System view
Combined-if } slot-id/cpu-id/vcpu- and the media
id

IP Address Plan
 SPU IP Address Plan example

The interface connect to The interface connect to
core network A core network B
Signal-if 1 or more 1 or more
Media-if 2 per SPU 2 per SPU
 Use 1 or more IP address depends on customer’s requirement. For

example, SCTP need 2 but UDP need only 1. Both of the two sides signal-
if IP need configured to dispatch unit.
 The 2 media IP addresses should be configured in the different process
unit.

IP Address Plan Example
The The The

The signal to The media The signal Manage
Slot interface interface media to
core network to core to core ment
No. to core to core core
A network A network B address
network A network B network B
192.1.1.2
202.1.1.21 1
3,4 202.1.1.20 192.1.1.20
202.1.1.22 192.1.1.2
Signal-if 2
Signal-if and
and 192.1.1.2
The signal media-If The signal
media-If 202.1.1.23 address of 3
5,6 address of only lie on
only lie on I-SBC must 202.1.1.24 SPU I-SBC 192.1.1.2
SPU be set in the must be 4
board set in the
board signal signal
interface of interface of 192.1.1.2
dispatch 202.1.1.25 dispatch 5
processing processing
7,8 unit 202.1.1.26 192.1.1.2
unit
6

 Configure the Functional Entity

sbc function-entity function- create a function-entity and System view
entity-index enter the function-entity view
mode intercom-ip set the operating mode of the Functional entity
functional entity to intercom-ip view
sbc sip enable enable the SE2600 to process Functional entity
SIP packets view
include dispatch process-unit configure the signaling Functional entity
slot-id/cpu-id dispatching unit for the view
functional entity
include { process-unit configure the service Functional entity
slot-id/cpu-id | all } processing unit for the view
functional entity
• All PSTN/PLMN connections can share the same functional entity.

•
• In AVEA network, one SBC just one functional entity is enough.

 Function Entity could be considered as a virtual SBC
 Two working mode for function entity:
 proxy (A-SBC),
 intercom-ip (I-SBC)
 Configuration e.g.:
sbc function-entity 2 // configure function entity 2
mode intercom-ip // the working mode is I-SBC
sbc sip enable // enable SIP function
include dispatch process-unit 3/0 // set 3/0 as dispatch processing unit for function
entity2
include process-unit 3/1 // set processing units 3/1 belong to function entity 2
• There are 6 function entities in maximum in whole system ；

• Each function entity has one or more processing units, a processing unit can not
belong to different entities.
• Each function entity need to have one and only one dispatch processing unit

 Configure the Interworking Gateway Mapping Group

sbc mapgroup intercom-ip index create a intercom-ip System view
mapping group
clientaddr （ same A-SBC ） configure the client address IP-route
of the signaling mapping interworking
gateway mapping
group view
serveraddr （ same A-SBC ） configure the server address IP-route
of the signaling mapping interworking
gateway mapping
group view
softxaddr （ same A-SBC ） configure the Softswitch IP-route
address of the signaling interworking
mapping. gateway mapping
group view
media-clientaddr （ same A- configure the client address IP-route
SBC ） of the media mapping interworking
gateway mapping
group view
media-serveraddr （ same A- configure the server IP-route
SBC ） address of the media interworking
mapping gateway mapping
group view
match source [resource-index ] IP-route
{ ipv4-address | begin ipv4- permit the users who match interworking
address end ipv4-address | ipv6- a mapping group according gateway mapping
address | begin ipv6-address end to source addresses. group view
ipv6-address }
enable enable a interworking IP-route
gateway mapping group interworking
gateway mapping
group view

Interworking Gateway Mapping Group
 When SE2600 works as I-SBC (interworking gateway mode), it must

configure the interworking gateway mapping group:
 For Core network A, SE2600 is the device of Core network B.
 For Core network B, SE2600 is the device of Core network A.
 Creating a mapping group aims to bind the signaling address mapping and
the media stream address mapping
Mapping for signaling proxy, which records Softswitch B

the mapping relationship of addresses in SBC
IP header ( for signaling route )
B2BUA
and SDP (for media route )
Softswitch A
signaling port
media port
Mapping for media proxy, which records the
mapping relationship of addresses in IP header
( for media route ) according to SDP

Rules for Interworking Gateway Mapping Group
Configuration
 5 IP addresses
 Signal-if Set in dispatch Set in dispatch
 Client Processing unit Processing unit
 Server
 Media-if
 Client Bearer Net
 Server Softxaddr A
Softxaddr B
 Softxadd :
Softswitch IP
Set in service Set in service
processing unit processing unit

Interworking Gateway Group Configuration
Set in dispatch Set in dispatch

Processing unit Processing unit SoftxaddrASoftxaddrB ：
sbc mapgroup intercom-ip 3010
IP1 IP2
clientaddr IP1
Bearer Net serveraddr IP2
202.1.1.2 IP3 192.1.1.2
SoftxaddrA IP4 SoftxaddrB media-clientaddr IP3
media-serveraddr IP4
Set in service Set in service
processing unit processing unit softxaddr 192.1.1.2
match source 202.1.1.2
Enable
SoftxaddrA address ： SoftxaddrBSoftxaddrA ：
202.1.1.2 sbc mapgroup intercom-ip 3020
SoftxaddrB address ： clientaddr IP2
192.1.1.2 serveraddr IP1
media-clientaddr IP4
SoftxaddrA side signaling address: IP1 media-serveraddr IP3
SoftxaddrB side signaling address: IP2 softxaddr 202.1.1.2
SoftxaddrA side media address: IP3 match source 192.1.1.2
enable
SoftxaddrB side media address: IP4


 configure the SIP well-known port
 As the interworking gateway, the SE2600 must configure the well-know port.
Otherwise, SE2600 can not communicate with the Softswitch.

sbc wellknownport clientaddr
[ vpn-instance vpn-instance-index
] ipv4-address { ras | sip } port configure the SIP well- System view
sbc wellknownport clientaddr ipv6- known port of the SE2600.
address sip port

Networking Example
Core Network A
A->B signal Interworking IP

B->A signal address: 200.1.1.2
A->B media
B->A media
IP address: 200.1.1.12
Eth-interface 1/0/7
SE2600
A->B media
B->A media
IP address: 192.1.1.12
L L S S S S Eth-interface 1/0/1
P P P P R R Interworking IP
U U U U address: 192.1.1.2
U U
1 2 3 4 9 10
Core Network B

Data Plan in Example
 IP addresses and the boards
The The
The The The
The signal signal to media to Manage
Slot interface to media to interface
to core core core ment
No. core core to core
network A network network address
network A network A network B
B B
Interface IP only lie on Interface IP only lie
1,2 192.1.1.12 200.1.1.12
LPU on LPU
Signal-if
Signal-if and 192.1.1.2 and 200.1.1.2
media-If 1 media-If 200.1.1.2 1
3,4 192.1.1.20
only lie on 192.1.1.2 only lie on 0 200.1.1.2
SPU board 2 SPU 2
board

Configuration in Example
 Configuration interface and IP address
interface GigabitEthernet1/0/1 // physical interface
undo shutdown // enable the port
ip address 192.1.1.12 255.255.255.0 // for downlink interface
interface GigabitEthernet1/0/7
undo shutdown // enable the port
ip address 200.1.1.12 255.255.255.0 // for uplink interface
interface Signal-if3/0/0 // logical interface

ip address 192.1.1.20 255.255.255.255 // for signal-if , in processing unit 0
interface Signal-if3/0/1
ip address 200.1.1.20 255.255.255.255 // for signal-if, in processing unit 0
interface Media-if 3/0/0

ip address 192.1.1.21 255.255.255.255 // for media-if, in processing unit 0
ip address 192.1.1.22 255.255.255.255 //for media-if , in processing unit 1

 Configure function entity
sbc function-entity 1
mode intercom-ip // SE2600 work as I-SBC
include dispatch process-unit 3/0 // set processing unit 3/0 as dispatch processing
unit
include process-unit 3/1 // put processing unit 3/1 into function entity 1 as a service
processing unit
include process-unit 3/0 // put processing unit 3/0 into function entity 1 as a service
processing unit NOTE: dispatch unit can act as process unit.
sbc sip enable
 Configure IP-Route Interworking Gateway Mapping Group

sbc mapgroup intercom-ip 3010 // define an interworking gateway mapping
group
clientaddr 192.1.1.20 // set the client address for signaling mapping.
serveraddr 200.1.1.20 // set the server address for signaling mapping.
media-clientaddr 5 192.1.1.21 // set the client address for media mapping.
media-clientaddr 10 192.1.1.22
media-serveraddr 5 200.1.1.21 // set the server address for media mapping.
media-serveraddr 10 200.1.1.22
softxaddr 5 200.1.1.2 // set the IP address of Softswitch A
match source 192.168.1. 2 // set the source addresses be permitted.
enable // enable IP-Route Interworking Gateway

 Configure IP-Route Interworking Gateway Mapping Group
sbc mapgroup intercom-ip 3020 // define an interworking gateway
mapping group
clientaddr 200.1.1.20 // set the client address for signaling mapping.
serveraddr 192.1.1.20 // set the server address for signaling mapping.
media-clientaddr 5 200.1.1.21 // set the client address for media
mapping.
media-clientaddr 10 200.1.1.22
media-serveraddr 5 192.1.1.21 // set the server address for media
mapping.
media-serveraddr 10 192.1.1.22
softxaddr 5 192.1.1.2 // set the IP address of Softswitch B
match source 200.1.1. 2 // set the source addresses be permitted.
enable // enable IP-Route Interworking Gateway

 Configure well know port
 sbc wellknownport clientaddr 192.1.1.20 sip 5060
 sbc wellknownport clientaddr 200.1.1.20 sip 5060
 sbc wellknownport softxaddr 192.1.1. 2 sip 5060

 sbc wellknownport softxaddr 200.1.1. 2 sip 5060

SIP Interworking Configuration
 Function description
 The SE2600 supports conversion between SIP over SCTP and SIP over UDP packets.
 At present, the SIP over SCTP function supports 60 CAPS for every pair of SPUs.
Therefore, user traffic volume must be determined to evaluate whether the SE2600
performance meets requirements.
 Configuration preparation
 The function entity for the SIP over SCTP function must use one processing unit both
as a dispatch unit and service unit, and no more processing unit can be configured.
 The relevant license must have been obtained.

SIP Interworking Configuration
[Platform] sbc function-entity 1

[Platform-function-entity-1] sbc sctp enable
[Platform-function-entity-1] sbc sctp-link 1
[Platform--function-entity-1-sctp-link-1] description link_to_core1
[Platform- function-entity-1-sctp-link-1] mode client
[Platform- function-entity-1-sctp-link-1] local-addr 190.17.156.11 190.17.156.12
[Platform- function-entity-1-sctp-link-1] remote-addr 190.17.155.11 190.17.155.12
[Platform- function-entity-1-sctp-link-1] local-port 6666
[Platform- function-entity-1-sctp-link-1] remote-port 5060
[Platform- function-entity-1-sctp-link-1] enable
The mapping group configurations do not change.

Contents

6. Others
Routine maintenance -- SBC
1. display sbc detect status.
Item Description
function-entity:2: Index of a functional entity
Softswitch: IP address of the detected Softswitch
VPN: Index of the VPN instance to which the detected Softswitch belongs
FC: Number of consecutive detection failures
SC: Number of consecutive detection successes
DS: Detection status: Up and Down (Up indicates that the detected Softswitch is normal and Down indicates that the detected
Softswitch is faulty.)
SD: Whether to shut down the Softswitch forcibly (Y indicates that the Softswitch is to be shut down forcibly and N indicates
that the Softswitch is not to be shut down forcibly.)
Status: Combined status of DS and SD (If DS or SD is Down, Status is Down; if both DS and SD are Up, Status is Up.)
2. display sbc dual-homing status.

Contents

6. Others
Others – PBN signaling network layout of SBC
Signaling network layout
PE1 PE2
Trunk + LACP + Static route
Internal LPU
Trunk +LACP + Static route
External LPU
Active Active
Active Active
SBC
LPU1 LPU2
 Only LPU has physical connection with Router

 LPU is like internal router of SBC
 The LPU of signaling interface work at active/active mode
 Router should support LACP + Static route

At the beginning of the project we designed the SIP use UDP, so the Signaling LPU is active/standby mode,
now we will use load-sharing mode so that the IP plan need changes too.
GE optical fiber,
LPU Internal 10.19.96.33
1-1-0 LPU /Slot 0 Single-mode 17750-1
Signaling 10.19.96.36 (.34 and .35 for 255.255.255.248(/29)
Active / Standby VRRP)
GE optical fiber,
SPU Internal 10.19.96.66
Signaling ~ 10.19.96.65 255.255.255.224(/27) No physic connection
SBC1 Active / Standby 10.19.96.94
LPU External 10.19.96.193 GE optical fiber,

Signaling 10.19.96.196 (.194 and .195 for 255.255.255.248(/29) 1-1-1 LPU /Slot 0 Single-mode 17750-1
Active / Standby VRRP) GE optical fiber,
SPU External 10.19.96.210
Signaling 10.19.96.213 (.211 and .212 for 255.255.255.248(/29) No physic connection
Active / Standby VRRP)
10.19.96.33 GE optical fiber, Single-

LPU Internal 10.19.96.34 255.255.255.252(/30) 1-1-0 LPU /Slot 0 mode 17750-1
Signaling:
Load-sharing
10.19.96.37 GE optical fiber, Single-
10.19.96.38 255.255.255.252(/30) 2-1-0 LPU /Slot 1 mode 17750-2
10.19.96.66
SPU Internal
~ 10.19.96.65 255.255.255.224(/27) No physic connection
Signaling
SBC1 10.19.96.94
LPU External 10.19.96.194 10.19.96.193 255.255.255.252(/30) GE optical fiber, Single-

Signaling: 1-1-1 LPU /Slot 0 mode 17750-1
Load-sharing 10.19.96.198 10.19.96.197 255.255.255.252(/30) GE optical fiber, Single-
2-1-1 LPU /Slot 1 mode 17750-2
10.19.96.210
SPU External
10.19.96.213 (.211 and .212 for 255.255.255.248(/29) No physic connection
Signaling
VRRP)

SCTP
Active SPU2 Standby
IP1-1 IP1-2 SPU1
LPU1 Active LPU2 Active
Active Active
PE1 PE2
IP2-1 IP2-2
GMSC

UDP
IP1-1 SPU1 Active SPU2 Standby
LPU1 Active LPU2 Active
Active Route Backup Route
Active Active
PE1 PE2
IP2-1
PLMN

Others – PBN media network layout of SBC
media network layout
PE3 PE4
VRRP + ARP + Static route
Internal LPU
VRRP + ARP + Static route
External LPU
Active Active Standby

Standby
SBC
LPU1 LPU2

Others – PBN Media network layout of SBC
Media network layout
LPU1 Active LPU2 Standby
Active
Standby
VRRP
PE3 PE4
IP4-1
PSTN
There is no perfect BFD solution for active/standby network layout

But SBC support ‘media detect’ function which can release the call if there is no media stream
been detected for a while. The range of

Others – PBN Media network layout of SBC
Media network layout
LPU1 Active LPU2 Standby
Active
Standby
VRRP
PE3 PE4
IP4-1
PSTN
 There is no perfect BFD solution for this active/standby network layout.

 But SBC can support ‘media detect’ function. It can release the call if there is no media
stream been detected for a while. The detection period range is 20 ~ 3600 seconds.

Thank you
www.huawei.com
Copyright©2011 Huawei Technologies Co., Ltd. All Rights Reserved.

The information contained in this document is for reference purpose only, and is subject to
change or withdrawal according to specific customer requirements and conditions.

07 - MSOFTX3000 SBC SIP Introduce - 201306 V2 1

Uploaded by

Document Information

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

07 - MSOFTX3000 SBC SIP Introduce - 201306 V2 1

Uploaded by

Copyright:

Available Formats

MSOFTX3000 & SBC

SIP Configuration Introducution

201306 Turkey AVEA

HUAWEI TECHNOLOGIES CO., LTD.

1. Network layout for SIP Overview

 SIP is over SCTP inner AVEA network

 SIP is over UDP for interconnecting with PLMN/PSTN

 Both of GMSC and SBC can support SIP-I.

 SBC can translate SIP/SCTP to SIP/UDP

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

1. Network layout for SIP Overview

VMSC SIP3 Load- SBC 01 Load- SIP1

 Same for GMSC, 2 SIP trunks at load-sharing mode

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

 AVEA SBC can take the TT SBC as the softswitch

 We suggest the route is:

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

WHY not use the dual-homing function in SBC?

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

1. Network layout for SIP Overview

Add SIP Office Direction

Add sub-route for the SIP OFC

Add route for the SIP OFC

Add route analysis Add prefix analysis

 Signal bearer type: UDP, TCP or SCTP

Add SIP SCTP links Add SIP TCP links

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

1. Network layout for SIP Overview

SBC forwards message to Softswitch A:

IP1- Connect to Core Network A IP2- Connect to Core Network B

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

Define the physical interface in LPU board and the

Set the IP address and route for

Create a mapping group aims to bind the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

Command Function View

eth-trunk trunk-id Set the physical belong to a certain Ethernet interface

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

Processing unit 0 Processing unit 1

A processing unit is a multi-core processor, each

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

Command Function View

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

 SPU IP Address Plan example

Signal-if 1 or more 1 or more

Media-if 2 per SPU 2 per SPU

 Use 1 or more IP address depends on customer’s requirement. For

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

The The The

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

Command Function View

• All PSTN/PLMN connections can share the same functional entity.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

• There are 6 function entities in maximum in whole system ；

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

Command Function View

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

 When SE2600 works as I-SBC (interworking gateway mode), it must

Mapping for signaling proxy, which records Softswitch B

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

Set in dispatch Set in dispatch

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23