63CallPilot Mini/CallPilot 150 Installation and Maintenance GuideChapter 10TroubleshootingIntroductionTroubleshooting CallPilot Mini/CallPilot 150 problems involves determining the symptoms anddiagnosing the cause of the problem.A problem can be the result of more than one component failure. Diagnosing a CallPilot Mini/CallPilot 150 problem involves isolating the cause, and determining whether the malfunctioninvolves a failed hardware component or the CallPilot Mini/CallPilot 150 software configuration.Important: After you have determined the cause of the problem, and corrected the problem byreplacing a component or changing the software configuration parameters, you must test theCallPilot Mini/CallPilot 150.Diagnosing problemsA malfunctioning CallPilot Mini/CallPilot 150 can be caused by a faulty component or theCallPilot Mini/CallPilot 150 software configuration. The following sections describe thesymptoms that occur when CallPilot Mini/CallPilot 150 malfunctions. The symptoms aredescribed first, followed by the procedures to confirm and correct the problem.The RS-232 terminal cannot communicate with CallPilot Mini/CallPilot 150Communication problems appear as garbled text or a blank screen. You need to determine if theproblem is a communication problem, or if CallPilot Mini/CallPilot 150 is not working at all.1 Check to see if CallPilot 150 responds to the Feature Codes.Press ≤·°⁄ on any Norstar telephone connected to the system. CallPilot 150 shouldrespond with the Pswd: display prompt. The Log: display prompt can also appear if thetelephone is not assigned a mailbox.Note: If you are troubleshooting a CallPilot Mini, skip step 1. The CallPilot Minidoes not support Feature Codes.Note: CallPilot 150 Feature Codes might not be the default codes shown here. Formore information on determining CallPilot 150 feature codes, refer to “DeterminingCallPilot 150 Feature Codes” on page 43.
