1 Introduction
This document is a guideline that provides an example of configuring the Signaling System #7 (SS7) stack layers for IPWorks AAA. The SS7 configuration in this document is based on:
IPWorks 2+2 deployment
2+2 deployment: 2 x SCs (SC-1 and SC-2) and 2 x PLs (PL-3 and PL-4) in the IPWorks system. The configuration example of AAA running on PL-3 and PL-4 is provided in this document.
The SS7 stack configuration is as the prerequisite for the following IPWorks AAA related functions/scenarios
- Wi-Fi Mobility Management (WiFi MM)
- Diameter over SCTP
- Secure Entitlement Server (SES) Support
- Wi-Fi AAA
1.1 Target Groups
This document is intended for the installation personnel.
1.2 Related Information
Trademark information, typographic conventions, and definition and explanation of abbreviations and terminology can be found in the following documents:
2 Prerequisites
This section describes the prerequisites required for the configuration.
2.1 Documents
Before using this document to perform the SS7 configuration, the users are required to read the following documents:
This document provides common SS7 configurations for IPWorks, for other SS7 configuration, you can refer to the following documents:
- Configuring SS7, SCTP
- Configuring SS7 Signaling Network, SCCP, M3
- Configuring SS7 Signaling Network, M3 IETF
- Configuring SS7 System Components
- Configuring SS7 TCAP
- Reconfiguring SS7 Network, Creating and Defining GT Routing
- Configuring SS7, INAP
- Configuring SS7, MAP
2.2 Users
The installation personnel are required to have prior knowledge about:
- Intermediate UNIX and Linux skills
- SS7 knowledge
2.3 Tool
The stack can be configured by using the GUI tool:
- Signaling Manager: It is a Java tool delivered with
the TE stack.
- Note:
- Ensure that the target host supports GUI mode.
2.4 Condition
Before configuring SS7, make sure that the following conditions are met:
- Ensure that the SS7 CAF is installed and running normally
on PL-3 and PL-4:
# cmw-status -v su | grep -i ss7 -A 4
safSu=SC-2,safSg=2N,safApp=ERIC-ss7caf.mgmt AdminState=UNLOCKED(1) OperState=ENABLED(1) PresenceState=INSTANTIATED(3) ReadinessState=IN-SERVICE(2) -- safSu=SC-1,safSg=2N,safApp=ERIC-ss7caf.mgmt AdminState=UNLOCKED(1) OperState=ENABLED(1) PresenceState=INSTANTIATED(3) ReadinessState=IN-SERVICE(2) -- safSu=PL-4,safSg=NWA,safApp=ERIC-ss7caf.core AdminState=UNLOCKED(1) OperState=ENABLED(1) PresenceState=INSTANTIATED(3) ReadinessState=IN-SERVICE(2) -- safSu=PL-4,safSg=2N,safApp=ERIC-ss7caf.netwcontrol AdminState=UNLOCKED(1) OperState=ENABLED(1) PresenceState=INSTANTIATED(3) ReadinessState=IN-SERVICE(2) -- safSu=PL-3,safSg=NWA,safApp=ERIC-ss7caf.core AdminState=UNLOCKED(1) OperState=ENABLED(1) PresenceState=INSTANTIATED(3) ReadinessState=IN-SERVICE(2) -- safSu=PL-3,safSg=2N,safApp=ERIC-ss7caf.netwcontrol AdminState=UNLOCKED(1) OperState=ENABLED(1) PresenceState=INSTANTIATED(3) ReadinessState=IN-SERVICE(2)For more information about how to check IPWorks software information, refer to View Software Information.
3 Preparation
This section provides the preparation procedures that need to be done before SS7 configuration.
3.1 Configuring Signaling Manager
To configure the tool Signaling Manager, do the following:
- Log on to the SC-1.
# ssh root@<MIP_OAM_IP>
- Find the path to PSO storage where SS7 configuration and
log files are stored:
# cat /usr/share/pso/storage-paths/config
# <path to config PSO storage>
# cat /usr/share/pso/storage-paths/no-backup
# <path to no-backup PSO storage>
- Create links to the path where SS7 configuration and log
files are stored.
# ln -s <path to config PSO storage>/ss7caf-ana90137/etc /opt/sign/etc
# ln -s <path to no-backup PSO storage>/ss7caf-ana90137/log /opt/sign/log
- Note:
- If the path /opt/sign/etc or /opt/sign/log already exists, remove it.
- Create the folder for template files.
mkdir –p /opt/sign/cnf_template
- On the SC-1, check whether PL-3 and PL-4 IP addresses
are correct in the file /etc/hosts.
# vi /etc/hosts
169.254.100.4 PL-4 169.254.100.3 PL-3
- Configure cp.manager.address in the Signaling Manager configuration file signmgr.cnf.
# vi /opt/sign/etc/signmgr.cnf
cp.manager.address=ss7cafcpmaddress:6669
Save the file and exit.
- Check if the Signaling Manager can be started on SC-1.
# /opt/sign/EABss7050/bin/signmgui -own.conf /opt/sign/etc/signmgr.cnf &
- Note:
-
- If the JAVA cannot be found, use the command export JAVA_HOME=/opt/sign/EABss7069/jre
- If no X11 DISPLAY variable was set, try to log out the
SC-1, and then log on again by using the -X option:
# ssh -X root@<MIP_OAM_IP>
3.2 Starting from Template Configuration File
The SS7 configuration template file contains the default configuration information for IPWorks AAA. Before the SS7 configuration, you need to start Signaling Manager from the template.
- Log on to SC-1.
# ssh root@<MIP_OAM_IP>
- Copy the SS7 template files.
# scp root@SC-1:/opt/ipworks/common/others/*.cim /opt/sign/cnf_template/
- Start the Signaling Manager on the SC-1 if it is not started
yet.
# /opt/sign/EABss7050/bin/signmgui -own.conf /opt/sign/etc/signmgr.cnf &
- After the main Signaling Manager window
pops up, select File > Open from
the menu bar, then select template. cim file
in the Template tab.
Select /opt/sign/cnf_template/SS7CAF_wifi_wifimm_ses_sctp.om.cim.
- Select Tools > Expert Mode and Tools > Configuration Mode > Initial.
- Note:
- Expert Mode enables all the properties to be visible in the Signaling Manger.
4 SS7 Network Plan
This section provides the SS7 network plan that is associated with the SS7 configuration for different IPWorks AAA functions.
The basic SS7 configuration is set in the SS7 configuration template file. To realize one or more IPWorks AAA related functions, you need to adapt the configuration to site-specific SS7 network. Meanwhile, according to actual requirement, you might also need to remove unused functions from the default configuration template. Both IPv4 and IPv6 are supported to work with CUDB.
For more information about the configurations, see Section 5 Procedure.
Table 1 and Table 2 list all configuration parameters values according to different AAA functions. These configurations will be applied in Section 5 Procedure.
- Note:
- The following parameter values are used as examples in this document. Except for the value of SSN for "Local" site type, other values might be changed according to customer's network plan.
|
Function |
Site Type |
SSN |
SPC |
SCTP Port |
SCTP IP |
|---|---|---|---|---|---|
|
Diameter over SCTP |
Local |
- |
- |
2905 2906 |
10.170.63.117 tnote-VIP_SS7_IP1 |
|
Wi-Fi AAA |
Local |
149 |
100 |
2905 2906 |
10.170.63.117(1) |
|
Remote |
6 |
200 |
2905 |
10.175.185.11(2) | |
|
Wi-Fi MM |
Local |
147 |
100 |
2905 2906 |
10.170.63.117 (1) |
|
Remote |
6 |
202 |
2905 |
10.175.161.190 (2) | |
|
SES |
Local |
7 |
100 |
2905 2906 |
10.170.63.117 (1) |
|
Remote |
6 |
203 |
2905 |
10.175.161.115 (2) |
(1) SS7 eVIP
traffic IP address <VIP_SS7_IP1>
For more information about these IP addresses, refer to the section Exported IP Addresses in IPWorks Network Connectivity Overview.
|
Function |
Translation Type (TT) |
Numbering Plan (NP) |
Nature of Address (NOA) |
Number Series (NS) |
Primary Termniation Indicator (PTI) |
Entityset (ES) |
|---|---|---|---|---|---|---|
|
Wi-Fi AAA |
Wildcard |
E.212 |
International number |
460* |
Change to "Route on SSN" |
RemoteSPC:200, SSN:6 |
|
Wi-Fi MM |
40 |
E.212 |
International number |
4343* |
Change to "Route on SSN" |
RemoteSPC:202, SSN:6 |
|
SES |
40 |
E.212 |
International number |
240* |
Change to "Route on SSN" |
RemoteSPC:203, SSN:6 |
5 Procedure
This section provides an example of configuring SS7 for AAA, including the following topics:
- Section 5.1 Removing SS7 Configuration of Wi-Fi AAA
- Section 5.2 Removing SS7 Configuration of Wi-Fi MM
- Section 5.3 Removing SS7 Configuration of SES
- Section 5.4 Removing SS7 Configuration for Diameter over SCTP Only Used
- Section 5.5 Configuring SS7 for Diameter over SCTP
- Section 5.6 Configuring SS7 for Wi-Fi AAA
- Section 5.7 Configuring SS7 for Wi-Fi MM
- Section 5.8 Configuring SS7 for SES
- Section 5.9 Validating and Restarting SS7 Stack
- Section 5.10 Verifying Stack Configuration
There's no dependence on the SS7 configurations for the IPWorks functions. The functions Wi-Fi AAA, Wi-Fi MMM, SES use the same SCTP instance.
Choose appropriate procedures to follow in order to satisfy actual requirement.
SS7 supports IPv6. If you want to enable IPv6, use IPv6 address in the follow configure process.
5.1 Removing SS7 Configuration of Wi-Fi AAA
When the Wi-Fi AAA function is not used, you can choose to remove the configuration from the default SS7 configuration template in Signaling Manager.
Remove the Wi-Fi AAA related parameters values according to the following table:
|
Operation Sequence |
Navigation Pane |
|---|---|
|
1 |
TCAP > TCAP > TCAP Subsystems > TCAP Subsystem:149 Network # 1 |
|
2 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > GT Translators > 4,*,6,4,460*--> Prim:RemoteSPC: 200, SSN: 6 |
|
3 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Entitysets > Prim:RemoteSPC: 200, SSN: 6 |
|
4 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Remote SAPs > RemoteSPC: 200, SSN: 6 |
|
5 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Local SAPs > LocalSPC: 100, SSN: 149 |
|
6 |
Sign Networks > Network #1 > Remote Sign Points > NetworkID: 1, RemoteSPC: 200 |
|
7 |
Sign Networks > Network #1 > SCCP SAPs > Network #1, SSN: 149 |
|
8 |
M3UA IETF > M3UA > Remote SPs > RemoteSP#1 Type:IPSP serves RemoteAS#40001 |
|
9 |
M3UA IETF > M3UA > Remote SPs > RemoteSP#2 Type:IPSP serves RemoteAS#40001 |
|
10 |
M3UA IETF > M3UA > Remote ASes > RemoteAS#40001 RC:0 |
|
11 |
M3UA IETF > M3UA > Local SPs > LocalSP#1 Type:IPSP serves LocalAS#1 |
|
12 |
M3UA IETF > M3UA > Local SPs > LocalSP#2 Type:IPSP serves LocalAS#1 |
|
13 |
M3UA IETF > M3UA > Local ASes > LocalAS#1 LocalSPC: 100 |
After all the values are removed, validate the configuration and then restart SS7 stack to make the configuration take effect, see Section 5.9 Validating and Restarting SS7 Stack.
5.2 Removing SS7 Configuration of Wi-Fi MM
When the Wi-Fi MM function is not used, you can choose to remove the configuration from the default SS7 configuration template in Signaling Manager.
Remove the Wi-Fi MM related parameters values according to the following table:
|
Operation Sequence |
Navigation Pane |
|---|---|
|
1 |
ETSI MAP > ETSIMAP > ETSIMAP Subsystems > ETSIMAP Subsystem: 147 |
|
2 |
TCAP > TCAP > TCAP Subsystems > TCAP Subsystem:147 Network # 1 |
|
3 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > GT Translators > 4,40,6,4,4343*--> Prim:RemoteSPC: 202, SSN: 6 |
|
4 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Entitysets > Prim:RemoteSPC: 202, SSN: 6 |
|
5 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Remote SAPs > RemoteSPC: 202, SSN: 6 |
|
6 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Local SAPs > LocalSPC: 100, SSN: 147 |
|
7 |
Sign Networks > Network #1 > Remote Sign Points > NetworkID: 1, RemoteSPC: 202 |
|
8 |
Sign Networks > Network #1 > SCCP SAPs > Network #1, SSN: 147 |
|
9 |
M3UA IETF > M3UA > Remote SPs > RemoteSP#5 Type:IPSP serves RemoteAS#40003 |
|
10 |
M3UA IETF > M3UA > Remote SPs > RemoteSP#6 Type:IPSP serves RemoteAS#40003 |
|
11 |
M3UA IETF > M3UA > Remote ASes > RemoteAS#40003 RC:0 |
|
12 |
M3UA IETF > M3UA > Local SPs > LocalSP#5 Type:IPSP serves LocalAS#3 |
|
13 |
M3UA IETF > M3UA > Local SPs > LocalSP#6 Type:IPSP serves LocalAS#3 |
|
14 |
M3UA IETF > M3UA > Local ASes > LocalAS#3 LocalSPC: 100 |
After all the parameters are removed, validate the configuration and then restart SS7 stack to make the configuration take effect, see Section 5.9 Validating and Restarting SS7 Stack.
5.3 Removing SS7 Configuration of SES
When the SES function is not used, you can choose to remove the configuration from the default SS7 configuration template in Signaling Manager.
Remove the SES related parameters values according to the following table:
|
Operation Sequence |
Navigation Pane |
|---|---|
|
1 |
ETSI MAP > ETSIMAP > ETSIMAP Subsystems > ETSIMAP Subsystem: 7 |
|
2 |
TCAP > TCAP > TCAP Subsystems > TCAP Subsystem:7 Network # 1 |
|
3 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > GT Translators > 4,40,6,4,240*--> Prim:RemoteSPC: 203, SSN: 6 |
|
4 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Entitysets > Prim:RemoteSPC: 203, SSN: 6 |
|
5 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Remote SAPs > RemoteSPC: 203, SSN: 6 |
|
6 |
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Local SAPs > LocalSPC: 100, SSN: 7 |
|
7 |
Sign Networks > Network #1 > Remote Sign Points > NetworkID: 1, RemoteSPC: 203 |
|
8 |
|
|
9 |
M3UA IETF > M3UA > Remote SPs > RemoteSP#7 Type:IPSP serves RemoteAS#40004 |
|
10 |
M3UA IETF > M3UA > Remote SPs > RemoteSP#8 Type:IPSP serves RemoteAS#40004 |
|
11 |
M3UA IETF > M3UA > Remote ASes > RemoteAS#40004 RC:0 |
|
12 |
M3UA IETF > M3UA > Local SPs > LocalSP#7 Type:IPSP serves LocalAS#4 |
|
13 |
M3UA IETF > M3UA > Local SPs > LocalSP#8 Type:IPSP serves LocalAS#4 |
|
14 |
M3UA IETF > M3UA > Local ASes > LocalAS#4 LocalSPC: 100 |
After all the parameters are removed, validate the configuration and then restart SS7 stack to make the configuration take effect, see Section 5.9 Validating and Restarting SS7 Stack.
5.4 Removing SS7 Configuration for Diameter over SCTP Only Used
In case that only the function Diameter over SCTP is used, you can choose to remove the parameters values according to the following table:
|
Operation Sequence |
Navigation Pane |
|---|---|
|
1 |
M3UA IETF > M3UA |
|
2 |
Sign Networks > Network # 1 |
|
3 |
TCAP > TCAP |
|
4 |
System Components > System Components >ECM > ECM > Services> Traffic > Processes > GEN RP |
|
5 |
System Components > System Components > OAM > OAM > Process Types > BE > Modules > MTPL3 |
|
6 |
System Components > System Components > OAM > OAM > Process Types > BE > Modules > SCCP |
|
7 |
System Components > System Components > OAM > OAM > Process Types > BE > Modules > TCAP |
|
8 |
System Components > System Components > OAM > OAM > Process Types > BE > Modules > ETSIMAP |
|
9 |
System Components > System Components > OAM > OAM > Process Types > NMP > Modules > MTPL3 |
|
10 |
System Components > System Components > OAM > OAM > Process Types > NMP > Modules > SCCP |
|
11 |
5.5 Configuring SS7 for Diameter over SCTP
Perform the following procedures to fulfill the example network that is described in Section 4 SS7 Network Plan.
- Note:
- When only the function Diameter over SCTP is used, it is necessary to perform the following procedures:
5.5.1 Configuring SCTP
Set the value of SCTP according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
SCTPs > SCTP FE > SCTP End Points > FE: IP Address Table #1 > Port Number |
Port |
2905 |
|
SCTPs > SCTP FE > SCTP End Points > FE: IP Address Table #1 > SCTP Local Address |
Address |
10.170.63.117 |
|
SCTPs > SCTP FE > SCTP End Points > FE: IP Address Table #2 > Port Number |
Port |
2906 |
|
SCTPs > SCTP FE > SCTP End Points > FE: IP Address Table #2 > SCTP Local Address |
Address |
10.170.63.117 |
5.5.2 Validating and Restarting SS7 Stack
After all the values are set, validate the configuration and then restart SS7 stack to make the configuration take effect, see Section 5.9 Validating and Restarting SS7 Stack.
5.6 Configuring SS7 for Wi-Fi AAA
Perform the following procedures to fulfill the example network that is described in Section 4 SS7 Network Plan.
- Note:
- When only the function Wi-Fi AAA is used, it is necessary to perform the following procedures:
5.6.1 Configuring Sign Networks
Set the value of Sign Networks according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
Sign Networks > Network #1 > Remote Sign Points |
Remote SPC |
200 |
|
Sign Networks > Network #1 > Local Sign Points |
Local SPC |
100 |
|
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Remote SAPs > RemoteSPC: 200, SSN: 6 |
Subsystem Number |
6 |
|
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > GT Translators > 4,*,6,4,460*--> Prim:RemoteSPC: 200 SSN: 6 |
Translation Type |
Wildcard |
|
Numbering Plan |
E.212 (Land mobile) | |
|
Nature of Address |
International number | |
|
Number Series |
460* | |
|
Primary Termination Indicator |
Change to 'Route On SSN'. | |
|
Entityset |
Prim:RemoteSPC: 200 SSN: 6 |
5.6.2 Configuring M3UA IETF
Set the value of the M3UA IETF according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#1 Type:IPSP serves RemoteAS#40001 |
Port |
2905 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#2 Type:IPSP serves RemoteAS#40001 |
Port |
2905 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#1 Type:IPSP serves RemoteAS#40001 > Remote SP Address |
Address |
10.175.185.11 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#2 Type:IPSP serves RemoteAS#40001 > Remote SP Address |
Address |
10.175.185.11 |
5.6.3 Configuring SCTP
Set the value of SCTP according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
Use All Local Addresses |
Yes | |
|
Port Number |
2905 | |
|
SCTPs > SCTP FE > SCTP End Points > FE: IP Address Table #1 > SCTP Local Address |
Address |
10.170.63.117 |
|
Port Number |
2906 | |
|
SCTPs > SCTP FE > SCTP End Points > FE: IP Address Table #2 > SCTP Local Address |
Address |
10.170.63.117 |
5.6.4 Validating and Restarting SS7 Stack
After all the values are set, validate the configuration and then restart SS7 stack to make the configuration take effect, see Section 5.9 Validating and Restarting SS7 Stack.
5.6.5 Verifying Stack Configuration
See Section 5.10 Verifying Stack Configuration.
5.7 Configuring SS7 for Wi-Fi MM
Perform the following procedures to fulfill the example network that is described in Section 4 SS7 Network Plan.
- Note:
- When only the function Wi-Fi MM is used, it is necessary to perform the following procedures:
5.7.1 Configuring ETSI MAP
Set the value of ETSI MAP according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
ML Timer |
600 |
5.7.2 Configuring Sign Networks
Set the value of Sign Networks according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
Sign Networks > Network #1 > Remote Sign Points |
Remote SPC |
202 |
|
Sign Networks > Network #1 > Local Sign Points |
Local SPC |
100 |
|
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Remote SAPs > RemoteSPC: 202, SSN: 6 |
Subsystem Number |
6 |
|
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > GT Translators > 4,40,6,4,4343*--> Prim:RemoteSPC: 202 SSN: 6 |
Translation Type |
40 |
|
Numbering Plan |
E.212 (Land mobile) | |
|
Nature of Address |
International number | |
|
Number Series |
4343* | |
|
Primary Termination Indicator |
Change to 'Route On SSN'. | |
|
Entityset |
Prim:RemoteSPC: 202 SSN: 6 |
5.7.3 Configuring M3UA IETF
Set the value of the M3UA IETF according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#5 Type:IPSP serves RemoteAS#40003 |
Port |
2905 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#6 Type:IPSP serves RemoteAS#40003 |
Port |
2905 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#5 Type:IPSP serves RemoteAS#40003 > Remote SP Address |
Address |
10.175.161.190 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#6 Type:IPSP serves RemoteAS#40003 > Remote SP Address |
Address |
10.175.161.190 |
5.7.4 Configuring SCTP
See Section 5.6.3 Configuring SCTP.
5.7.5 Validating and Restarting SS7 Stack
After all the values are set, validate the configuration and then restart SS7 stack to make the configuration take effect, see Section 5.9 Validating and Restarting SS7 Stack.
5.7.6 Verifying Stack Configuration
See Section 5.10 Verifying Stack Configuration.
5.8 Configuring SS7 for SES
Perform the following procedures to fulfill the example network that is described in Section 4 SS7 Network Plan.
- Note:
- When only the function SES is used, it is necessary to perform the following procedures:
5.8.1 Configuring ETSI MAP
Set the value of ETSI MAP according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
ML Timer |
600 |
5.8.2 Configuring Sign Networks
Set the value of Sign Networks according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
Sign Networks > Network #1 > Remote Sign Points |
Remote SPC |
203 |
|
Sign Networks > Network #1 > Local Sign Points |
Local SPC |
100 |
|
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > Remote SAPs > RemoteSPC: 203, SSN: 6 |
Subsystem Number |
6 |
|
Sign Networks > Network #1 > Local Sign Points > NodeID:0, LocalSPC: 100 > SCCP Sign Point > SCCP > GT Translators > 4,40,6,4,240*--> Prim:RemoteSPC: 203 SSN: 6 |
Translation Type |
40 |
|
Numbering Plan |
E.212 (Land mobile) | |
|
Nature of Address |
International number | |
|
Number Series |
240* | |
|
Primary Termination Indicator |
Change to 'Route On SSN'. | |
|
Entityset |
Prim:RemoteSPC: 203 SSN: 6 |
5.8.3 Configuring M3UA IETF
Set the value of the M3UA IETF according to the following table:
|
Navigation Pane |
Operation Pane Properties |
Value |
|---|---|---|
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#7 Type:IPSP serves RemoteAS#40004 |
Port |
2905 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#8 Type:IPSP serves RemoteAS#40004 |
Port |
2905 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#7 Type:IPSP serves RemoteAS#40004 > Remote SP Address |
Address |
10.175.161.115 |
|
M3UA IETF > M3UA > Remote SPs > RemoteSP#8 Type:IPSP serves RemoteAS#40004 > Remote SP Address |
Address |
10.175.161.115 |
5.8.4 Configuring SCTP
See Section 5.6.3 Configuring SCTP.
5.8.5 Validating and Restarting SS7 Stack
After all the values are set, validate the configuration and then restart SS7 stack to make the configuration take effect, see Section 5.9 Validating and Restarting SS7 Stack.
5.8.6 Verifying Stack Configuration
See Section 5.10 Verifying Stack Configuration.
5.9 Validating and Restarting SS7 Stack
- Note:
- To ensure that IPWorks can provide SS7 related services after SS7 is configured, it is recommended to do the validation and restart of SS7 Stack.
To validate and restart the SS7 stack, do the following:
- Validate the configuration by selecting Edit > Validate.
- If there are validation errors, click Results to view error description and go to the respective configuration.
- Select Tools > Process View... > Configure in the process view dialog box, and select Initial Configuration to make any update take effect.
- Restart SS7 Stack on SC-1.
amf-adm restart safSu=SC-1,safSg=2N,safApp=ERIC-ss7caf.mgmt
amf-adm restart safSu=SC-2,safSg=2N,safApp=ERIC-ss7caf.mgmt
amf-adm restart safSu=PL-3,safSg=2N,safApp=ERIC-ss7caf.netwcontrol
amf-adm restart safSu=PL-3,safSg=NWA,safApp=ERIC-ss7caf.core
amf-adm restart safSu=PL-4,safSg=2N,safApp=ERIC-ss7caf.netwcontrol
amf-adm restart safSu=PL-4,safSg=NWA,safApp=ERIC-ss7caf.core
- Select File > Connect and make sure that the status is Active in the status bar.
- Save the configuration file as another name by selecting File> Save As.
- Close the Signaling Manager.
5.10 Verifying Stack Configuration
Before verifying stack configuration, make sure that the values in Table 1 are configured correctly, and all stack processes in remote host are running.
To verify whether the stack configuration is correct, do the following:
- Note:
- Perform the steps on both the local and remote hosts.
- Start Signaling Manager.
# /opt/sign/EABss7050/bin/signmgui -own.conf /opt/sign/etc/signmgr.cnf &
- Send status by following the below table based on different
functions.
Function
Navigation Pane
Operation
Wi-Fi AAA
M3UA IETF > M3UA > Local ASes > LocalAs#1 LocalSPC:100
Click Actions > select M3IETF-Local AS Status > click Send
Wi-Fi MM
M3UA IETF > M3UA > Local ASes > LocalAs#3 LocalSPC:100
SES
M3UA IETF > M3UA > Local ASes > LocalAs#4 LocalSPC:100
Example:
- Send status by following the below table based on different
functions.
Function
Navigation Pane
Operation
Wi-Fi AAA
M3UA IETF > Remote SPs > RemoteSP#1 Type:IPSP servers RemoteAS#40001
Click Actions > select M3IETF-Status of RemoteASP/IPSP > click Send
Wi-Fi MM
M3UA IETF > Remote SPs > RemoteSP#5 Type:IPSP servers RemoteAS#40003
SES
M3UA IETF > Remote SPs > RemoteSP#7 Type:IPSP servers RemoteAS#40004
Example:
- Check if the selected process status is active in the Action Results tab in the information pane.
6 Post Activities
After configuring SS7 on the IPWorks node, configure the SS7/SCTP stack on the peer node and check if the two nodes can communicate.
7 Appendix A: Opening Trace Log
This section describes how to start and use the Trace Viewer Tool (TvTool).
- Note:
- If the users receive a message indicating that the Java command
is not found, set the environment variable for Java as follows.
# export JAVA_HOME=/opt/sign/EABss7069/jre
# export PATH=$JAVA_HOME/bin:$PATH
If the users log out and in the system, the above commands must be executed again.
- Start the Signaling Manager.
# /opt/sign/EABss7050/bin/signmgui \
-own.conf /opt/sign/etc/signmgr.cnf & - Open the Expert Mode and Initial Configuration Mode in Signaling Manager.
- Change the start command line for your interested module process as shown in the following figure by adding -t.
- Restart the stack to enable the modification.
- Copy EABss7049 from PL node
to SC node if it is not installed on SC node.
# scp -r root@PL-3:/opt/sign/EABss7049 /opt/sign
- The SS7 trace log directory is /opt/sign/log/ss7trace.log. Open the trace log:
# /opt/sign/EABss7049/bin/tvtool -f /opt/sign/log/ss7trace.log
- Let the program run in the background:
# /opt/sign/EABss7049/bin/tvtool -f /opt/sign/log/ss7trace.log &
8 Appendix B: Examples of Removing Instance
This section provides the example figures to show how the operation looks like in Signaling Manager.
Figure 4 Remove an SCCP Entityset Instance
Figure 7 Remove Local SP Instance
Figure 8 Remove a Remote SP Instance
Figure 9 Remove a Local AS Instance
Reference List
| Ericsson Documents |
|---|
| [1] Trademark Information. |
| [2] Typographic Conventions. |
| [3] Glossary of Terms and Acronyms. |
| [4] Signaling Manager User Guide. |
| [5] Configuring SS7, SCTP. |
| [6] Configuring SS7 Signaling Network, SCCP, M3. |
| [7] Configuring SS7 Signaling Network, M3 IETF. |
| [8] Configuring SS7 System Components. |
| [9] Configuring SS7 TCAP. |
| [10] Reconfiguring SS7 Network, Creating and Defining GT Routing. |
| [11] Configuring SS7, INAP. |
| [12] Configuring SS7, MAP. |
| [13] View Software Information. |
| [14] IPWorks Network Connectivity Overview. |

Contents



















