Battery Feed Test (also called Port Diagnostic Test) (#35)

The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing, transmission, and balance. This test checks the signaling and switchhook capabilities of the battery feed chip by terminating the port, applying battery power, and detecting the resulting current.

Table 53. TEST #35 Battery Feed Test �
Error Code	Test Result	Description/Recommendation
	ABORT	Necessary system resources could not be allocated to run this test. Retry the command at 1-minute intervals no more than 5 times. If the test continues to abort, escalate the problem.
1000	ABORT	System resources are unavailable. The port may be busy with a valid call. This result is also reported for the system's Music-On-Hold port when it is off-hook, which it usually is. Enter display port GGGVSpp to determine the station's extension. Enter status station *extension* to determine the service state of the port. If the port is in use, wait until the port is idle. Retry the command at 1-minute intervals no more than 5 times. If the test continues to abort, escalate the problem.
1004	ABORT	A valid call seized the port during the test and aborted the test. Use the display port GGGVSpp command to determine the station extension. Use the status station *extension* command to determine the service state of the port. If the port is in use, wait until the port is idle before testing. Retry the command at 1-minute intervals no more than 5 times. If the test continues to abort, escalate the problem.
1005	ABORT	This test was aborted due to a configuration problem. The test is not applicable for this type of analog port. This error can be ignored.
1018	ABORT	Administration has disabled the test. The default for the Test? field on the station form is y. Determine why this field has been set to n on this station (this may be due to the ringing application Test #48, which can be disturbing to customer or terminal equipment). To enable the test for a particular station being tested, enter change station *extension*. Change the Test? field on the station form to y.
1392	ABORT	This port is currently a TTI port and the test does not execute on it. Verify that the port is a TTI port: Enter the display port GGGVSpp command (the display shows that the port is a TTI port). Enter the list configuration command (the display shows a t for the port). If both commands indicate that the port is a TTI port, the abort is correct for the test, and no action is necessary. If either command indicates that the port is not a TTI port, escalate the problem.
2000	ABORT	Response to the test request was not received within the allowable time period.
2100	ABORT	System resources required to run this test are not available. Retry the command at 1-minute intervals no more than 5 times. If the test continues to abort, escalate the problem.
	FAIL	The port's battery feed chip is unable to supply sufficient power to the terminal equipment. This test result might be marginal, and the terminal equipment may be operating satisfactorily. Retry the command at 1-minute intervals no more than 5 times. If the test continues to fail, determine whether the customer is experiencing problems on this line. Replace the Media Module only if the customer is experiencing problems.
	PASS	The port's battery feed chip is able to provide sufficient power to the station equipment to detect on-/off-hook, but may not be able to supply power for touch-tones. If touch-tones are inoperative on this station, replace the Media Module because this port is inoperative. Investigate user-reported troubles on this port by running other port tests, by examining station wiring, or by inspecting the station.
Any	NO BOARD	The test could not relate the internal ID to the port (no board). This result could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. Check to make sure that the board translations are correct. Use the list configuration command, and resolve any problems. If the board is correctly inserted, issue the busy board GGGVS command. Issue the reset board GGGVS command. Issue the release board GGGVS command. Issue the test board GGGVS long command. This re-establishes the link between the internal ID and the port. If this is not the case, check to make sure that a valid board is inserted.