Anyone know anything about Integrated Solution III (IS III) Voicemail?

[Phonia]

I've got (yet another) ancient Legend, this one with an IS III that's intermittently dropping calls and preventing users from reaching the main autoattendant. Does anyone know anything about this system, whether it's Y2K compliant, etc.? Phonia
Telecom Goddess

 

[franke]

I believe the IS III is a lite version of the Audix. Unless your customer took advantage of the Y2K offer by Lucent back in the day, then the machine is not Y2K compliant and to my knowledge, AVAYA is no longer offering the patch, nor are they supporting the IS III. Unless you are willing to write your own Unix patch and or track down the parts I would suggest this customer upgrade to a newer Voice Mail system.

 

[Phonia]

From what I've been able to find since posting this question, I tend to agree with you. I somehow doubt that Avaya was even supporting this platform in 1999... and be that as it may, according to support.avaya site docs, it's supposed to be rebooted every THIRTY days (as opposed to 90-180 on later systems), so I think this system is probably showing the classic signs of "well past rebooting time."

For these and countless other reasons, I'm happily able to recommend to the customer that it's really time to get rid of this system... sheesh

Thanks for your response! Phonia
Telecom Goddess

 

[netcon1]

There were two issues with this system. One was the Y2k bug patch, and the other was the Y@K01 problem.

UNIX file systems record their date codes differently than Microsoft systems, so the Y2K problem did not happen on Y2K, but on September 9th 2001 (Unix date code 999,999)

There was no fix for this second one. When that date rolled over, it caused corruption in the database on the ISIII and caused issues like you are experiencing.

I am not saying that that is your problem, as there are many variables, however...

Easy way to tell is to go into the customer/subscriber extension forms and look at the profiles of each mailbox. If you see "swiglies" or data were it should not be, then there is corruption in the ISIII database.

The only known fix for this from AVAYA at the time was to back date the unix software 11 years and reenter the information in each mailbox to the correct info and the problem.

Also correct any system forms that show the same conditions.

That should fix the corruption and allow calls to transfer to valid extensions in the voicemail system. They will drop otherwise.

The best!!!! way to fix this is to forklift the old box, however, customers with these type of voicemails tend to be partial(CHEAP!) to these systems.

Come to think of it, I think the Pentagon still has one....I will have to check!!!

Netcon1