Definity "Collect Digits" 1

[Guest_imported]

I have a Vector that, after the step "Collect Digits" the user will get disconnected if she uses it. (There are other options after the collect digits, but there is a pause.)

Is there somewhere I can start looking to debug this?

thanks,

 

[BHodgins]

How about if you post your vector for us to look at?

 

[Guest_imported]

1 Collect 4 digits after announcement 2875
2 goto step 15 if digits = 1
3 goto step 17 if digits = 2
4 goto step 19 if digits = 4
5 route-to number 2473 with cov n if digit = 3
6 route-to number 2926 with cov n if digit = 0
7 goto step 10 if digits > 999
8 goto step 17 if digits > 0
9 Route-to number 2926 with cov n if unconditionally
10 stop
11 goto step 18 if digits < 1000
12 goto step 18 if digits >2899
13 route-to digits with coverage y
14 stop
15 messaging skill 99 for extension 2925
16 stop
17 messaging skill 99 for extension 2202
18 stop
19 messaging skill 99 for extension 2300
20 stop
21 announcement 2886
22 goto step 1 if unconditionally
23 stop

 

[netcon1]

Problem solved

The collect digits should be 1 digit not 4 if the next options are only one digit conditions

Judging by the vector script you have here, you cannot do a collect digit of 4 digits and expect 1,2 or 3 digit results.

Netcon1

 

[netcon1]

Also your step 7 is taking the caller to step 10 where the vector stops.

Thus dropping the caller.

Netcon1

 

[netcon1]

You may want to break down the selector code steps into sub-steps with sunmenu items and prompts. That way you can collect 1 digit for the initial options, and rout the caller to another step which prompts and collects 4 digits for the extension number or service requested.

Netcon1

 

[JBantz]

I believe you can collect multiple digits, then do a route-to if the digit =1 or =2. The collect step collects up to #### amount of digits. If you enter less than #### amount, it will record what you enters then pass that on at timeout to the next step of the vector.

We used to prompt callers to enter a 1 if they knew their parties extension, then if they pressed 1, give them the option to enter an extension and route to it. This made our vectors longer, and required more announcements. now we prompt for multiple digits upfront, and do our route-to step for single digits as well as for extension numbers from the same collected digits. We also put a step in to go back to the original collect digits after announcement step if the caller enters Zero (for those among us who like to hit zero when they get to any automated menu). It is important to put the route-to for 0 (or any other special dialable numbers) right after the collect step. The route-to will route the caller to any dialable extension in your phone switch if not intercepted in the vector.

Example:
01 wait-time 0 sec hearing silence
02 collect 4 digits after announcement ####
03 goto step 2 if digits = 0
04 route-to number #### with cov n if digit = 1
05 route-to number #### with cov n if digit = 2
06 route-to digits with coverage Y
07 route-to number #### with coverage n if unconditionally
08 busy
09 stop

If your caller enters in an extension (related to step 6) that is invalid, it will ding the event log, and fall through to the next vector step.

This works on r9.5, and not work in all releases.

Does anyone see any other gotchas related to doing routing this way?
JB

 

[Guest_imported]

Thanks for all the responses. (I learned something, GASP!)


The Line:
7 goto step 10 if digits > 999

Should say:
7 goto step 11 if digits > 999

thanks again!

 

[telcoguy]

You can mix 1 digit with for example 4 digit collection,
the only thing is, the vector will wait for 3 digits until vector times out with the timing set up in your system settings,if you collect 4 digits and only request one from the caller.
This can be fixed by requesting the caller to put a # after
they put in 1 digit.
This will start vector processing straight away for 1 digit,
and with 4 digits you are OK as well, as this is the full lenght.