Embedded VM - Caller is getting cutoff

[gotrojans]

Callers have been intermittently getting cutoff when leaving VM messages on the embedded VM system.

Yesterday when manually stopping/starting VM, I got the following error.

vtPageQFileInit - failed to read trans.dat

Consequently, we decided to restart the 3300 or MCD.

Any suggestions to fix this?

Thanks

Ron

 

[jrgood0852]

You performed the reboot already, or not? If not I'd see if this fixes it. Thanks.

Always look out for the next tech. because one day it will be you!

 

[gotrojans]

Yes. We did the system reboot. It didn't help.

Ron

 

[kwbMitel]

Calls getting cut off when the caller is using a cell phone can be relatively common.

You might want to try and get specific date time info for messages so that you can see if there is anything in common

SMDR data should tell you VM port and Trunk

You could also try accessing the diag.dat file using FTP access to the vmail directory and see if any clues are in there.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[gotrojans]

I wish that it was a cell phone issue, but it is not. It happens internally and externally. All VM ports are available.

Ron

 

[kwbMitel]

Internally is very odd. I would definitely try and nail down the time those occur and look at the diag.dat file

**********************************************
What's most important is that you realise ... There is no spoon.

 

[jrgood0852]

A DBMS Check Full gives no errors? If it does, backup/restore time.

Always look out for the next tech. because one day it will be you!

 

[kwbMitel]

DBMS check has nothing to do with voicemail.

DBMS check simply compares the running version of SW in RAM with the stored version of SW on the harddrive

**********************************************
What's most important is that you realise ... There is no spoon.

 

[gotrojans]

Actually, our business part installed the latest patch for our hardware and even did a backup/restore. Neither worked.

Ron

 

[kwbMitel]

We need to know if the problem is port specific or random ports

How about taking some ports out of the hunt group (except the last one)

Easiest method might be to create a cos with permanent DND enabled and then apply that COS to 25% of the ports and see if the problem clears. If not, try a different 25% and so on.

**********************************************
What's most important is that you realise ... There is no spoon.