I am working on a new 128 mb four port flash voicemail for the dx80 and have been having some issues with all the ports going into a loop. It appears to start on port one and grabs line one on the system. I have tried to turn the system off and restart and that will clear the problem for a short time. Now the auto attendant has stopped working all together. The voicemail seems to be working o.k. Can anyone give me some help on this issue?

What software rev on the DX80?

RBF,
It's 33 sw and the latest VM flash 4. I asked him to post here, I've been working with him and tried everything I could remember from when I had this problem. We adjusted the call abandon time and the disconnect supervision time, and it has not helped. It doesn't happen on every call but seems to happen daily. I think there is a solution to this that I can't remember. Any ideas?
Mark

Upgrade the software in the DX80. We had several 33 cabinets where the ports would go offhook and grab a line. You could watch the ports and lines go busy and cycle through. F39 fixed the issue for us. Tech support had some files for the voicemail to fix this but I had little faith in that. Reset would fix the issue temporarily but would come back without rhyme or reason.

I have a F39 system doing the same thing Comdial said it's a problem they have seen before and i need to upgrade to F40. Also make sure you are receiving a disconnect from the phone company. Even if you have the routing boxes set to disconnect it seems to confuse the DX-80 if they dont receive a disconnect

I found my notes. I had this happen with 33 SW and 39 SW and both times it was a bad loop from the CO, on the 39 it was disconnect supervison, not being provided and on the 33 two lines would cause the trouble no matter what port they were plugged in to, we got the CO to use 2 different pair to drop the lines in and the trouble went away. I don't think this is a software issue. I have "in skin" VM in every level of software made for the DX80, both hard drive 8 port and 4 port flash 64 and 128. The two locations I've had this trouble at (out of about 125) the trouble has been CO related and NOT resolved by a softawre change. I would be pleased if it were that easy.
Mark

I just installed the new software so I should know in a few days if it worked or not
I did notice that the first item on the corrected issues page that comes with the software pretty much described my problem but i'm not holding my breath.

I still dont think i'm getting a proper disconnect from the CO. This is Verizon territory and they have a GTD5 switch they are changing the "PERM" setting is there anyone out there that knows if this is correct?

Thanks for all your help and replys. I did a cold start on the system and started from the default settings. This seems to have resolved the issue so far. I (along with marks great help and trouble shooting) think it may have been just a glich in the software. I will let you know if this problem resurfaces.
:toast:

Read FAQ DX80-000015 dated Sep 03 for your answer. When you did a cold start and re-programmed fresh you eliminated your original mis-programming.

Punch, I went through that with him and it was still having a problem, cold restart did seem to work (so far) though, so maybe did miss that when I explained it to him.
Mark

I don't think the cold start will fix it for long. He needs togo to A40. F39 had this problem for sure. A33 I think did. Just upgrade and be done with it. It has to do with the DX80 not getting wink on a disconnect. Hope this helps

Jim
SST Communcations
Long Island, New York

FYI it's been 6 days since I upgraded to F40 and it has not locked up i think it may have fixed the problem but i'll give it another week to be sure

Could it be the reload of SW and not the change of chips that solved it? Did you try a cold start and have it fail before you upgraded the SW?

There might be a software issue causing this, but I have lot's of 33 & 39's in the field with VM and no troubles.

Markk- last info I got was that it was a specific run of voice mail revs mixed with either a33 or a39 that bring out this issue. There were supposedly patches to load on the offending voice mails. Never tried them though.

Markk
We tried at least 3 cold starts and reprogramed everything from scratch still had the problem.
I also have quite a few 33's and 39's out there without the problem so it must have been a specific run like RBF said

I'll have to try and plant this information in my permenant memory banks.

If it means anything this was a new 128mb. VM board 8.5.11b and an older 33 SW in the DX. It hasn't lost it's pointy head again yet.
Mark

F39 really had this problem. You would mostly see it if the CO didn't always have wink on disconnect. It takes a while to come up and I guess if disconnect sup is 100% from the LEC you would be ok be I had to go to A40 on all of my F39's. No more problem. I did not see it as much on the A33.

Jim Hoey
SST Communications
Long Island, New York