DS1 Tie Trunk Seizure Test (#136)

The DS1 Tie Trunk Seizure Test is run to verify the trunk's signaling capability. The test is composed of two parts. The first part queries the Media Module for the following errors: Loss of Signal, Red Alarm, Blue Alarm, Yellow Alarm, and Hyperactivity Alarm. The second part of the test is performed by sending a seizure message to the DS1 Interface Media Module and expecting an active reply by the DS1 Interface Media Module. If maintenance software does not receive any reply and the timer expires, the test fails. Once the active message is received, a dial pause message is sent to the DS1 Interface Media Module. If the DS1 Interface Media Module replies with a dial pulse tone message when the far end responds to the seizure, then the DS1 tie trunk Seizure Test passes. If the far end does not respond to the seizure and the timer expires, and the DS1 Interface Media Module sends a reorder message back to the maintenance software, then the test fails.

This second part of this test cannot be run on a trunk if one of the following cases is true:

Table 83. TEST #136 DS1 Tie Trunk Seizure Test �
Error Code	Test Result	Description/ Recommendation
	ABORT	Internal system error Retry the command at 1-minute intervals a maximum of 5 times.
1000	ABORT	System resources required to run this test were not available. The port may be busy with a valid call. Use the display port GGGVSpp command to determine the trunk group/member number of the port. Use the status trunk command to determine the service state of the port. If the port is in use, wait until the port is idle before testing. If the port status is active but the port is not in use (no calls), check the error log for error type 1025 (see the error log table for a description of this error and required actions). The port may be locked up. If the port status is idle, retry the command at 1-minute intervals for a maximum of 5 times.
1004	ABORT	Far end is seizing the trunk while the test is ongoing. A glare situation is detected. Current test is designed to be aborted. Use the display port GGGVSpp command to determine the trunk group/member number of the port. Use the status trunk command to determine the service state of the port. If the port is in use, wait until the port is idle before testing. If the port status is idle, retry the command at 1-minute intervals for a maximum of 5 times.
1005	ABORT	Test failed due to incompatible configuration administered in trunk group form. Verify the following fields on the trunk group administration screen: Is trunk direction incoming only? Is trunk outgoing type either automatic or immediate-start? Is trunk the 24th port of the DS1 Interface Media Module while common control channel signaling is specified? If the trunk has been administered using the above information, then this test should abort.
1018	ABORT	The test was disabled via translation. You may want to determine why the test has been disabled before you enable it. Verify that the 'Maintenance Test' field on the 'Trunk Administration' screen is set to 'n.' To enable the test, change the trunk administration and enter 'y' into the 'Maintenance Test' field. Repeat the test.
1020	ABORT	The test did not run due to an already existing error on the specific port or due to a more general Media Module error. Examine the error log for existing errors against this port or the Media Module and attempt to diagnose the already existing error. Retry the test.
1040	ABORT	The test is invalid for this trunk port because it is administered as an access endpoint. Use display port to verify that this port is administered as an access endpoint. In this case the test should abort.
2000	ABORT	Response to the test request was not received within the allowable time period. Retry the command at 1-minute intervals for a maximum of 5 times.
2053	ABORT/ FAIL^*	At least one of the following errors is found on the DS1 Media Module: 1281: Loss of Signal 1793: Blue Alarm 2049: Red Alarm 2305: Yellow Alarm 1537: Hyperactivity Look for the above error types in the Hardware Error Log and follow the procedures given in the appropriate DS1-BD/MM-DS1-BD Maintenance documentation for the listed error types.
2100	ABORT	Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times.
	FAIL	The far-end trunk did not respond to the seizure of the near-end trunk within the allowable time period. This test could have associated in-line errors in the error log. Enter the list configuration board GGGVS command. Eventually, the board and all of its ports will be taken out of service and extraneous on-board alarms will be generated. Replace the Media Module with a TN767C V3 or later. Verify that the 'Trunk Type' field on the 'Trunk Administration' screen matches the trunk type administered on far-end switch. Look for DS1-BD or MM-DS1 errors in the hardware error log. If present, refer to the DS1-BD (DS1 trunk Media Module) Maintenance documentation or to the MM-DS1 (MM-DS1 trunk Media Module) Maintenance documentation. Retry the test at 1-minute intervals for a maximum of 5 times.
2000	FAIL	Response to the seizure message was not received within the allowable time period. Enter the list configuration board GGGVS command. Eventually, the board and all of its ports will be taken out of service and extraneous on-board alarms will be generated. Replace the Media Module. Verify that the 'Trunk Type' field on the 'Trunk Administration' screen matches the trunk type administered on far-end switch. Look for DS1-MM errors in the hardware error log. If present, refer to the DS1-MM Maintenance documentation. Retry the test at 1-minute intervals for a maximum of 5 times.
	PASS	The trunk can be seized for an outgoing call.
Any	NO BOARD	The test could not relate the internal ID to the port (no board). This could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted. Check to ensure that the board translations are correct. Use the list config command, and resolve any problems that are found. If the board was found to be correctly inserted in step 1, issue the busyout board command. Issue the reset board command. Issue the release busy board command. Issue the test board long command. This should re-establish the linkage between the internal ID and the port. If this is not the case, check to see that there is a valid board inserted.
*Earlier G1 Software Versions reported Error Code 2053 as a FAIL