paul bennett

if you have moved the exts hasnt the class of service changed ?

acejavelin

Verify the COS for the room extensions is correct (using COS1 on a regular basis for Rooms in hopitality environments usually eliminates this issue). Then if you know the PMS system is functioning, have them issue an "Interface Resync" command to synchronize the PMS and 3300 systems. You could also have the front desk do a "Move" in the PMS system of these room, move it to a vacant room then move it back, this will usually update those rooms as well.

You could also try this command from the maintenance terminal (you may have to turn off AUTO COMPLETION), it works in the SX2000 so I would assume it will work in the 3300:

PCB KILL PROG pmsmgr

You should get a response that the program was killed. Then do a PCB STAT ALL and verify the process restarted, if it did not, issue this command:

PCB CREATE PROG pmsmgr

Careful using PCB, issued incorrectly it could cause, lets just say, erratic behavior of the system.

Of course, a RESET SYSTEM command works too, but not all PMS vendors support the 3300's RQINV request inventory command to resync the databases, so you may have to get the property manager or PMS tech support to issue a resync command anyway...

__________________
Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost.

This is Telephony’s First Law of Equivalent Exchange.

bobcheese

depending on the version of software check either the COS for the option 'hotel room extension' set to yes or if R9 (I think) or newer then check that the ext number is in the 'guest room assignment' form. If the ext is not set as a bedroom by one of these two ways then it wont allow the PMS to check in/out