V20 - Forcing In/Out Office status Codes (aka *64)

[SimoneR]

Hi,
We upgraded to v20 and modified all the ring groups or IVRs according to the new functions, but now we've got an issue when forcing in/out office status.
I've seen that there is now a new function to force the status on the app independently for each department that seems working correctly.
The old code used till v18 (*641, *642 and *64) does not affect the call routing of any department, even if we receive the vocal confirmation by pbx.
I've noticed that the related code setting is now absent on the codes page; is this function still operational? If not, will in the future?
If yes, at which levels act?

Many thanks

 

[jclark]

Have you checked previous replies in this post for using the web client in order to Force the Office hours ?

This will not work for my client, they do not use the Web Client at all. Even if I could get them to use it which isn't possible as they don't have computers where the phone it, it would be to difficult for them. Plus the webclient only allow you to set it for so long.

 

[TheodorosG_3CX]

As per previous replies this will be available with the API as per guideline here.

 

[jclark]

As per previous replies this will be available with the API as per guideline here.

As per previous replies, this doesn't work if it's hosted. So this doesn't help me. So whats your solutions / fix for those customers?

 

[techforceuk]

Regarding your question, the dial codes to force the system in and out of office hours are not available in v20.

This feature is now under the department level and is triggered by the web client or PWA logged in with a user who has the appropriate role to override office hours:

I don't understand why this basic feature of a phone system has been removed. My customers need to be able to switch between day/night from a phone not a PC. This has caused massive problems been forced to "upgrade" to V20 to then have a needed feature removed.

 

[Evolute IT]

I don't understand why this basic feature of a phone system has been removed. My customers need to be able to switch between day/night from a phone not a PC. This has caused massive problems been forced to "upgrade" to V20 to then have a needed feature removed.

https://www.3cx.com/docs/call-api-linux/#h.nx3a0hqytc3w

 

[Taptoo]

As per previous replies this will be available with the API as per guideline here.

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

 

[erectaat]

I tested it right now while upgrading and i confirm it works correctly.

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

Yes it's a almost dev function but it works fine (even on standard that theorically has no Call Flow - Aka "Call Processing Script" - functions).
P.S. Remember to update the BLF to the new non-modifiable codes #61 (IN office) or #62 (OUT of office)

 

[TheodorosG_3CX]

@erectaat Thank you for information and i'm glad this is working as expected.
Keep in mind that the Call Processing Script will keep updating with more and more capabilities.

 

[NicholasP_3CX]

Please keep in mind that the dial code will put ALL departents to out of office. To be able to do this PER department you will still need to use the web client.

 

[doncol]

For self hosted you can enable the dial codes in v20. You can enable the dial codes for system mode by adding the prefix (eg. *64) as the value to the DIALCODEOUTOFFICE parameter (Admin | Advanced | Parameters). Then the dial codes can be used as before and assigned as custom speed dial entries to DSS buttons. *641 = In Office; *642 = Out of Office; *64 or *640 is system default hours.

 

[hlubiak]

We just ran into the same issue. was able to fix it with the predefined scripts in my attachment. it pretty basic but should be easy to follow. version 20. hope this helps all. just tired of being told we removed that feature.

 

[akeynes]

We just ran into the same issue. was able to fix it with the predefined scripts in my attachment. it pretty basic but should be easy to follow. version 20. hope this helps all. just tired of being told we removed that feature.

We need the same functionality, but on a per-department basis.

The 'ForcePBXHours' example scripts look like what we need, however it overrides for *all* departments and not just the current department which doesn't make much sense given that office hours are per-department in v20.

Checking the scripts the "ps.GetAll<Group>().Where(x=>x.AllowCallService).Select(x=>" line seems to be what we would need to change as i'm assuming Group == Department.

In theory, we just need to modify that to limit it to whatever the current department is based on the current call in progress - i'm struggling to find any kind of documentation on how to accomplish this however?

The included HTML help in the call control API zipfile isn't really much help, it's just autogenerated class docs with some very brief descriptions but nothing on how it all hangs together.


Anyone got links to better documentation or pointers on how to accomplish this?

 

[Evolute IT]

We need the same functionality, but on a per-department basis.

The 'ForcePBXHours' example scripts look like what we need, however it overrides for *all* departments and not just the current department which doesn't make much sense given that office hours are per-department in v20.

Checking the scripts the "ps.GetAll<Group>().Where(x=>x.AllowCallService).Select(x=>" line seems to be what we would need to change as i'm assuming Group == Department.

In theory, we just need to modify that to limit it to whatever the current department is based on the current call in progress - i'm struggling to find any kind of documentation on how to accomplish this however?

The included HTML help in the call control API zipfile isn't really much help, it's just autogenerated class docs with some very brief descriptions but nothing on how it all hangs together.


Anyone got links to better documentation or pointers on how to accomplish this?

DM me, I understand those scripts well.

 

[JulienM]

We need the same functionality, but on a per-department basis.

The 'ForcePBXHours' example scripts look like what we need, however it overrides for *all* departments and not just the current department which doesn't make much sense given that office hours are per-department in v20.

Checking the scripts the "ps.GetAll<Group>().Where(x=>x.AllowCallService).Select(x=>" line seems to be what we would need to change as i'm assuming Group == Department.

In theory, we just need to modify that to limit it to whatever the current department is based on the current call in progress - i'm struggling to find any kind of documentation on how to accomplish this however?

The included HTML help in the call control API zipfile isn't really much help, it's just autogenerated class docs with some very brief descriptions but nothing on how it all hangs together.


Anyone got links to better documentation or pointers on how to accomplish this?

Hello,
I am also interested in modifying this script so that the schedule change is limited only to the user's default department who initiates the call.