EXCEPTIONS - V20

[a.gubbiotti]

Good evening,

I would need some clarification on how the "Exceptions" of an extension can be managed, in version 18 I used to use fake extensions that I called "dummies" which through the use of "exceptions" managed the flow of calls depending on the time therefore there were as many flows as possible, allowing you to divide the day into several times and direct the call to different entities depending on the time.

In version 20 there is no longer this possibility but only the use of the program item which, based on the time, changes the status of the extension of interest but if it has not logged in some way (Apps, telephones etc..) therefore if it is not registered the change of status does not work.



Is there a feature that can help me or emulate these "exceptions"?



I await a response

Greetings

 

[Charles_3CX]

You can use a simple call flow to achieve this: https://www.3cx.com/docs/manual/call-flow-designer/ and the specific project is https://www.3cx.com/docs/cfd-routing-calls-time-day/.

I can also inform you that the exceptions will be updated to bring back the specific time choices in a future update. We do not yet have an ETA for when it will be.

 

[AWS2P]

I can also inform you that the exceptions will be updated to bring back the specific time choices in a future update. We do not yet have an ETA for when it will be.

Hello, so does this implies when exceptions are used on V18 it's urgent not to migrate V20 and wait for future release update to bring back full feature ?

 

[Charles_3CX]

Hello, so does this implies when exceptions are used on V18 it's urgent not to migrate V20 and wait for future release update to bring back full feature ?

If there are any features that you use in v18 that are not yet available in v20, don’t update!

 

[TheodorosG_3CX]

@a.gubbiotti @aws2p Exceptions with more capabilities are now available in the new V20 Update 1