Posts Tagged: voip

Business and Telecommunication

Business requirement of telephony system, perceived from three dimensions, namely hardware, software and as a service.

Telecom sector business trends and changes happening in each generation of telephony. Analysis of next generation telecom business solutions and possible market areas for small and middle business companies.

In its life journey, telephony systems have traveled from plain old legacy systems to an era of advanced stage of Voice over IP communications supported by high-speed internet connection. Telecommunication feature requirement or demand has now moved to such a diversified stage that the business demand-supply chain keeps changing at a very fast rate. Let me to explain this.

As an example: A requirement or demand of a telephony feature like video conferencing is now no longer dependent on a particular way of implementation i.e. not only limited to hardware solution within an enterprise but have also available on mobile as an application software. It means that business solution of ‘video conferencing’ can be achieved via many dimensions like free soft-phone based, license soft-phone based, hardware based, Mobile/laptop based, or even home decor Television based.

This implies that telephony business must have dynamic business model and not sticking to particular solution. Business model must be capable to switch to alternative solutions at any moment. For big players this is not an issue of any concern, but small business players, must pick wisely what kind of telephony system they will use and what their sustainability is. They must think of moving their on-going business with telecom generations of high-speed internet and digitization.

In legacy telephony, business was oriented towards cost of each audio phone call, number of calls, and Local vs STD based calls, as this ware the core services available. Videos call at that time ware among major earning business solutions.

As a generation of telephony moves on, until 2.5 G to 3G, audio and video phone call is like default services and internet based, location based, on-demand or live streaming was on a high demand. At this stage, new business players who forecast this as an era of stating point of next generation telephony service were able to make a lot of money. Many entrepreneur and many small telecom businesses have grown up to support this demand both with hardware, software and as service.

Many software solutions and telephony applications were developed, protocols were defined and universal standards were placed. Businesses grew with software application around audio call, video call, conference, 3-way calling feature, announcement, advertisement service during telephony services. Hardware based solutions also grew in parallel and High-Definition quality were integrated with above listed telephony services. Small business which were software based have grown up and earned much, whereas big players have taken up this as a complete hardware and software solution, by building up of their own networks. Some business also grew targeting services of telephony application, whereas some targeted the support of telephony service, like Analysis and Analytical tools, testing tools etc. Legacy business was on backward compatibility support of these new telephony service.

At present telephony demand has changed a lot in its demand and implementation. From fixed hardware to mobile based app solutions. Business players have also re-shuffled and realigned themselves. Telecom operators are moving ahead to meet the demand with high speed internet solutions with legacy hardly contributing to a small percentage of profit. On other hand telecom R&D organisations / MNC have started working on next generation technology with high skilled human resources. Business players oriented towards software based adhoc service providers are also growing. Businesses are investing more on mobile based telephony solution like whatsapp, facebook, etc . A bulk of small business earning are also centralised around information on public platform and on advertisement. Telecoms are now moving towards IOT (internet of things) and wifi solutions. Hardware independent, time independent, resource independent fast and easy communication is needed with rich functions and high definition quality.

Small business players interested in telecom business must consider these changes in trends of telephony application demand and supply. Changes from fixed dialling system to mobile based automatic voice-recognition based high-speed internet service, must be analysed for any business investments. Legacy telephony in future is not going to last for couple of more years. SS7/ISDN based telephony system is going to vanish from market being replaced by high-speed and wifi solution.

Eventually telecom market is moving towards virtualization system capable fast and easy expansion of resource with change in demand, Big data and their analysis, single click software application supporting telephony functionality, hardware and location independent application and location-time applications. Those small business working on core legacy technology should try an attempt to move towards high-speed internet based telephony feature. Those small business working on hardware based legacy telephony should try an attempt to move towards digitization and integration within next generation hardware systems. Those small business working on services of legacy telephony should try an attempt to move towards adhoc or license free solution with telecom operator. Small business players interested in telecom business as a solution can work on providing mobile based soft-phone solution as a client solution. As side service they can provide VoIP data analytics, new VoIP features or Wifi solutions for middle business players. IOT – internet of thing is another major evolving in telecom sector, which small application and sensor based device communication are in trial, small and middle business sectors can also think towards this dimension of telecom solution. Telecom sector is vast and it depend so each business player’s vision and mission to work upon.

VOIP explained for enthusiasts

VoIP in depth:


  1. Definition & Overview
  2. Protocols & procedure
  3. Technical Details
  4. Features & Functionality
  5. Future Prospects


Definition & Overview:

The term VoIP represents Voice communication over/via IP-network. There are many advantages of having voice communication over IP network, termed as PS ( packet switching), over traditionally voice communication, over CS( Circuit switching), like fast, easy and efficient resource utilization with enhanced features. People who wish to communicate with each other with VoIP must support TCP/IP packing, called IP-nodes/Host. VoIP is also used to establish sessions/calls to different networks like circuit switches PSTN or GSM/UMTS users.

It is a technique of sending voice/media packets over IP-network. This solution of establishing session between two parties is adopted by next generation mobile communication like 4G. VoIP is incorporated with underline protocol stack like SIP, H.323, SDP, TCP/IP suit, etc. VoIP solutions are mainly driven with the help of supporting APPLICATION layer protocol, namely SIP (Session Initiation protocol) or H.323.

Protocols & procedure:

Predominantly SIP is a versatile text based protocol mostly used in enhance technology. SIP defines request and response mechanism like INVITE, Register, Option, Publish etc and 1xx, 2xx, 3xx, 4xx, 5xx, 6xx responses respectively.  It also defines routing mechanisms with the help of SIP-proxy server to discover called user details. A session is established between two nodes (IP-based) who wish to communicate by routing request to proxy server and querying database termed location server. Once two nodes (calling party and called party) learn each other IP-addresses, voice RTP packets are sent between them. SIP stacks maintains and control the established the voip session until it is closed. Session is released or cleared by sending BYE request to other party. SIP protocol standard is defined by IETF standards of 3261rfc and is being adopted by many new upcoming technologies. H.323 protocol on other hand is a protocol suit used earlier for VoIP solution. It is still used within certain old technology and enterprise solutions.

Technical Details:


This section describes VoIP architecture and solution in details based on SIP protocol. VoIP architecture is defined based on three tier model.
• User-plan or Application layer mainly consists of IP-nodes who are either Calling User/Nodes or Called User/Nodes. SIP based IP-nodes are termed as UA (User Agent). SIP based IP-Node that initiates session request is termed as UAC (User Agent Client) and SIP based IP-nodes who respond to the request is termed as UAS (User Agent Server).
• Middle tier is a Server-plan or a Routing plane which help in routing SIP based request to the destination and fetching relevant data. SIP based server like SIP-proxy server, Promedia Server, Gatekeeper (for H.323 protocol) is grouped in this tier. Promedia servers are used for establishing session between SIP and H.323 based UAs.
• Database tier of the VoIP architecture consists of servers who maintains data regarding User agents, session billing and session authentication and other. Location server, Registrar server, Authentication server, Billing Server, IVR server are such example servers of this layer. The protocol which is used between the SIP proxy server and the database layer server is RADIUS, which is mainly transaction based protocol.

Procedure of VoIP Session:

SIP session/signalling are done using either TCP or UDP as a transport layer, with TCP as a recommendation to achieve fast session establishment.
• SIP based IP-node which is either a calling party or called party, is configured with IP-address and can be located anywhere physically and connected through internet.
• Called Party must be registered to the VoIP network via preconfigured REGISTRAR Server IP-address and Proxy server
• Calling Party has to be VoIP registered in order to initiate a call to the called user, it must also be configured with a Proxy server
• Called Party registers itself by sending REGISTER request to the Proxy Server. The Proxy server in turn updates the REGISTRAR server with Called Party IP-address, and/or domain and/or MSIDN/sip-URI. SIP-URI is nothing but a Unique Resource Identifier in sip format like ‘sip:[email protected]’. This association created in REGISTRAR server is uploaded into Location Server which is called as AOR – Address of Record. In most cases both REGISTRAR server and LOCATION server can be colocated into one box.
• Calling Party that wish to establish a communication with called user, sends INVITE request to the Proxy or Out-bound Proxy server with called party MSISDN or SIP-URI. Outbound Proxy server is nothing but a proxy server, configured separately for handling calls/session, which is again a deployment specific. Here Calling User will act as a UAC- User agent client and Proxy server acts as UAS – User agent server.
• Out-bound Proxy server receives INVITE request, response with 100 Trying response to the Calling user/UAC acknowledging Calling user that INVITE request is received and is being processed so it does not send multiple INIVITE request.  The proxy server fetches called user AOR from the location server and receives the called user IP-address.
• Proxy server routes the INVITE request to the called user IP-address received in AOR from the location server.
• Called Party upon receiving INVITE request, will to start ring with tone, notifying the user about the incoming call, acknowledging back with 180 ringing response. In the 180 Ringing, called party adds its own IP-address which is traversed backed to the calling party.
• When called party picks the calls, it response with 200 OK.
• Calling party upon receiving 200 OK response send another SIP request ACK, which indicates the flow of voice RTP packet.
• Session can be broken by either party, by sending a BYE request.

RTP and Voice Packets:

Voice packets are being transmitted between calling party and called party directly end to end in particular codec format.  SDP – session description protocol suit is also deployed along with SIP stack which maintains all voice packets stream and their measurement reports. Both RTP and RTCP packets are sent over UDP as a transport protocol to achieve real time streaming. RTCP provides feedback about RTP packets sends in reverse direction.

Features & Functionality:

SIP based protocol leverage to add call features like call hold, Call Park, call conference, both audio and video call, multi user support and many other call functionality. It is easy to deploy and flexible enough to twist to achieve desired result of Voice over IP.

Future Prospects and Deployment:

VoIP solution is key to fourth generation mobile communication supporting multimedia services like audio, video, chat, conference, announcement services. This technology is commonly known as IMS – IP Multimedia Subsystem, a standards of 3GPP project. SIP session createс high voice quality via dedicated bearer reserved for each SIP session. If the access type is LTE, then the voip session is termed as VoLTE( Voice over LTE) and if access type is Wifi, the voip session is termed as VoWIFI.

SoftPhones – first steps and installation



The technical term ‘Softphone’ is used for software applications which run on any device (mobile, laptop or desktop), and has telephone like functionality. Soft Phones are used to place VOIP calls which are generally cheaper when making international calls. Most of those applications actually run on hard phones(phones made specially for VOIP purposes) but there are planty also made for mobile and pc. The softphones work similar to any actual phone, with functionalities  like outgoing & incoming voice calls and outgoing/incoming Video calls. They are basically IP based phones, providing VoIP ( voice over IP) functionality, governing protocols such as SIP( session initiation protocol) , or H.323 or SCCP or any other similar proprietary protocol.

Examples of softphones for desktop and mobile:   X-lite, zoiper, Pindo, vChat, Whatsapp , Skype.

Procedure & Functionality :

There is quite a big diversity in soft phones . Some are made to serve the masses, and they are mostly free, while others are business and enterprise oriented with license versions. Softphones can be classified as a type of IP-phone with no hardware. The software supplication of the softphone available based on the OS platform basis Linux, WINDOWs, MAC like X-lite, etc. Following are the procedure steps for setting up the softphone:

  1. Software Installation
  2. License key configuration, if any
  3. Configuration


  • After successful installation, License key is entered to within the application of the software to make it working.
  • Few trial version of the softphone are available with limited edition i.e., once softphone installation is installed and running, it bind itself with the PC/Desktop/Laptop MAC address and this information is send to centralised server of the software.
  • This is done to avoid multiple installation of softphone on same machine.
  • Once the tenure of license expire, softphone stops working until license is renewed again.
  • Post License key configuration, desired network and dial plan related configuration is done in order to get it registered with server, which is VoIP server.
  • The IP –address of the system (PC/Desktop/Laptop) is used as the IP-address of the softphone itself.


  • Initial configuration of the softphone after installation also involves providing the IP-address of the proxy server which will be anchoring all services of the softphone like registration and call.
  • Softphone does its registration with the VoIP network in which Softphone Address-of-record (AOR) is populated in the VoIP location server database, and now softphone ready to send or received any call.
  • Most common usage of such softphone to test the network functionality.
  • Another usage of such softphone to perform load and stress testing of the network.

On Mobile

In Public network for mobile user: softphone is generally available as a mobile application. The software applications  are uploaded to public server like PlayStore or AppStore, from where the user can download it on his mobile. Most such apps require the user to have stable internet connection to operate (with the exception of Pindo and Rebtel). In the mobile market softphones are dominated by free apps  and there is almost no paid versions.. Following are the procedure steps for setting up the softphone on mobile:

  1. Software Installation
  2. User Profile creation


  • Softphone application is downloaded from play-store in a single click and get installed automatically on the supported version of the Mobile OS/Platform.
  • After successful installation, softphone application is brought up on the mobile by a click and user profile is created. Since such softphone is available for public use, hence the user profile creation steps generally involves linking with public social network, like twitter, Facebook, LinkedIn etc, and name/password, and OTP verification to authenticate user mobile number
  • Upon successful completion of the user profile, installed softphone is available to function as per designed functionality/feature.


  • Most such softphones doesn’t require any pre-configuration of network details.
  • The Server/Network details is in build within the software downloaded and ready to use more readily


If I have to make a bet I would bet on softphones with html based user interface. They are mostly used for commercial purpose like Video-Conferencing, license based conferencing for entrepreneurs, meeting, three-way calling etc. They come with Pay-and-Use functionality, and most of them are based on SIP protocol for session creation and media streaming.

Top open source alternatives to Slack team chat

There are a lot of open source alternatives when it comes to team chat software.

As it is with every team collaborative environment, communication is very important. What software works best in your case depends on your requirements and preferences.
The first collaboration tool that comes in mind is the indispensable team chat. It does not matter if your work colleagues are sitting across the room from you or on the other side of the planet. Communication in real-time makes conversations faster, easier, reducing confusion and misunderstandings.
While some circles still think that chat applications van be distraction. And they sure can be one if not contained. But I believe that if you are committed to your work, you can come to agreement to reel of-topic chats. Creating “general” channels can help loosen up, leading to better work flow. But it is equally important to be able to give yourself the space to work uninterrupted. While writing this article I have three team collaboration tools running in background. Still I keep all my notifications silenced and I check them only when the breaks in my work allow for it.
I recommend using an open source tool that is made exclusively for work. I like to separate work from personal communications and that is the main reason for me to try the software listed bellow.


Slack is the corner stone when it comes to collaborative chat software. It is preferred by the software development companies and for a good reason. It is stable, well designed and with all the right options. But Slack is not open source not to mention that it is pay to use. As such it is not very flexible. As a simple example is that you cant self host it. For big companies with lots of sensitive data this is a major turn off.
Open source with its access to the code helps you ensure that all communications stay private. Of course I should mention the option to add or remove features to further improve your work flow.
Let’s check five open source Slack alternatives. From the classics to brand new applications, for your team’s communication needs.


An honorable mention. The truth is that it has no place in any modern company. IRC has been around for a while – about 30 years actually, and it has tons of open source implementations.
As always with the age, come the drawbacks. It lacks features that are must for every modern chat. Security and Identity management barely exist (they are implemented with bot services).
On the good side, IRC is universal. Both servers and clients are available for every platform you can think of. The interface while not something to brag about is intuitive and fast. And if you have been developing open source, you most probably already installed or used IRC.

Let’s Chat

Let’s Chat has a more modern approach to team chat. Its program (also called Let’s Chat) is with MIT license and written on top of the popular Node.js platform. You will find many of the things that are expected of chat client like Slack. Image embeds @mentions, logging and file management. With Let’s Chat you can create chat rooms for every team, or project. It can integrate with your existing authentication servers. This way you can use the same login across all your software in your organization. As an addition Let’s Chat has a nice API that allows it to connect with other tools too.
The program is easy to install and self hosting is not a problem too. You can do it by Vagrant or Docker, or as part of There is an online demo, that does not implement all the features of the project. You can still get the general Idea of the program.


Mattermost is another app with modern approach. It is advertised as private cloud Slack alternative. It is written in Golang with a bunch of JavaScript under the hood of React framework. It supports both public and private chats as well as one on one conversations. It saves archives and is very similar to Slack interface wise. You can find all the expected team chat features. For people switching from Slack there is an import function that will import channels and chat archives.
Sadly as of late only the Team Edition is open source and free.


Rocket chat is my personal favorite. While it can be buggy at times if you are not using the Rocket chat+ client it is a descent program.
Rocket.Chat is written in CoffeeScript and JavaScript on top of Meteor framework. It is available under MIT license. Like most others it is with descent interface and available for both desktop and mobile. It is feature rich with the only thing that I am missing is the “talk to self” option.
Installation is easy and everything is well documented. The server can be on-premise or cloud based on their servers (paid option). As with most programs now days its available on every viable platform. There is an online demo that you can check.
Rocket.Chat features an online demo, and you can check out its source code on GitHub as well. Rocket.Chat is available under an MIT license. was one of the less popular chats but things have changed fast. It rightfully sits among the top alternatives of Slack now. Riot has quite a bit of mobile and web tools that connect to Matrix network. Matrix is open network for secure and decentralized communication. Among the functions I should mention its VOIP implementation. Bridge integrations with Slack, Gitter and IRC are available, for easy replacement with the open source client.
It is the easiest tool to try since it is web based (both client and host). Riot is licensed under Apache 2.0 license.

Other options

This is my personal favorites list and it is far from exhaustive. I encourage you to try and find a few others before you decide what chat to use.
Don’t take everything written in this list for granted. Lately more and more open source software companies are turning the back on free software. Some time has passed since I used some of the tools above and can I give no guarantee that they are still free or open source.

Top 10 Free PBX Solutions – detailed comparison

Which are the top free PBX business solutions

Adopting an existing VOIP service from the top PBX providers will get the job done for most businesses. But no one said it is easy to find the right one. Providers do their best to fit the needs of every business on a case-by-case basis. Nevertheless, with gaps in usage cases, business team sizes, required features or safety, it may be about impossible satisfy everyone. For all those cases where a service won’t fill in the gaps, businesses can turn to open source solutions or platforms. And yes there are open source PBX software solutions out there. With them any business can develop and tailor their own in house PBX applications. Since these platforms are open source, all the source is available for free online, and can be tailored for every specific scenario.


Asterisk is the godfather of all open source PBX and VOIP solutions. And it continues to function as gold standard. It is the leading open source telephony platform, with an enormous feature lists which only continues to grow each year. The Asterisk tool kit is used by a mass quantity of developers around the world. Many of the suppliers on our list have either begun with, or are based completely on the Asterisk project. It is packed with the standard PBX VOIP features. Consisting of automatic telephone, an interactive voice response menu, conference calling, and voicemail. Asterisk makes it easy workable to turn any computer. The program is free and open source. To help get you started, Asterisk provides live web classes, as well as an Asterisk Definitive guide. Asterisk can be considered The Platform when it comes to creating your own VoIP or PBX.


SIP Foundry provides much of the solutions that the Asterisk engine can power. With SIPFoundry you can construct your own voice and video communications. In addition it support conference calls, messaging and chat. Like with Asterisk, the platform includes everything you might need to build your own PBX solution. Nevertheless, whilst Asterisk is 100% free and open source depending on guides. SIPFoundry has a somewhat different spin. It offers professional paid assistance to developers based upon customer needs. While an excess cost to think about, adopting a support team might be a essential step for some businesses looking to build their own system. With a focus on the marketplace, the tool is free for commercial or private use. The project has also brought in features from other open source projects. HylaFAX, FreePBX, Openfire and Postfix.


Elastix intends to bring in Asterisk’s features and other such projects, all under 1 easy-to-use interface. Elastix boasts support for a wide range of hardware consisting of Yeastar, Dinstar, Digium, Yealink and Snom. It was actually 1 of the first distributions that included a call center module. And it proceeds to supply the solutionfree under the GNU General Public License. It’s come to our attention that Elastix appears to provide up to 8 SIM calls for approximately 25 users, since writing this post. FreeSWITCH was also based off the Asterisk platform, and was created and developed by 3 of the original programmers of the Asterisk platform. Anthony Minessale II, Brian West and Michael Jerris.


FreeSWITCH is with a focus on modulator, cross-platform service, availability and stability. It provides 1 of the most flexible platforms to construct your own UC package. FreeSWITCH supports SIP, H.323 as well as WebRTC to leverage the latest advancements in the technology. It can integrate and interface with other some of the other open source PBX platforms. For less complexity FreeSWITCH utilizes open software libraries that preform the essential functions. FreeSWITCH delivers the calling features and some extras such as speech recognition. It even offers PSTN ports for digital and analogue circuits.


Voicetronix is equipment supplier and a solutions that offers an open source platform, but also an assortment of hardware. The do-it-yourself OpenPBX of Voicetronix is a web enabled PBX program. It comes with a web based user management portal, in addition to a management GUI for easy and rapid configuration. It is feature rich with car attendant, automatic call distribution call routing search groups and even voicemail. Unique features like call hunt groups, music on hold and call records are good solution for businesses in need of a basic call center software. With CRM baked and enabled into the platform, users may not require to adopt a separate CRM solution, saving time and money.


PBXInAFlash main feature is the ability set up your own PBX server in no time. The project has everything needed to set up a PBX system in under one hour. It uses CentOS, with integrated Apache web server, SendMail server, and MySQL database. In addition to firewalls and all essential protocols. Users have the option to pick from dozens of add-ons to tailor the system. Backups, Caller ID look up services, SSL keys, Google Voice integration, and fax support to name a few. With the number 1 goal of no bloat and no bugs, PBXInAFlash seems to be easiest and the quickest solution to adopt.


FreePBX combines the best of both worlds, and leverages the work. While the project uses the Asterisk system, users may download either just the GUI to add on to their current system, or the whole package. It consists of a per-configured program OS, Asterisk, and the FreePBX GUI. So while by adopting Asterisk, some knowledge may be required to take advantage of, or to create your own GUI, FreePBX brings it all together. FreePBX makes it feasible to establish your SIP Trunks that are part of the platform thanks to the integration. FreePBX also contains a long list of commercial modules and add-ons to enhance your system with even more features.


With a focus on open source implementation of a SIP server, with OpenSIPs its easy to set up your own PBX. The platform supports video, voice, IM and presence services. It is using modular design, it is scalable, and very much customizable. OpenSIPs enterprise class SIP server solution and a very fast one at that . OpenSIP has made a list of benchmarks and performance tests to back their claim up. Similar to Asterisk, OpenSIPs often records webinars, and makes in depth manuals for configuration. A web interface makes it easy to collect data and shows on the fly configurations.


Kamailio is an open source project with 15 years of constructive development. And while the original company left the project, it continues to expand, both the SIP server and Kamailio project continue to build on. With features like UDP asynchronous TCP and SCTP, TLS to ensure secure communications. VoIP data consisting of voice video and text, and even WebRTC support the hard work can clearly be seen. Kamailio also supports instant messaging, least cost routing, load balancing, routing fail-over. Realizing that security features are important they are offering the strongest level of security on this list. Authentication and authorization for enhanced security as well as the level of encryption that the platform gives makes it a good recommendation for any staff or business that needs to keep everything as locked down and protected as possible. As a result of all that, Kamailio may be a bit more challenging to adopt.


The 3CX Phone System is the last open source PBX based upon the SIP standard on the list. This solution allows extensions to make calls on the PSTN or standard services. The platform also offers an easy to understand web based GUI, and the process to is actually simple – an executable file. 3CX supports iOS and Android for mobile customers, of coarse Windows and Mac softphones are supported too. It appears to take out the hassle of development required to establish your own PBX server. WebRTC adoption makes web conferencing possible. Click2Call and CRM are also part of the features. As most others, internet training academy is readily available for users to understand how to manage the platform.

Voip for blind people – Team Talk 5

Open source Voip for visually impaired!

Team Talk 5 review

TeamTalk is VOIP conferencing system that people use to communicate using VoIP and/or video streaming. The part with video streaming puzzles me as the program has community made of mostly blind people. They can log in with a simple tt document and converse easily with their contacts. The project is open source and using open source solutions for most of its functionality.


  • Audio and video transfer with VOIP
  • Public and private channel creation
  • Sharing of desktop aplications
  • File sharing
  • Standalone server


The TeamTalk 5 conferencing system is composed of a client and hosted server. Most users will just need to install the client application, unless of coarse they want to have their own TeamTalk 5 server.
When installing the application on Windows, the visually impaired users, should install “TeamTalk 5 Classic. It is the client with better accessibility, since the Classic version works smoother with screen readers. There is also a regular TeamTalk 5 client developed for the masses.

Open Source

TeamTalk is a freeware. The program can be found on a lot of popular software websites. Its license permits, to be run on numerous clients or servers, it can be also redistributed free of charge. A permit must be nevertheless bought by developers that want to implement or use the code in third party programs.

TeamTalk client software have been build around the GitHub project TeamTalk5. The TeamTalk server is not part of the project and is therefore not publicly available.


The TeamTalk 5 can be downloaded for Windows, Mac OS X, and the most used Linux distributions – Debian, CentOS, and Raspbian. The server and client applications run on the same platforms. The only difference being that the client additionally supports the mobile platforms of iOS and Android.


For voice encoding TeamTalk uses the open source audio and video codecs. For the audio codecs it uses Speex and OPUS. And for the video stream encoding the program is relaying on WebM video codec.