Tracing a Cross-Connected SS7 Call Across Two STPs

An SS7 call can appear simple at the subscriber level while producing a detailed signaling trail across several network elements. In this case study, an originating mobile switching center sends an ISUP call toward a terminating exchange through two signaling transfer points. The objective is to identify each message, verify routing decisions, and locate any delay or failure.

The example uses a traditional circuit-switched path. The voice bearer travels over a trunk circuit, while SS7 signaling uses separate signaling links. Each STP examines the MTP3 routing label, forwards the message toward its destination, and leaves the call state to the originating and terminating switches.

This separation is essential during troubleshooting. A successful IAM transfer does not prove that the called party answered, and an STP that forwards messages correctly may still be connected to an exchange with faulty ISUP timers, trunk configuration, or number analysis.

The Network Scenario

The originating exchange, MSC-A, owns point code 2-10-1. The destination exchange, MSC-B, uses point code 3-20-1. They are connected through two STPs: STP-East has point code 1-1-1, and STP-West has point code 1-2-1. The STPs form a signaling backbone between the two exchanges.

MSC-A selects a voice circuit with a circuit identification code, or CIC, of 417. It creates an Initial Address Message containing the called number, calling party information, bearer capability, and routing details. The MTP3 label identifies MSC-A as the originating point code and MSC-B as the destination point code.

In practical operations, “cross-connecting” this call means that signaling crosses both transfer points before reaching the remote switch. It does not mean that either STP terminates the call. The STPs route packets; MSC-A and MSC-B control the circuit and call state.

Reading the First Signaling Trace

The first packet captured on the MSC-A to STP-East link is the IAM. Its forward sequence number, backward sequence number, service indicator, and routing label confirm that the message belongs to the MTP3 signaling network. The SLS value helps select a signaling link while preserving message sequencing.

STP-East receives the IAM, checks the destination point code, and consults its MTP3 routing tables. It does not translate the ISUP called number in this example. Instead, it forwards the message across the linkset toward STP-West. A matching SLS value and closely aligned timestamps show that the message has been relayed rather than regenerated.

The IAM then appears on the STP-West to MSC-B link. At this point, the trace should preserve the CIC and core ISUP parameters. A changed destination point code would indicate an unexpected route, while a changed CIC could create a circuit mismatch between the two exchanges.

Following Call Progress Messages

After MSC-B receives the IAM and reserves the corresponding trunk circuit, it returns an Address Complete Message. The ACM indicates that routing has progressed and that additional address information may be required before alerting or answer. It travels backward from MSC-B through STP-West and STP-East to MSC-A.

The calling number and presentation indicators are especially useful when validating subscriber identity delivery. Parameter interpretation should be checked against a reliable reference on ISUP calling number parameters, since screening, presentation restriction, and numbering-plan fields can affect what the terminating network displays.

When the called party answers, MSC-B sends an Answer Message. The ANM follows the reverse signaling route, and the voice path becomes active on CIC 417. If the call is rejected or times out, the trace will instead show a Release message with a cause value, followed by a Release Complete response.

Comparing Each Network Hop

The trace below represents a healthy call. Small timing differences are expected because each STP receives, queues, and transmits the message independently. Large or inconsistent gaps suggest congestion, link errors, route changes, or an overloaded signaling process.

Event Direction Point-code path CIC Time from previous event Diagnostic meaning
IAM MSC-A to MSC-B 2-10-1 → 1-1-1 → 1-2-1 → 3-20-1 417 — Call setup begins
ACM MSC-B to MSC-A 3-20-1 → 1-2-1 → 1-1-1 → 2-10-1 417 180 ms Destination has accepted routing
ANM MSC-B to MSC-A 3-20-1 → 1-2-1 → 1-1-1 → 2-10-1 417 2.4 s Called party answered
REL MSC-A to MSC-B 2-10-1 → 1-1-1 → 1-2-1 → 3-20-1 417 94 s Originating side released call
RLC MSC-B to MSC-A 3-20-1 → 1-2-1 → 1-1-1 → 2-10-1 417 35 ms Circuit is cleared

A useful comparison is the message timing at each capture point. If the IAM reaches STP-East immediately but remains there for several hundred milliseconds, investigate the local linkset, MTP3 congestion controls, and route availability. If it moves rapidly through both STPs but no ACM returns, the likely fault is closer to MSC-B, its trunk group, or its ISUP analysis.

Locating Faults From Missing Messages

A missing IAM on the STP-East to STP-West link points toward the first STP, its outgoing linkset, or an MTP3 routing problem. Check whether the destination point code is available, whether the route is prohibited, and whether the signaling link is in service. Link status alone is insufficient; a link can remain physically active while traffic is discarded by routing controls.

If the IAM reaches MSC-B but no ACM follows, inspect the terminating switch. Common causes include an invalid called-number format, an unavailable CIC, a blocked trunk, or an ISUP timer expiring before route completion. Cause values in REL messages can distinguish congestion, no circuit available, unallocated number, and temporary failure.

When the ACM appears but ANM does not, the network has progressed beyond basic routing. The terminating subscriber may not answer, alerting may be misconfigured, or a subsequent message may be delayed. Comparing T7 and other ISUP timers with observed timestamps helps separate normal ringing from a signaling failure.

Practical Trace Discipline

A reliable investigation correlates packet captures from all four interfaces: MSC-A to STP-East, STP-East to STP-West, STP-West to MSC-B, and the reverse direction. Filtering only by point code can mix unrelated calls, so combine the CIC, message type, OPC, DPC, and time window.

  • Confirm the OPC and DPC at every hop.
  • Track the CIC without assuming it changes at an STP.
  • Compare SLS values and message order across linksets.
  • Record ISUP cause codes and timer expirations.
  • Check signaling route status before changing trunk configuration.

The strongest evidence comes from synchronized timestamps and matching message fields. An NTP offset between probes can make a healthy STP appear slow, while an incorrect CIC correlation can make two separate calls look like one failed transaction.

A disciplined trace turns a multi-hop signaling path into a sequence of verifiable events. Apply the same method to a live capture: identify the IAM, follow it through both STPs, match the ACM and ANM, and use any missing response or release cause to narrow the fault domain.