Posting here because I don't have sufficient privileges to post in the ideas section. Apologies.
We are a property management systems provider for hospitality customers and one of our modules is hotel management. We are emulating the FIAS (Fidelio) interface and have implemented all of the hospitality features that 3CX supports, with a slight gotcha when it comes to wake up calls.
Our system (and I am sure we are not alone) allows a receptionist to schedule multiple wake up calls from our software over the duration of the guest stay (e.g. Monday 06:00, Tuesday 07:30, Thursday 06:00). The gotcha I have encountered is that 3CX seems to only support one wake up call per room, and will replace any existing scheduled wake up call with the most recent one sent. In my example, if the wake up calls were set in our system in the order Monday, Thursday, Tuesday then the only wake up call which 3CX will deliver would be Tuesday at 07:30 because that was the last one saved.
We have worked around this limitation in our interface with a bit of clunky periodic querying of our system and determining if the last wakeup request we sent to the PBX is in the past and if a newer one exists to send another wake up request to the PBX for the "next" one. This is a bit of a hack though, and the development suggestion would be to allow multiple wake up requests per extension as per my example. The FIAS protocol allows for this scenario (you can send multiple WR (wakeup request) and WC (wakeup cancel) messages with different dates and times and there is also a function to clear all wakeup calls which have been set for a room number).
We are a property management systems provider for hospitality customers and one of our modules is hotel management. We are emulating the FIAS (Fidelio) interface and have implemented all of the hospitality features that 3CX supports, with a slight gotcha when it comes to wake up calls.
Our system (and I am sure we are not alone) allows a receptionist to schedule multiple wake up calls from our software over the duration of the guest stay (e.g. Monday 06:00, Tuesday 07:30, Thursday 06:00). The gotcha I have encountered is that 3CX seems to only support one wake up call per room, and will replace any existing scheduled wake up call with the most recent one sent. In my example, if the wake up calls were set in our system in the order Monday, Thursday, Tuesday then the only wake up call which 3CX will deliver would be Tuesday at 07:30 because that was the last one saved.
We have worked around this limitation in our interface with a bit of clunky periodic querying of our system and determining if the last wakeup request we sent to the PBX is in the past and if a newer one exists to send another wake up request to the PBX for the "next" one. This is a bit of a hack though, and the development suggestion would be to allow multiple wake up requests per extension as per my example. The FIAS protocol allows for this scenario (you can send multiple WR (wakeup request) and WC (wakeup cancel) messages with different dates and times and there is also a function to clear all wakeup calls which have been set for a room number).
