1.

Matrix Type1 Protocol details

This protocol is common for RS232 serial communication port as well as for TCP/IP,

Following table summarizes the flow of messages between the Eternity and PMS.
PMS to Eternity Eternity to PMS

PMS-Eternity synchronization SMDR OG Call Details

Check-In Mini Bar Details

Check-Out Room Clean Status

Guest In (Guest Present) DND

Guest Out (Guest Absent) Data Transfer (in fixed format)

Set/Cancel Alarms Room Status

Set/Cancel Message Wait Alarm Status

Set/Cancel DND Online OG SMDR

Alarm Status User Defined Fields (UDF)

Room Occupancy Display

Room Shift

Room Clean Display

Guest Name
Dynamic Lock Level

Guest Group Assignment

Data Transfer Request

SMDR OG Detail Request

Update Room Clean Status

Update Room Occupancy Status

How the PMS interface works?

The PMS must be capable of interacting with the PBX. For e.g. when the receptionist checks in the
guest from the computer (the PMS), the PMS will send this information to the PBX. Likewise, when the
receptionist checks out a guest, the PMS will send this information to the PBX and wait for check out
details like SMDR OG details, Mini bar details, etc. from the PBX.
• All the communication between the PBX and the PMS follow a fixed protocol.
• The messages exchanged follow a fixed format known as the message format.
• The length of the message can vary between 7 to 128 bytes.
• The message text contains only ASCII characters (0x00 to 0xff).
• Original Message-It is sent by the PMS or PBX to initiate the communication (Check-In (PMS J
PBX), Mini Bar details (PBX J PMS)).
• Error Message-It is sent by the PBX to notify that an error while execution of the original message
due to wrong code or wrong parameters.
• Response message-It is sent by the PBX to the original message like alarm status of the room,
cleanliness status of the room etc.
• The protocol also uses two ASCII encoded characters:
• ACK for message acknowledgment.
• NAK for message Negative acknowledgment.
• The ACK signal is identified by character 0x06 (i.e. Hex 06). It is sent by the receiver as an
acknowledgment of receiving a message in the proper format and with correct code and
parameters.
• To elaborate: Consider a case wherein the receptionist Checks-In a guest. When the receptionist
checks in the guest from the computer the PMS sends a message in a defined format (as explained
below) to the PBX. On Receiving the message the PBX checks the message format, code and
parameters. If all of them are correct, it accepts the message and executes it and sends an ACK
signal to the PMS. ACK signal is not sent if response message is sent.
• The NAK signal is sent by the receiver as a negative acknowledgment of received message, due to
improper format or data error. NAK is identified by character 0x15.
• The Hex 06, Hex 15 does not appear in the message except in BCC.
The Message Format
The format of the exchanged message is as given below:
STX-Feature Code-Message Count-Process Code-Message Data-ETX-BCC

STX
• STX stands for start text. It marks the beginning of the message. It is a field of 1 byte identified by
character 0X02 (i.e. Hex 02). Due to this reason, Hex 2 will not be used in any other field
except BCC (byte check code).

Feature Code
• Feature Code follows the STX. Feature code is a field of 2 bytes. The feature code is a predefined
code and unique for each of the feature like Check-In, Check-Out, Guest In, Guest Out, etc.
distinctly. For e.g. the feature code for Check-In is 10, for Check-out is 11, etc. The length of the
message depends on the feature Code. If the receptionist wants to Check- In a guest, he/she
needs to key in the station number as the parameter along with the message to the PBX, but in
case he/she wants to set an alarm at a station they need to pass the station number, the alarm type
and the date/time as the parameters to the PBX. The number of parameters is different in each
case, and they depend on the feature. As the number of parameters vary feature wise, the length of
the message varies.

Message Count
• Message count follows the feature code. Message Count field is one byte in length. This field is
used to eliminate the chances of execution of duplicate messages. Most of the PMS vendors use
message count for the above purpose. Message Count is incremented on delivery/receipt of
ACK/error message/response message. The Eternity also supports Message Count. The range of
message count is 0-9 (mode 10). The message count is kept programmable match it with that of
PMS. In case the PMS does not support the message count, the message count at the PBX
can be also set to zero. However message count =0 might lead to duplication of messages.
Consider following cases to understand the significance of Message Count.

Case 1:
• Initially, the Message count in PMS and in PBX is 0.
• PMS sends a Check–In message to the PBX with message count 0. PBX receives the message
with message count 0. The received message is found to be of the proper format so the PBX
executes it and sends an ACK signal to the PMS and increments its own message count to 1. On
receiving ACK, PMS increments it’s the count to 1.
• Now the message count in the PMS and the PBX is 1. The next message to be transferred will
have the message count 1.

Case 2:
• Assume that Message count in PMS and in PBX is 0.
• PMS sends a Check-In message along with a station number to the PBX with message count 0.
PBX receives the message with message count 0. The message is found to be of improper format
by the PBX. It sends NAK signal to the PMS. The PBX does not increment its the message count to
1. The message count at the PBX is still 0 and awaiting the message with message count 0 from
the PMS. On receiving NAK from PBX, PMS resends the message with message count 0.

Case 3:
• Assume that Message count in PMS and in PBX is 0.
• PMS sends a Check-In message along with a station number to the PBX with message count 0.
The message is of proper format. The PBX executes it. PBX sends an ACK signal to the PMS and
increments its own message count to 1. But the ACK signal is converted to NAK during
transmission. On receiving NAK, PMS resends the message with message count 0 (normal
response to NAK). But the PBX is expecting a message with message count 1, so when it receives
a message with message count 0, it sends an ACK in response but does not go ahead with
execution of the current message since it is a duplicate message. Also it does not increment its
message count. On acceptance of ACK the PMS increments the message count to 1 and the next
message to be transferred will be with the message count 1.

Case 4:
• Assume that Message count in PMS and in PBX is 0.
• PMS sends a Check-In message along with a station number to the PBX with message count 0.
The PBX identifies message is of proper format and begins execution. During Execution the PBX
realizes that the invalid station number is keyed in. PBX sends an error message to the PMS and
increments its own message count to 1. On receiving the error message the PMS increments the
message count to 1. It has to resend the previous message with a valid station number. However
the message count of that message will be 1.

Case 5:
• Assume that Message count in PMS and in PBX is 0.
• PMS sends an alarm status enquiry for a station to the PBX with message count 0. The PBX
identifies message is of proper format and begins execution. The execution at the PBX is complete.
PBX sends a response message to the PMS with the message count 0 and then increments its
own message count to 1. The response message contains all details about the alarm setting of the
station. On receiving the response message the PMS increments the message count to 1.

Process Code:
• Process code follows the message count. Process code is a one byte field in length.
Type of Message Process Code

Original Message 1

Response Message 2

Error Message 0 or 3
• When error message with process code ‘0’ indicates there is a wrong parameter in the original
message. Consider messages like Check-In, which requires station number as a parameter. If the
received value is not a station number, the response is an error message with process code ‘0’.
• An error message with process code ‘3’ indicates there is an execution error in the original
message. Consider messages like Room Shift which requires a source station number and
destination station number. If the source station is empty or the destination is already occupied, the
original message cannot be executed and the error message will bear the process code ‘3’. Also
when a request for alarm is being processed, if the alarm count is already maximum then the
response message is an error message with process code 3.
Message Data:
• It is an optional field. The length of this field can vary from 0 to 121 bytes. All the features do not
require this field. Consider the three cases listed below:
• If the PMS wants to synchronize itself with PBX, it only requests for synchronization. No
additional parameters are required.
• In case of Check-in, the station to be checked-in is the message data.
• In case of setting an Alarm at a station, the station number, the alarm type and the alarm
day/time are in the message data.
• The number of additional parameters is different for different features. If the feature code requires
one or more parameters they are passed as message data in the message. Since the number of
parameters is not fixed the length of the message data field is also not fixed.
• Parameters in the message data are of fixed length. However these parameters may not actually
have the value with the fixed length. In such cases null characters are padded to the values to
make them full length fixed.
• For e.g. The field length for a station no is 6 digits. Now in case the station number is 101 that is
Checked In then the PMS shall send number as: 101NullNullNull (Three ASCII null characters after
will pad NULL characters to 101 and send it in message data.

ETX:
• ETX stands for end of text. It marks the end of the data. It is a field of 1 byte identified by character
0X03 (i.e. Hex 03). Due to this reason, Hex 3 will not be used in any other field except BCC. (byte
check code).

BCC: Byte Check Code

• It is a field of one byte in length. It always follows an ETX. The BCC is an Exclusive OR of all the
field except STX i.e BCC = Feature Code ^ Message Count ^ Process Code ^ Message Data ^
ETX ( ^ is symbol of Exclusing OR). It is used for checking the validity of the data transferred. BCC
is calculated and appended to the message while sending the original message and also calculated
while the message is received If the BCC received in original message does not match with the
calculated BCC, it is treated as an invalid message and a NAK is sent in response.

Messaging Protocols
All the communication between the PBX and the PMS follows a fixed protocol. The exchanged
messages follow a fixed format. The communication between the PMS and the PBX could be
originated from either side. In either case one end is the sending end and the other end is the receiving
end. Both the ends are governed by a set of rules called messaging protocols. The administration
parameters like Acknowledgement timer, Message Count, Retransmission count, Retransmission
request count are taken care by both the ends.

If the length of the data parameters (e.g. station number) is less than the size specified, it must be
filled with padding characters as specified in this document to match the size. For example, when a
request for Check-In is sent the station number is expected as a data parameter. The size specified for
the station number is 6 bytes. If the station number happens to be 3 digits (300), then the PMS will
append three NULL characters (ASCII) with the station number to match the specified size.

Rules for sending a message.

• All the messages strictly follow the message format.
• The feature code is prefixed with STX and message data is suffixed with ETX. The Byte Check
Code is calculated and appended to the ETX.
• The ACK and NAK signals are not integrated in the message.
• When an ACK/error message/response message is received the message count of the sender is
incremented by one and new value becomes the message count for the next message. In the
process if the message count value has reached the maximum limit it is set to zero.
• When a NAK is received from the receiver the re-transmission counter is decremented by one and
the previous message is resent with the same message count. This process goes on till the re-
 transmission counter value is not zero or ACK/error message/response message is received for
that particular message.
• If the re-transmission counter value reaches zero, before ACK/error message/response message is
received, PBX assumes that the PMS is down and starts sending enquiry (ENQ) message at every
3 secs.
• This continues till ACK is received from the PMS. Once the ACK is received for ENQ PBX resumes
its sending process from the last message.
Rules for receiving a message
• Verify whether the received message (STX to BCC) is valid in length and format. If not send a
NAK-a request for re-transmission after decrementing re-transmission request count.
• If the format and length of the received message are valid, calculate the BCC. Compare the
calculated BCC with the received BCC. If they are not equal, send a NAK-a request for re-
transmission after decrementing its re-transmission request counter.
• If the message format and the BCC are valid in the message and the message could be executed
success fully the ACK/response message which ever is relevant is sent to the sender and the
message count is incremented.
• The error message sent back to the sender has the same feature code, message count but
different process code.
• The response message sent back to the sender has the same feature code, message count but
different process code and the relevant message data.
The Message Exchange
The set of actual messages that can be exchanged between the PMS and the PBX may vary from
PMS to PMS. However, all the messages strictly follow the message format. The message format is:
STX-Feature Code-Message Count-Process Code-Parameter1….Parameter n-ETX-BCC
Where,
Field Value

STX Hex 2 (Fixed)

Feature Code Depends on the feature (variable)

Message Count Depends on the message flow (variable)

Process Code Depends on the message type and feature (variable)

Parameter 1 Depends on the feature (Optional)

Parameter 2 Depends on the feature (Optional)

: :

Parameter n Depends on the feature (Optional)

ETX Hex 3 (fixed) 1 byte

BCC Exclusive-OR of all the bytes from feature code to ETX

Following two encoded Signals are used for efficient message exchange.
Encoded Signal Value

ACK Hex 6 (fixed)

NAK Hex 15 (fixed)

Null Hex 00

Message Format
Note:
• The station number is expected to be of 6 digits. If it is less than 6, pad it with ‘NULL’ (ASCII 000).
• Message Count is of range 0 to 9.

PMS Link Synchronization:

A request for synchronization from the PMS to PBX.
PMS to PBX • STX-01-Message Count-1-ETX-BCC

PBX to PMS • ACK or

NAK
The message count sent by the PMS will be sync. by the PBX.

Check-In:
A request by the receptionist for checking in a guest at a particular station.

PMS to PBX • STX-10-Message Count-1-Station Number-ETX-BCC

PBX to PMS • ACK or

NAK or
STX-10-Message Count-0-ETX-BCC or
STX-10-Message Count-3-ETX-BCC

Example:(In Hex)
02 31 30 30 31 33 30 30 31 00 00 03 01
PMS to PBX

Check-Out:
A request for checking out a guest from a particular station.
PMS to PBX • STX-11-Message Count-1-Station Number-ETX-BCC

Please ensure the COM port is assigned for Hotel Report generation before
issuing this command.
PBX to PMS • ACK or
NAK or
STX-11-Message Count-0-ETX-BCC or
STX-11-Message Count-3-ETX-BCC

Example:(In Hex)
02 31 31 30 31 33 30 30 31 00 00 03 00
PMS to PBX

Guest-In:
A request for ‘Guest-In’ at a particular station by the receptionist.
PMS to PBX • STX-12-Message Count-1-Station Number-ETX-BCC

PBX to PMS • ACK or

NAK or
STX-12-Message Count-0-ETX-BCC or
STX-12-Message Count-3-ETX-BCC

Example:(In Hex)
02 31 32 30 31 33 30 30 31 00 00 03 03
PMS to PBX
Guest-Out:
A request for checking out a guest temporarily from a particular station by the receptionist.
PMS to PBX • STX-13-Message Count-1-Station Number-ETX-BCC

PBX to PMS • ACK or

NAK or
STX-13-Message Count-0-ETX-BCC or
STX-13-Message Count-3-ETX-BCC

Example:(In Hex)
02 31 33 30 31 33 30 30 31 00 00 03 02
PMS to PBX

Set/Cancel Message Wait:

A request by the receptionist for setting or canceling the message wait feature at a station.
PMS to PBX • STX-14-Message Count-1-Station Number-Flag-ETX-BCC
Where,
Flag 0 = Cancel, 1 = Set.

PBX to PMS • ACK or

NAK or
STX-14-Message Count-0-ETX-BCC

Example:(In Hex)
02 31 34 30 31 33 30 30 31 00 00 31 03 34
PMS to PBX

Change Room Clean Status:

A request for updating the room clean status by the PMS.
PMS to PBX • STX-15-Message Count-1-Station Number-Room Clean Status-ETX-BCC
Where,
Room Clean Status: 1= Maid Present, 2=Dirty, 3=Clean, 4=To be Inspected, 5=
Out of Service

PBX to PMS • ACK or

NAK or
STX-15-Message Count-0-ETX-BCC

Example:(In Hex)
02 31 35 30 31 33 30 30 31 00 00 33 03 37
PMS to PBX

Set/Cancel Alarm:
A request for set/cancel an alarm at a station by the receptionist.
PMS to PBX • STX-16-Message Count-1-Station Number-Alarm Type-Alarm Time-Greeting Mode-
ETX-BCC
Where,
Alarm Type Meaning Alarm Time
0 Cancel All Alarms -
1 Once Only Alarm HHMM
2 Daily Alarm HHMM
DDMMYYYYHHMM
3 Reminder (Date-Time Alarm) OR
MMDDYYYYHHMM

Greeting Mode Meaning

1 Automated
2 Personalized

PBX to PMS • ACK or

NAK or
STX-16-Message Count-0-ETX-BCC or
STX-16-Message Count-3-ETX-BCC

Example:(In Hex) 02 31 36 30 31 33 30 30 31 00 00 33 31 37 30 34 31 39 37 34 31
PMS to PBX 34 33 30 32 03 09

Guest Name:
A request for associating a guest name at a station by the receptionist
PMS to PBX
• STX-17-Message Count-1-Station Number-Guest Name-ETX-BCC
Where,
Guest Name is of max. 18 characters, if less than 18 terminate with Null characters.

PBX to PMS • ACK or

NAK or
STX-17-Message Count-0-ETX-BCC

Example:(In Hex) 02 31 37 30 31 33 30 30 31 00 00 4D 72 2E 20 44 61 76 69 64 00
PMS to PBX 00 00 00 00 00 00 00 00 03 E2

Set/Cancel DND:
A request by the receptionist to set or cancel the DND at a station
PMS to PBX • STX-18-Message Count-1-Station Number-Flag-ETX-BCC
Where,
Flag 0 = Cancel DND, 1 = Set DND.

PBX to PMS
• ACK or
NAK or
STX-18-Message Count-0 -ETX-BCC
Example:(In Hex)
02 31 38 30 31 33 30 30 31 00 00 41 03 48
PMS to PBX

Room Shift:
A request by the receptionist to shift a guest from a source station to a destination station.
PMS to PBX • STX-19-Message Count-1-Station Number-Destination Station Number-ETX-BCC

PBX to PMS • ACK or

NAK or
STX-19-Message Count-0-ETX-BCC or
STX-19-Message Count-3-ETX-BCC

( Here, the PBX shall send the message :

STX-19-Message Count-3-ETX-BCC, in case
destination station is occupied or source station is not occupied)

Example:(In Hex)
02 31 39 30 31 33 30 30 31 00 00 33 30 30 32 00 00 03 09
PMS to PBX

Alarm Status:
A request by the receptionist to know the alarm status of a particular alarm type at a station
PMS to PBX • STX-20-Message Count-1-Station Number-Alarm Type-ETX-BCC
Where,
Alarm Type is of the range 1 to 3.
Alarm Type Meaning Alarm Time
1 Once Only Alarm HHMM
2 Daily Alarm HHMM
DDMMYYYYHHMM
3 Reminder (Date-Time Alarm) OR
MMDDYYYYHHMM

PBX to PMS • ACK or

NAK or
STX-20-Message Count-0-ETX-BCC (Invalid Parameter or command error)

STX-20-Message Count-2-Station Number-1-NULL-NULL-NULL-NULL-NULL-ETX-

BCC (No once alarm is set on the station)
STX-20-Message Count-2-Station Number-2-NULL-NULL-NULL-NULL-NULL-ETX-
BCC (No daily alarm is set on the station)
STX-20-Message Count-2-Station Number-3-NULL-NULL-NULL-NULL-NULL-
NULL-NULL-NULL-NULL-NULL-NULL-NULL-NULL-ETX-BCC (No date-time alarm
is set on the station)

STX-20-Message Count-2-Station Number-Alarm Type-Alarm Time–Greeting Mode

ETX-BCC (First alarm set on the station is retrieved)

Example:(In Hex)
02 32 30 30 31 33 30 30 31 00 00 31 03 33
PMS to PBX
Room Occupancy Status:
A request by the receptionist to know the room occupancy status.
PMS to PBX • STX-21-Message Count-1-Station Number-ETX-BCC

PBX to PMS
• ACK or
NAK or
STX-21-Message Count-0-ETX-BCC (Invalid Parameter or command error)
STX-21-Message Count-2-Station Number-Room Occupancy Status-ETX-BCC.
Where,
Room Occupancy Status; 1=Occupied, 2=Vacant, 3=Reserved, 4=Guaranteed

Example:(In Hex)
02 32 31 30 31 33 30 30 31 00 00 03 03
PMS to PBX

Room Clean Status:

A request by the receptionist to know the room clean status. This is only a quarry and doesn’t alter the
room status.
PMS to PBX • STX-22-Message Count-1-Station Number-ETX-BCC

PBX to PMS • ACK or

NAK or
STX-22-Message Count-0-ETX-BCC or
STX-22-Message Count-2-Station Number- Room Clean Status-ETX-BCC
Where,
Room Clean Status: 1= Maid Present, 2=Dirty, 3=Clean, 4=To be Inspected, 5= Out
of Service
Example:(In Hex)
02 32 32 30 31 33 30 30 31 00 00 03 00
PMS to PBX

Change Dynamic Lock Level (Call Privilege):

A request by the receptionist to change the dynamic lock level of a station
PMS to PBX • STX-23-Message Count-1-Station Number-Call Privilege-ETX-BCC
Where,
Call Privilege Meaning
0 Internal Calls
1 Local Calls
2 Long Distance Calls
3 International Calls

PBX to PMS • ACK or

NAK or
STX-23-Message Count-0-ETX-BCC

Example:(In Hex)
02 32 33 30 31 33 30 30 31 00 00 33 03 32
PMS to PBX
Assign Guest Group:
A request by the receptionist to assign a guest group for a particular station
PMS to PBX • STX-24-Message Count-1-Station Number-Guest Group-ETX-BCC
Where,
Guest Group is from 00 to 99.

PBX to PMS • ACK or

NAK or
STX-24-Message Count-0-ETX-BCC

Example:(In Hex)
02 32 34 30 31 33 30 30 31 00 00 33 33 03 06
PMS to PBX

Data Update Station Wise:

A request by the receptionist to update the data of a station (The PBX would send all the related
parameters of receipt of this command).
PMS to PBX • STX-25-Message Count-1-Station Number-ETX-BCC

PBX to PMS
• ACK or
NAK or
STX-25-Message Count-0-ETX-BCC or
STX-25-Message Count-2-Parameter1.......Parameter11-ETX-BCC**

Data Update for all Stations:

A request by the receptionist to send SMDR OG reports of all the stations.
PMS to PBX • STX-26-Message Count-1--ETX-BCC

PBX to PMS
• ACK or
NAK or
STX-26-Message Count-0-ETX-BCC or
STX-26-Message Count-2-Parameter1.......Parameter11-ETX-BCC**

Request for SMDR OG details of all stations:

A request by the receptionist to send SMDR reports of all the stations.
PMS to PBX • STX-27-Message Count-1-ETX-BCC

PBX to PMS
• ACK or
NAK or
STX-27-Message Count-0-ETX-BCC or
STX-27-Message Count-2-Parameter1.......Parameter16-ETX-BCC**
(Use the same format that is programmed for SMDR-OG while transferring the SMDR
OG details of all stations on request from PMS.) ##
**
Padding Character
Parameter Size in (in case data field is
Description Data Format
No. Byte/s of less than its
intended size)
Flexible number of the Ascii String NULL
01 6
extension
02 Guest Name 18 Ascii String NULL

03 Room Occupancy Status 1 Ascii Char

04 Room Clean Status 1 Ascii Char

HHMMG Space, when Alarm

05 Alarm Once Only 6
is not set
HHMMG Space when alarm is
06 Alarm-Daily 6
not set
DDMMYYYYHHMMG Space when alarm is
Reminder Alarm (Date and
07 16 Or not set
Time)
MMDDYYYYHHMMG
Call Privilege (Dynamic Ascii Char
08 1
Lock Level)
09 Message Wait 1 Ascii Char

10 Guest Group 2 Ascii char

11 DND Status 1 Ascii Char

##
Data Format Padding
Parameter No. Description Size in Byte/s
character
01 Check-In Call Status 1 Ascii Char

02 Check-Out Call Status 1 Ascii Char

Space 1

03 Flexible Number 6 Ascii String NULL

Space 1

04 Trunk Number (Software Port) 5 Ascii String

Space 1

05 Telephone Number 16 Ascii String NULL

Space 1
DD-MM-YYYY
06 Date 10 OR
MM-DD-YYYY
Space 1
 07 Time 5 HH:MM

Space 1
Ascii String 0 as prefix if
08 Duration 6
less than 6
Space 1
Ascii String 0 as prefix if
09 Units e.g. 0012 4
less than 4
Space 1
Ascii String 0 as prefix if
10 Cost e.g. 0012.50 7
required
Space 1
11 Call Type Indicator 1 Ascii Char

12 Maturity 2 Ascii Char

Change Room Occupancy Status:

A request by the receptionist to change the Room Occupancy status of the station.
PMS to PBX
• STX-28-Message Count-1-Station Number-Room Occupancy Status -ETX-BCC
Where,
Room Occupancy Status; 1=Occupied, 2=Vacant, 3=Reserved, 4=Guaranteed

PBX to PMS • ACK or

NAK or
STX-28-Message Count-0-ETX-BCC

Mini Bar:
The maid transfers the details of the Mini Bar then the PBX to the PMS by issuing the command 1056-
Item Number-Item Quantity for the station.
PBX to PMS • STX-51-Message Count-1-Station Number-Item Number -Item Quantity-ETX-BCC
Item Number is from 00 to 99.
Item Quantity is from 00 to 99.

PMS to PBX • ACK or

NAK or
If none of them is received before the acknowledgement timer decreases to zero
the next operation begins.

User Defined Field

When SA command for User Defined field or Feature access code for the same is dialed from station
following message shall be sent to PMS
PBX to PMS • STX-52-Message Count-1-Station Number-User Defined Fields-ETX-BCC
Where,
User Defined field can be of maximum 78 digits. Where 0 to 9, # and * are valid
digits.
PMS to PBX • ACK or
NAK

Message Wait:
Message wait can be set by the VMS or a station of the PBX. This should be informed to the PMS.
PBX to PMS • STX-53-Message Count-1-Station Number-Flag-ETX-BCC
Where,
Flag 0 = Message Wait Cancel,
1 = Message Wait Set,
2 = Message Wait to served.

PMS to PBX • ACK or

NAK

Alarm:
Alarm can be set/cancel by the guest. This should be informed to the PMS.
PBX to PMS • STX-54-Message Count-1-Station Number-Flag-ETX-BCC
Where,
Flag 0 = Alarm Cancel, 1 = Alarm Set, 3 = Alarm Acknowledgement,
4 = Alarm not Answer
2 is not used.

PMS to PBX • ACK or

NAK

Room Clean Status:

Room clean status can be updated by the SA. This should be informed to the PMS.
PBX to PMS • STX-55-Message Count-1-Station Number-Room Clean Status-ETX-BCC
Where,
Room Clean Status: 1= Maid Present, 2=Dirty, 3=Clean, 4=To be Inspected, 5=
Out of Service

PMS to PBX • ACK or

NAK