Troubleshooting guide
Table Of Contents
- Chapter 1 Getting Started
- Chapter 2 Initial Setup
- Connect PC to Controller
- Establish Communication with Controller
- Enable Licenses and Options
- MCD Software Installer Tool Requirements for AMC
- 3300 ICP System Requirements for AMC
- Automatic Sync with AMC via MCD Software Installer Tool (Rel 6.0 or later)
- Automatic Sync via System Administration Tool
- Manual License and Options Entry via MCD Software Installer Tool
- Manual License and Options Entry via System Administration Tool
- Install the Online Help (Optional)
- Verify the Operation of the Controller
- Chapter 3 Installation and Programming
- Install Hardware
- Determine Controller Module Configuration
- Identify Controller Component Options
- Remove Controller Cover
- Install Controller Modules
- Install Controller Stratum 3 Clock Module
- Install Controller Hardware
- Rack Mount the Controller
- Wall Mount the CX/CXi and CX II/CXi II Controller
- Install Service Units and Cabinets
- Installing SX-200 Bays
- Install Telephones
- Install and Configure Music on Hold
- Program 5485 IP Paging Unit
- Register IP Devices from the Telephone
- Program System
- Install Hardware
- Chapter 4 Software Installation
- About Installing and Upgrading Software
- Install System Software Manually
- The MCD Software Installer Tool
- Upgrade System Software
- System Software Installation Details
- Installing MSL Software on APC (CX/CXi) or APC-CX(i) II (CX II/CXi II)
- Installing MSL Software on an MXe Server
- Installing System Software on the FTP Server
- Upgrade to MCD 5.0 and Group Licensing
- Upgrade the 3300 ICP Software on the MXe Server
- Upgrading/Installing with Maximum Elements Change
- Upgrade to Rel 6.0 or later with Flexed Dimensions
- Apply a Software Patch
- Distributing New Firmware to IP Phones
- Load IP Phone Software Remotely
- Downgrading to a Previous Software Release
- Chapter 5 Maintenance
- Check System
- View Logs
- Detect Device Moves for E911
- Analyze IP Phone Issues
- Power Down the Controller
- Perform a System Reset
- Back Up a Database
- Restore a Database
- Migrate SX-2000 Database Across Platforms
- Converting a PRI Database on a Universal NSU
- Export Configuration Data
- Import Configuration Data
- Restoring Default Addresses on MXe Server
- Assign Static IP Addresses to IP Phones
- Providing Power Over Ethernet to Devices (CXi/CXi II)
- Recover MXe Server
- Chapter 6 Install and Replace Units
- Component Replacement Notes
- Add or Replace Controller FRUs
- Controller Modules
- Stratum 3 Clock Module
- System i-Button/System ID Module
- Analog Main Board
- Analog Option Board
- Application Processor Card
- E2T or RTC Processor
- Hard Drives
- Fan Complex
- Power Supply Unit
- Redundant Power Supply
- RAID Controllers
- Line Cards
- Controller Card (AX)
- Flash Cards (AX)
- Memory Module (CX, CXi, AX)
- Install Cabinet FRUs
- Appendix A Hardware Reference
- Appendix B Installation Planner
- Reserved IP Addresses
- MXe Server/MXe/AX/CXi/CXi II Requirements for IP Networking
- Controller Configuration Settings (RTC)
- DHCP Configuration Settings
- Programming E2T via Debug Cable or Secure Telnet
- Configuring External DHCP Settings for E2T
- Configuring a Windows 2000 or Windows 2003 DHCP Server (Rel 7.0 and later)
- System Administration Tool Settings
- IP Phone Settings
- Telephone Programming Guide
- Increasing DSP Resources
- Appendix C Typical Network Configurations
- Network Configuration Examples
- Cisco Discovery Protocol (CDP)
- CXi/CXi II/MXe/MXe Server Configuration
- AX Configuration Procedures
- CXi, CXi II, MXe and AX-Specific Guidelines
- Windows 2000 FTP Server
- Appendix D Status LEDs
- Controller LEDs
- Network Services Unit LEDs
- Analog Services Unit LEDs
- ASU II Card LEDs
- IP Device LEDs
- Peripheral Cabinet LEDs
- SX-200 Bay LEDs
- Digital Services Unit LEDs
- In-Line Power Unit LEDs
- Appendix E FRU Part Numbers
- Appendix F System Capacity and Parameters
- Appendix G Older Hardware and Software
- Procedures for Older Controllers
- Programming the Controller DHCP Server Settings (prior to Rel 7.0)
- To use an alternative DHCP server (prior to Rel 7.0)
- Configuring a Windows 2000 DHCP Server (prior to Release 7.0)
- Program DHCP for VLAN (prior to Rel 7.0):
- Connect a Windows 95/98 PC to the NSU via Dial-Up
- Physically Connecting the PC to an NSU
- Creating a Dial-Up Network Connection on Windows 95/98
- Migrate SX-2000 PBX Hardware
- Collecting System Logs Manually
- Collecting System Lockup Logs Manually
- Peripheral Cabinet
- Digital Service Unit (DSU)
- Index
- Procedures for Older Controllers
![](/manual/mitel/3300/troubleshooting-guide-english/images/img-301.png)
292
3300 ICP Technician’s Handbook
Notes:
1 All 3300 systems can support a maximum of 64 members in a group page.
However, the MXe Standard with 64 E2T channels should restrict the number
of members in a group page to less than 32 to reduce the risk of conflict with
trunk E2T channels.
2. In these configurations there are always more E2T sessions available than
can be used by the T1/E1 trunks, and the full balance of 64 can be used in a
group page with no restrictions.
3. The 192 Gateway is not defined in any software setup procedures, but is a
special case of the resource allocations based on the specific hardware
modules installed.
4. When the system boots up, if it detects either of the following hardware
configurations, the number of voice mail ports will be automatically reset to
zero:
- two DSP II modules and one VEC module, or
- one DSP II module and four dual T1/E1 framers
5. The MXe Controller has been shipped in three different versions since it was
introduced. The original version has four AD21262 DSP devices on the main
board; the later versions (MXe II and MXe III) have four AD21363 DSP
devices. The MXe II and MXe III can be configured as a 192 channel TDM
gateway, as shown in this table. Although not shown in this table, it is possible
to upgrade the original MXe to a 192 Gateway, but with some limitations since
it does not have as much DSP resources available. The original MXe can only
be used as a 192 Gateway when a second VEC module is installed. The two
options shown for the 192 channel TDM gateway that do not have the second
VEC cannot be used, because they will not have enough DSP resources to
function properly.
Table 57: MXe, MXe Server, and 192 Channel PSTN Gateway
DSP Resources (continued)
MXe
Configuration
Maximum Resources Supported
Dual
Framers
E2T
Ports
Echo
Canceller
G729a
Licenses
T.38
Licenses
Max # IP
Sets in IP Page
Max # of
Conferees
RFC4733
DTMF
Voice Mail
Page 3 of 3