Trixbox with SKYPE
Here's what I'd like to be able to accomplish:
Program Asterisk to (on a schedule) place calls from a list and deliver a spoken message to the answerer.
I would like to have a publicly accessible web interface on which users can enter a list of numbers to be dialed, the date and time of the broadcast, and the voice message that is to be delivered. The calls ideally would be made through SKYPE out.
Does anyone know of how I can go about getting this done?
I am not much of a programmer but If someone gets me started I think I can carry on.
Any suggestions would be appreciated.
Paying someone to help me is not out of the question but not my first thought of course.
It would not be a very good idea to run a Skype client on the same network that your Asterisk box is connected. Skype will automatically set up a node or worse yet a super node on the box that your Skype client is installed. What that means is that other Skype customers will almost immediately be able to make VoIP calls that are going through your network. It could be hundreds or even thousands of calls depending on your system configuration. Skype has an intelligent algorithm that calculates your system speed and bandwidth and the more your system can handle, the more calls it will process through your node. That additional bandwidth usage will degrade your Asterisk VoIP calls and also hog your downloads etc. Additionally, if you uninstall Skype, the software that sets the node up will remain and its bandwidth usage will continue. It must be manually de-installed by someone that knows how to get it all out of your system.
Not really true, the Skype client is a node, it can become a supernode which is the problem you are on about.
Assuming you use something like uplink with Skype on a windows box it can be disabled by making a reg file
* Save and run the following text as NoSuperNode.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Skype]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Skype\Phone]
"DisableSupernode"=dword:00000001
as for being a supernode after removing Skype, I think your tin foil helmets on too tight.
I came across SiSky from Yeastar (http://www.yeastar.com/Products/SiSkyEE.asp) and initial tests seemed to be positive. Should help a bunch with your project.
J
I stand somewhat corrected. Apparently now there is a way to disable Skype super nodes beginning with Skype version 3.0. My experience with Skype precedes this version. Additionally, the license that you accepted used to prevent you from disabling this function. It was such a pain in the neck to remove Skype, that it left a bad tastes and I will never use it again as a result of this.
http://snapvoip.blogspot.com/2006/10/how-to-be-or-not-to-be-skype...
http://snapvoip.blogspot.com/2007/07/skype-supernode-skype-and-fi...
As far as my comment about the Skype client continuing after turning off Skype or uninstalling it. The software used to load the Skype node on startup even if you uninstalled the Skype Client software. I don't know if they changed their software to correct this situation, but this is what their own description of how it works on their web page:
The page describing Skype usage on the site states;
"Skype (www.skype.com) is a free P2P (peer to peer) application that provides free voice-over-IP communication over the Internet. Use of Skype on systems attached to the Laboratory network is not prohibited per se. However, Skype calls are routed across the Skype network through other Skype systems, called SuperNodes. Any system running the Skype application runs the risk of surreptitiously being elevated to the status of SuperNode. Computers with a fast connection to Internet (such as at Fermilab), combined with high speed CPU, are most likely to become SuperNodes. A SuperNode can generate a considerable amount of traffic by opening a large number of concurrent connections for off-site systems, even after the local user has discontinued using the Skype application on his system. Generally, the user needs to reboot his system to stop the SuperNode call-routing activity."

Member Since:
2008-08-16