Skip to main content

SS7 — Signalling Stack (STP / HLR / IP-SM-GW / CAMEL-GW)

The SS7 stack (OmniSS7) terminates SIGTRAN transport — SCTP associations carrying M3UA — and routes SS7/MAP traffic across the signalling network. A single service provides the whole stack, and OmniWeb presents it as four element views for its different roles: STP (Signalling Transfer Point, the SS7 router), HLR (Home Location Register), IP-SM-GW (IP Short Message Gateway) and CAMEL-GW (CAMEL Gateway). All four are backed by the same shared client, so the SIGTRAN transport and routing they share is the same underlying stack seen from different angles.

← Operations Guide

Each view is a per‑instance element page reached from the sidebar when an SS7 stack runs in the site's inventory. All traffic goes through the OmniWeb backend proxy to the stack's API, so it stays behind the single authenticated gateway; responses come back in a {status, response} envelope. The documentation link in each element page header (the in‑context help button) opens this page. Each view is organised into tabs. Message rates and other time‑series are presented as Grafana dashboards reached from the element page — OmniWeb does not duplicate those charts natively.

The stack at a glance​

The SIGTRAN transport underneath every role is the same, so the Peers and SCTP Connections tabs appear in all four views and read the same data.

The STP peers tab showing M3UA peer status — ASP and association state, endpoints, routing context and uptime for each signalling peer

The Peers tab reports M3UA peer status (/api/m3ua-status): every M3UA/M2PA peer, with its ASP state, association state, local and remote endpoints, routing context, protocol and mode, and per‑peer uptime statistics. This is where you confirm each signalling neighbour's application‑server process is up and in service.

The STP SCTP connections tab listing each SCTP association with role, endpoints, stream counts, byte and message counters and last activity

The SCTP Connections tab lists the underlying transport (/api/sctp-connections): every SCTP association with its status, role, local and remote IP/port, inbound and outbound stream counts, bytes and messages sent and received, last activity, and any last error — plus aggregate totals across all connections. It is the layer to check when a peer shows down: whether the SCTP association itself is established.

STP — routing​

The STP view is the SS7 router. Alongside the shared transport tabs it carries the Routing tab, plus Network Map, Overview and an SS7 Events feed.

The STP routing tab showing point-code routes and global-title routes with their target peers and priorities

The Routing tab shows the full M3UA routing configuration (/api/routing): the configured peers, the point‑code (PC) routes and the global‑title (GT) routes.

  • Point‑code routes direct traffic to a destination point code (dest_pc) via a target peer, with a network indicator, point‑code mask and priority. Operators can add a PC route (POST /api/routing/pc-routes, giving the destination point code and target peer) and delete one (DELETE /api/routing/pc-routes/{dest_pc}-{peer_id}).
  • Global‑title routes match a GT prefix and forward to a target peer with a priority and optional SSN, translation‑type and nature‑of‑address details and a description. Operators can add a GT route (POST /api/routing/gt-routes, giving the prefix and target peer) and delete one (DELETE /api/routing/gt-routes/{prefix}:{peer_id}).

This is where you confirm, and adjust, how the STP forwards SS7 messages toward each destination.

HLR​

The HLR view surfaces the register's active subscribers and the link to the HLR back‑end, alongside the shared transport tabs, an Overview and an SS7 Client tab.

The HLR subscribers tab listing active subscribers with IMSI, VLR, serving MSC, registration time and duration

The Subscribers tab lists the active subscriber register (/api/subscribers): every subscriber who has sent an UpdateLocation and not yet a CancelLocation, each row showing IMSI, VLR, serving MSC, registration time and duration, with counts of unique VLRs and MSCs. An operator can clear all tracked active subscribers (DELETE /api/subscribers) to reset the register's view.

The HLR links tab showing connectivity to the configured HLR API — status, latency and version

The HLR Links tab checks connectivity to the configured HLR API (/api/hlr-links): the status (up, degraded or down), measured latency, reported version and the target host. It is the quickest way to confirm the stack can reach the HLR back‑end.

IP-SM-GW​

The IP-SM-GW view is the short‑message gateway. It carries the SMSc subscriber tracker and the link to the SMSc back‑end, alongside the shared transport tabs and an Overview.

The IP-SM-GW SMSc links tab showing connectivity to the configured SMSc API — status, latency and version

The SMSc Links tab checks connectivity to the configured SMSc API (/api/smsc-links): status (up, degraded or down), latency, reported version and target host — the SMS‑path equivalent of the HLR link check.

The IP-SM-GW SMSc subscribers tab listing tracked subscribers with MSISDN, IMSI, HLR/VLR GT, message counts and status

The SMSc Subscribers tab lists the subscribers tracked by the SMSc subscriber tracker (/api/smsc-subscribers): each with MSISDN, IMSI, HLR GT and VLR GT, messages sent and received, status and last update, plus active/failed and unique‑HLR counts. An operator can clear all tracked SMSc subscribers (DELETE /api/smsc-subscribers).

CAMEL-GW​

The CAMEL-GW view surfaces the CAMEL sessions the gateway is running, alongside the shared transport tabs and an Overview.

The CAMEL-GW sessions tab listing active CAMEL sessions with call state, CAP version, IMSI, calling/called numbers and duration

The CAMEL Sessions tab lists all active CAMEL sessions managed by the gateway (/api/camel-sessions): each session's state, CAP version, service key, IMSI, calling and called numbers, start time and duration, with counts of sessions initiated and answered. It is where you watch live CAMEL call handling in real time.

Status​

The Status endpoint (/api/status) reports the overall node health that the Overview tabs summarise: the node identity and role, whether the service is ok, its uptime, and a peer summary of how many signalling peers are active out of the total. This is the first read to confirm the stack is running and its peers are in service.

  • STP — the SS7 routing element (point‑code and global‑title routes).
  • HLR — the Home Location Register element (active subscriber register and HLR link).
  • IP-SM-GW — the IP Short Message Gateway element (SMSc subscribers and link).
  • CAMEL-GW — the CAMEL Gateway element (live CAMEL sessions).
  • The MSC/VLR raises the UpdateLocation and CAMEL signalling this stack routes and tracks.
  • The SMSc is the back‑end the IP-SM-GW's SMSc link and subscriber tracker resolve against.
  • ← Operations Guide
Last updated on