MTP2 State Machine: LSSU Signals and Link Alignment Sequence
MTP2 is the data-link layer of SS7. It provides reliable transfer of signaling units between directly connected signaling points, using flags, sequence numbers, acknowledgments, error detection, and retransmission control. Before user traffic can pass, both ends must agree that the signaling link is operational.
That agreement is managed by the MTP2 state machine. Link Status Signal Units, or LSSUs, carry the status information needed during startup, failure recovery, processor outages, and service transitions. Understanding their sequence is essential when troubleshooting an SS7 link that remains unavailable or repeatedly cycles through alignment.
The same principles apply when SS7 signaling is transported across IP networks. In legacy switch environments, M2UA adaptation can preserve MTP2-like service behavior while moving lower-layer transport responsibilities into SIGTRAN.
MTP2 Responsibilities At The Link Layer
MTP2 sits between the physical signaling channel and MTP3. It accepts signaling units from MTP3, formats them for transmission, and validates incoming units before delivering them upward. Its control mechanisms include forward and backward sequence numbers, backward and forward indicator bits, length indicators, and cyclic redundancy checks.
Three common signaling unit types are used. Message Signal Units carry MTP3 and higher-layer messages. Fill-In Signal Units maintain an active link when no user messages are waiting. Link Status Signal Units communicate local link conditions and alignment progress.
The state machine prevents MTP3 traffic from using a link before both endpoints have completed synchronization and proving. This protects the network from corrupted sequence information, mismatched configuration, and unstable physical or logical connections.
How The Alignment Sequence Begins
When a link is activated, MTP2 first verifies the local bearer and begins initial alignment. Each endpoint sends status information through LSSUs rather than ordinary signaling traffic. The receiving side examines these units to determine whether the remote endpoint is responding and whether the link can proceed to proving.
A normal alignment indication tells the far end that the local MTP2 process is ready to establish service. Emergency alignment is used when the link has a higher-priority recovery requirement, depending on the national or regional standard in use. The exact priority behavior can vary, but the purpose remains the same: coordinate both ends before entering service.
If either side detects a problem during this phase, it can report an out-of-service or processor-related condition. The link then remains unavailable, or returns to an earlier state, until the fault clears and alignment restarts.
LSSU Status Codes And Their Meaning
LSSU status fields are short but operationally significant. Names and bit assignments differ between ITU-T, ANSI, and vendor implementations, so engineers should always compare observed values with the applicable specification. The following descriptions reflect common SS7 terminology.
| LSSU indication | Typical meaning | State-machine effect |
|---|---|---|
| SIN | Normal alignment | Indicates routine alignment activity |
| SIE | Emergency alignment | Requests or reports priority alignment |
| SIO or SIOS | Out of service | Prevents normal signaling traffic |
| SIPO | Processor outage | Reports inability of a signaling processor to operate normally |
| SIB | Busy | Indicates that the link or receiving function cannot accept normal service |
LSSUs are not substitutes for MTP3 user messages. They are local link-management signals, usually exchanged during alignment or abnormal conditions. A trace showing repeated SIO, SIPO, or SIB indications often points toward a physical-layer fault, a failed signaling processor, incompatible configuration, or a state-machine timer expiring.
The interpretation of an LSSU must include direction and timing. A status unit sent by the local endpoint may describe its own condition, while a received status unit describes the remote endpoint’s view. Correlating both directions is more useful than counting a single status code.
Proving The Link Before Service
Alignment is followed by proving, a controlled test period designed to confirm stable transmission. During proving, the endpoints exchange signaling units and monitor errors, acknowledgments, sequence behavior, and link timing. The objective is to demonstrate that the path can carry traffic reliably rather than merely respond to a startup message.
Error monitoring is central to this stage. Excessive bit errors, invalid signal units, lost acknowledgments, or repeated retransmissions can prevent the link from reaching the in-service condition. Depending on the implementation, the link may return to alignment, enter an unavailable state, or declare a processor outage.
Timers govern how long the state machine waits for expected events. Alignment, proving, acknowledgment, and recovery timers may have different names across standards and vendors. A timer expiry should therefore be read as evidence that an expected transition failed, not as proof of one specific physical defect.
Common Reasons Alignment Fails
A link can remain in alignment when the two ends disagree about signaling rate, coding, timeslot assignment, channel framing, or point-code configuration. On traditional TDM links, incorrect clocking and wiring are frequent causes. On IP-based signaling systems, SCTP association health, adaptation-layer mapping, and gateway configuration can produce similar symptoms.
Persistent LSSU exchanges may also result from incompatible protocol variants. Differences in status-code interpretation, proving parameters, emergency behavior, or timer values can stop otherwise reachable endpoints from becoming active. Vendor traces are particularly valuable because they reveal the internal state name associated with each transmitted or received LSSU.
A practical diagnostic process begins with the physical or transport bearer, then checks L2 traces, timer events, and MTP3 availability indications. Confirm the direction of each LSSU, identify the last successful state transition, and compare both endpoints’ configuration before changing timer values.
Reading The MTP2 State Machine In Practice
A simplified sequence is: unavailable, initial alignment, aligned, proving, and in service. Fault conditions can move the link backward from any operational stage. Processor outage, excessive errors, or loss of the bearer typically causes MTP2 to send an appropriate LSSU and notify MTP3 that the link cannot carry signaling traffic.
Use these recommendations when analyzing an alignment trace:
- Record the first LSSU exchanged after activation and the direction in which it travels.
- Match every status indication with timer starts, timer expiries, and state changes.
- Check whether both endpoints use the same national or international protocol variant.
- Separate transport failures from MTP2 configuration or proving failures.
- Verify recovery behavior after clearing a processor outage or bearer interruption.
A healthy link should progress predictably, stop sending alignment status once service is established, and carry MSUs with valid sequence and acknowledgment behavior. Unexpected returns to alignment usually indicate a recurring defect rather than a harmless restart.
Apply The Sequence To Network Operations
MTP2 alignment is a negotiation of readiness, reliability, and control. LSSUs provide the visible markers of that negotiation, while timers, error counters, and state transitions explain why a link advances or falls back. Engineers who understand the sequence can distinguish a blocked bearer from a protocol mismatch and avoid treating every unavailable indication as the same fault.
Use this model when reviewing SS7 or SIGTRAN traces, documenting operational procedures, or training teams responsible for signaling links. Apply the state transitions and LSSU meanings to a real capture, then validate each interpretation against the governing standard and equipment documentation.
