OGM Autodials "dies" after 15 minutes

superdave

I bought IVM a few weeks ago and have been testing it to set up my OGM (options, etc.)

Everything seems fine, until tonight when I tried running a full call list of several hundred numbers. I started the OGM Autodial, watched it make a half-dozen called and walked away for an hour. When I got back, the system had stopped calling, apparently 15 minutes after the start of autodialing.

When I tried restarting the OGM (pause-start-pause-start), the message log said "resuming" but NOTHING happened. I had to completely kill and restart the IVM.

When I restarted the OGM, it ran again fine (for 15 minutes) and then just stopped. As before, I could not restart the OGM, despite the on screen login indicating that the OGM was ready to process the next number.

If it helps, I'm using a single Lucent Win Modem on Windows XP.

castiron

superdave wrote:

I bought IVM a few weeks ago and have been testing it to set up my OGM (options, etc.)

Everything seems fine, until tonight when I tried running a full call list of several hundred numbers. I started the OGM Autodial, watched it make a half-dozen called and walked away for an hour. When I got back, the system had stopped calling, apparently 15 minutes after the start of autodialing.

When I tried restarting the OGM (pause-start-pause-start), the message log said "resuming" but NOTHING happened. I had to completely kill and restart the IVM.

When I restarted the OGM, it ran again fine (for 15 minutes) and then just stopped. As before, I could not restart the OGM, despite the on screen login indicating that the OGM was ready to process the next number.

If it helps, I'm using a single Lucent Win Modem on Windows XP.

Dave,

Check to see if your modem is on the list of supported modems here:

http://www.nch.com.au/ivm/modems.html

Certain modems run into some pretty major problems.

superdave

castiron-

Thanks for pitching in to help. The Lucent Win Modem is on the recommended list:

http://www.nch.com.au/kb/10063.html

I've done some more testing and have some info.

In one case, it looks like an incoming call may have interfered, but other times it seems to have just stopped cold.

However, what I am now seeing (or finally noticing) is that IVM taskbar icon pops up a little note about "Lucent Win Modem: Unknown".

Tonight it ran for one hour and 40 minutes before hitting the error.

It's as though IVM has a temporary failure to communicate with the modem and then is unable to reacquire it. Pause/Start OGM does not work or help. However, stopping IVM completely and then restarting IVM returns everything to normal (until the next time).

1) Is there a reason/bug/setting why IVM loses the modem and can't detect it again?

2) Is this a known problem that is fixed in update/patch?

3) Is there a trick to force it to re-detect the modem without restarting IVM?

Note: my next step will be to check for updated modem drivers and to remove/add the modem back into IVM. I may also try a modem test button after the next failure (but before restarted IVM).

Is there any known issue on IVM "forgetting" it's modem (and patch/upgrade that fixes)?

Thanks

pythonpoole

I have never encountered or heard of this problem before. Perhaps NCH can shed some light on this. I am unsure what to suggest except what you already plan on doing (looking for new modem drivers). If your modem came with any diagnostic test programs I suggest you run them now. It sounds like the modem may be faulty, or at least the driver may be.

superdave

pythonpoole wrote:

I have never encountered or heard of this problem before. Perhaps NCH can shed some light on this. I am unsure what to suggest except what you already plan on doing (looking for new modem drivers). If your modem came with any diagnostic test programs I suggest you run them now. It sounds like the modem may be faulty, or at least the driver may be.

I found a few similar posts here on the forum going back a year about OGM failing after a while for other users. It is possible that an incoming call interferes with the modem, but so far, nothing short of completely exiting IVM and restarting has made it re-recognize the modem once it has halted.

My latest workaround is to use the Task Scheduler in Win XP to start then stop then restart IVM every half-hour.

It would be nice if NCH chimed in if this is a know problem or if there is a setting/parameter to fix this.