Comdial DXP & DXP Plus Troubleshooting: 10 Common PBX Problems

Step-by-step troubleshooting for common Comdial DXP and DXP Plus cabinet, station, trunk, voicemail, programming, and hardware problems.
Use this guide to isolate the failure before changing programming or replacing hardware. Determine whether the issue affects one phone, a group of extensions, a station card, a trunk group, voicemail, one cabinet, or the entire Comdial DXP or DXP Plus system.

This guide applies broadly to Comdial DXP and DXP Plus digital communications systems, including systems using Impact and Impact SCS phones, Impression phones, single-line stations, analog trunks, T1 or PRI interfaces, voicemail, auto-attendant applications, and expansion cabinets. Exact hardware, menu choices, access codes, and maintenance procedures vary by software release and site configuration.

Before changing programming or hardware: Obtain or verify a current, restorable system backup. Record cabinet LEDs, alarms, affected cards, trunk symptoms, power events, and recent carrier or network changes. Avoid factory resets, repeated power cycles, card swaps, or route-table changes until basic power, cabling, carrier, and physical hardware checks are complete.

Identify the DXP or DXP Plus System First

Many sites refer to the installation as a “Comdial Impact system” because the desk phones say Impact or Impact SCS. However, Impact generally identifies the phone family. Before using cabinet-level troubleshooting procedures, identify whether the PBX is a DXP, DXP Plus, FXS, FXT, or another Comdial platform.

What you find What it identifies Why it matters
Impact, Impact SCS, 8012S, 8024S, 8312S, or 8324S label on a telephone Telephone or endpoint family Useful for user features, station-level testing, display behavior, button operation, and replacement-phone compatibility
DXP or DXP Plus labeling on the cabinet, processor, services board, maintenance paperwork, or VMMI software PBX platform Required for power, card, trunk, cabinet, programming, backup, and recovery troubleshooting
Separate voice-mail cabinet, PC, hard-drive voice-mail system, or application module Voicemail platform Required when callers cannot reach greetings, mailboxes are full, or message-waiting indications fail
One main cabinet plus additional cabinets or expansion connections Multi-cabinet installation Important when only a group of stations or one area of the building is down
Record this information: Cabinet model, services board or processor type, software version, cabinet count, card types and slot positions, phone models, trunk type, voicemail type, carrier details, and the location of the most recent programming backup.

Table of Contents

  1. Comdial DXP and DXP Plus troubleshooting overview
  2. Identify the Comdial system and configuration
  3. No dial tone or blank display on one or more phones
  4. System will not power up after an outage
  5. Incoming or outgoing trunk failures
  6. Cannot access VMMI or programming
  7. Voicemail or auto attendant not working
  8. Calls not routing correctly
  9. Station cards, ports, and groups of dead phones
  10. Forwarding, DND, buttons, and feature problems
  11. System freezes, restarts, or needs repeated reboots
  12. System alarms, card faults, and diagnostic information
  13. Frequently asked questions
  14. Replacement and upgrade planning
1Dial Tone 2Power 3Trunks 4VMMI 5Voicemail 6Routing 7Stations 8Features 9Reboots 10Alarms
DXP / DXP Plus Dial Tone

1No Dial Tone or Blank Display on One or More Phones

A Comdial phone with no display, no intercom tone, or no dial tone can be caused by a failed telephone, damaged station cable, wall jack, building cross-connect, station port, station card, cabinet power problem, or shared wiring issue. The first goal is to determine whether the fault follows the phone or stays with the location.

Check first: Test a known-good compatible Comdial phone at the affected jack. Then test the suspected failed phone at a known-good jack or station port. This two-way test separates telephone failure from wiring, port, card, or cabinet trouble.

Troubleshooting steps

  • Determine whether the problem affects one extension, adjacent extensions, one department, one cabinet, or every phone on the site.
  • Reseat the telephone line cord and handset cord; inspect for loose connectors, damaged locking tabs, cuts, pinched cable, moisture, or corrosion.
  • Test the affected phone at a known-good extension and test a known-good compatible phone at the affected location.
  • Inspect the wall jack, patch panel, MDF, cross-connect, and station cable pair for loose, open, shorted, or damaged connections.
  • If several phones fail together, identify their station-card ports and inspect the associated card, cabinet, and any shared cable path.
  • If all phones are dead, proceed to the power and boot section before replacing individual telephones.
Power System Boot

2System Will Not Power Up or Phones Are Dead After an Outage

A utility outage, brownout, surge, failed UPS battery, failed cabinet power supply, loose power connection, unsuccessful processor boot, or expansion-cabinet issue can leave a Comdial DXP or DXP Plus system partially or completely offline. A power event can also affect voicemail, carrier equipment, network switches, and gateway hardware.

Do not repeatedly power-cycle the PBX: Confirm stable AC power and allow the cabinet to complete a normal startup sequence. Repeated restarts can make a marginal power supply, processor, storage component, or card problem worse and may complicate recovery.

What to do

  • Verify that the wall outlet, circuit breaker, surge protector, UPS, and cabinet power cord are operating normally.
  • Check main and expansion cabinets separately where the installation uses more than one cabinet.
  • Inspect visible cabinet, power-supply, services-board, processor, and card LED indications before reseating any hardware.
  • Allow adequate time for full PBX, voicemail, and connected network equipment to complete startup after utility power returns.
  • Check optional battery-backup equipment and cables for loose connections, aged batteries, or a failed backup assembly.
  • If there is a burning odor, heat damage, visible component damage, water exposure, or repeated power alarm, leave the affected equipment powered down and arrange qualified service.
Trunks Carrier Service

3Incoming or Outgoing Calls Fail

When internal extension-to-extension calls work but incoming or outgoing calls fail, the DXP station side may be operating normally. The likely source is an analog line, PRI or T1 circuit, carrier outage, trunk card, gateway, route assignment, trunk access setting, DID routing issue, or station calling restriction.

Isolate the call failure: Identify whether the problem is inbound only, outbound only, one DID number, one trunk group, one area code, one extension, all outside calls, or intermittent calls. Record the tone, announcement, error message, or exact call behavior.

Troubleshooting steps

  • Test internal calls, incoming calls, and outgoing calls separately from more than one extension.
  • Test more than one outside line or trunk group where available and compare with a known-good route.
  • Check whether all trunks are affected or only a specific analog, T1, PRI, or gateway interface.
  • Verify carrier service at the demarcation point when an outage, alarm, or no-service condition is suspected.
  • Review trunk status, route access, line selection, digit manipulation, caller-ID treatment, and station class of service before modifying the dial plan.
  • For T1 or PRI service, record alarms and error conditions and obtain carrier test results before reseating line-interface hardware.
Programming VMMI Access

4Cannot Access VMMI, Remote Programming, or System Administration

Comdial DXP Plus systems may be administered through the Visual Man Machine Interface (VMMI). Administration access can fail because of the wrong PC software version, incorrect credentials, cable or port problems, modem configuration, serial settings, failed maintenance-port access, a changed PC configuration, or a services-board issue.

Before programming: Confirm the actual system model, software release, database version, and connection method. Use only documentation and programming tools appropriate for that installed release. Preserve the existing database and create a verified backup before making route, card, station, or system changes.

Recommended checks

  1. Confirm that the site is a DXP or DXP Plus and identify the installed software release.
  2. Verify the correct version of VMMI or other approved administration software for the system.
  3. Confirm the appropriate connection method: direct maintenance-port connection, properly configured modem path, or other approved site-specific service connection.
  4. Check PC serial or USB-to-serial adapter settings, cable type, COM port, baud rate, modem initialization, and driver compatibility where applicable.
  5. Verify the services-board maintenance connection and visible board status before assuming a password or software issue.
  6. Do not expose legacy PBX programming access directly to the public internet. Use controlled local or secure remote access managed by a qualified provider.
Voicemail Auto Attendant

5Voicemail, Auto Attendant, or Message Waiting Is Not Working

Voicemail trouble may involve a separate voice-mail server, hard-drive voicemail unit, integration ports, call-forward-no-answer programming, an incorrect pilot destination, a failed station or application port, full storage, mailbox issues, or a power problem affecting the voicemail equipment.

Check first: Call the voicemail pilot number directly from an internal phone. Then place a test call to an affected extension and observe whether it rings normally, forwards to voicemail, reaches the wrong destination, or rings indefinitely.

Verify these items

  • Determine whether all voicemail users are affected or only one mailbox or department.
  • Confirm that the voicemail system, server, application module, or associated power supply is running.
  • Check voicemail storage capacity, mailbox limits, message retention, and the ability to log into a mailbox.
  • Verify the voicemail pilot number, hunt group, integration ports, and no-answer or busy forwarding destination.
  • Check whether the affected extension has an unintended call forward, Do Not Disturb condition, or changed coverage path.
  • Back up greetings, mailbox settings, and voicemail configuration before restarting, replacing, or repairing voicemail storage equipment.
Call Routing DID / Hunt Groups

6Calls Ring the Wrong Phone, Go Straight to Voicemail, or Route Incorrectly

Incorrect routing can result from changed day/night service, holiday routing, DID assignments, attendant programming, line ringing assignments, hunt-group membership, call forwarding, no-answer timers, station class of service, or voicemail integration. The safest approach is to isolate the exact call type before modifying any programming.

Document before editing: Record the number dialed, time of day, originating caller type, intended destination, actual destination, and whether the error affects every call or only a particular route. Preserve the current database before changing routing tables.

Troubleshooting steps

  • Identify whether the issue affects an internal transfer, an outside incoming call, a specific DID, a hunt group, an attendant route, or an after-hours path.
  • Test during the relevant service mode: day, night, lunch, holiday, overflow, or alternate schedule.
  • Verify DID or direct-inward-routing destinations and compare the affected route with a known-good route.
  • Check hunt-group membership, ringing assignments, overflow rules, coverage, and forwarding destinations.
  • Review station class of service, toll restriction, account-code requirements, and line access if outbound calls route incorrectly or fail.
  • Confirm voicemail pilot routing and no-answer treatment if callers are sent to voicemail too early or bypass voicemail entirely.
Station Cards Ports / Wiring

7Several Phones Are Dead or a Group of Extensions Fails Together

When multiple Comdial phones go dead together, the fault is less likely to be individual handsets. Look for a shared station card, common cable path, cross-connect problem, expansion-cabinet issue, card seating problem, cabinet power condition, or processor communication issue.

Look for the pattern: Map each failed extension to its physical location, cable path, card, and card slot. A group of failures that aligns with one card or one building area provides a much more useful diagnosis than a general report that “some phones are dead.”

Recommended checks

  • Determine whether affected phones share a station card, expansion cabinet, telecom closet, floor, or cable bundle.
  • Test a known-good compatible telephone at one affected jack and at one known-good jack.
  • Inspect patch blocks, MDF punch-downs, surge protectors, building wiring, and any recent construction or electrical work.
  • Check card LED status and cabinet power indicators before reseating cards.
  • For an approved maintenance window, use model-specific documentation and qualified service personnel for card reseating or replacement.
  • If a replacement station card is used, confirm the correct part number, cabinet compatibility, software requirements, and programming impact before installation.
Features Forwarding / DND

8Call Forwarding, DND, Transfer, Pickup, Buttons, or Other Features Do Not Work

Feature failures can occur because of an active forwarding or Do Not Disturb condition, changed button programming, a missing line appearance, a hunt-group change, a station class-of-service restriction, a user procedure error, or a failed phone or key module. Not every Comdial installation uses the same programmed access codes.

Review these settings

  • Determine whether the problem affects one extension, a department, or all users of the feature.
  • Check active call forwarding, Do Not Disturb, message waiting, account-code, extension lock, and callback conditions.
  • Compare the affected station's button assignments and class of service with a working station of the same type.
  • Verify pickup groups, hunt groups, shared lines, coverage arrangements, attendant functions, and overflow destinations.
  • Use the correct user guide for the specific telephone family before changing user-level settings.
  • If buttons are physically unresponsive, sticky, damaged, or have no LED behavior, test the phone at a known-good port before reprogramming the station.
System Stability Processor / Power

9System Freezes, Restarts, or Needs Frequent Reboots

A DXP or DXP Plus system that periodically freezes, loses multiple phones, drops trunks, fails to process calls, or only recovers after a restart may have a weak power supply, processor or services-board problem, unstable battery backup, overheating, poor grounding, a failing card, a backplane or connector problem, storage or database trouble, or another aging hardware issue.

A reboot is not a permanent repair: If restart activity temporarily restores service, preserve alarms, logs, LED patterns, configuration data, and the timing of the failure. Frequent reboots are a business-continuity warning and should trigger immediate backup verification and replacement planning.

Next steps

  • Record the date, time, symptom, affected phones, trunks, voicemail behavior, alarms, and any recent utility event before restarting.
  • Check cabinet temperature, fan operation, ventilation, dust buildup, heat sources, and physical environmental conditions.
  • Inspect UPS status, battery condition, grounding, AC stability, surge protection, and power-supply indicators.
  • Check whether failures affect one card, one cabinet, all cabinets, one trunk group, or unrelated functions across the system.
  • Verify that a current system database backup exists and that the backup is readable with the correct administration tools.
  • Consider maintaining compatible spare power supplies, processors, services boards, or critical interface cards where those parts remain available.
System Alarms Cards / Trunks / Logs

10System Alarms, Card Faults, Trunk Errors, and Diagnostic Problems

Comdial DXP and DXP Plus alarms can point to cabinet power, services-board, processor, station-card, trunk-card, PRI or T1, voicemail, external interface, or carrier problems. The exact alarm name, LED condition, maintenance procedure, and repair path depend on the installed hardware and software release.

Before clearing an alarm: Record the full alarm text or code, date and time, cabinet and card slot, affected ports or trunks, LED state, and the event that preceded the fault. Clearing an alarm does not prove that the cause has been corrected.

Common alarm categories

  • Power alarms: Check AC input, UPS, battery backup, power-supply status, cabinet connections, and grounding.
  • Processor or services-board alarms: Check boot status, board LEDs, backup availability, maintenance access, and recurring restart behavior.
  • Station-card alarms: Check card seating, port pattern, affected extensions, station wiring, MDF connections, and shared cable paths.
  • Analog, T1, or PRI trunk alarms: Check the carrier handoff, physical circuit, framing or service status, cabling, error history, and provider test results.
  • Voicemail alarms: Check server or module power, storage, application status, integration ports, mailbox capacity, and routing to the voicemail pilot.
  • External interface alarms: Check paging, door phone, relay, serial, SMDR, CTI, caller-ID, modem, and third-party equipment connections as applicable.

Frequently Asked Questions

What are the most common Comdial DXP and DXP Plus problems?

Common Comdial DXP and DXP Plus problems include phones with no dial tone, one or more dead station ports, failed station or trunk cards, cabinet power issues after outages, incoming or outgoing call failures, voicemail integration problems, VMMI programming access issues, call-routing errors, recurring alarms, and systems that freeze or require repeated restarts.

What is the difference between Comdial Impact phones and a Comdial DXP or DXP Plus?

Comdial Impact and Impact SCS generally identify telephone families, while DXP and DXP Plus identify PBX platforms. Impact phones may be installed on DXP, DXP Plus, FXS, or FXT systems. Phone-level troubleshooting should be separated from cabinet, card, trunk, backup, and system-programming troubleshooting.

Why does one Comdial DXP extension have no dial tone?

A single extension with no dial tone may have a failed phone, handset or station cable, wall jack, cross-connect, station port, or station card. Test a known-good compatible phone at the affected location, then test the affected phone at a known-good location. If several adjacent phones fail, investigate shared wiring, a station card, cabinet power, or an expansion cabinet.

Why can Comdial DXP extensions call internally but not make outside calls?

If internal calling works but outside calls fail, the station side of the PBX is often functioning. Check the trunk group, analog line, PRI or T1 circuit, carrier service, line card, route programming, outgoing access code, toll restriction, account-code requirement, and station class of service.

How do I connect to Comdial DXP Plus VMMI?

DXP Plus VMMI access depends on the system release, PC software version, credentials, and connection method. Documentation describes connecting a PC directly to the maintenance port on the services board or, where configured, using modems over an outside telephone line. Confirm the exact system model and software release before attempting administration changes, and obtain a verified database backup first.

What should I do before restarting a Comdial DXP or DXP Plus?

Record the failure time, affected stations or trunks, visible cabinet LEDs, alarms, recent power or carrier events, and current system condition. Verify stable AC power and UPS status, and make or verify a current backup if the system remains accessible. Avoid repeated power cycles, card swaps, database clears, or programming changes without model-specific documentation and a qualified technician.

When should a Comdial DXP or DXP Plus be replaced instead of repaired?

Repair can be reasonable for a clearly isolated fault such as one compatible phone, station cable, station port, card, or readily available power supply. Replacement planning becomes more important when the system has recurring processor or power failures, unreliable backups, repeated card or trunk problems, scarce compatible parts, unsupported carrier interfaces, recurring voicemail failures, or repair costs approaching a supported replacement platform.

Replacement Planning Legacy PBX

When Replacement Is the Better Fix

A Comdial DXP or DXP Plus can sometimes remain practical when the failure is clearly isolated and compatible parts are available: one failed phone, damaged cable pair, station card, trunk interface, power supply, voicemail component, or known programming issue. A repair is more defensible when the system has a current verified backup and reliable support remains available.

Replacement planning becomes urgent when the PBX has recurring power or processor trouble, no dependable backup, recurring card faults, repeated trunk failures without a carrier cause, unstable voicemail, difficult programming access, scarce parts, unsupported services, or repairs that are becoming more expensive and disruptive than a modern replacement system.

Document before an emergency: Save and verify the system database. Record extensions, DID routing, line and trunk details, voicemail, attendant consoles, paging, door phones, fax lines, alarm panels, elevator phones, cordless devices, call accounting, external relays, analog devices, cabinet layout, cards, software release, and critical business-call flows.

A replacement does not need to be cloud-only. Businesses that prefer local control can evaluate on-premise or hybrid IP-PBX options based on user count, simultaneous calls, SIP trunking, analog-device requirements, remote-worker needs, paging, door access, hospitality needs, and local support availability.

To compare a compatible refurbished option, system expansion, modernization plan, or complete business phone-system replacement, request a phone system quote.

On-Premise and Hybrid Comdial Replacement Options

Businesses replacing an end-of-life Comdial DXP or DXP Plus system may prefer an on-premise or hybrid design instead of moving all calling to a public cloud platform. Existing cabling, analog devices, local survivability, internet reliability, privacy, operational control, and a preference for owning the PBX can all support that decision.

A Comdial replacement should begin with a complete inventory of extensions, outside lines, voicemail, paging, fax machines, alarm panels, elevator phones, door-entry equipment, cordless phones, conference rooms, call accounting, remote users, and any hospitality-specific functions. Comdial Impact and Impression digital phones normally cannot be reused directly on a modern SIP-based PBX, but selected analog phones and special-purpose analog devices may be retained through properly designed FXS gateways, analog telephone adapters, or compatible interfaces.

1. Yeastar P-Series Appliance Edition

Yeastar P-Series Appliance Edition is a modern, appliance-based IP-PBX option for small and midsize organizations that want local call control, browser-based administration, SIP trunking, IP phones, remote-user support, and flexible auto-attendant routing.

It can be a good choice for Comdial customers that want a purpose-built PBX appliance rather than a general-purpose server, while still gaining SIP endpoints, mobile and desktop clients, modern voicemail, call routing, and hybrid-work capability.

2. 3CX on a Local Server or Private Appliance

3CX can be deployed on a local server, mini-PC, or private virtual machine. It can be attractive when a business wants software-based PBX control, mainstream SIP endpoints, web administration, softphones, call queues, IVRs, and a hybrid approach for remote users.

This approach is often most appropriate for organizations that are comfortable maintaining a server or working with an experienced telecom provider. It can suit a larger Comdial replacement when the customer has many extensions but relatively modest simultaneous-call requirements.

3. Grandstream UCM6300 Series

The Grandstream UCM6300 Series provides an appliance-first approach for businesses that want a locally installed IP-PBX with SIP extensions, conferencing, remote-connect features, compatible IP phones, paging and intercom possibilities, and selected analog connectivity options depending on the equipment chosen.

It can fit small offices, medical practices, retail businesses, warehouses, and other Comdial replacement projects where the owner prefers a self-contained appliance and wants to move from proprietary digital phones to standard SIP endpoints.

4. Avaya IP Office

Avaya IP Office remains an established option for organizations that need more complex call handling, local or hybrid deployment, SIP trunks, analog-device support through appropriate interfaces, voicemail, contact-center features, multi-site capability, and access to experienced business-telephony dealers.

5. Sangoma Switchvox On-Premises

Sangoma Switchvox On-Premises is a modern unified communications platform that can be a strong Comdial DXP or DXP Plus replacement for small and midsize businesses that want for a small or midsize business that wants to retain an on-premise PBX rather than move fully to hosted UCaaS. Sangoma continues to market Switchvox On-Premises as a fully supported, on-site UC platform capable of handling up to 1,000 phones and 200 concurrent calls.

Before selecting a replacement, identify all existing Comdial functions that must be retained: extensions, simultaneous calls, analog lines, SIP trunks, PRI or T1 services, fax devices, alarm panels, elevator phones, paging, door entry, cordless phones, conference rooms, attendant consoles, voicemail, call accounting, remote users, and any hospitality or special-purpose requirements.

Choosing the Right Replacement

Priority Often a Good Fit
Simple local appliance with modern hybrid and remote-worker features Yeastar P-Series Appliance Edition
Software-based PBX with local-server deployment and broad SIP flexibility 3CX installed locally
Traditional appliance ownership with a self-contained IP-PBX approach Grandstream UCM6300 Series
Established enterprise telephony, advanced call handling, and dealer support Avaya IP Office
On-premise UC with SIP phones, softphones, queues, reporting, CRM integration, and browser-based management Sangoma Switchvox On-Premises

It is generally best suited to businesses with more involved call flows, multiple sites, specialized analog devices, call-center requirements, or a preference for an established enterprise telephony platform with a broad dealer and support ecosystem.