Call Manager 5 Vector digit programming change

[rustytelco]

Has anyone encountered an issue with using Call Manager 5 and how vectors need to be written?
I have been told by Avaya tier 4 we can not have 4 digit dial with announcemanet before a single digit statement as the single digit input will not be reconnized. The # key would but not a single or up to 3 digit function.
We have to re-program all our vectors with announcements to be single digit to be redirected to another vector that would allow 2 digit or more input etc.
Our existing programming designed by our Avaya partner for a simple auto attendant function that does not work when single digit is pressed:
Multimedia? n Attendant Vectoring? n Meet-me Conf?n Lock? n
Basic? n EAS? n G3V4 Enhanced? n ANI/II-Digits? n ASAI Routing? n
Prompting? y LAI? n G3V4 Adv Route? n CINFO? n BSR? n Holidays? y
Variables? n 3.0 Enhanced? n
01 wait-time 2 secs hearing silence
02 collect 4 digits after announcement 3722
03 goto step 9 if digits = #
04 goto step 11 if digits = 0
05 route-to digits with coverage y
06 wait-time 1 secs hearing silence
07 goto step 11 if unconditionally
08 stop
09 route-to number 3700 with cov y if unconditionally
10 stop
11 route-to number 1705 with cov y if unconditionally
12stop

Has any one had this issue with the other versions of Call Manager or is it just CM 5 problem that the vector is not a seperate program enitity within the CM? The Avaya partner was not aware of this issue with CM 5 when programming the auto attnedant function.

 

[Stinney]

This is not something new. This is how it has worked in previous CM versions.

If you have a collection step of 4 digits, but have steps that are checking for 1 digit, the system will wait for additional digits, as it's looking for a total of 4. Once it determines that no other digits are being pressed, it moves onto the next step.

This is controlled by the Prompting Timeout value in the system-parameters features, page 11. Whatever this is set for is how long the system will wait for digits to be pressed before proceeding with processing the vector. The higher the value, the longer it's going to wait.

I bet if you call the number that routes to the vector you posted, press 0 and wait long enough, it will route properly.

The Prompting Timeout might have gotten changed when you upgraded and that's why you think there's an issue.

- Stinney

Quoting only proves you know how to cut and paste.

 

[rustytelco]

What is the standard setting for the prompting time out?

 

[Stinney]

Whatever you want it to be. We have ours set to 4 seconds. You don't want to make it too short or it will move on if someone is pausing too long to enter digits.

- Stinney

Quoting only proves you know how to cut and paste.

 

[rustytelco]

If I understand what you are saying is that the set in the vector that has wait time 1 second does nothing because of the system setting?

 

[Stinney]

Essentially correct, if you were trying to use it to wait for user entry, all it's doing is making the caller wait 1 additional second before moving on in the vector.

- Stinney

Quoting only proves you know how to cut and paste.