This package contains: ====================== 1. PEP Number: CP404PEPG15S 2. Problem Description: ======================= Failure of the T1 cards booting into service results in Event 1 errors being generated. A pop-up window will also appear indicating that at least one service has failed to start. When in this failure mode, neither Setup Wizard nor Configuration Wizard will complete properly. It is recommended that PEP CP404PEPG15S be applied to all CP4.0 T1/SMDI CallPilot servers. Install this PEP according to the appropriate circumstance: a) New System or Re-image System: PEP should be installed before Setup Wizard is run. Note that Setup Wizard may automatically start on a new system. In this case, 'cancel' the Setup Wizard in order to proceed to install this PEP. b) Release Upgrade from CP2.5: After the CP2.5 data has been restored using Upgrade Wizard, PEP CP404PEPG15S should be uninstalled and reinstalled. To summarize: - Install PEP on a new system or after re-imaging, but before running Setup Wizard - Proceed to configure system and migrate the CP2.5 data - Uninstall this PEP - Re-install this PEP. Note: Restoring the CP2.5 data on CP4.0 system reverses the PEP changes. Systems that have been previously configured successfully with Configuration Wizard will not spontaneously suffer the issue resolved by PEP CP404PEPG15S. However this PEP should be applied to all CP4.0 T1/SMDI CallPilot servers to safeguard the system in the event of future maintenance or hardware upgrades. 3. List of CRs that are addressed by this PEP: ============================================== Q01500043 Failed to Upgrade, T1 connectivity issues during boot up 4. Installing the PEP: ====================== This PEP is intended to be installed on CallPilot 4.0 (04.04.04.00) servers with that were installed with or upgraded to any Service Update level. In order to install the PEP: ---------------------------- - Launch the runme.exe to start the installation of the PEP. The runme executable can be found in the PEP's root directory. - A reboot is required before the server can be brought back into service. - After application of this PEP the Configuration Wizard must be used to (re)configure the "Switch Configuration". This step must be performed even if there are no user-definable fields changed. Note: - This PEP has to be applied after EACH AND EVERY 'restore' of CP2.5 data. - Please see the Configuration advisement at the end of the readme file. Uninstall: ---------- Go to Start>Programs>CallPilot>System Utilities>PEP Maintenance Utility. Click Show PEPs. Select CP404PEPG15S, and click Remove. Reboot is required after uninstall. =========================================================================================================== Configuration advisement, validate CallPilot and switch T1 integration settings for design intent accuracy: =========================================================================================================== All CallPilot T1/SMDI systems MUST be configured for 'Ground-Start' line-side T1 configured for B8ZS and D4 Framing, no other T1 configuration parameters are supported. Nortel advises all customers when installing PEP number: CP404PEPG15S, to schedule an inspection of CallPilot T1 integration set-up with the CS 2100 or SL-100 switch in the same maintenance window. Inspection should include, for Meridian Intelligent Peripheral Equipment (MIPE) based Lineside T1 service. Inspect the Lineside T1 line-card dip-switches are set correctly as follows: Settings for SL-100 Line Side T1 DIP switch 1*: Switch 2: On for Ground Start Switch 7: Off Switch 8: Off to disable Cutoff on Disconnect Settings for SL-100 Line Side T1 DIP switch 2*: Switch 1: On for D4 framing Switch 2: Off for B8ZS line coding Switch 6: On for autoforward * switch settings not specified are customized to site Refer to 555-4001-022_SL100 "Line Side T-1 Interface for IPE Services Guide_MSL14_06.02" for details on T1 Line Side configuration. Ensure the CS 2100 or SL-100 is programmed according to the CallPilot 4.0 rack-mount 1002rp installation and configuration T1/SMDI integrations NTP. It is critical to ensure attributes such as UCD/ACD agent login and logout codes are data-filled according to CallPilot design integration. WARNING: CS 2100 or SL-100 systems with CallPilot deployed without proper usage of the UCD/ACD agent login/logout codes associated with the CallPilot channels run the risk of over-loading switching system resources during situations when CallPilot channel resources are off-line and ACD agents are logged in to the line-side T1 service in yellow or red status because the far end (CallPilot) is off-line.