19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Error log entries <strong>and</strong> recommended actions<br />

Table 216: PRI-CDR Error Log Entries<br />

Error<br />

Type<br />

Aux<br />

Data<br />

Associated Test Alarm<br />

Level<br />

PRI-CDR (Call Detail Recording Link)<br />

Notes:<br />

a. Error Type 0: run the short <strong>test</strong> sequence first. If every <strong>test</strong> passes, run the long <strong>test</strong><br />

sequence. Refer to each <strong>test</strong>’s description, <strong>and</strong> follow its procedures.<br />

b. Error Type 18: the CDR link is busied out <strong>and</strong> the CDR link is torn down.<br />

c. Error Type 257: Link Retry <strong>test</strong> (#215) failed. An <strong>error</strong> was detected when setting up the<br />

link. See the preceding section Procedures for Restoring the CDR Link for resolution.<br />

d. Error Type 513: the CDR physical link is down for one of the following reasons:<br />

● Cable to the CDR output device is disconnected.<br />

● CDR output device is powered off.<br />

On/Off<br />

Board<br />

Recommended Action<br />

0 (a) 0 Any Any Any <strong>test</strong> cdr-link primary |<br />

secondary<br />

18 (b) 0 busyout cdr-link<br />

primary|secondary<br />

257 (c) Any Link Retry <strong>test</strong> (#215) MIN 1<br />

WRN<br />

WRN OFF release cd-link primary<br />

| secondary<br />

OFF <strong>test</strong> cd-link primary |<br />

secondary l<br />

513 (d) <strong>test</strong> cdr-link primary |<br />

secondary<br />

1025 (e)<br />

1281 (f) Any<br />

1. Minor alarms may be downgraded to Warning alarms based on the value used in set options.<br />

● The data extension where the CDR output device connects to has been busied out or<br />

there is a scheduled daily interchange.<br />

1. Check the connectivity of wire <strong>and</strong> cable among wall jacket, data module, <strong>and</strong> the<br />

CDR output device.<br />

2. Enter status data extension <strong>and</strong> verify that the data extension of the CDR<br />

output device is in the in-service/idle state. If the data extension is not available, see<br />

Procedures for Restoring the CDR Link for resolution.<br />

3. Use display system-parameters maintenance to see the start time of daily<br />

maintenance.<br />

4. If the <strong>error</strong> occurs <strong>and</strong> is resolved during of daily maintenance, it can be ignored.<br />

Issue 5 May 2009 789

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!