v20 In/OoO override from phone app

Status
Not open for further replies.

UITcaf

Silver Partner
Basic Certified
Joined
Aug 1, 2019
Messages
15
Reaction score
2
had a client on v20 call today that out of office override wasn't working, so, we investigated...

after reading this thread:
https://www.3cx.com/community/threads/dial-code-641-or-642-dont-work-v20-upgrade-on-primes.127727/

it seems the claim is that #64 options -- #640 #641 #642 -- no longer work in v20. (even though dialing those codes clearly still plays a message telling the caller that the options ~are~ still working.)

this is completely unsustainable for many of our clients. not all of our clients use the webclient, or, even have devices that they can access the web client from.

MANY of our clients, in fact, we would hazard a guess to say that the MAJORITY of our clients, only use their desk phone or the mobile app to call #64x and set global in- or out-of-office overrides for their offices every. single. day. in fact, SEVERAL clients have #640/#641/#642 set up as hotkeys on their deskphones for ease of use/immediate access at the press of a button.

can these long-running, frequently-used, and client-expected features please be restored? if fact, the feature could even be improved in v20! dialing #640/#641/#642 could still just override the default/in/out status of ALL calls like it normally does. but then, depending on which group you belong to, NEW codes could be added (like #643/#644/#645) to set just the caller's group call routing to default/in-/out-of-office settings.

again, this all comes down to the fact that clients have relied on this feature for years; that they can use it from their phones only/from anywhere with just a phone, they don't need a web browser, a PC device, or even a webclient "login." (we even have some clients that do HAVE web browsing capabilities but explicitly DON'T want their employees using it for various reasons: security concerns, don't have the time and/or desire to spend resources training their staff on it, etc.)

or, at very least, the global and group overrides need added to the mobile app. (but, again, this still leaves clients just using desk phones completely lacking!!)

thoughts all? thank you for your consideration!!!
 
Last edited:
  • Like
Reactions: Evolute IT
quick aside/follow-up - even setting out of office in the web client under the profile menu's "override office hours" option does not seem to work...

we set that override to 15 minutes and it is now showing: "Current office hours: Office is closed Until 08/02/2024 12:14 PM "

BUT, when we call the client, it still is using the default/open office call routing.

so, thought on this as well? thanks again!!
 
I’ve found installing v20 sets OOO and holiday destinations to ignore office hours and accept call
 
thanks alphabetic. those options are intriguing! but, we do have some immediate initial concerns about those laborious work-arounds just based on the documentation itself:

Prerequisites
IMPORTANT: The following ~is meant to be run in a development environment,~ not on a production 3CX machine.

-these are all production machines

Linux
As a prerequisite, you will need to ~install a self-hosted or on-premise~ 3CX v20 for Debian 12.

-many clients on cloud hosting

and, even if the API could make it work, who pays for our time fighting to restore a feature clients have been using for over a decade? we don't want to eat the cost. and, our clients don't want to pay us to apply a workaround for a feature they have suddenly had taken away from them.

and, as per our previous post, the currently recommended webclient override option doesn't even seem to work right now as a quick-fix for client's that are complaining/that just want the feature to work again; preferably as close to the way it always has worked in the past without needing to resort to API workarounds for every client we have.

and, ultimately, if the option does truly exist in the API, then, it means it exists as a feature. simply adding it back as an option as an on/off setting in the admin portal (like it has always been until v20) would really resolve this quickly! (especially since v20 migrations are importing the previous v18 server's #64x settings but then it seems simply ignoring them unless you jump though the proposed API modification hoops.) basically that would be our major request... just add it back in the admin portal config menus/as default/as it has always been since the option clearly does obviously exist in the server code/API.
 
Last edited:
Even using the API to change the office hours is a GLOBAL option. This will perform the change across all the departments, which could clash with the department office hours.

Use this with caution.

The best method to change the departments office hours and force in or out remains the web client switch

1722859053231.png
 
Status
Not open for further replies.

Forum statistics

Threads
111,953
Messages
589,913
Members
164,847
Latest member
mike.carter.991