CCNA 200-301

CCNP Enterprise

CCNP Security

CCIE Enterprise Lab

CCIE Security Lab

CCNP Service Provider

CCNP Data Center

CCNP Collaboration

CCIE DC Lab

Verifying the health of a Primary Rate Interface (PRI) on a Cisco IOS or IOS XE voice gateway requires checking three distinct operational layers: physical T1/E1 framing, Q.921 Data Link signaling on the D-channel, and Q.931 Network Layer call control. Whether you are performing routine maintenance, auditing active voice capacity, or diagnosing an unexpected trunk outage, knowing which CLI diagnostics to run—and how to read their outputs—lets you isolate carrier vs. router issues in seconds.

Essential Cisco IOS Commands to Check PRI Status

Use the following Cisco IOS CLI command template to quickly determine whether a T1 (:23) or E1 (:15) PRI trunk is operational. Replace <slot/subslot/port> with your voice interface card location (for example, 0/0/0 or 0/1/0).

! 1. View the Layer 1, Layer 2, and Layer 3 summary for all ISDN interfaces
Router# show isdn status

! 2. Check ISDN status for a specific T1 PRI (D-channel :23) or E1 PRI (D-channel :15)
Router# show isdn status serial <slot/subslot/port>:23
Router# show isdn status serial <slot/subslot/port>:15

! 3. Verify the D-channel serial interface line and protocol state
! Expected healthy output: "Serial0/0/0:23 is up, line protocol is up (spoofing)"
Router# show interfaces serial <slot/subslot/port>:23

! 4. Quickly list the up/down status of all serial D-channels on the router
Router# show ip interface brief | include Serial

! 5. (MGCP Gateways Only) Verify PRI backhaul status to Cisco Unified Communications Manager
Router# show ccm-manager

Once you have retrieved the baseline status from the CLI, the next step is understanding what each layer state in the output actually indicates.

Interpreting show isdn status Output and Layer States

The show isdn status command breaks PRI health down into the bottom three layers of the OSI model. When you execute the command on a healthy router, the output looks like this:

Global ISDN Switchtype = primary-ni
ISDN Serial0/0/0:23 interface
        dsl 0, interface ISDN Switchtype = primary-ni
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0x807FFFFF
    Number of L2 Discards = 0, L2 Session ID = 14
    Total Allocated ISDN CCBs = 0

Follow this sequential progression from top to bottom to interpret the output accurately:

  1. Verify the ISDN Switchtype (Global and interface ISDN Switchtype)
    Before checking line states, confirm that the configured switch type matches the carrier’s central office switch. Common North American T1 PRI values include primary-ni (National ISDN-2), primary-dms100, and primary-5ess, whereas international E1 PRI deployments typically use primary-net5 or primary-qsig. A mismatch prevents Layer 2 or Layer 3 negotiation from completing properly.
  2. Evaluate Layer 1 Status (Physical Layer)
  3. ACTIVE: Physical framing and electrical signaling between the Cisco router’s T1/E1 port and the carrier smartjack or CSU/DSU are synchronized.
  4. DEACTIVATED: The physical circuit is down due to a cabling fault, carrier outage, or hardware failure.
  5. SHUTDOWN: An administrator has manually issued the shutdown command on either the T1/E1 controller or the Serial D-channel interface.
  6. Analyze Layer 2 Status (Data Link / ITU-T Q.921 LAPD)
  7. State = MULTIPLE_FRAME_ESTABLISHED and TEI = 0: This is the required operational state for an active PRI. Terminal Endpoint Identifier (TEI) 0 is statically assigned for point-to-point PRI circuits, and the router has successfully exchanged Q.921 frames with the carrier switch.
  8. State = TEI_ASSIGNED: Layer 1 is typically ACTIVE, and the local router recognizes TEI 0, but Layer 2 LAPD keepalives are not established with the provider. This happens when the telco drops Layer 2 during idle periods, when D-channel signaling is misconfigured, or on MGCP gateways when the TCP backhaul connection to Cisco Unified Communications Manager (CUCM) is down.
  9. State = AWAITING_ESTABLISHMENT: The router is actively transmitting SABME (Set Asynchronous Balanced Mode Extended) frames to initiate the Layer 2 handshake and is waiting for an acknowledgment (UA) from the carrier switch.
  10. Confirm Layer 3 Status (Network Layer / ITU-T Q.931)
  11. Active Layer 3 Call(s): Displays the real-time count of calls currently connected or in setup/teardown across the trunk, alongside active Call Control Blocks (CCBs).
  12. Free Channel Mask: A hexadecimal bitmask representing idle B-channels (1 = free, 0 = busy/reserved). Note that if you also checked show interfaces serial, seeing line protocol is up (spoofing) is normal behavior—ISDN D-channels spoof an “up” state so higher-layer routing and voice processes know the interface is available on demand.

When Layers 1 through 3 report healthy states, administrators frequently need to inspect individual voice channels and active call legs in greater detail.

Checking Active PRI Calls and Real-Time B-Channel Usage

Use the following CLI commands to inspect individual B-channel states, caller ID details, call durations, and active DS0 timeslots on a Cisco voice gateway.

! 1. Display all active ISDN calls, including Calling/Called numbers, B-channel used, and duration
Router# show isdn active

! 2. Filter active ISDN calls to a single PRI interface
Router# show isdn active serial <slot/subslot/port>:23

! 3. Check the service state (0=In Service, 1=Maintenance, 2=Out of Service)
!    and Busy/Idle status of every individual B-channel (1-23 on T1, 1-31 on E1)
Router# show isdn service serial <slot/subslot/port>:23

! 4. View a summary of all voice ports and DS0 timeslots (S_CONNECT = active call, S_IDLE = free)
Router# show voice call summary

! 5. Inspect active call legs, negotiated codecs (e.g., g711ulaw), and DSP status
Router# show voice call status

Even when show isdn status and active call checks look normal at a glance, intermittent audio static, dropped calls, or periodic D-channel flaps often hide at the physical T1/E1 controller level.

Inspecting T1/E1 Controller Alarms, Slips, and Framing Errors

To audit the physical health of the TDM circuit, execute show controllers t1 <slot/subslot/port> (or show controllers e1 <slot/subslot/port>). Follow these steps to evaluate carrier alarms and performance counters:

  1. Check Controller State and Carrier Alarms
    Look at the first two lines of the output. A healthy circuit displays T1 0/0/0 is up and No alarms detected. If an alarm is present, identify the fault domain based on the alarm type:
  2. Receiver Loss of Signal (LOS): The router detects no electrical signal on the receive pair. This points to an unplugged cable, a broken RJ-48C wire, a reversed pinout (requiring a T1 crossover cable), or a powered-off carrier smartjack.
  3. Loss of Frame (LOF / Red Alarm): Electrical signal is present, but the router cannot synchronize with the incoming frame pattern because the framing format mismatches the carrier configuration.
  4. Alarm Indication Signal (AIS / Blue Alarm): The local connection to the nearest piece of carrier equipment is intact, but an upstream telco multiplexer or repeater has lost its signal and is transmitting an all-ones keepalive pattern downstream.
  5. Remote Alarm Indication (RAI / Yellow Alarm): Your router is receiving a valid signal from the carrier, but the remote carrier switch cannot synchronize with the signal your router is transmitting outbound.
  6. Verify Framing and Line Code Settings
    Confirm the configured physical parameters listed directly below the alarm status:
  7. T1 PRI Standard: Framing is ESF, Line Code is B8ZS (Extended Super Frame and Binary 8-Zero Substitution). Older legacy circuits occasionally use SF (D4) and AMI.
  8. E1 PRI Standard: Framing is CRC4, Line Code is HDB3 (or NO-CRC4 if the provider disables Cyclic Redundancy Check multiframing).
  9. Audit the 15-Minute and 24-Hour Error Counters
    Review the Total Data summary line and the current 15-minute bucket for accumulating physical errors. Run clear counters if you need to reset historical totals and observe fresh real-time accumulation:
  10. Slip Secs (Clock Slips): Measures seconds in which buffer underruns or overruns occurred due to clock synchronization drift between the router and the carrier. Any incrementing Slip Secs usually means the controller is set to clock source internal instead of clock source line, or the router lacks network-clock-participate and network-clock-select statements in global configuration.
  11. Line Code Violations (LCV): Counts bipolar violations (BPVs) or excessive zeros on the physical copper pair. Incrementing LCVs indicate degraded cabling, loose connectors, electromagnetic interference (EMI), or failing port hardware.
  12. Path Code Violations (PCV): Counts CRC-6 errors (on ESF T1) or CRC-4 errors (on E1). High PCVs combined with LCVs confirm physical layer corruption along the circuit path.
  13. Framing Loss Seconds (Fr Loss) and Errored Seconds (Err Secs): Tracks seconds where frame synchronization was lost or bit errors occurred, which directly cause audible clicks on voice calls or drop the D-channel out of MULTIPLE_FRAME_ESTABLISHED.

If your inspection reveals a down D-channel, active carrier alarms, or stuck signaling states, you can move directly into structured recovery and debugging.

How to Troubleshoot and Reset a Down PRI Circuit

When a PRI trunk goes down and will not pass calls, follow this step-by-step recovery workflow to isolate the layer failing and restore service:

  1. Bounce the Serial D-Channel Interface and T1/E1 Controller
    If the circuit became wedged after a carrier maintenance window, administratively resetting the interface forces a clean Q.921 and physical layer renegotiation. Always wait 5 to 10 seconds before re-enabling the port so the provider switch registers the loss of signal:
    ios
    Router# configure terminal
    Router(config)# interface serial <slot/subslot/port>:23
    Router(config-if)# shutdown
    ! Wait 5-10 seconds
    Router(config-if)# no shutdown
    Router(config-if)# exit
    ! If Layer 1 remains down, bounce the physical controller:
    Router(config)# controller t1 <slot/subslot/port>
    Router(config-controller)# shutdown
    ! Wait 5-10 seconds
    Router(config-controller)# no shutdown
    Router(config-controller)# end
  2. Isolate Layer 1 DEACTIVATED States with Loopback Testing
    If Layer 1 remains DEACTIVATED (as covered above) or show controllers reports an LOS alarm, test the router’s internal hardware by applying a software local loopback under the controller configuration:
    ios
    Router(config)# controller t1 <slot/subslot/port>
    Router(config-controller)# loopback local

    Run show controllers t1 <slot/subslot/port>. If the controller transitions to up (looped) with No alarms detected, the router’s voice interface card is healthy. Next, remove the software loopback (no loopback) and insert a physical RJ-48C loopback plug into the end of the T1/E1 cable that plugs into the carrier demarc. If the controller comes up with the plug installed, your router and cabling are verified good, and you can escalate the outage to the telecom carrier.
  3. Diagnose Layer 2 Handshake Failures with debug isdn q921
    When Layer 1 is ACTIVE but Layer 2 will not reach MULTIPLE_FRAME_ESTABLISHED, inspect the real-time LAPD frame exchange:
    ios
    Router# terminal monitor
    Router# debug isdn q921

    Evaluate the debug output based on the frame direction (TX -> sent by the router, RX <- received from the carrier):
  4. Healthy Keepalives: You will see periodic RRp (Receiver Ready poll) and RRf (Receiver Ready final) messages exchanged in both TX -> and RX <- directions every 10 seconds.
  5. Unidirectional SABME (TX -> only): If the router repeatedly sends SABME frames and receives zero RX <- traffic, the carrier has not activated the D-channel on their switch or a partial physical fault is blocking the receive path.
  6. Receiving DM (Disconnected Mode) Frames: If the router sends SABME and receives RX <- DMf, the carrier switch is actively refusing the Layer 2 connection, usually due to D-channel provisioning problems on the provider side.
  7. MGCP Backhaul Check: If an MGCP gateway stays stuck in TEI_ASSIGNED, verify that isdn bind-l3 ccm-manager is configured under interface Serial<slot/subslot/port>:23 and that CUCM reachability is intact.
  8. Trace Call Setup and Teardown Errors with debug isdn q931
    If Layer 2 is established (MULTIPLE_FRAME_ESTABLISHED) but inbound or outbound calls fail to connect, enable Layer 3 call signaling debugs:
    ios
    Router# debug isdn q931

    Place a test call and follow the message sequence (SETUP -> CALL_PROC -> ALERTING -> CONNECT). When a call fails, inspect the DISCONNECT or RELEASE message for the Cause i = line, which provides the ITU-T Q.850 disconnect reason—such as 0x8090 (Normal call clearing), 0x8081 (Unallocated/unassigned number), 0x8091 (User busy), or 0x80A2 (No circuit/channel available). Once you capture the trace, immediately turn off debugging to protect router CPU resources:
    ios
    Router# undebug all

While CLI commands and debugs are indispensable during active troubleshooting, relying purely on manual checks leaves your voice infrastructure vulnerable to unnoticed trunk drops outside business hours.

Automated SNMP Monitoring Tools for Cisco PRI Trunks

To detect PRI failures proactively, enable ISDN SNMP traps on your Cisco router (snmp-server enable traps isdn layer2 and snmp-server enable traps ds1) and integrate the gateway with an SNMP monitoring platform that polls Cisco voice MIBs:

  1. SolarWinds VoIP & Network Quality Manager (VNQM)
    Designed specifically for Cisco Unified Communications environments, SolarWinds VNQM automatically discovers T1/E1 PRI trunks on Cisco ISR gateways. It tracks historical B-channel utilization, monitors DS1 physical alarms, and triggers immediate alerts when a D-channel drops out of Layer 2 establishment or experiences high clock slip rates.
  2. Paessler PRTG Network Monitor
    PRTG provides pre-configured SNMP sensors for Cisco voice gateways that monitor both the D-channel interface operational state (ifOperStatus) and real-time active DS0 channel counts via the cpmActiveDS0s OID (1.3.6.1.4.1.9.10.19.1.1.4). Administrators can set capacity thresholds to alert when a PRI trunk approaches saturation.
  3. ManageEngine OpManager
    OpManager includes built-in Cisco WAN and VoIP router monitoring templates that poll RFC 2495 DS1-MIB counters for Loss of Signal (LOS), Loss of Frame (LOF), and AIS alarms. It also functions as an SNMP trap receiver to process instant demandNbrLayer2Change alerts sent by the router the moment Q.921 status changes.
  4. Zabbix
    As an enterprise open-source monitoring platform, Zabbix supports Low-Level Discovery (LLD) of Cisco serial interfaces and voice ports. Using standard Cisco IOS SNMP templates or custom OID items, Zabbix can poll isdnLapdOperStatus (1.3.6.1.2.1.10.20.1.3.4.1.2) to graph when a PRI moves between inactive(1), l1Active(2), and l2Active(3).
  5. LibreNMS
    LibreNMS offers automatic discovery for Cisco IOS and IOS XE devices, natively parsing IF-MIB, DS1-MIB, and CISCO-POP-MGMT-MIB. It generates time-series graphs of concurrent voice calls per PRI and dispatches notifications via Slack, PagerDuty, or email if a serial D-channel or T1/E1 controller changes state.

When building custom SNMP monitors or escalating complex signaling issues to Cisco Technical Assistance Center (TAC), consult the primary Cisco command and standards documentation below.

Official Cisco IOS Reference and TAC Documentation Overview

The following technical specifications and Cisco documentation resources define the exact CLI behavior, MIB objects, and troubleshooting standards for Cisco ISDN PRI interfaces:

  • Cisco IOS Voice Command Reference & Cisco IOS Dial Technologies Command Reference
    Authoritative command syntax and output field definitions for show isdn status, show isdn active, show isdn service, show voice call summary, debug isdn q921, and debug isdn q931 across Cisco IOS and IOS XE releases.
  • Cisco IOS Interface and Hardware Component Command Reference
    Hardware diagnostic specifications for show controllers t1 and show controllers e1, detailing ANSI T1.403 and ITU-T G.703/G.704 physical framing states, loopback modes (local, network line, network payload), and 15-minute/24-hour performance interval tables.
  • Cisco TAC Technotes for T1/E1 and PRI Diagnostics
  • Verify and Troubleshoot T1 PRI Layer 1 and Layer 2 Problems: Standard TAC decision tree for isolating physical layer DEACTIVATED states using RJ-48C hardware plugs and interpreting Q.921 LAPD frame exchanges.
  • Troubleshooting T1/E1 Controllers Prior to Opening a Service Request: Defines the mandatory baseline logs (show tech-support, show controllers, show isdn status, and show logging) required for hardware RMA validation.
  • Understanding debug isdn q931 Disconnect Cause Codes (Document ID: 18148): Comprehensive mapping of hexadecimal Q.850 cause codes returned in Layer 3 debug traces to ITU-T call clearing definitions.
  • Standard and Enterprise SNMP MIB Definitions
  • ISDN-MIB (RFC 2127): Defines standard Q.921 D-channel operational polling via isdnLapdOperStatus (1.3.6.1.2.1.10.20.1.3.4.1.2).
  • CISCO-ISDN-MIB: Defines enterprise trap notifications, including demandNbrLayer2Change (1.3.6.1.4.1.9.9.26.2.0.3), triggered when LAPD transitions into or out of MULTIPLE_FRAME_ESTABLISHED.
  • DS1-MIB (RFC 2495): Defines dsx1LineStatus (1.3.6.1.2.1.10.18.6.1.10), a bitmask integer reporting physical layer T1/E1 alarms (RAI, AIS, LOF, LOS, and loopback states), alongside slip and code violation tables.
  • CISCO-POP-MGMT-MIB: Defines cpmActiveDS0s (1.3.6.1.4.1.9.10.19.1.1.4) for tracking concurrent active DS0 channels across the voice gateway.

By combining rapid CLI status checks (show isdn status and show isdn active), deep physical controller inspections (show controllers t1/e1), targeted Q.921/Q.931 debugging, and automated SNMP polling, you can maintain full visibility over your Cisco PRI voice trunks and resolve circuit disruptions before they impact users.

Please follow and like us:
Last modified: November 17, 2026

Author

Comments

Write a Reply or Comment

Your email address will not be published.