Jump to content

tmittelstaedt

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by tmittelstaedt

  1. If it was me I'd backup-image my system, uninstall IVM, download and install the trial version and see if it works better. If not then restore from the backup image.
  2. There is no fix. The problem is that Microsoft changed the TAPI interface in Windows 7. There are other products affected by other software vendors. If NCH changes IVM to work with Windows 7 then it would not work on XP. A few modem manufactures may have modified their drivers to work but the vast majority of modem manufacturers use the Microsoft-provided drivers. To fix this problem NCH really needs to come out with a new version of IVM that is ONLY certified to work on Windows 7, specifically Windows 7 64 bit, specifically with a handful of modem chipsets. Keep in mind the vast majority of cheap older modem chipsets aren't supported under Windows 7. The computer scrap dealers around here have cardboard boxes full of PCI modems. But only a few, like the Intel winmodems, will work under Windows 7 64 bit. Until Microsoft EOL's Windows XP in 2014 it is difficult for developers like NCH because most people can easily round up an old XP system somewhere to run IVM on, and it's not like a voicemail system really needs to be a super powerful CPU.
  3. This is kind of answered here http://www.nch.com.au/ivm/modems.html Voice Modems End-of-Call Detection problems Some voice modems incorrectly detect the end-of-call tone. On the IVM, use the "End-Of-Call Tone Detection Settings" (on the Settings - Devices tab) to correct defects. (a) If the modem does not detect end-of-call when it should, tick the Enable Software Based Detection box. ( If the modem detects end-of-call when it should not (and therefore hangs up), untick the enable detection during playback option Your problem is when you updated IVM it reset the parameters on the modem driver. You will have to go into telephoney devices, go to properties of your telephoney device, and try different settings there. The first 2 settings are the key ones to fix this, try different combinations of these until you hit the right one.
  4. tmittelstaedt

    Encryption

    This would only be an issue if you had multiple mailboxes on IVM that had recipient e-mail addresses in them that used different domains. The obvious answer for you is register your own domain name, setup e-mail addresses for all your employees in your own domain name, setup the IVM mailboxes to send direct to those e-mail addresses, and setup IVM to use plain, unauthenticated SMTP to deliver mail direct to the host (gmail) that your domain name is on. Since your delivering to the destination mailserver for the recipient address there is no requirement for authentication or encryption.
×
×
  • Create New...