IVR direct calling

[emtexcc]

Hello,

I have a problem after updating on latest version of 3cx with calling direct extensions with 3 digit.

So I have IVR
Enter 1 for something,2 for something,3 for something and 4 for something.

So when trying to call 3xx internal number it doesn't recognize xx numbers only number 3 and it transfers me to "3 for something"

IVR_INTERDIGIT_TIMEOUT is 10 sec
IVR_DIRECT_DIALING_GRAMMAR is [0-9]{3}

Are there any changes for this?

 

[Alphabetic]

I would try creating a new IVR for the sake of testing.

Reboot your services if you can.

Where are you seeing IVR_INTER... I cannot find it on my system.

 

[emtexcc]

I would try creating a new IVR for the sake of testing.

Reboot your services if you can.

Where are you seeing IVR_INTER... I cannot find it on my system.

it is a custom parameter that I found on forum posted by 3CX support
restarting didn't help. This was working but after update it doesn't work

 

[VasilisV_3CX]

Hi @emtexcc,

Can you tell us what settings you have on the IVR? Is the type set to DTMF or Standard? Does this happen to both internal and external calls to the IVR?

Note that your IVR should be set to Standard for direct dialing as per the 3CX Academy Digital Receptionist training:



The interdigit timeout shouldn't affect anything, it just sets the timeout between button presses.

 

[emtexcc]

Hi @VasilisV_3CX

it is standard. Only external calls when people trying to reach us to internal numbers. This was working fine until I did update to latest version of 3CX.

It doesn't recognize se last 2 digits only the first one.

 

[emtexcc]

Update:

seems that this is working when call from my extension IVR and dial another extension but from outside when people are connected to IVR they can't dial direct extension only menu options it only recognize the first number entered not 2 after.
Is there any quick fix for it ?

 

[VasilisV_3CX]

Hi @emtexcc,

Thanks for the update, since it's working from internal calls, and not from external calls - it seems that the issue is occuring on your SIP Trunk Provider's side. Are you using a supported SIP Trunk Provider?