Communication in the post-PRISM world
You'll want to run FreeSWITCH in the foreground while you work out your own phone framework because the CLI offers comprehensive warnings and errors that are essential to help you debug your configuration files. When your phone setup is complete, you can consider running FreeSWITCH as a daemon and turning it into a service that runs in the background and runs every time the server gets booted.
For all practical purposes, you now have a working intranet equivalent to Skype, but you also have much more. Besides phoning other users on the network, you can record conversations, create groups of users you can phone all at once (the first user to pick up their phone "captures" the call), create conference calls, set up videoconferencing  and, if you run a VPN, allow colleagues, family, and friends to communicate securely using the service from beyond your premises. If you have a VoIP line from your carrier, you can also easily configure FreeSWITCH to link to the outside world through the conventional phone network.
The thing about services like Skype (and Facebook, YouTube, Flickr, etc.) is that a lot of people use them precisely because a lot of people use them. Once you transcend this circular logic, however, you may realize that being able to phone everyone for free and letting a third party do the heavy lifting is not such an enormous advantage if it means sharing your sensitive conversations with organizations that have no business snooping into your calls. At that point, avoiding Microsoft's phone service by implementing your own starts to make sense.
Additionally, setting up a basic Skype-like system is not hard with open source software. You can have basic and secure SIP services working with FreeSWITCH's out-of-the-box installation up and running in minutes. That said, building on the basic setup and using FreeSWITCH to expand your telephony services is a very interesting and tempting project. However, you should note that phone systems are complex and audio- and videoconferencing are still hard to do, so, if you are overambitious, you could find yourself in over your head. But, that's half the fun, isn't it?
- Source of inspiration for this article: https://prism-break.org/
- Microsoft helps out the NSA: http://www.theguardian.com/world/2013/jul/11/microsoft-nsa-collaboration-user-data
- The Jingle videoconferencing protocol: http://xmpp.org/extensions/xep-0166.html
- Jitsi: https://jitsi.org/
- WebRTC: http://www.webrtc.org/
- Setting up WebRTC is hard: http://blog.vline.com/post/52644825765/tunneling-webrtc-over-tcp-and-why-it-matters?gclid=CMGHj6ur5LgCFebJtAod4GsAAA
- WebRTC demo online: https://apprtc.appspot.com
- The FreeSWITCH SIP server: http://freeswitch.org/
- Ekiga Softphone: http://www.ekiga.org/
- Configuring Dialplan: http://wiki.freeswitch.org/wiki/Dialplan_XML
Buy this article as PDF
New release marks the arrival of AMD’s unified driver strategy.
A new study by IDC charts big changes in the big hardware market.
Azure CTO says Redmond has already considered the unthinkable.
Lead developer quells rumors that the Debian version is slated for center stage.
MSBuild is now just another GitHub project as Redmond continues its path to the light.
Malware could pass data and commands between disconnected computers without leaving a trace on the network.
New rules emphasize collegiality in coding.
Upstart lands in the dust bin as a new era begins for Linux.
HP's annual Cyber Risk report offers a bleak look at the state of IT.
But what do the big numbers really mean?