We're using a Comdial FX003 switch running VMMI software version/release 191, latest support feature set 17a, build number 17.02.00.

The problem: whenever someone calls in on weekends, this is what they hear:

"That is not a valid entry. Good morning" (or afternoon, evening, etc, depending on the time of day.

Any solutions to this? Is it really a timing issue and if so what do I do to get rid of this annoying message?

I am assumming that it has comdial/key voice vm attached. It sounds like a trans.txt issue and the vm is receiving digits from the switch with which it does not know what to do. Running a trace and comparing test calls to what is expected from trans.txt can clear this up.

Kerry

Thanks for your fast reply! I've heard that before about it possibly being a trans.txt issue, I will go into that and see what comes across and will run a comparison. But first I need to figure out exactly what this trans.txt does and what happens if I manipulate/change it.

Thanks for the feedback, but I am open to more suggestions if there are any!

Kerry is right. trans.txt is a translation file, when the system hears digits it translates those digits into an action. It's well explained in the manual which is available on line. Click on manuals above.
mark

one other thing to look at is what routing box answers on the weekend. If it is different then the others that answer during the week. It may be as simple as going to the routing box that answers andput is own number into the digit 9 field.

example: if its routing box 801 in option 9 in should say 801.

Let us know what you find out.

I get the same response whenever I dial into voicemail from any station: I sorry that is not a valid entry....If you know your party's extension.........??

jimbo32 said:
"I get the same response whenever I dial into voicemail from any station: I sorry that is not a valid entry....If you know your party's extension.........??"

From every station? When I ran across that it was because a routing box had button "9" programmed. Clear the programming for button 9. :-)

-jeremy

Did we ever get a solution to this?
I have a DX80 w/ 8 port HD doing the same thing with the digit 9 set to 800 and 801 respectively and without digit 9 programmed, it doesn't seem to matter.
Mark

Adding the routing boxes own nuber to the "*" field fixed this for me as the transfer was adding a *, not a 9.

Should fix for internal users if they are calling the vMail port. I don't know much about your system or handsets but we have a DSS button that is programmed to enter the gateway and ask for the password. This may not be an option for you. It isn't for our single-line handsets.

Hope this helps. Someone will correct me if I am wrong or if there is a better solution.

My situation was that it would play on an incoming call on CO Lines answered by the auto attendant. I ended up changing the file extension on the prompt so it wouldn't play. There is a separate invalid digit prompt that plays if the call is in house. I've had no more complaints since I did this. I didn't try putting the box number in the * field, when you do that you would need to give the directory box a new routing number, since * is directed to the directory box by default. That's still a good work around if it solves the trouble.
Mark

Was yours a DX80? Typically, the * is programmed to go to 9998, which is the Directory box. The reason I ask if it's a DX80 is because of a Custom field entry Comdial had in the older DX80 voicemails.

Mark,

Which prompt would play that you changed the file extension to? By changing the file extension, you are probably now filling the error.log file with errors relating to the system's inability to find a certain file.

It's been several months now and I don't recall. The VM was one of the really early 8 port hard drive systems. I think you helped me with this one and we turned the error log off.

We have a DXP Plus. Same situation as Mark, it would play on incoming lines answeredd by the auto attendant. For those boxes only, we changed the * to be the box number and put another button (say 3) to go to 9998. We put this in our greeting also. I guess the system was adding digits in the transfer [(800,*,*) found running a trace] and was not playing the greeting because it tried to translate the digits first OR the greeting was being cut off by the digits. Don't know why it said invalid digit but it would go to box 821, not the directory. When I put 800 in the * field of itself, this stopped. Have not tried clearing 9 as mentioned earlier though.