Avaya S8700 Maintenance Manual page 1707

For multi-connect configurations

Hide thumbs Also See for S8700:

Table of Contents

ISDN-SGR (ISDN-PRI Signaling Group)

Table 8-388. Test #637 Remote Layer 3 Query

Description / Recommendation

There are no associated B channels in an ISDN in-service or maintenance

service state. This is a NORMAL ABORT.

1. Administer or release an ISDN trunk or PRI endpoint before retrying the

The signaling channel is down. Therefore, no messages can be sent to the

far-end switch or terminal adapter.

1. Examine the results of Tests #636 and #639 and follow recommendations

Could not allocate the necessary system resources to run this test.

1. Retry the command at 1-minute intervals up to 5 times.

Internal system error or administration problem

1. Determine whether any B channels are administered. If not, then this is a

Internal system error. See description of ABORT with error code 2500.

A message was composed and sent to the far-end switch or terminal adapter.

The ISDN PRI specification allows up to 2 minutes for a reply. Check the Error

evidence of a Remote Layer 3 Query failure. If no new errors were logged

since this test was run, then this switch and the far-end switch or terminal

adapter can exchange call control messages. If there is still a problem with a

particular ISDN trunk or PRI endpoint, busyout the trunk and run the long test

sequence, paying particular attention to the results of Test #258 (ISDN Test

test. For an ISDN trunk, use the status trunk group#/member#

command to verify the ISDN trunk state. For a PRI endpoint use status

pri-endpoint extension. Then, retry this test when at least one B channel

is in the in-service or maintenance states.

provided there.

normal ABORT, since this test cannot run unless at least one B channel is

administered. If at least one B channel is administered, there is an internal

system error. Retry the command at 1-minute intervals up to 5 times.

''ISDN-SGR (ISDN-PRI Signaling Group)''

for errors of type 2305 for

Continued on next page

Issue 1 May 2002

Troubleshooting