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.

H323-STN (H.323 IP Station)<br />

MO Name in Log Alarm Level Initial Comm<strong>and</strong> to Run Full Name of MO<br />

H323-STN WRN <strong>test</strong> station extension H.323 IP Station<br />

H323-STN covers implementation of the maintenance for native mode H.323 endpoints. Native<br />

mode H.323 applications such as Netmeeting or Proshare provide only what is needed to<br />

support the H.323 st<strong>and</strong>ard. Communication Manager can invoke very little in the maintenance<br />

area. Communication Manager reports <strong>error</strong>s as they are detected via the RAS registration <strong>and</strong><br />

keep-alive mechanism. Communication Manager PINGs the endpoint via the signaling path, for<br />

example via C-LAN, <strong>and</strong> via the media path, for example, via Medpro.<br />

The H.323 station type is not attached to a port board. Insertion of the station is not driven by<br />

board insertion, it is driven by successful registration of the endpoint. The H.323 station is<br />

maintained via a set of explicit TCP/IP ping requests <strong>and</strong> <strong>error</strong>s reported by the switch software,<br />

which terminates the H.323 signaling portion of each endpoint. H323-STN follows st<strong>and</strong>ard<br />

maintenance methodology <strong>and</strong> supports <strong>test</strong>, busyout, release <strong>and</strong> status comm<strong>and</strong>s.<br />

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

Table 137: H323-STN Error Log Entries<br />

Error<br />

Type<br />

Aux<br />

Data<br />

Associated Test Alarm<br />

Level<br />

On/Off<br />

Board<br />

Recommended Action<br />

0 0 Any Any <strong>test</strong> station extension<br />

1 (a) Registration Status<br />

Inquiry <strong>test</strong> (#1372)<br />

257 (b) Signaling Path PING<br />

<strong>test</strong> (#1373)<br />

513 (c) Media Path PING <strong>test</strong><br />

(#1374)<br />

WRN OFF<br />

WRN OFF<br />

WRN OFF<br />

Notes:<br />

a. Error Type 1 reports the registration status of the endpoint. If Communication Manager<br />

claims the endpoint is registered <strong>and</strong> receives keep-alive h<strong>and</strong>shakes from the endpoint,<br />

the <strong>test</strong> passes. If keep-alive h<strong>and</strong>shaking fails, the <strong>test</strong> fails. If the user has intentionally<br />

un-registered the station from the server, the station is basically an AWOH station <strong>and</strong> is no<br />

longer being maintained; no <strong>test</strong>s will run for this station.<br />

b. Error Type 257 tracks failures of the signaling path PING <strong>test</strong>. The <strong>test</strong> attempts to send a<br />

PING packet to the endpoint IP address, as reported during registration. The PING packet<br />

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

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

Saved successfully!

Ooh no, something went wrong!