I had a problem with IVM when accessing voice mailboxes. I was accessing the mailboxes via Axon from a logged in extension in Express Talk.
This is my setup:
PC1 (windows 2003 server). Runs Axon (version 1.09) and IVM (version 4.02). All set up and happy. Axon is logged into VOIP providers and the lines work fine. It is possible to call the VOIP number, and the call transfers to IVM after a few rings, caller hears the OGM and can leave a message.
PC2 (windows XP). Runs Express Talk (version 2.06). Also, all set up and happy with Axon on the other machine. Can make calls to the VOIP lines, can receive calls ok.
Now to the problem I had. To pick up messages left in a voice mailbox, I used Express Talk to call IVM (default extension 199). I heard the message ok. I then press '8' to enter mailbox control, (intending to change the OGM). I hear nothing. Now, the incoming port must be working because I've heard the voice give me the date and time of the message, and I've heard the message, but now I hear nothing even though the IVM log claims it's playing the prompt file. This was a 'hard' problem, ie it happened every time.
So, I'm suggesting there's a bug, either with Express Talk, or with IVM, or with Axon.
I found that in Express Talk, if I unset Options>Other>Enable Key Tone, then it worked properly, and I could hear the IVM prompts. This is my current workaround. With 'Enable Key Tone' set, I have the problem, with it cleared I can hear all the prompts. It seems that the keytone, when enabled and once a key is pressed, stops the delivery of sound. (Note that with keytone disabled, the keys do perform the mailbox actions correctly - this is because the setting only affects whether or not you hear the keytone, not whether or not the tone is sent).
It may help in tracking the problem to mention that I also found that after I had pressed a key and the line was silent, if I placed the call on HOLD and then un-held the call, the sound was restored again until I pressed a key at which point it was back to silence again.
I've posted this information to help anyone with a similar problem, and also so that the people at NCH can reproduce the problem and hopefully fix it in due course.
Kev.