I am using Virtual Modem version 1.7.3 to connect PC's in my retail locations with the corporate polling server. This allows me to stop using POTS lines into each store and complete nightly polling using existing broadband connections.
So far everything works, but sometimes the v-modem on the corporate side stops functioning and my polling fails to complete. I have 39 stores to poll, so the re-work to reset things on the corporate server side and re-poll can be very time consuming.
Is there any way I can log modem activity from the virtual modem software to understand why the modem stops functioning, or can I reset/restart the v-modem using the command line? If I can reset the modem with a command line call, I can incorporate that into the batch files that run nightly to poll the stores.
Version 1.7.3 is a comparatively old version. We recommend upgrading to the current version 2.1.1 in which a log of bugs have been fixed since 1.7.3
To log the modem activity you can use Portmon, but you will hardly see the cause of the issue as it happens randomly - there will be just too many entries.
Does the frequency of errors depend on the quantity of connections?
If possible, try running the new trial virtual modem on another machine to test if the same will happen.
How long ago did the disconnections started happening?
Replacing the existing configruation will be difficult, how can I find a list of bug fixes for the most recent version of code? Also, what is the upgrade cost from 1.7.3 to 2.1.1?
We began logging changes starting from version 2.0, so here is the list:
<version>2.1.1</version> <whatsnew>Developer API components digitally signed.</whatsnew>
<version>2.1</version> - Drivers digitally signed. - 64-bit Windows support. - Automatic update feature added allowing to be always up-to-date. - Now it is possible to originate or answer TCP connections with any TCP/IP enabled device or software.