ISUP loopback testing on T1/DS1 trunks

A T1/DS1 trunk loopback confirms that a voice call can be signalled across SS7 and returned over the bearer path. Unlike a simple bit-error test, it exercises MTP3 routing, ISUP call setup, Channel Identification Code mapping, media handling and orderly release. A clear pass or fail ties the result to a defined route, switch pair and direction.

Most Australian carriers use E1, although legacy PBXs, industrial systems and imported equipment may retain T1/DS1. A Sydney–Melbourne leased circuit is more likely to be E1 today, while older campus or branch installations can still use T1 trunks. Configuration errors are easy: E1 provides 32 timeslots, a conventional T1 carries 24 DS1 channels, and each circuit needs an accurate timeslot-to-CIC map.

Preparing the trunk and test environment

Start with a physical baseline. Record framing, including D4 superframe or extended superframe, line coding, CSU/DSU settings, line and signal alarms, and current bit-error counts. Clear active alarms before testing; a local or remote CSU/DSU loopback checks the bearer but says nothing about SS7.

Identify the exact circuit, near and far endpoints, SS7 link and point codes. Confirm which direction carries calls, which timeslots belong to the trunk group and where the far-end loopback or service test is invoked. Do not confuse a physical T1 loopback with SS7 carried over a separate SIGTRAN transport.

Use a switch maintenance console or approved test terminal capable of displaying MTP3 and ISUP messages. Teams new to message tracing can use the structured SS7 training modules to map IAM, ACM and ANM before touching live traffic.

Running the ISUP loopback procedure

Set the boundary. Record the span, endpoints, point codes, SS7 link IDs, affected timeslots and test direction. Confirm that the far end can enter its documented ISUP loopback. For an Australian carrier interconnect, the ACMA-licensed carrier should control network-side work under its change process.

Build the call. Place the test from a controlled terminal or PBX and select the required trunk group and CIC. The originating exchange should send an IAM toward the correct MTP3 destination, then receive ACM and ANM. Use only a reserved, authorised destination: Australian 02, 03, 07 and 08 geographic prefixes and 04 mobile ranges are live numbering spaces, while 000 and 112 must never be dialled for testing.

Read the trace. Check IAM routing, the selected CIC, destination and cause fields, ACM/ANM, speech or tone transfer, and the final REL/RLC exchange. Silence can indicate a media or clip problem rather than failed signalling, so inspect both directions of audio. Repeat in the opposite direction if the service is asymmetric.

Close cleanly. Release the test call through the normal ISUP path, confirm resources return to idle and verify that no new alarms appear. Save the trace and results with AEST or AEDT timestamps, including daylight-saving changes, then attach them to the carrier or technical work order.

Separating bearer, signalling and voice failures

A failed result becomes useful when each layer is assessed separately:

Check What it proves Pass indication Important limit
T1/DS1 bearer loopback CSU/DSU, line coding and timeslot continuity Stable framing and no line or signal alarms Does not prove SS7 routing
MTP3 signalling test Link, routing and message transfer Expected acknowledgement and error-free exchange Does not create an ISUP call
ISUP service loopback Call processing, CIC selection and release IAM, ACM/ANM and a completed release Media depends on the selected test mode
Voice-path check Returned audio or test tone Two-way audio without clipping or one-way silence May not expose every signalling defect

Read the result by layer. Physical continuity can be sound while CIC mapping or ISUP routing fails, and a completed call can still hide one-way audio. Comparing the outcomes identifies whether the fault belongs to the bearer, signalling transport, call processing or media path.

Practical controls for reliable testing

Apply these controls for dependable results:

  • Record framing, line coding, timeslot-to-CIC mapping and test direction before the first call.
  • Compare line, signal and error counters before and after the loopback.
  • Separate physical, MTP3, ISUP and voice-path results because one pass does not prove the others.
  • Use a controlled test number and block calls to customers, 000, 112 and premium services.
  • Capture message traces and correlate the SS7 link, CIC, timeslot and timestamps.
  • Repeat both directions where possible and retain evidence in the change record.

Australian operations teams often call a successful test a clean call and chase the tones when audio is missing. That shorthand is useful only when the bearer trace, SS7 message trace and CIC record are correlated; otherwise it can conceal the actual fault.

Recording results and isolating failures

A failed loopback is not automatically a failed T1. If physical checks pass but the IAM is not acknowledged, focus on MTP3 routing, point-code configuration and signalling-link capacity. If setup completes but no audio returns, examine media handling, transcoding, clip allocation and the far-end return path.

A practical takeaway is to save a repeatable baseline for every trunk, separate each test layer and retain the message trace with the result. That evidence lets the next fault be isolated without repeating the whole exercise or risking live traffic.