07-14-2006 08:42 AM
07-14-2006 08:43 AM
07-14-2006 11:30 AM
@rolfk wrote:
The type of API as a command interface however suggests that you couldn't really pass audio data directly to and from LabVIEW into Skype.
Rolf Kalbermatter
Message Edited by rolfk on 07-14-2006 11:08 AM
In this case, Does it really matter if he can't receive audio? The fact that he's recieving the call, and the fact that his cell phone probably has caller ID, should be enough info to know that his machine is calling him. (But then why not go the text message route?) If one wants to develop a full set of drivers for Skype, then that's a different story 😉
If sound is of utmost importance, If his computer has a microphone, shouldn't Skype's API know how to enable the mic? Then he could pick up the alarm sound externally, somehow (through speakers)? Is it completely necessary to have the sound be passed directly to and from LV to Skype?
08-04-2006 02:06 PM
08-04-2006 02:40 PM
I'm sorry to hear that you are still having problems with sending a text message. If I remember correctly from another post, you are able to use Outlook but the LabVIEW function gives you an error? Is there anyone in your IS department that might help? You have to get the name of the SMTP server (not the Microsoft Exchange Server) from them and also verify that it's not set up to reject anything that doesn't originate from Outlook. I think trying to interface to Skype or GoogleTalk might be an interesting exercise but one that might take a while to get working.
08-04-2006 02:46 PM
08-04-2006 02:48 PM
http://digital.ni.com/public.nsf/allkb/5C55FAEDC7BF5C0C862570930054D39F
I tried the following idea from the link posted above and that works fine too..
As a final note, the most common difficulty encountered when using LabVIEW to send e-mail is choosing the appropriate mail server. One technique to troubleshoot mail server difficulties is to use the telnet command as described in the following steps:
1) Go to: Start >> Program Files >> Command Prompt
2) In the command prompt window, type: “telnet [name of server] 25” and press enter
If the connection request is accepted by the server, you can verify that the mail server is valid. Thus, using that server name in LabVIEW should be successful.
08-04-2006 03:06 PM
Well, there are good IS departments and then there are bad IS departments. The good ones realize that they are a service provider to the rest of the company. The bad ones think they are the center of the universe. Giving a trusted employee the name of the server so that you can conduct company business should be no different than you being trusted with Internet access. When faced with a bad IS department in the past, I've relied on management to force the issue up the chain of command. That's what management is for.
In the meantime, maybe I or someone else can come up with a different approach. It probably won't help you but as a side project, I'm going to start experimenting with some Internet telephony. We're switching to a SIP-based VoiP phone network and dialing anywhere from any pc should be fairly simple. With free SIP-phone software, we can already make a call between any 2 pc's with a soundcard. I'll let you know if I run across something that might apply to your situation.
08-07-2006 03:35 PM
Came across this today and it rung a bell (like a phone). Uses web services to call a phone number in LV 8.20 and read a text file out aloud
http://zone.ni.com/devzone/conceptd.nsf/webmain/29543201344aa09f86256d740066839e
For 7.x and 8.0, more generic description of using web services
http://zone.ni.com/devzone/conceptd.nsf/webmain/5CF258A718A3DD70862571C10001C23C
10-16-2006 02:20 PM