Solved forwarding rule for external calls only

[bit101]

Hi togehter,

before the update to 3CX PBX version 16 Update 7 it was possible to set in the 3CX desktop client a rule for "Away" that
internal calls has to forward to the same extension and all external calls are forward to another extension.

Since the update when i set the rule "Away" -> Internal calls forwarding to -> same extensions it wont work. When i call the extension
from internally it does not ring. Neither the desk telephone nor the 3cx app.

What could be the reason?

Regards, beon

 

[JohnS_3CX]

Hello,

The fact that calling the extension internally shows that it wont ring, means that something other than the update is the issue.

Try to register your extension on the webclient, or better yet create a couple of test extensions (leaving their settings as default) and try your test scenario on them.


https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Also include information as per this post so we know what the setup is

 

[bit101]

Hi John,

no it shows nothing. When i try to call from the webclient internally it brokes the call. It doesn´t ring, simply nothing happens. When i switch back to "available" it works as expected.

The PBX Version 16.0.1078 is running on Debian 9 in a datacenter, locally we have an SBC with the newest version. We use Snom D385 Telephones with Firmware 10.1.54.16, the 3CX Clients are Webclient and Windows Deskop Clients.

 

[bit101]

I just created i new extension with Number 10. Then i set the rule for "away" for internal calls with the same extension 10.
When i call internally from extension 00 or 03 to 10 i get the logfile messages [CM303001]: Call(C:371); Forwarding loop detected: destination Extn10, path: [10]
The PBX says call "call failed".

But how can i set a rule that all internally calls shall ringing and all external calls are forward to another externsion?!

 

[Alphabetic]

What are you trying to acheive? You want to set a rule so that the call will be forwarded back to the extension it was ringing in the first place - why?

you cannot create a forwarding rule so that internal calls can get through but external calls cant

I would suggest going to the ideas section and upvoting

https://www.3cx.com/community/threads/choose-to-receive-internal-but-not-external-calls.49529/

 

[JohnS_3CX]

You cannot loop calls, so what you see it expected.

Ultimately what do you want to achieve?

 

[bit101]

Hi togehter,

we simply would like to achieve that an extension is "when desired" not available from external calls by forwarding to another extension and always available for internal calls during the business hours. How can we achieve that?!

Before the update to 16 update 7 we achieve that by set a loop to his self only for internal calls.

 

[ChrisC_3CX]

Hello @beon,

As a first note, please bear in mind that there is no actual option built-in to 3CX to enable the behavior you describe. You may however try the following workaround:

• Create a Ring Group and add the said extension as a member.
• In the Away Profile Status of that extension, have internal calls route to the Ring Group and the External forwarding to route to your desired destination.
• This should allow direct internal calls to that extension actually reach the extension via the Ring Group, since the Ring group calls will ignore the Profile status except in some specific situations. All external calls will of course follow the routing you specify.

Note: Whether the above configuration will suit your needs depends on your current configuration and on the call flow involving the extension in question. Please let us know if this works for you.

 

[bit101]

Hi Chris,

thanks for the workaround, we will try this.

But as i said, this functionality have worked before we update to 16 update 7! No it does'nt..:-(

 

[ChrisC_3CX]

@beon Even if this was possible with older versions, please note that it should not have been the case since this type of configuration would cause a loop as mentioned by @JohnS_3CX. That said, I can confirm that it should not be possible with the current version of 3CX and the behavior you are currently experiencing is expected. Hopefully, the workaround provided in my previous reply will suit your requirements.

 

[bit101]

Hi Chris,

your workflow works as expected. Many thanks!

I agree with you, but finally using a ringing group we have the same behavior (loop to itself).

 

[ChrisC_3CX]

@beon

Glad you got it working!

In a sense you are right it does loop once but the call does not get stuck in an infinite loop as it would with the initial configuration.