TeleDynamics Think Tank

By Nathan Miloszewski, on behalf of Yeastar

When it comes to VoIP PBX systems, channel partners need to determine whether an on-premise solution or a cloud-based service is best suited for their customer.

Each solution has its strengths. For the instances in which you determine that an onsite IP PBX is the best option for your customer, we’ve put together these guidelines to help you sell against the hosted solutions offered by your competitors. Here at Yeastar, we work with thousands of channel partners who find themselves in competition with cloud-based VoIP service providers and have identified the most compelling arguments for an on-premise solution. Think of each one as an additional arrow in your sales quiver.

By Stefan Eriksson, Marketing and Communications Manager of Konftel

Remote meetings with poor quality audio are often exhausting. Misunderstandings become more likely because it’s difficult to hear nuances and other subtleties in conversation. So you want to aim for the best sound quality possible during teleconferences. The following is a quick explanation of different technical requirements for audio quality.

• A purely mobile solution gives you great flexibility and mobility, but sometimes at the expense of sound quality. Many mobile operators now offer HD Voice in their networks, which delivers HD audio if the phone supports the technology.
• Traditional analog telephony delivers an acceptable sound quality, but with limitations in frequency range. Sometimes known as telephone quality or narrowband.
• VoIP, i.e., digital telephony via the data network (voice over IP), allows for extended frequency range, but with some compression. IP makes it possible to achieve superior audio quality, also called HD audio or wideband.
• Remember that all local networks and accessories, e.g. Wi-Fi, DECT (wireless telephony) or Bluetooth^®, affect the transmission capacity and can have an adverse impact on the sound quality.
• All of Konftel’s phones and conference units offer HD audio in contexts where PBXs and networks support it.

Replacing a legacy PBX that a company has used for years with an IP PBX can be intimidating, and understandably so. That’s why we recommend a transition method that allows the new technology to be gradually introduced over time. This not only ensures business continuity but also gives the associates plenty of time to adjust to the new equipment.

Businesses are constantly trying to boost productivity so they can do more – and grow more – with less. SIP telephony is a great example of this. Compared with legacy PBX-based phone systems, IP phone systems allow companies to do much more, with less hardware and fewer resources.

Ensuring business continuity in case of unexpected service loss is an essential component of any IP telephone system. In a previous blog post we mentioned various failover mechanisms that can be deployed to address different scenarios. Here, we’ll take a closer look at two in particular: backup SIP trunk or ITSP, and failover servers. You may be surprised to discover how easy and affordable they are to set up – especially when compared with the costly alternative of service interruption.

Open source with open access vs. open source:
Make sure you know which one suits you and your customer. 

Open source telecommunications systems are not all created equal. All are open source in the sense that they are built using publicly and freely available code like Asterisk. However, not all of them allow access to the root programming level, which allows you to modify or customize aspects of the code to suit specific requirements or preferences. If a system restricts root-level access, certain features may be customizable, but don’t count on having much leeway. Be sure you know which one best suits your customer.

These features absolutely must be in your IP PBX suite offering

When proposing IP voice solutions to small businesses, certain applications and features are so essential that the customer won’t even consider purchasing a system without them. According to a study of more than 200 small businesses conducted by SoftwareAdvice, the phone system applications most often cited as “required” are:

Two solid strategies for distinguishing yourself in the marketplace and protecting your margins

“Cheap is the last refuge for the marketer who can't figure out how to be better.”  - Seth Godin

We consider session border controllers (SBCs) to be a best practice in most enterprise contexts because of the improved security, control and overall VoIP system functionality they lend.

So what exactly are SBCs and why do you need one?

National telephone operators have been investing less in maintaining traditional PSTN networks and paying more attention – and money – to building out their mobile and Internet protocol (IP) networks. AT&T launched its Project Velocity IP in 2012 with the intention of expanding its wired broadband IP network to reach 75% of its customer locations in three years. In Europe, British Telecom and Deutsche Telekom both have their sights set on all-IP. DT’s website says, “The network of the future is an integrated, all-IP network.”

A common reason some businesses still cling to their PSTN lines even when they’ve switched to a VoIP (voice over IP) phone system is to have a failover option. Here we look at some other failover mechanisms that don’t require a PSTN line, as well as the key benefits to switching to all-IP.