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.

Table 135: H323-SGR Error Log Entries 2 of 2<br />

Error<br />

Type<br />

2561(m) Any Registered to LSP Inline Error MIN OFF<br />

2817 (n) T303 Timer timed out<br />

3585 (o) Layer 3 Test (#1673) MIN OFF<br />

3841 -<br />

3942 (p)<br />

Aux<br />

Data<br />

Any<br />

Associated Test Alarm<br />

Level<br />

On/Off<br />

Board<br />

Recommended Action<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 appropriate <strong>test</strong>’s description, <strong>and</strong> follow its recommended<br />

procedures.<br />

b. Error Type 1: Failure of the C-LAN hardware (IP-PROCR in S8300 systems) carrying the<br />

signaling group chel. To determine which C-LAN had been administered for this signaling<br />

group, find the near-end node name on the signaling group form, then find the C-LAN<br />

or IP-PROCR with the same node name on the ip-interfaces form.<br />

Check for <strong>error</strong>s against the CLAN-BD MO.<br />

c. Error Type 18:The signaling group in question has been busied out by comm<strong>and</strong>. Release<br />

the signaling group, if appropriate, with release signaling-group grp#.<br />

d. Error Type 257: Tracks failures of the H.323 signaling-group PING <strong>test</strong>. See Signaling<br />

Group Ping Test (#1387) for <strong>test</strong> failure information.<br />

e. Error Type 513: Tracks excessive round-trip delay of the H.323 signaling-group PING <strong>test</strong>,<br />

if the round-trip delay exceeds 4 seconds. See Signaling Group Ping Test (#1387) for <strong>test</strong><br />

failure information.<br />

f. Error Type: 770: Tracks excessive latency <strong>and</strong> packet-loss from background IP<br />

measurements collected by the Media Processor Board. Indicates that <strong>test</strong> packets sent<br />

from a media processor circuit pack to the far-end IP address specified on the signaling<br />

group form have exceeded the IP latency <strong>and</strong> loss thresholds, as administered on the<br />

system-parameters ip-options form. Exceeding these thresholds indicates that the<br />

IP network may not be providing sufficient quality of service for adequate transmission of<br />

voice. If the signaling group has been administered to enable BYPASS, then Error Type<br />

1025 also occurs.<br />

g. Error Type 1025: The signaling group has been placed into a BYPASS condition because<br />

of IP network congestion. The signaling group accepts incoming calls, but every outgoing<br />

call is denied. The system routes these calls over a secondary route, if one has been<br />

administered.<br />

494 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

2 of 2

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

Saved successfully!

Ooh no, something went wrong!