The following list contains the type of messages sent from the PMS to the system, and from the system to the PMS.
PMS messages can be used to manage a Suite or Linked Suite in the same manner as managing a Room except using the Suite Pilot number or Linked Suite Pilot number of the guest room extension (where applicable).
|
PMS to System |
System to PMS |
|
Enquire |
Enquire |
|
Acknowledgment |
Acknowledgment |
|
Negative Acknowledgment |
Negative Acknowledgment |
|
Are You There |
Maid Status |
|
Check In/Check Out Message |
Message Registration |
|
Message Waiting |
Message Waiting |
|
Wake-Up |
Alert |
|
Credit Limit |
Request to Initialize |
|
Station Restriction |
|
|
Name |
|
|
Name Transfer |
|
|
Affiliation |
|
|
Location |
|
|
Suite Messages |
|
|
General Reset |
|
|
End |
|
These are messages using single byte ASCI characters:
Enquire (ENQ) – ASCII character HEX 05 – This characters is sent from the PMS to the System or from the System to the PMS to indicate that the sender would like to initiate a transmission to the receiver. All transmission messages must be preceded by ENQ.
Acknowledgement (ACK) – ASCII Character HEX 06 – This character is sent to acknowledge that the previous message was accepted. See Protocol description for more details.
Negative Acknowledgement (NAK) – ASCII Character HEX 15 – This character is sent to indicate that the previous message was not accepted. See protocol description for more details.
These messages have the following general format:
Each box represents 1 byte. Each data message is prefaced with an STX (the ASCII character for start-of-text) and is completed with the character ETX (the ASCII character for end-of-text). The characters mentioned in the messages below are all in upper case, unless otherwise stated.
If the extension number is less than 5 to 7 digits in length, it is padded with blank characters. For messages sent from the system to the PMS, blanks are padded on the RIGHT side. For messages sent from the PMS to the system, blanks are padded on the LEFT or RIGHT side, but not both. The space character (ASCII 32, HEX 20) must be used.
Note: Extension length can be changed from 5 to 7 digits in the Hotel Options form. The examples in this topic reflect the 5-digit length.
Note: If an older PMS application that supports the 5-digit DN format only receives a message in the 7-digit format, the PMS application identifies the message as invalid. In such cases, in accordance with existing PMS protocol behavior, the PMS application responds with a Not Acknowledged (NAK) message.
This message is sent by the PMS to ensure that the system is still responsive.
Check In operations include:
changing the Call Restriction to Local or Long Distance, according to the Hotel Options form (see figure)
setting the Call Block to be affected or unaffected, as specified in the Hotel Options form
resetting the Message Registration to zero.
deleting the Wake-Up
Name, Affiliation, and Location fields: These are treated according to the "Keep Teldir Entry on Checkout" option. In SX2K and Pre-8.0 3300, this is a COS option and when enabled, these fields are maintained as is. With the option disabled, the Teldir entry is deleted. In 3300 8.0 and above, the option "Keep Teldir Entry" is a per guest room option. With the option enabled, these fields are maintained as is. With the option disabled, the Teldir entry is re-initialized with a blank entry.
Check Out operations include
resetting the Message Registration to zero
setting the Call Restriction to the Check Out value defined in the Hotel Options form
clearing any pending Wake-Up calls
setting the Call Block value to the Check Out value defined in the Hotel Options form
clearing any Do Not Disturb functions
clearing the Message Waiting lamp
having all messages deleted against this guest, in systems using Message Center.
Name, Affiliation, and Location fields: These are treated according to the "Keep Teldir Entry on Checkout" option. In SX2K and Pre-8.0 3300, this is a COS option and when enabled, these fields are maintained as is. With the option disabled, the Teldir entry is deleted. In 3300 8.0 and above, the option "Keep Teldir Entry" is a per guest room option. With the option enabled, these fields are maintained as is. With the option disabled, the Teldir entry is re-initialized with the default entry. For more information on the default entry, refer to 3300 documentation.
Note: If you are using Suite Services, check in and check out functions must be performed on Suite Pilot Numbers, not on individual suite extension numbers.
The message has the following format:
where:
X is the Check In/Out status code:
ASCII character 1 for Check In
ASCII character 0 for Check Out
SP is the ASCII blank character
n is an extension number digit in ASCII
The format of this message is the same for both directions. The status code sets the new state of the message waiting lamp. If from the PMS to the system, this message indicates that the room's message waiting lamp is to be turned on or off to indicate the presence of a non-voice mail message for the occupant. From the system to the PMS, the message indicates that voice mail or a source other than the PMS turn the message waiting lamp on or off.
The Message Waiting message has the following format:
where:
SP is the ASCII space character
X is the Message Waiting Lamp status code
ASCII character 1 for Lamp On
ASCII character 0 for Lamp Off
n is an extension number digit in ASCII
The PMS system can inform the system to set a wake-up call for a particular guest station. Wake-up calls can be programmed against guest rooms, suite pilot numbers and suite members but cannot be programmed against Linked Suite Pilot numbers.
The Wake-up message has the following format:
where:
t is the wake-up time digit in ASCII
n is an extension number digit in ASCII
The wake-up time is specified in 24 hour time. All four characters, filled with ASCII spaces, represents a wake-up deletion.
The PMS uses a Credit Limit message to set a credit limit on a guest room or suite. The system does not make any call restriction decisions; the PMS is solely responsible for informing the system of any action to take in regards to credit limit exhaustion.
Note: Emergency Services (911/999) and internal calls are never restricted.
Credit limit support works in conjunction with the existing Surcharge and Multiplier values described in Using Message Registration system documentation. One or both of these fields must be given values in the Hotel Options form in order to use the Credit Limit or Alert messages. Totals calculated using the Surcharge and Multiplier values may be printed at any time.
Note: When a credit limit is applied to a Linked Suite, it is applied in full to each member suite. For example, if a $100 Credit Limit is applied to a Linked Suite consisting of 3 Member Suites, each Member Suite may make up to $100 in calls for a total of $300 for the Linked Suite.
A Credit Limit message has the following format:
where:
1 is the Credit Limit status code in ASCII
SP is the ASCII blank character
X is an guest room or suite pilot digit in ASCII
NNNNN is the maximum monetary units available (maximum 50000) in ASCII
An Alert message is used by the system to notify the PMS when the established telephone credit limit has been reached. The PMS may then send a Station Restriction message to the system to apply previously programmed Class of Restriction parameters (calls in progress are not affected when a credit limit is reached).
An Alert message has the following format:
where:
1 is the Alert Message status code in ASCII
SP is the ASCII blank character
X is an guest room or suite pilot digit in ASCII
A Station Restriction message can be used to establish call restrictions. When this message is sent from the PMS to the system, it brings predefined Call Restrictions into effect as programmed in the Hotel Options.
Note: Emergency Services (911/999) and internal calls are never restricted.
The Station Restriction message has the following format:
where:
S is one of the following status codes in ASCII:
0 – Internal
1 – Local
2 – Long Distance
3 – Option 1
4 – Option 2
5 – Option 3
X is an guest room or suite pilot digit in ASCII
This message is sent from the PMS and is used to program the Telephone Directory of the system with the guest's name. If using Suite Services, the Name associated with a Linked Suite should also be programmed as the Affiliation of each Member Suite.
The Name message has the following input format:
where:
SP is the ASCII space character
c is a character of the NAME string (maximum 21 characters) in ASCII
n is an extension number digit in ASCII
X is the operation code. Use of the string operation code allows for addition and deletion of a specific name against an extension. The String Operation code is the first byte of the status code, and may be one of these options :
ASCII Character 1 - (addition) – the name is ADDED to the current list of names against this station. If there is no name against this number, a new telephone directory entry is created.
ASCII Character 2 - (replacement) – the name is used to REPLACE the first name found against this number. All other names against this number are not altered
ASCII Character 3 - (deletion) – all names associated with the specified extension number are DELETED from the telephone directory. The name in the message is ignored by the system.
ASCII Character 4 – (transfer) – See below.
The maximum length of the NAME field is 21 characters. The NAME string is left-justified within the NAME field, and padded with spaces (between name and extension number.) The length of a name can be up to 20 characters. If the name is 20 characters, the 21st character must be an ASCII space. The string can contain ASCII characters (lower case letters, upper case letters and numbers with the exception of square brackets "[" and "]" and pipe "|".) If the NAME string does not contain a comma, the string is treated as a LASTNAME. If the NAME string includes a comma, it is treated as the form LASTNAME,FIRSTNAME. When a comma is used, the total length of the string can be 21 characters. The comma cannot be in the 1st or 21st location, and the string cannot contain more than 1 comma.
When interfacing with a 33000 ICP 8.0 UR4, if there are spaces between the LASTNAME and FIRSTNAME (i.e. LASTNAME , FIRSTNAME), the spaces will be removed by the system (i.e. LASTNAME,FIRSTNAME.) However, when interfacing with an SX2000 or an earlier version of 3300, no spaces are permitted immediately before or after the comma. These will result in unpredictable behavior.
If there are multiple space-separated strings in either the LASTNAME or FIRSTNAME (i.e. a two part first or last name, for example, LASTNAME,MARY JANE) then these spaces are maintained intact.
This message is sent from the PMS to instruct the system to move the specified name from one extension to another extension. This function will not transfer room associated data such as COS, COR, interconnect number, room status, wake-up time, and meter unit totals.
Note: The Message Center messages will follow the name from one room to another.
The Name Transfer message has the following input format:
where:
c is a character of the name in ASCII
n is an extension digit number in ASCII (maximum 5 or 7 digits total)
This message is sent from the PMS and is used to program the Telephone Directory of the system with the guest's affiliation. This is displayed in the Telephone Directory form under Department. The words department and affiliation are synonymous within this text.
Linked Suite names should be programmed in the Telephone Directory as the department/affiliation for each Member Suite.
The Affiliation message has the following input format:
where:
X is the string operation code, with the same definitions as the NAME message
ASCII Character 1 - (addition) – the name is ADDED to the current list of names against this station. If there is no name against this number, a new telephone directory entry is created.
ASCII Character 2 - (replacement) – the name is used to REPLACE the first name found against this number. All other names against this number are not altered
ASCII Character 3 - (deletion) – all names associated with the specified extension number are DELETED from the telephone directory. The name in the message is ignored by the system.
SP is the ASCII space character
c is a character of the department (maximum 10 characters) in ASCII
n is an extension number digit in ASCII
The length of the affiliation can be up to 10 characters and only one string may be used. It is left-justified, with blanks used for padding. A telephone directory entry is considered a unique name-telephone number pair.
For example, consider the following Telephone Directory form.
|
Name |
Telephone Number |
Department |
Location |
Prime |
|
Green, Jayne |
120 |
Trillium |
March |
No |
|
Smith, Joe |
120 |
Mitel |
Kanata |
No |
Both Joe and Jayne share the same telephone number. However, they can each have a corporate directory entry with its own department and location as shown above.
The PMS/System interface allows the entry of multiple names and departments against the same telephone number. This is done by having the department message described above immediately follow a name message. If the telephone number on the department message matches the telephone number on the earlier name request, the department is added to this name-number combination.
Assuming extension 120 does exist on the system, the following PMS to system messages can be sent to enter both Joe and Jayne into the PBX's corporate directory.
The ADD and REPLACE operations for the DPT function code perform the same function. That is, they take the current department and replace it with the given string.
The location message allows a location to be entered against a telephone directory entry. The functionality is much the same as the department message except for the following message format.
The Location Message has the following input format:
where:
LOC is the location function code
X is the string operation code, with the same definitions as the NAME message
ASCII Character 1 - (addition) – the name is ADDED to the current list of names against this station. If there is no name against this number, a new telephone directory entry is created.
ASCII Character 2 - (replacement) – the name is used to REPLACE the first name found against this number. All other names against this number are not altered
ASCII Character 3 - (deletion) – all names associated with the specified extension number are DELETED from the telephone directory. The name in the message is ignored by the system.
SP is the ASCII space character
c is a character of the location (maximum 10 characters) in ASCII
n is an extension number digit in ASCII
To enter a location against a specific telephone directory entry, use the following PMS messaging scheme:
To enter a name, department, and location against a particular extension, use the following messaging sequence. To create a unique telephone directory entry, the first message of the triplet must be the NAM1 message. The department and location can follow in any order. They must however, not be interlaced with name, department, or location messages for other telephone numbers.
Note: For Name, Location, and Affiliation messages, Hotel Class of Service is not required.
A Linked Suite may be formed, added to, deleted from, and dissolved using an available Linked Suite Pilot number. Upon formation of a Linked Suite, the provision of Shared Telephone Services (STS) is active or inactive. Member suites may be checked in or out during provisioning of Linked Suites or independently.
Note: Although both PMS and CDE (SX2000) or ESM (3300) can be used to manage Linked Suites at the same site, we recommend using a PMS system. Guest Services cannot be used to provision Linked Suites at this time.
The general suite message has the following format:
where:
STE is the Suite function code
N is one of the following Suite function variables:
0 for create linked suite, check in, no STS
1 for create linked suite, check in, STS active
2 for add suite, check in
3 for remove suite, check out
4 for breakdown linked suite, check out
5 for change linked suite pilot number, no check out
6 for add suite, no check in
7 for delete suite(s), no check out
8 for create linked suite, no check in, no STS
A for create linked suite, no check in, STS active
B for breakdown linked suite, no check out
SP is the ASCII blank character
X is an extension or suite number digit
The number of Member Suite Pilot Numbers is dynamic. Each Linked Suite and Member Suite Pilot number is 5 to 7 digits maximum in length. A maximum of 4 member suites may be included in a single Linked Suite message. If more than 4 members are included in a Linked Suite (maximum 32 members without STS), then several Suite Messages must be sent.
Each time a hotel extension makes a trunk call, the system sends a message to the PMS to update the total count of outside calls made against the guest room. No distinction is made between local and long-distance calls. Message Registration works by counting the number of meter pulses made over the duration of the call.
The Message Registration message has the following output format:
where:
SP is the ASCII blank character
n is an extension number digit in ASCII
The status code in this case is a fee or peg count. This is the one exception to the length of the status code, being 4 bytes instead of 2.
If the system does not receive a proper acknowledgment from the PMS, it generates a hotel log indicating the PMS is out of order. When the PMS is out of order, the system generates occupancy logs for every check in and check out operation.
The Maid Status message is sent to the PMS whenever the Room Status Condition attribute is modified. The Maid dials a Feature Access code and a new Maid Status code from a hotel extension. The attendant can also change the Room Status Condition from the console, and automatic updates can be done via CDE or ESM. The updates will also be sent to the PMS system.
If Suite Services is used, Maid Status messages can be invoked using any suite telephone and are applied to the Suite Pilot number.
The Maid Status Message has the following format:
where:
X is the maid status code in ASCII (See Below)
SP is the ASCII space character
n is the station number digit in ASCII
The Feature Access code that is dialed by the Maid changes the condition attribute of the Room Status as stored in the database of the system; it never changes the occupancy. When a Feature Access code is dialed, the system sends both a Function and Status code to the PMS, and the PMS should interpret the codes in the following way:
|
Maid Status Code |
Room Condition |
|
1 |
maid present |
|
2 |
clean |
|
3 |
not clean |
|
4 |
out of service |
|
5 |
to be inspected |
|
6 |
Occupied/Clean |
|
7 |
Occupied/Not Clean |
|
8 |
Vacant/Clean |
|
9 |
Vacant/Not Clean |
Maid Status codes 1 to 5 would typically be used by a hotel which does not use a PMS interface. Here, the Maid, or Room Supervisor would enter the appropriate code to update the system database. Maid Status codes 6 through 9 would typically be used by a hotel that uses a PMS. To ensure proper use of the codes, program the PMS to accept these messages and to produce a discrepancy report when one exists between the occupancy status as indicated by the Maid Status code and the actual occupancy as stored on the PMS database.
For example, a Maid cleans a room and notes that there are no signs of the guest still occupying the room. She enters the Maid Status Feature Access code and dials 8, indicating that the room is now vacant and clean. However, the PMS notes that the guest room is still occupied. At this point a discrepancy report is output from the PMS notifying the hotel personnel.
Note: Maid Status codes do not change the occupancy as stored in the database of the system. These Status codes result in a message being sent to the PMS, and are used to indicate what the Maid believes the occupancy status of the room is.
This message is sent by the PMS to indicate that it is beginning a database swap or general reset cycle. During this cycle the PMS will reset the system database to match the PMS's database. See PMS Recovery from Failure section below.
This message is sent by the PMS to end the GRS cycle. See PMS Recovery from Failure section below.
This message is sent by the system to recommend the PMS initiate a GRS cycle. This will be sent to the PMS only after a reboot of the system following the first communication from the PMS. See PMS Recovery from Failure section below.
