Create an inbound rule to a user extension in v20

[contoured_solutions]

Greetings,

Like many folks, I have been in the process of moving my customers to v20 over this past month or so. I am running into an issue and was hoping to get some feedback.

In v18 and below, you could create inbound rules which allowed you to assign an extension (among other things) as a destination. It no longer seems possible to simply create an inbound rule where the destination is a user extension, you need to assign a number as a DID to that user's extension. The trouble is that, with one particular customer, I need inbound calls to go to a user extension, but still be able to control where that inbound call goes to after hours. This can easily be done when the inbound destination is a ring group, call queue or digital receptionist, but not a user extension. Any advice?

 

[Jason_H]

This can be done in the users call forwarding rules, by status if they are on auto schedule, or diligent about changing their status.

If they keep their status available all the time you would have to create an exception, also under call forwarding.

 

[contoured_solutions]

The problem is that I am already using the call forwarding rules for this user extension. The client wanted a solution for multiple users to be able to control where the inbound calls a directed. To solve this, I created an extension which forwards to different destinations depending on the status which then allows users to easily redirect inbound calls from the main number.

 

[Les Webb]

Creating a Department is the way I've done this. Assign the DID to the Department and then you have the call forwarding rules you need

 

[providencetg]

The problem is that I am already using the call forwarding rules for this user extension. The client wanted a solution for multiple users to be able to control where the inbound calls a directed. To solve this, I created an extension which forwards to different destinations depending on the status which then allows users to easily redirect inbound calls from the main number.

I agree with you on this. There are times when changes make for progress but I fail to see how this does in this case. Managing it from the user's call forwarding rule is not ideal in many cases because you want to ensure that it does not change. You were able to do this with inbound rules in 18. Yeah, department is a work around but at this stage of the game, we should not need a work around for something like this.

To me, it's almost like a completely different team developed v20 that had no understanding of v18 functionality and important features to manage systems in a production environment. To add to this, while 3CX is pushing this upgrade, we are trying to manage our client relationships, which has not been going well.