I am developing a VB.NET Windows service that is checking a BMS database for new alarms and To warn the phone call: Remotely operators I am currently using a .NET TAPI wrapper and SAPI 5.3 interop assembly, and the steps I'm taking to call on the phone:
- Start the TAPI interface;
- call the number of operators;
- Voice modem wave-out device ID
- Set the voice output on that device ID;
- Make SAPI Magic
If I compile the code as a Windows console or a form application, but it's working fine, but as soon as I compile it as a Windows service, Then step 5 never happens - voice modem calls but keeps quiet; Everything works, digital also monitors. Now I know that Windows services do not have to interact with the desktop, so there are no sound and playable sounds like UI elements, but I struggled to do an alternative search. I am not involved in using the wave API and it can be developed, any ideas in a reasonable time frame?
SAPI usually needs any type of message pumps and window handles, which are windows Services usually do not happen. You can create messages to handle things safely (Note that any HWD will open up to you in the service, so make sure that you are running your service as a user, and the system or local MacIn Not the form of attack in the form). You will also need to pump messages (rouyn or apps. Duvelents or likes) as well.
Comments
Post a Comment