Nortel Norstar & BCM: Top 10 Troubleshooting Guide
Step-by-step solutions for the most common Nortel phone system problems — covering Norstar CICS/MICS, BCM50/450, and Meridian systems.
1 Phone Not Ringing
When a phone stops ringing for incoming calls, the cause can range from a simple cord issue to a system-level programming problem. The key diagnostic is whether one phone or multiple phones are affected.
If a Single Phone Is Not Ringing
- Check the handset cord. The coiled handset cord is the most common failure point. Swap it with a known working cord and test.
- Check the line cord. Unplug and firmly reseat the line cord at both the phone and the wall jack. Listen for a click to confirm proper seating.
- Swap phones. Move the suspect phone to a known working jack. If the problem follows the phone, the phone is defective. If a working phone fails at the same jack, the issue is wiring or port-related.
- Check ringer volume. Press Feature *80 to verify the ringer is turned on. Press Feature *81 to adjust volume.
- Check line appearance. Verify the incoming line appears on the phone. Press Feature *0 (Button Inquiry) and press each line button to confirm lines are programmed.
- Check Do Not Disturb. Press Feature 85 to toggle DND off. The display should read "DND off."
If Multiple or All Phones Are Not Ringing
- Check the KSU. Verify the main control unit has power (LED lit) and is not in an error state.
- Check for alarm codes. If phones display alarm messages or have no display, see Issue 5: System Dead.
- Check incoming lines. Plug a test phone directly into the demarcation point to verify dial tone is present from the carrier.
- Check line programming. Enter programming mode and verify lines are still assigned to sets. If programming was lost, see Issue 8: Lost Settings.
2 No Dial Tone
No dial tone can affect a single phone, a group of phones, or the entire system. The troubleshooting path depends on scope.
Single Phone - No Dial Tone
- Reseat all cords. Unplug and reconnect both the handset cord and line cord at the phone and wall.
- Check the phone on another jack. If it works elsewhere, the jack or wiring is the problem. If it still fails, the phone may be defective.
- Check for dial tone at the demarc. If there's no dial tone at the main distribution frame, the issue is with the carrier line, not the phone system.
- Run a station test. Press Feature *805 to run a display/self-test. If the display doesn't respond, the phone is likely defective.
Multiple Phones - No Dial Tone
- Check KSU power. Verify the power supply LED is on. If dark, check the outlet, surge protector, and circuit breaker.
- Check for a failed line card. If specific groups of phones are affected (e.g., all phones on expansion module 2), the line card or fiber cable connecting the module may have failed.
- Check carrier lines. If all external calls fail but internal calls work, the T1/PRI or analog trunk may be down. Contact your carrier.
- Verify module connections. Power down the KSU, reseat fiber cables between the main unit and expansion modules, then power back up.
3 Voicemail Not Working
Voicemail problems are among the most searched Nortel issues. The most common scenarios: voicemail not answering calls, mailbox password forgotten, and voicemail completely inaccessible.
Voicemail Not Answering Calls
- Check voicemail DN. Press Feature 985 on any Norstar phone. The display shows the voicemail DN (directory number). Verify this matches what's programmed in call routing.
- Check CallPilot/StarTalk module. On the KSU, verify the voicemail module has power and its status LED is normal (green, not red or flashing).
- Check line programming. Lines must be programmed to forward to voicemail on no answer or busy. Verify under Lines → [line] → Prime Set and check forward settings.
- Restart the voicemail module. If the module is unresponsive, power down the KSU, wait 30 seconds, and power back up. Allow 3-5 minutes for the voicemail to fully initialize.
Resetting a Mailbox Password
This must be done from an M7310, M7324, or T7316 phone with admin access.
- Press Feature 983
- Enter the admin password:
- 2-digit extensions: enter
1200000 - 3-digit extensions: enter
1020000 - 4-digit extensions: enter
10020000
- 2-digit extensions: enter
- Press MBOX, then CHG
- Enter the mailbox number (extension number)
- Press RESET to reset the password to the default (
0000) - The user must then log in with Feature 981 and change the password
Creating a New Mailbox
- Press Feature 983 and enter admin password
- Press MBOX, then ADD
- Enter the new mailbox number (typically the extension number)
- Enter the extension number
- Enter the last name, then first name
- Select a Class of Service (default is usually acceptable)
- Press NEXT through remaining prompts
- Press HEAD/REL to save and exit
BCM CallPilot (Not Answering)
- Log into Element Manager and navigate to Telephony → CallPilot
- Verify the CallPilot application service is running (green status)
- Check the application builder to verify the auto-attendant is active
- Verify that lines are routed to the correct CCR (Custom Call Routing) tree
- If the service is stopped, restart it from Element Manager and check logs
4 "Feature Inactive" or "Invalid Feature" Error
When a phone displays "Feature Inactive" or "Invalid Feature," it means the feature code you entered is not available on this phone or system. This can indicate a programming issue, a restriction, or system-level corruption.
Common Causes
- Phone not programmed for that feature. The feature may require a button to be programmed first. Use Feature *3 to program a button.
- Class of Service restriction. The phone's COS may not allow the feature. Check under Terminals & Sets → [extension] → Restrictions.
- Feature keycodes lost. After a power outage, if the backup battery has failed, the system may lose its feature keycodes. This is a serious issue — see Issue 8.
- Wrong feature code. Verify the code against the feature code reference below.
Diagnostic Steps
- Try the same feature on another phone. If it works there, the issue is specific to the first phone's programming.
- Try a basic feature like Feature 9 (page). If even basic features show "Feature Inactive," the system may have lost programming.
- Enter programming mode (Feature **CONFIG / Feature **266344) and check if programming is intact. If settings are blank or default, programming was lost.
- Check the backup battery in the KSU. If it's more than 5 years old or shows signs of corrosion, it should be replaced.
5 System Dead / All Phones Show No Display
When all phones go dark with no display and no dial tone, the main control unit (KSU) has lost power or failed. This is a system-level emergency.
Immediate Diagnostic Steps
- Check AC power to the KSU. Verify the power cord is connected, the outlet has power (test with a lamp), and any surge protector or UPS is functioning.
- Check the power supply LED. On the KSU, look for the power/status LED. If it's off, the power supply has likely failed.
- Check for tripped circuit breaker. If the KSU is on a dedicated circuit, check the breaker panel.
- Listen for fan noise. On larger systems (BCM450, Meridian M1), listen for cooling fans. No fan noise confirms no power.
- Check for burning smell. If you detect an electrical burning odor, do NOT attempt to power the system on. A component has failed and requires replacement.
Three Most Common Failures
| Failure | Symptom | Action |
|---|---|---|
| Power Supply | Entire KSU dark, no LED, no fan | Replace power supply module |
| Line Card / DSU | Callers hear ringing but phones don't ring; no outbound calls | Replace or reseat the line card |
| Programming Corruption | System boots but all settings lost (extensions, routing, voicemail gone) | Reload from backup or reprogram from scratch |
6 Time and Date Are Wrong
The system clock may drift over time or reset after a power outage. This is one of the most searched Nortel admin tasks, especially around daylight saving time changes.
Norstar CICS / MICS - Change Time & Date
- Press Feature **266344 (spells CONFIG)
- Enter the admin password:
- 2-digit extensions:
23646(spells ADMIN) - 3-digit extensions:
123646 - 4-digit extensions:
1223646
- 2-digit extensions:
- Display shows "1. System" — press NEXT
- Press SHOW at "2. Time and Date"
- Press SHOW at "1. Time"
- Enter the hour using 24-hour format (e.g., 14 for 2:00 PM)
- Press NEXT and enter minutes
- Press NEXT repeatedly to reach "2. Date"
- Enter year, month, and day as prompted
- Press HELD / RLS to exit
Meridian 1 / CS1000 - Change Time & Date
- Log into the system via terminal (TTY or SSH)
- Enter
LD 2(Load 2 - System Time and Date) - Enter command:
TTAD(Display current time and date) - To change, enter:
SET - Enter the new time in 24-hour format:
HH:MM - Enter the new date:
YYYY MM DD - Verify with
TTADagain - Enter
****to exit LD 2
BCM50 / BCM450 - Change Time
- Log into Element Manager
- Navigate to Administration → System Time
- Set the correct time and date
- Click Apply then OK
7 BCM Red Alarm LED
A red status LED on the BCM50 or BCM450 indicates a critical alarm. The system is designed to show two green LEDs when operating properly. A red LED means something has failed and needs immediate attention.
Step 1: Clear the Alarm
- Log into Element Manager via the OAM port (leftmost RJ45 port on the BCM50)
- Navigate to Alarm Manager
- Review the alarm list, sorted by date/time (most recent at top)
- Note the Alarm ID and description
- Select the alarm and click Clear
- If the alarm clears and does not return, the issue may have been transient
- If the alarm returns immediately, proceed to Step 2
Step 2: Identify the Root Cause
Match the Alarm ID to the component that generated it:
| Component | Alarm ID Range | Common Cause |
|---|---|---|
| System Resources | 1xx | Database corruption, disk failure |
| Telephony | 2xx | DSU/trunk module failure, line card issue |
| Networking | 3xx | Network interface down, IP conflict |
| Media Services | 4xx | VoIP gateway, DSP resource issue |
| Applications | 5xx | CallPilot service failure, application crash |
Step 3: Common BCM Failures
- Disk drive failure. BCM50 and BCM450 systems use compact flash or hard drives that degrade over time. If the system won't boot past the alarm state, the drive may have failed. A re-image may be required.
- DSU/DSM module failure. If telephony alarms persist, the digital station unit may need reseating or replacement. Try reseating the module first.
- Power supply degradation. If the system frequently alarms and resets, the power supply may be failing. Check for unusual heat or noise.
- Firmware corruption. After clearing alarms, if the system is unstable, a firmware reload via Element Manager may be necessary.
- Two green LEDs: System running normally
- One green, one red: Critical alarm — check Element Manager immediately
- One green, one amber: Minor alarm — review when convenient
- Both flashing: System booting — wait for initialization to complete
- Both off: No power — check power supply and AC input
8 Lost Programming / Settings Reset
If the system has lost all programming (extensions, line assignments, voicemail, call routing), it typically means the backup battery has failed and a power outage wiped the memory. This is the most damaging failure mode for legacy Nortel systems.
Norstar CICS / MICS - Check and Restore
- Enter programming mode: Feature **266344, password
23646(or123646/1223646for 3/4-digit extensions) - Check 1. System → 1. Sys Speed Dial — if this is empty, programming was lost
- Check 2. Terminals & Sets — if only extension 221/221 appears, programming is at factory defaults
- If programming is lost, you must reprogram from your last backup (if you have a Norstar Programming Record) or from scratch
- Replace the backup battery before reprogramming, or the next power loss will wipe everything again
BCM50 / BCM450 - Backup and Restore
- Log into Element Manager
- Navigate to Administration → Backup and Restore
- If a previous backup exists, select it and click Restore
- If no backup exists, you must reprogram the system manually
- After restoring, immediately create a new backup to a USB drive or network location
Programming Access Codes Reference
| Function | Feature Code | Notes |
|---|---|---|
| Config (Programming) | Feature **266344 | Spells CONFIG; requires admin password |
| Admin Password (2-digit) | 23646 | Spells ADMIN; default only |
| Admin Password (3-digit) | 123646 | For 3-digit extension systems |
| Admin Password (4-digit) | 1223646 | For 4-digit extension systems |
| Startup (Full Reset) | Feature **7827887 | Spells STARTUP; erases ALL programming |
| Profile (Region Set) | Feature **7763453 | Spells PROFILE; erases ALL programming |
| Dialpad (Set Dial Mode) | Feature **3425723 | Spells DIALPAD |
9 Phone Buttons Not Working
Unresponsive buttons on Nortel phones are common as the hardware ages. The issue can be physical (stuck or worn buttons) or programming-related (buttons not assigned).
Diagnostic Steps
- Run your hand across the keypad. If a button feels physically stuck or doesn't "click," it may be mechanically worn or jammed. Debris under the keys is common on older phones.
- Unplug and replug the line cord. This performs a soft reset of the phone. The phone re-registers with the KSU and may clear temporary glitches.
- Check what's programmed on the button. Press Feature *0 (Button Inquiry), then press any button. The display shows what's programmed on it. If it says "Not Assigned," the button needs programming.
- Program a button. Press Feature *3, press the button you want to program, then enter the feature code or line number you want assigned.
- Swap the phone. If buttons still don't work after reprogramming, the phone's keypad membrane may have failed. Swap with a known working phone to confirm.
Common Button Programming
| To Program... | Steps |
|---|---|
| Line appearance | Feature *3 → press button → press line button or enter line number |
| Intercom | Feature *3 → press button → press Intercom button |
| Speed dial (personal) | Feature *3 → press button → Feature *4 → enter number |
| Voicemail access | Feature *3 → press button → Feature 981 |
| Call forward | Feature *3 → press button → Feature 4 |
| Page | Feature *3 → press button → Feature 9 |
10 Call Forwarding Issues
Call forwarding not working is a frequent support request. The most common causes are permission restrictions, incorrect programming, or users not following the correct steps.
Setting Up Call Forward (Internal)
- Press Feature 4
- Enter the destination extension number
- The display confirms "Forward to: [extension]"
- To cancel: Press Feature #4
Setting Up Call Forward (External)
To forward calls to an outside number, the phone's Class of Service must allow external forwarding. If you get "Feature Inactive" when trying to forward externally, the COS restriction is blocking it.
- Enter programming mode: Feature **266344, password
23646 - Navigate to 2. Terminals & Sets → [extension] → 3. Restrictions
- Check the Filters section for restrictions on external numbers
- Verify the Class of Service allows external forwarding
- Exit programming and test: Feature 4, then enter the external number (including route access code, e.g.,
9 + number)
Call Forward Not Working - Checklist
Norstar Feature Code Quick Reference
The most commonly used feature codes for Nortel Norstar CICS, MICS, and BCM phone systems. Keep this page bookmarked for quick access.
| Feature | Code | Cancel Code |
|---|---|---|
| Call Forward | Feature 4 | Feature #4 |
| Call Transfer | Feature 70 | — |
| Conference (3-way) | Feature 3 | — |
| Voicemail | Feature 981 | — |
| Voicemail Admin | Feature 983 | — |
| Voicemail DN (display) | Feature 985 | — |
| Do Not Disturb | Feature 85 | Feature #85 |
| Page (all sets) | Feature 9 | — |
| Last Number Redial | Feature 5 | — |
| Speed Dial (personal) | Feature *4 | — |
| Speed Dial (system) | Feature *6 | — |
| Button Inquiry | Feature *0 | — |
| Button Programming | Feature *3 | — |
| Ringer On | Feature *80 | — |
| Ringer Volume | Feature *81 | — |
| Contrast | Feature *7 | — |
| Language | Feature *50 | — |
| Ring Type | Feature *6 | — |
| Call Display | Feature 811 | — |
| Station Test | Feature *805 | — |
- Config: Feature **266344 (password: ADMIN / 23646)
- Startup (erases all): Feature **7827887
- Profile (erases all): Feature **7763453
- Dialpad: Feature **3425723
- Default admin password: CONFIG / 266344
About Nortel Norstar & BCM Systems
Nortel (originally Northern Telecom) was one of the largest telecommunications manufacturers in the world. The Norstar line, introduced in 1988, became one of the most widely deployed business phone systems ever made, with an estimated 43 million users worldwide across the Norstar, BCM, and Meridian product lines.
Nortel filed for bankruptcy in 2009, and Avaya acquired portions of the company. Avaya ended support for the BCM product line on October 1, 2018. Despite this, hundreds of thousands of Norstar and BCM systems remain in active service today — which is exactly why troubleshooting resources like this page remain essential.
Common Nortel Phone Models
| Model | Type | Typical Use |
|---|---|---|
| T7316e | Display phone | Most common business set; admin/programming |
| T7208 | Display phone | Standard office phone |
| M7310 | Display phone | Programming and admin (legacy) |
| M7324 | Display phone | Attendant console, high button count |
| M7208 | Display phone | Basic office phone (legacy) |
| i2004 | IP phone | CS1000/Meridian IP phone |
| 1120e | IP phone | CS1000 IP phone (newer) |
| 1140e | IP phone | Executive IP phone |
System Models
| System | Type | Capacity |
|---|---|---|
| Norstar CICS | Compact Key System | 4-8 lines, 8-24 extensions |
| Norstar MICS | Modular Key System | Up to 24 lines, 274 extensions |
| BCM50 | IP-PBX | Up to 30 users |
| BCM450 | IP-PBX | Up to 300 users |
| Meridian 1 / CS1000 | Enterprise PBX | Thousands of users |