RemoteWaitEntry Service

The RemoteWaitEntry service allows a client to be notified when parties are added to the wait list using an LRS device, such as a T900.

Wait Entry

Using a device such as a T900, parties may be added to the waitlist. When the party is added, the LRSN will send clients connected to the RemoteWaitEntry service a <RemoteWaitEntry> message. The client will then respond with a <RemoteWaitEntryAck> message. The <RemoteWaitEntryAck> contains a
status code that indicates if the wait entry was accepted.

📘
For full remote wait entry functionality on the T900, the client should also subscribe to the TableMan service to provide wait time information to the T900.

Sent from the LRSN server to the client when a wait list item is added on a remote device such as a T900.

Attribute	Description	Details
id	Transaction ID to be included in `<RemoteWaitEntryAck>` message	Always present
action	Action remote wait entry device is taking. Currently, the only supported action is `add`, which adds an entry to the wait list.	Always present
size	Size of party.	Always present for `add`
seatingpref	Seating preference of party. Possible values are `Smoking`, `Non-smoking`, and `First Available`.	Always present for `add`
name	Name of party.	Always present for `add`
pager	Pager (or mobile phone) guest has been assigned. The pager attribute consists of two semi-colon delimited values. The first value is a number indicating the type of pager the guest has. The second field indicates the actual pager number or mobile phone number assigned to the guest. Possible values for the pager type are: `2` - LRS Guest Pager (Coaster Call, Adverteaser, Specialty pagers) `5` - Mobile Phone	Always present for `add`
src	The `src` attribute indicates the source of the remote wait entry request. The `src` is string, the exact format and meaning of which depend upon the type of device and it’s configuration. However, a device will always have the same src value.	Always present

<!-- Need a description of this example -->

<RemoteWaitEntry id="57" action="add" size="2" seatingpref="Non-smoking" name="Geoffrey" pager="2;16" src="NEED TO ADD THIS>

<!-- Guest added with a mobile phone -->

<RemoteWaitEntry id="23" action="add" size="4" seatingpref="First Available" name="Jenny" pager="5;8675309... NEED REST OF THIS EXAMPLE >

The client acknowledges receipt of a <RemoteWaitEntry> message with a <RemoteWaitEntryAck> message.

Attribute	Description	Details
id	Value of id attribute form `<RemoteWaitEntry>` message	Always present
ret	Return value of `<RemoteWaitEntry>` operation. If not present, `ESUCCESS` is assumed. Possible values include `ESUCCESS`, `EDUP` if entry is not accepted because it is a duplicate, and `EOPFAIL` for general failure.	Optional

<RemoteWaitEntryAck id="23" ret="0" />