cannot pull config 1

[mikev80]

Here's a challenge. IP403 with 2 expansion modules (ds16 and POTS8), working fine until migration of new voicemail server, addition of DS30, and upgrade to 2.1.15. After implementation, everything works out great. The following day an agent pushes his Send All Calls button, goes to lunch, comes back, pushes button again to begin answering phone. The button did not toggle off. Administrator goes to Manager to check on the problem. Manager finds IP unit prompts for password, after entering password the Manager's config does not load. TFTP log says xxxx.cfg not received ok. Administrator station's able to view call status, and even run monitor with the same password. Send All Call button still does not toggle. The same user who went to lunch can toggle his Do Not Disturb on PM Pro, but not on the actual button and the button does not match up to his PM Pro state. To toggle on the phone he has to unplug the phone and plug it back in, then he's able to toggle the state ONCE before it locks up again. Rebooting the system makes it stable until the following morning. once someone's Send All Call button locks up, that's when Manager's unable to pull config (or maybe it's just a that we notice that problem first). Removed DS30, reverted back to old cfg file before all the changes, everything worked fine for 3 days. Added the DS30, and sure enough the following day the problem occurred. No users are asigned to the DS30 ports. I'm completely lost on this one. Any ideas besides upgrading to 2.1.24?

 

[IPGuru]

that is the $64000 Question

 

[Spanning]

New Maint Release Due in November 2004 , as for 2.1.248901 our customer has no faults to report.

Thank you

Tra

 

[dlatt1283]

We had a similar issue with a client after upgrading to 2.1.24. We were having people disabled from hunt groups, their DND and Hunt Group Enable buttons were freezing, and we were unable to pull a config from Manager. AVAYA gave us the 2.1.248901 patch, and we were stable for a little bit, and it started happening again. It turns out that when you have voice mail pro at version 2.1.10, vm pro sends a lot of tftp requests to the control unit. The control unit can only handle up to 32 tftp request, then it starts dumping the excess requests and causing errors (like disabling people from hunt groups, freezing buttons, not allowing you to pull a config, etc). If you have a site that has a good amount of users and has a fairly large call volume, and your VM Pro is version 2.1.10, you will experience this problem. This was the explanation we got after spending 2-3 weeks on the phone constantly with AVAYA. AVAYA gave us an upgrade to 2.1.12 VM Pro, and it fixed the problem. So, just fair warning to you...ask AVAYA for the 2.1.12 VM Pro.