IVR using Force strict digit timeout set to NO

I have an interesting question, will probably need to experiment to get the answer, but if someone knows the answer it would help.

What I want to do is have a IVR which has Force Strict Digit Time-out set to NO.

The theory I want to test is basically what happens to any other digits dialled when the system reacts to the first digit dialled.

If I have a second IVR set up will those extra digits be accepted by the second IVR.

ie: first IVR is set so that digit 1 will call second IVR which will has 3 digit option.
Incoming caller dials 1234, so IVR one calls IVR 2 which then hears the digits 234 and takes that corresponding option.

Or will the incoming caller need to dial 1 and then wait for IVR 2 and then dial 234.

Neat idea. Any luck in your trials ? I tried it with Set(TIMEOUT(digit)=0.1) and immediate pattern matching – seems to work. Like this (pardon my AEL dial plan syntax):

context hmm1 {
    _X! => goto hmm234,s,1;
    s => {
        Answer();
        Set(TIMEOUT(digit)=0.1);
        Background(beep&silence/4);
    }
}

context hmm234 {
    _XXX => NoOp();
    s => {
        Set(TIMEOUT(digit)=1);
        Background(beep&silence/4);
    }
}
1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.