Print Page | Close Window

Multiple applications controlling modems

Printed From: Way2call Communications
Category: Hi-Phone Software Development Kit (SDK)
Forum Name: Hi-Phone DLL
Forum Description: Discussion on the Hi-Phone product family, its DLL, samples and development tools
URL: http://www.way2call.com/forum/forum_posts.asp?TID=25
Printed Date: May 03 2024 at 10:48pm


Topic: Multiple applications controlling modems
Posted By: Jos
Subject: Multiple applications controlling modems
Date Posted: May 20 2009 at 12:07pm
Hi all,

 We need to control diferent Hi-Phone USB Desktop Lite modems installed in the same PC with diferent applications, one by each.

 We are making some tests and when the second application calls to InitializeDriver it returns "already initialized" and subsequent calls to other functions (as GetNumdevs) from this second application always return error driver not initialized. Hi-Phone log tells something as "Error, Single proccess please". It seems that first application locks the driver and we must to control all modems installed in the equipment with the same application (I dont understand why this limitation if all other api calls are refered to an specific modem id).

Are there any method to access every modem from a diferent application? 

Many thanks.


Replies:
Posted By: doronsh
Date Posted: May 24 2009 at 2:32pm

The MD DLL works with one (single) process only, control / access  multiple Hi-Phone devices.

If some software design requires multiple processes (applications, exe)
to access multiple Hi-Phone devices, then
- A single process will be a server that can control / access multiple Hi-Phone devices.
   This process works with MD DLL API from its one 'end'.
   From its other 'end', it communicates with client processes,
   using any preferred IPC (Inter Process Communication).

- A multiple clients processes can communicate (IPC) with the server process
   so they can all control / access multiple Hi-Phone devices.

Posted By: Jos
Date Posted: May 25 2009 at 2:50am
Ok, I'm working now in the internal "proxy" (a service) that controls all modems and export an interface (Local TCP-IP) to all other applications that require the use of them.  It's clear that this solution will resolve my problem but I dont understand why this limitation at modem driver that forces me to include another intermediate process without work (only a bridge) in all my modems operations.

Thanks.


Print Page | Close Window