Avaya 03-300430 User Manual
BRI-SET, Various Adjuncts
Issue 1 June 2005
721
BRI Remote Loop Back Test (#627)
This test checks the integrity of a circuit-switched B-channel connection between the switch and
the endpoint.
In this test, the endpoint is put in the “maintenance busy” state to prevent the switch from
issuing calls to the endpoint during the test. An application message containing a loop back
activate request for the appropriate B channel is sent to the endpoint. The endpoint responds
with a loop back activated response. Maintenance then sends data to the endpoint over the B
channel under test. Since the B channel is looped back at the endpoint, maintenance should
receive the data that it sent. If no data is detected, the test fails. An application message
containing a loop-back deactivate request is then sent to the endpoint to discontinue the remote
loop-back test. The endpoint responds with an MIM message containing a loop-back deactivate
response. Maintenance then releases the endpoint so that it is available to terminate calls.
the endpoint.
In this test, the endpoint is put in the “maintenance busy” state to prevent the switch from
issuing calls to the endpoint during the test. An application message containing a loop back
activate request for the appropriate B channel is sent to the endpoint. The endpoint responds
with a loop back activated response. Maintenance then sends data to the endpoint over the B
channel under test. Since the B channel is looped back at the endpoint, maintenance should
receive the data that it sent. If no data is detected, the test fails. An application message
containing a loop-back deactivate request is then sent to the endpoint to discontinue the remote
loop-back test. The endpoint responds with an MIM message containing a loop-back deactivate
response. Maintenance then releases the endpoint so that it is available to terminate calls.
2012
ABRT
Internal system error.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1113
FAIL
The signaling link is not “bound” to the adjunct or endpoint. For BRI
endpoints supporting MIM initialization, this error indicates that the
endpoint has not been bound to a signaling link (that is, SPID initialization
has not been completed). Since the signaling link associated with the
endpoint is not identified until SPID initialization completes, this error does
not imply that the signaling link is connected or disconnected at Layer 2 nor
does it provide the status of TEI assignment for the endpoint. For ASAI
adjuncts and BRI endpoints not supporting MIM initialization, this error
indicates that the link is disconnected at Layer 2. Since the signaling link
associated with the endpoint has been identified via administration, the link
is only “unbound” from the endpoint when it is disconnected.
endpoints supporting MIM initialization, this error indicates that the
endpoint has not been bound to a signaling link (that is, SPID initialization
has not been completed). Since the signaling link associated with the
endpoint is not identified until SPID initialization completes, this error does
not imply that the signaling link is connected or disconnected at Layer 2 nor
does it provide the status of TEI assignment for the endpoint. For ASAI
adjuncts and BRI endpoints not supporting MIM initialization, this error
indicates that the link is disconnected at Layer 2. Since the signaling link
associated with the endpoint has been identified via administration, the link
is only “unbound” from the endpoint when it is disconnected.
1. Execute status bri-port location and see the associated
PASS
The signaling link is connected at Layer 2 and “bound” to the BRI endpoint
or ASAI adjunct.
Table 243: Test #626 Signaling Link Status Test (continued)
Error
Code
Code
Test
Result
Result
Description / Recommendation
2 of 2