Avaya 03-300430 User Manual

Page of 2574
Communication Manager Maintenance-Object Repair Procedures
2316 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
 
Tie Trunk Seizure Test (#73) 
and Tie Trunk Dial Test (#747)
For wink-start, delay-dial and TN2140 (cont-seize-ack or discont-seize-ack) trunks, this test 
activates the M lead and checks for a response from the far end within 10 seconds.
For TN497, the test seizes a trunk and outpulses a pause. The port reports uplink the result of 
the seizure. This test can be disabled using the Test field on the Trunk Group Administration 
screen.
For TN439, Test #747 is run instead of #73. This test seizes a trunk and outpulses a pause digit. 
This test aborts on ports administered as access endpoints.
Table 832: Test #73,#747 Tie Trunk Seizure Test 
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The 
trunk may be busy with a valid call. Use display trunk-group 
xx
 to determine the trunk group/member number of the port. Use 
status trunk to determine the service state of the port. If the 
service state indicates that the port is in use, then the port is 
unavailable for certain tests. Wait until the port is idle before 
retesting.
1. If the port status is active, but the port is idle (no calls), then 
check the Error Log for Error Type 1025 (see Error Log table for 
description of this error and required actions). The port may be 
locked up. The far-end PBX may not be releasing.
2. If the port status is idle, then retry the command at 1-minute 
intervals up to 5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has 
been aborted. Use display trunk-group xx to determine the 
trunk group/member number of the port. Use status trunk to 
determine the service state of the port. If the service state indicates 
that the port is in use, then the port is unavailable for certain tests. 
Wait until the port is idle before retesting.
1. Retry the command at 1-minute intervals up to 5 times.
 1 of 3