Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Merlin Mail 3

Status
Not open for further replies.

tonysprout

Vendor
Apr 7, 2003
39
GB
I have a version 3 Merlin Mail in a Magix 3 v7. Mailbox 207 had audio problems in vmail only. Swapped out the module for other problems and reloaded a full back-up. Mailbox 207 still has volume problems (from any phone). The volume of prompts or customer greetings and messages will raise and lower.
Deleting and recreating the mailbox doesn't help. Is there any way I can renumber that mailbox? Customer has DID so don't want to change his extension number.
 
Tony,

Is this a Merlin Messaging in your Magix system or Merlin Mail R3.0 Standalone.

Sounds like there might be corruption on particular operating file on the hard drive that the Station 207 MBX is referenced at. The processor shouldn't have anything to do with this problem as it acts fairly "dumb" in the call routing process - dumping the call to the VM.

There is no way to get around that problem that I know of. Maybe one of the techs knows a way.

I believe that repairing the MM R3.0 will solve the problem.
 
It's a module in the Magix. I've figured out that it's a software glitch since it followed the database on a reload. This has been one %&**#!!! installation. All problems are fixed except this one, and I don't want to tell the customer I have to start over on the vmail. Thanks for replying Drewmich.
 
Tony,

Not sure what you mean by it "followed the database"?? The only database files are Brooktrout's DB files on the hard drive. The Processor shouldn't have had anything to do with the issue you described.
 
"Database" in my corner of the world refers to the part of the program that is user/tech programmable and is saved by doing a back-up.
The problem is known and is located in the "database."
The solution is 1) Reprogram the entire voicemail after checking to see if the problem exists in a defaulted database with only mbx 207 in it, or 2) Find a way to "tag" that portion of the programming as bad and not use it. In some other voicemails, you can change the mailbox number of the bad mailbox, and create a new mailbox with the old mailbox number.
Before I proceed with either, I guess I'll have the customer delete and recreate the mailbox again.
Thanks for helping.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top