Room number translation

The DV2000/DV4 provides the ability to translate from the room (or extension) numbers sent by the PMS to the mailbox numbers used by the VMS, and vice-versa. This done using a translation table that maps the room number directly to the mailbox number using simple substitution.  For sites with multiple PMS instances, there is a separate hospitality server instance for each PMS, each with its own configuration (including its own translation table).

Note:  The general (or default) translation table is not used for PMS translations.  It is only used to translate extension numbers coming from the PBX (and possibly those dialed by callers in the auto attendant).  Likewise, the PMS translation tables are only used to translate to and from the PMS; they are never used when communicating with the PBX, not even for phone control or PMS pass-through.

Configuration

The configuration of PMS translation table is covered Translation section under System Configuration | Configuring Features | Hospitality.

Room to Mailbox Translation

On receipt of any message packet from the PMS, if the message contains a room number the system will perform a forward lookup in the translation table.  If the given room number is found, it will be replaced with the associated mailbox number before the command specified by the message is processed.

The PMS translation table provides a many-to-one relationship for room numbers to mailbox numbers.  This means that every room number maps to one and only one mailbox number, but multiple different room numbers can map to the same mailbox number.  For example, the following translation table is entirely valid:

In this case, the room numbers 71101, 81101 and 21101 all map to mailbox 1101.  This is valid.

Room vs. Extension Numbers

In some cases, a room may have multiple physical phones, each with its own extension, and the PMS may be sending commands with extension numbers rather than room numbers.  This can be handled using a translation table similar to that shown above.  In this case, 71101, 81101 and 21101 are all extensions in room 1101 and the PMS may send a check in for each extension rather than a single check in for the room number.  Using a translation table like this allows the VMS to map all 3 extensions onto one mailbox.

PBX Link Does Not Use Translations

If a PBX link is also being used to pass phone control states, name changes, and so forth to the PBX, you would need to assign each extension to the MWI address fields in the mailbox as well, because translations are not supported for the PBX link.  In this example above, you could assign 71101 to the address MWI 1, 81101 to MWI 2 and 21101 to MWI 3, all in mailbox 1101.  If there is a hunt group associated with the room, say 1101, then you should assign it to the Office Extension address (which will also assign it to MWI 0 automatically).  The Office Extension address is used when dialing wakeup calls, so it should always be used for the extension (or hunt group) that should be called for the wakeup call.

Mailbox to Room Translation

Whenever the VMS needs to send a message to the PMS for a room, it will perform a reverse lookup in the translation table to get all room numbers associated with the given mailbox number.  A message will then be generated and sent to the PMS for each room number found.

Using the example in the previous section, if the VMS needed to pass a maid status change on to the PMS for mailbox 1101, it would look for 1101 in the translation table (searching on the mailbox number field).  It would find 3 entries, for rooms (or extensions) 21101, 71101 and 81101.  It would then send a maid status update message for each one.  The same process would apply for MWI (voice message count) updates.

If no translations are found for a given mailbox number, then a single message will be sent using the mailbox number as the room number.