Best practice for "DND" only for external calls

[A.Takacs]

Hi

Probably a newbee question but bear with me... v20 here. What is the best practice to setup a "Do not Disturb" status only for external calls ? Ie external call would go to voice mail or whatever but internal would still ring "normaly".

 

[Guillaume Bourgeois]

Hello,
3CX does not offer a "Do Not Disturb" option that affects only external calls, but you can achieve a similar result using exception rules. You can target a range of phone numbers to be redirected to voicemail.
For example, if you notice that all the numbers in your call history start with 1 (E.164), you could create a range like this.





Don't forget to cover scenarios where calls come from anonymous numbers.

 

[bitn2]

Or you can use 1 department for 1 user and assign the did to the department. The user is still avaiable after hours for internal calls and external calls are going to voicemail or anything else.

 

[A.Takacs]

Thank for the suggestions - some I have not thought about.

Ideally I'd like it to be an user-selectable status (per 3cx terminology). Not quire sure any of those would work if I want to keep the normal built-in one and define it as a custom one (again might be missing something),

 

[Guillaume Bourgeois]

This request has been made in the past, and what you are asking for is not possible.

Thread 'Status - Accept internal calls and forward external calls' https://www.3cx.com/community/threa...-and-forward-external-calls.86729/post-409271

However, upon detailed analysis of the 3CX CallControlAPI, there is a property documented for future use (not currently available) in the forwarding profiles called 'ForceInternal.' There are no details provided, but we can infer from the name that it might allow a different action for internal calls than the default behavior. Without wanting to give false hopes, I must mention that this is only a clue; nothing indicates it is for this purpose, nor when or if it will be implemented.




@ConceptsWeb
Do you know anyone at 3CX who could tell us what is planned for this property ?

 

[Evolute IT]

This request has been made in the past, and what you are asking for is not possible.

Thread 'Status - Accept internal calls and forward external calls' https://www.3cx.com/community/threa...-and-forward-external-calls.86729/post-409271

However, upon detailed analysis of the 3CX CallControlAPI, there is a property documented for future use (not currently available) in the forwarding profiles called 'ForceInternal.' There are no details provided, but we can infer from the name that it might allow a different action for internal calls than the default behavior. Without wanting to give false hopes, I must mention that this is only a clue; nothing indicates it is for this purpose, nor when or if it will be implemented.

View attachment 42850


@ConceptsWeb
Do you know anyone at 3CX who could tell us what is planned for this property ?

Maybe Ernesto knew before he left. Otherwise, not sure. It's an Integer so it's hard to tell what values will be allowed/possible.

 

[bitn2]

Thank for the suggestions - some I have not thought about.

Ideally I'd like it to be an user-selectable status (per 3cx terminology). Not quire sure any of those would work if I want to keep the normal built-in one and define it as a custom one (again might be missing something),

Than you need to use an ringggroup per user with just the user in there. Than configure your status to except calls from ringgroups and forward the internal calls to the ringgroup.

 

[noord]

We would need a 'ring my phone' normally option here then:

 

[Guillaume Bourgeois]

We would need a 'ring my phone' normally option here then:
image.png

If your intention is to "formally request" a feature that is not currently available, please use the designated topic for such requests :
https://www.3cx.com/community/forums/server.73/
Do a search before creating a new suggestion ; perhaps someone has already posted the idea, and you can simply vote on it.

* However, you will need to find a Gold, Platinum or Titanium partner to make the post, as logically, only the most committed partners are allowed to publish ideas.
Everyone is eligible to vote.

 

[A.Takacs]

@Guillaume Bourgeois so you are implicitly confirming that this is actually not possible, not even in conjunction with the "mysterious" ForceInternal property ?

 

[Guillaume Bourgeois]

@Guillaume Bourgeois so you are implicitly confirming that this is actually not possible, not even in conjunction with the "mysterious" ForceInternal property ?

The **ForceInternal** property (not yet available) is part of a list with other properties that can be manipulated, for example, through the CallFlow Designer (and not via a graphical user interface). That said, generally, when parameters are accessible via an API, they are also visually available in the graphical interface.

That being said, we still don't know what this property will actually do or if it will even be developed.

Maybe @edossantos_sipcaller has heard about this property ?

I would be surprised, though, since it's not directly related to CFD and CRM.

Alternatively, instead of using the graphical interface, would a code-based approach (dial code) be an acceptable solution?

If so, I can certainly help you build a CallFlow that could add/remove exception rules without changing the status (Available). This would effectively route calls to voicemail without the need to manually add exception rules.