DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects
3-917PMS-LINK (Property Management System Link)
3
b. The Link Retry Test (#215) fails. The Aux Data field contains either the
Channel ID of Data Channels on Network Control circuit pac k (that is, 3 for
Channel 01, 4 for Channel 02, 5 for Channel 03, 6 for Channel 04) or an
Error Type of 99 indicating no data channe ls are available for setting up
the link, or an Error Type of 255 for the internal system error generated
upon initialization or power-up . Refer to the ‘‘Procedures for Restoring the
PMS Link ’’ section for resolution.
c. The PMS physical link is down due to the following causes: cable to the
PMS device is disconnected; the PMS device is powered off; o r the data
extension to which the PMS device connec ts has been busied out. The
Aux Data field contains the Channel ID of Da ta Channels on Network
Control circuit pack (that i s, 3 for Channel 01, 4 for Channel 02, 5 for
Channel 03, 6 for Channel 04) or an Error Type of 255 for the internal
system error generated upon initialization or power-up. Check the
connectivity of wire and c able among wall jacket, d ata module, and the
PMS dev ice. En ter status data
extension
and verify that the data
extension of the PMS device is in in-service/idle state. If the d ata extension
is not available, then refer to the ‘‘Procedures for Restoring the PMS Link’’
section for recommended repair strategy.
d. No communication between DEFINITY Generic 1 or Generic 3iV2 and
PMS for a period of time (the time is specifi ed in "system hospitality"
administration). The PMS Link is torn down. To clear this error, refer to the
‘‘Procedures for Restoring the PMS Link’’ section.
e. The link was taken down because the switc h could not receive an
incoming message from the PMS. The message from the PMS repeatedly
had corrupted data or the switch received requests for acknowledgmen t
but never received a messag e to be processed. I f this error type recurs
frequently (that is, more than once a month), then ad vise the customer to
call the vendor of the PMS to check out the PMS devic e. Once the PMS
Link is successfully estab lished, this error disapp ears from the Hardware
Error Log.
f. The link was taken down because the switc h could not send an outg oing
message. The message, which was sent but not acknowledged, was
flushed. If this error type recurs freq uently (that is, more than once a
month), then advise the customer to c all the vendor of the PMS to check
out the PMS device. Once the PMS Link is successfully estab lished, this
error disap pears from t he Hardware Error Lo g.
g. The PMS has been busied out for maintenance at the request of the PMS.
The PMS Link is torn down. The reason code (N), if present, is that
supplied b y the PMS in the request message. If this error type recurs
frequently (that is, more than once a month), then ad vise the customer to
call the vendor of the PMS to check out the PMS devic e. Once the PMS
Link is successfully estab lished, this error disapp ears from the Hardware
Error Log. No alarm is raised against this error.
h. PBX buffer overflows due to either heavy call traffic or PMS protoco l
message rate being faste r than the PMS/PBX protocol specifications
allow. The PMS Link is torn down. PMS Link maintenance software waits