Inbound rule with IVR

[InterNext.online]

So in Trunk sip item and inbound rules like Yannish asked do you have the main number ?

As I have already said, yes, the default trunk number is also set to the IVR and set to the IVR as the default did direct number, so. Technically it can't be that it goes directly to 80001 and skipping 80000

 

[InterNext.online]

At this moment I've created the IVR and the inbound rules.
So and the inbound rule for calls is at the top. So there is something not going right. The number is 31852019062 that is the main number, and it skips 80000 instead to go to it.

In the previous version of 3CX PBX (15.5) it worked, at 16 it somehow won't and it is a clean server. Not a back-up we did it from scratch.

 

[AWS2P]

1. Did your inbound rules move up or down from inbound list since V15.5 ?
2. Have you checked how incoming numbers are presented from your trunk ?

 

[InterNext.online]

1. Did your inbound rules move up or down from inbound list since V15.5 ?
2. Have you checked how incoming numbers are presented from your trunk?

There is nothing changed after from version 15.5, we copied the whole settings from one to the other (and checked it of course). Created everything on a fresh 3CX PBX server, so there can't be any change. The trunks are verified and have verification from 3CX, so that we do not change. The way the numbers comes in is not a problem. The strangest thing is the other server for a client doesn't have this issue

 

[InterNext.online]

Okay, problem solved. What's changed nothing, only removed the ring group that it was trying to put everything to. Now it works fine. Guys thank you, what was wrong I really can't say, but it has been solved. @aws2p many thanks for your help, but it seems the server now wants to work properly. So still my thanks.

 

[AWS2P]

Well done, it's not easy to help with nothing else than words in forum

 

[InterNext.online]

Well done, it's not easy to help with nothing else than words in forum

Indeed, normally I've contact with the customers on the phone, but this issue was one that was really strange. After removing the ring group it solved itself. Never happened before.