Auto Attendant not ringing extensions 2

[richarddurham]

My Auto Attendant will not ring any extensions. When AA prompts callers to enter the ext they are trying to reach, the system just stops. It's like AA is not talking to IP Office. I am running a 412 system with IP Office 3.1.65 loaded and VM Pro.

 

[jml2665]

has it ever worked?

sounds like the transfer module is not setup correctly, each valid starting digit with the appropriate number of question marks needed for your dialing plan, needs to be connected to a transfer module with the $KEY in the "Specific Tab" destination field.

 

[richarddurham]

My flow is 1??? goes to transfer to extension. General properties of "Transfer to extension" is Token name = Transfer to extension and Specific tab = $KEY. Looks like it should work...any ideas?

 

[Wally1775]

Richard, do you have a timeout defined for the menu? I ran into this bug before, I added a timeout value and just set it to replay the menu and everything started working fine. I was puzzled because it was an upgrade of a 3.0 installation with no VM changes, and it had worked prior to the 3.1 upgrade. It seems to be a bug in the 3.1 software, I told Avaya about it recently.

 

[richarddurham]

I do have a timeout set. I also went in and bumped it up but made no difference. Still refuses to ring the extension entered. Still looking for a clue guys. Thanks to all so far.

 

[bobbdeep]

Be sure to remove 1 from your touch tones as it will cause a conflict with the 1???

 

[richarddurham]

Thanks bobbdeep, but it is unchecked....running out of ideas....open to all suggestions

 

[TheDoz]

Is this a new install or one that worked before an upgrade?Do you have a 3 digit dialing plan (2?? for example ) or 4 digit (2???)in the V-mail Menu? Make sure this is going to a Xfer action with $KEY in the specific destination.

"A politician is a fellow who will lay down your life for his country.

 

[richarddurham]

We did upgrade to 3.1.65 about 4 weeks ago. Nobody complained about the problem until last week. Might have happened because of the upgrade....

 

[jml2665]

by rule the VMPro should have been upgraded too, hopefully it was.

I had something similiar in a lab system a while back, and the only thing I could do to get it working again was to delete and re-add the modules. Never figured out why but it may have had something to do with all the un-install / re-installs and exports / imports done during testing.

You might try removing the modules then save it, re-add the modules back, link them and save it. See if that helps ya

 

[TheDoz]

In Voice mail pro if all looks correct and something does not work properly, you have to delete and rebuild your Modules from scratch. Also, you may have to delete shortcode to your AutoAttendant then re-enter it back.

"A politician is a fellow who will lay down your life for his country.

 

[richarddurham]

EUREKA!!!!
Thanks Doz and JML2665...that's exactly what it took to fix the problem...whooda thunk....
Thanks to all for their help... tek tips rules......