jSS7 Lab Dashboard

🏠Dashboard Overview

Selamat datang di jSS7 Lab Dashboard! Platform ini mensimulasikan jaringan SS7 (Signaling System 7) lengkap di environment lab terisolasi RFC 1918. Gunakan menu kiri untuk mengkonfigurasi komponen, menjalankan simulasi, dan memonitor traffic signaling.

0

Paket Ditangkap

↑ real-time

0

Pesan SS7

MAP+ISUP+CAP

0

MQTT Published

topics: ss7/mirror/#

0

ELK Indexed

index: ss7-*

⚡Status Layanan

📊Distribusi Protokol (Live)

🌐Network Info

Lab Subnet	10.0.0.0/24
SS7 Simulator	10.0.0.100:2905 (SCTP)
Mirror Gateway	10.0.0.200 (libpcap)
MQTT Broker	10.0.0.10:1883
Elasticsearch	10.0.0.50:9200
Kibana	10.0.0.50:5601
Logstash	10.0.0.50:5044

🚀Quick Actions

🗺️Network Topology – Lab RFC 1918

Arsitektur Fisik: Semua node berada di subnet 10.0.0.0/24. Traffic SS7 mengalir dari SS7 Simulator → Mirror Gateway (capture) → MQTT Broker → ELK Stack untuk analisis dan visualisasi.

SS7 Simulator

jSS7 Stack (STP/MSC/HLR simulasi), M3UA Port 2905, Java/Maven

Mirror Gateway

Python libpcap capture, normalisasi, publisher MQTT, 4 NIC

MQTT Broker

Mosquitto, port 1883 TCP & 9001 WS, persistence, QoS 0-2

ELK Stack

Logstash input MQTT, Elasticsearch index ss7-*, Kibana port 5601

⚙️Konfigurasi jSS7 Stack

jSS7 adalah implementasi open-source dari SS7 protocol stack berbasis Java. Di sini Anda dapat mengkonfigurasi titik-kode MTP3, parameter SCCP, routing label, dan perilaku simulasi. Konfigurasi disimpan di /etc/jss7/jss7.properties.

MTP3 / STP

SCCP

TCAP

M3UA / SIGTRAN

Routing

MTP3 – Message Transfer Part Level 3 (ITU-T Q.704)

MTP3 mengatur routing sinyal antar titik-kode (Point Code). OPC = Origin, DPC = Destination, NI = Network Indicator (national/international).

OPC – Originating Point Code

DPC 1 – Destination Point Code

DPC 2

Network Indicator (NI)

SI SCCP

SI ISUP

SI TUP

Preview jss7.properties

SCCP – Signaling Connection Control Part (ITU-T Q.713)

SCCP menambahkan kemampuan routing global title (GT) dan sub-system numbering (SSN) di atas MTP3. SSN 6=HLR, SSN 8=MSC/VLR, SSN 149=MAP.

Local SSN

Remote SSN

GT Indicator

Translation Type (TT)

Numbering Plan

Encoding Scheme

SCCP Global Title (Digits)

SCCP Message Types Reference

Hex	Nama	Mode
0x09	UDT – Unit Data	CL
0x12	XUDT – Extended Unit Data	CL
0x01	CR – Connection Request	CO
0x02	CC – Connection Confirm	CO
0x04	RLSD – Released	CO
0x06	DT1 – Data Form 1	CO
0x0A	UDTS – Unit Data Service	Error
0x10	ERR – Protocol Error	Err

TCAP – Transaction Capabilities Application Part (ITU-T Q.771)

TCAP mengelola dialog/transaksi antar aplikasi. Begin=buka dialog, Continue=lanjutkan, End=tutup normal, Abort=batalkan.

Dialog Timeout (ms)

Component Timeout (ms)

Max Dialog Count

Invoke Timeout (ms)

TCAP Package Type Default

TCAP Package Types

Begin (0x02)
Memulai dialog baru. Berisi Originating Transaction ID (OTID). Digunakan MAP sendAuthInfo, updateLocation, dll.

Continue (0x05)
Melanjutkan dialog. Berisi OTID + Destination TID (DTID). Biasa di pertengahan sequence.

End (0x04)
Menutup dialog dengan normal. Hanya berisi DTID. Response akhir.

Abort (0x07)
Menutup dialog dengan error (P-Abort atau U-Abort). Berisi reason code.

M3UA – MTP3 User Adaptation Layer (RFC 4666)

M3UA memungkinkan SS7 berjalan di atas IP/SCTP. Port standar adalah 2905. Komponen: AS (Application Server), ASP (AS Process), SGP (SG Process).

Server IP

Server Port (SCTP)

Routing Context (RC)

Traffic Mode

Heartbeat Interval (ms)

Max Retransmission

M3UA Message Flow

ASP (Client)

SGP (Server)

ASPUP ──────────────────────────────────────────────────▶

◀────────────────────────────── ASPUP ACK

ASPAC (RC=100) ──────────────────────────────────────▶

◀────────────────────── ASPAC ACK

DATA (MTP3 payload) ─────────────────────────────────▶

BEAT (heartbeat) ───────────────────────────────────▶

◀──────────────────── BEAT ACK

Routing Table – MTP3 Signaling Routes

Setiap entri routing mendefinisikan: DPC tujuan, link yang digunakan, dan prioritas. SLS (Signaling Link Selection) digunakan untuk load-sharing.

📨Konfigurasi MQTT Broker (Mosquitto)

MQTT (Message Queuing Telemetry Transport) adalah protokol lightweight pub/sub. SS7 Capture mengirim data ke topik ss7/mirror/#. Logstash subscribe ke topik ini untuk dimasukkan ke Elasticsearch.

Broker Settings

Bind IP

Port TCP

WebSocket Port

Max Connections

Max Queued Messages

Max QoS Level

Keepalive (detik)

Autosave Interval (detik)

Persistence Location

Allow Anonymous (non-produksi)

Topic Hierarchy SS7

ss7/
├── mirror/
│   ├── map/
│   │   ├── updatelocation
│   │   ├── sendauthenticationinfo
│   │   ├── insertsubscriberdata
│   │   └── cancellocation
│   ├── isup/
│   │   ├── iam
│   │   ├── acm
│   │   └── anm
│   ├── cap/
│   │   └── initialdp
│   └── sccp/

Test Publish MQTT

Topic

QoS

Payload (JSON)

🗃️Konfigurasi ELK Stack

ELK Stack terdiri dari Elasticsearch (indexing & search), Logstash (pipeline), dan Kibana (visualisasi). Data SS7 masuk melalui Logstash MQTT input → difilter → diindeks ke Elasticsearch → divisualisasi di Kibana.

Elasticsearch

Logstash Pipeline

Kibana

Elasticsearch Settings

Cluster Name

Node Name

Network Host

HTTP Port

JVM Heap Min (g)

JVM Heap Max (g)

Shards per Index

Replicas

Refresh Interval

Index Mapping SS7

Logstash Pipeline – ss7-mqtt.conf

input {
  mqtt {
    host       => "10.0.0.10"
    port       => 1883
    client_id  => "logstash-ss7"
    topics     => ["ss7/mirror/#"]
    qos        => 1
    clean_session => true
    codec      => json
  }
  tcp { port => 5000; codec => json_lines }
  udp { port => 5001; codec => json_lines }
}

filter {
  date {
    match  => ["timestamp", "ISO8601"]
    target => "@timestamp"
  }
  
  # Parse SS7 fields
  if [protocol] {
    grok { match => { "message" => ["%{WORD:protocol}/%{WORD:operation}"] } }
  }
  
  # IMSI → MCC untuk geo-mapping
  if [imsi] {
    mutate { add_field => { "[geo][mcc]" => "%{[imsi][0,3]}" } }
    translate {
      field       => "[geo][mcc]"
      destination => "[geo][country]"
      dictionary  => { "510" => "Indonesia" "460" => "China" "404" => "India" "262" => "Germany" "310" => "USA" }
      fallback    => "Unknown"
    }
  }
  
  # Anonymize MSISDN & IMSI (SHA256)
  if [msisdn] {
    fingerprint { source => "msisdn" target => "msisdn" method => "SHA256" key => "changeme_prod" }
  }
  if [imsi] {
    fingerprint { source => "imsi" target => "imsi" method => "SHA256" key => "changeme_prod" }
  }
  
  # Tagging
  if [protocol] == "MAP"  { mutate { add_tag => ["ss7","map","signaling"] } }
  if [protocol] == "CAP"  { mutate { add_tag => ["ss7","cap","camel"] } }
  if [protocol] == "ISUP" { mutate { add_tag => ["ss7","isup","voice"] } }
}

output {
  elasticsearch {
    hosts    => ["http://10.0.0.50:9200"]
    index    => "ss7-%{+YYYY.MM.dd}"
    template => "/etc/logstash/templates/ss7-template.json"
    template_name     => "ss7"
    template_overwrite => true
  }
  stdout { codec => rubydebug }
}

Kibana Settings

Server Host

Server Port

Elasticsearch URL

Index Pattern

Time Field

Recommended Kibana Visualizations

📊 Pie Chart – Distribusi protokol (MAP/ISUP/CAP/SCCP)
Aggregation: Terms pada field "protocol.keyword"

📈 Line Chart – Volume pesan per menit
Aggregation: Date Histogram pada "@timestamp", interval 1m

📋 Data Table – Top MAP Operations
Aggregation: Terms pada "data.operation_name"

🗺️ Map – Distribusi geografis IMSI berdasarkan MCC
Field: geo.country, metrik count

🌡️ Heat Map – Error distribution per jam per tipe
X: @timestamp interval 1h, Y: error_type.keyword

📍Simulasi MAP – Location Update Procedure

MAP UpdateLocation adalah prosedur ketika UE (handset) berpindah ke jaringan baru. MSC mengirim MAP UpdateLocation ke HLR, HLR membalas dengan InsertSubscriberData, kemudian HLR mengkonfirmasi. Semua proses diikuti oleh Mirror Gateway.

Referensi: 3GPP TS 29.002 Section 8.1.2 | ITU-T Q.771 (TCAP)

Parameter Simulasi

IMSI (15 digit)

MSISDN (E.164)

VLR Number

MSC Number

Location Area Code (LAC)

Cell ID

Jumlah Iterasi

Interval antar pesan (ms)

Status Simulasi

Siap untuk dijalankan.

Ladder Diagram – MAP Location Update

UE

MSC/VLR

STP

HLR

Mirror

Payload JSON yang Dihasilkan

📞Simulasi ISUP – Call Setup Flow

ISUP (ISDN User Part) menangani setup dan teardown panggilan telepon di jaringan SS7. Flow standar: IAM (setup) → ACM (ringing) → ANM (answer) → REL (release) → RLC (complete).

Referensi: ITU-T Q.763 | ITU-T Q.764

Parameter Panggilan

Calling Party Number (A)

Called Party Number (B)

Circuit Identification Code (CIC)

OPC → DPC

Nature of Address

Calling Category

ACM Delay (ms)

ANM Delay (ms)

REL Delay (ms)

Release Cause

Status

Siap.

Ladder Diagram – ISUP Call Setup

Switch A

STP

Switch B

Mirror

🔌Simulasi CAP – CAMEL Application Part

CAP (CAMEL Application Part) digunakan untuk layanan value-added seperti prepaid charging, roaming intelligent network, dan call forwarding cerdas. SCP (Service Control Point) mengontrol panggilan melalui SSF (Switch Service Function).

Referensi: 3GPP TS 29.078 | CAMEL Phase 3 & 4

Parameter CAP

IMSI

Service Key

Default Call Handling

Calling Party

Called Party

Event Type (DP)

CAMEL Phase

Siap.

Ladder Diagram – CAP InitialDP → Apply Charging

UE/SSF

STP

SCP

Mirror

📦Live Packet Monitor

Total: 0 paket

#	Waktu	Protokol	Operasi	Src	Dst	Size	Info

🔬Protocol Stack – SS7 over SIGTRAN

Protocol Stack (klik untuk detail)

Application Layer – MAP, CAP, INAP 3GPP TS 29.002/29.078

TCAP – Transaction Capabilities ITU-T Q.771-775

SCCP – Signaling Connection Control ITU-T Q.711-714

MTP3 – Message Transfer Part L3 ITU-T Q.704

M3UA – MTP3 User Adaptation RFC 4666

SCTP – Stream Control Transmission RFC 4960

IP – Internet Protocol RFC 791

Ethernet – Data Link Layer IEEE 802.3

Detail Protokol

Klik salah satu layer di kiri untuk melihat detail protokol

Capture Points – Di Mana Data Ditangkap?

🌐

Ethernet Frame

libpcap promiscuous mode, interface eth0

🔗

SCTP Reassembly

Fragment reassembly, checksum verification

📦

M3UA Extraction

Transfer msg class=1, type=1 (DATA)

🔍

SCCP/TCAP/MAP

ASN.1 BER decode, field extraction

📋System Logs

🔧Diagnostik & Troubleshooting

Jalankan Diagnostik

Common Issues & Solutions

Hasil Diagnostik