[psykomotor]

Hi,

After working through an issue with technical support, it transpires the following behaviour is by design:

- When all users in a ring group reject a call, the caller is cut off totally, not handled as per the 'Destination if no answer' setting.

We are about to deploy 3CX to a client who has a sales team with no technical background. We could instruct them not to press the 'reject call' button, but the information will most likely be forgotten, disregarded or totally ignored - simplicity to the end user is paramount in this environment.

We have the ring group set up to transfer to voicemail if the call is unanswered, but as it turns out, we have no control over the call if it is rejected.

My proposal is as follows:

Allow control over the 'Destination if rejected' - This would have the same options as 'Destination if no answer'.

I think there are very few scenarios in the real world where anyone would want someone calling into their organization to be cut off, so even using the 'destination if no answer' setting would surely be better, but having control as proposed would give the greatest flexibility.

[pcunite]

I am starting to see 3CX's short comings and I hope they address them.

* When a caller enters the PBX system, NEVER (caller's perception) let them leave it. You guide the caller's hand through any and all routes until you are forced to send them to voicemail.

The above 3CX fails at. It lets the caller now they are moving around, when you dial an external number it just gives up, it does not even care and all it's rules don't even matter at that point. Why have rules then?