Sangoma Reaffirms Open Source Communications Commitment and Leadership at AstriCon

New Releases of Both Asterisk and FreePBX Software Announced

AstriCon, ORLANDO, Fla., October 9, 2018 – Sangoma Technologies Corporation (TSX VENTURE: STC), a trusted leader in value-based Unified Communications (UC) and UC as a Service (UCaaS) solutions and the world’s largest provider of open source communications solutions, today at the annual AstriCon users and developers conference, announced Asterisk 16 and FreePBX 15, the next major releases of the world’s two most popular open source communications projects.

“On behalf of all the employees of Sangoma and Digium, I would like to welcome the global community of open source communication developers to AstriCon,” said Bill Wignall, President and CEO of Sangoma. “It is clearly the premier event in the world today for this part of our industry, with attendance approaching 1,000 people, dozens of speaking sessions from amongst hundreds of submitted abstracts, and a full exhibitor floor. I’m very excited about this year’s event, and as we work hard at bringing our two companies together, I’d like to take this opportunity to assure the community of our commitment to these critical open source projects that mean so much to the communications world. I hope that today’s major releases of both Asterisk 16 and FreePBX 15 demonstrate that we are already actively delivering even more innovation that will further enhance the missions of the two projects and their value to the communities.”

Read the Full Press Release

FreePBX EndPoint Manager & PhoneApps Now Free for Digium D Series Phones

Great news for Digium D Series phone owners. Sangoma is pleased to announce that the latest Edge release of FreePBX EndPoint Manager (EPM) and PhoneApps now support the Digium D Series phones free of charge. In the past you would need to purchase a commercial module license to use Digium phones with EPM and PhoneApps as a 3rd party phone, but now that Digium is part of the Sangoma family we want to save you money!

Currently this includes the following D Series Digium phones: D40/45, D50, D70 and all D6X. As of this release the D80 is not supported in FreePBX or PBXact, but we are working on getting that done ASAP for all of our users.

The following versions of EPM and PhoneApps are the minimum version you need to be using to have Digium phone support unlocked for free.

  • FreePBX or PBXact 14 EndPoint Version 14.0.2.153 or greater
  • FreePBX or PBXact 13 EndPoint v13.0.118.103 or greater
  • FreePBX or PBXact 13 or 14 Restapps 13.0.92.20 or greater

Stay tuned here for more updates, and welcome to the new Sangoma!

Sangoma, Open Source Communications & AstriCon

With Sangoma now the primary developer and sponsor of the world’s two most widely used open source communication software programs (Asterisk and FreePBX), I find myself working for the largest open source communications company in the world! And with AstriCon two weeks away, this is a good time to reflect on that journey.

I’m not sure I saw this coming, especially coming from the UNIX System V world where I saw Linux totally supplant what we had built there. And when I went to Dialogic from that world, I latched onto Linux drivers immediately for my products. This had the effect of showing me both sides of the disruption in the UNIX/Linux atmosphere. Ultimately Linux ended up being better for the customers, and the industry, and it’s now in more places than UNIX could have ever imagined.

Here at Sangoma, with Asterisk and FreePBX, the disruption caused by those products is somewhat mature. It has changed the industry, but there is still more to do. Voice obviously isn’t as central to enterprise communications as it used to be, but it is still important. And Asterisk is still an open source communications platform, so it is still there for creative minded people to build on. This has led to our growth as a company, and will be part of our continued growth.

Now that Sangoma is at the helm of both of these products, we are still getting questions about whether Asterisk and FreePBX will merge. Before I answer that question, I want to make a point that we at Sangoma take the “stewardship” of these open source platforms seriously. We’re not going to do anything rash. Both Asterisk and FreePBX will continue. They serve two different purposes. Asterisk is a development platform for many different kinds of communication solutions. The most widely known of course is a PBX, with FreePBX being an example of a such a PBX. FreePBX is built on Asterisk, so they don’t compete at all. They are complementary and have always been complementary.

Yes, developer teams can share ideas and new features as applicable given a PBX is an important result of Asterisk, but that doesn’t mean they’ll merge.

Join Sangoma at AstriCon to hear more about it!

Remote IP Phone Security Using VPN

Using VPN (IP-Sec) is a completely different way to provide a secure VoIP solution. Using already well-established encryption tunnel technologies, a secure tunnel is created between the remote phone and the IP‑PBX.

In this example, the IP‑PBX resides behind a typical network firewall. The firewall is the border element between the Internet and LAN. The remote phone is located on a remote network across the Internet and the remote phone is establishing a VPN (IPSec) tunnel to the IP‑PBX. VPN (IPSec) is a network protocol suite that authenticates and encrypts the packets of data sent over the network. The firewall is relaying the VPN (IPSec) tunnel from the remote phone to the IP‑PBX.
Security Best Practices

In this example, the IP‑PBX resides behind a firewall, the firewall is the border element between Internet (or untrusted network zones) and Local Area Networks (or trusted zones). The firewall is a network security device and will forward the VPN (IPSec) traffic from the remote phone to the IP‑PBX.
Security Best Practices

If you enjoyed this blog, and would like to learn more about Security Best Practices for VoIP, download our whitepaper here: sangoma.com/voip-security-best-practices/

Remote IP Phone Security with SBCs

A remote phone deployment is completely different than SIP trunking. Remote phones are dynamic in location, and require significantly more calling features. Remote phones cannot be considered as peers, since phones register for services and change IP addresses often across multiple devices and locations.

Remote phones require automatic provisioning with file servers and possibly require web access and REST API access to the IP‑PBX. The interconnectivity between a remote phone and IP‑PBX is complicated with many communication requirements.

The application of security solutions involves providing a Session Border Controller (SBC) solution that is used to define the remote phone to the IP‑PBX relationship between various networks using VoIP application layers, file provisioning and other services while ensuring signaling and media are secure. This method highlights the strength of the SBC to protect the IP‑PBX, while providing solutions for remote phones located behind other firewalls.
Security Best Practices

In this example, the IP‑PBX resides behind an SBC. The SBC is the border element between Internet (or untrusted network zones) and Local Area Networks (or trusted zones). The SBC is a network security device as well as a VoIP security device that monitors incoming and outgoing network and voice traffic and decides whether to allow or block specific traffic based on a defined set of network and voice security rules.
Security Best Practices

If you enjoyed this blog, and would like to learn more about Security Best Practices for VoIP, download our whitepaper here: sangoma.com/voip-security-best-practices/