Lync Phone Edition (LPE)

Lync Phone Edition (LPE) – AudioCodes offer Teams Ready device upgrade


AudioCodes is introducing a replacement program for Microsoft LPE (Lync Phone Edition) devices that will stop working with Microsoft Office 365 services beginning on October 31, 2018 when only TLS 1.2 compliant devices will be supported. The offer can be found and claimed on the AudioCodes website at

What are Lync Phone Edition (LPE) devices and why won’t they work?

Lync Phone Edition (LPE) devices are the IP Phones first launched alongside Lync 2010.  The phones were produced by third-party certified vendors like Polycom, HP/Snom & Mitel/Aastra.  All of them run Windows CE 6.0 and a Microsoft written Lync Phone client. Windows CE – and therefore Lync Phone Edition – doesn’t support TLS 1.2, therefore, when Microsoft enforces TLS 1.2 only on Office 365, these devices will no longer connect.

Lync Phone Ediiton (LPE)

AudioCodes offers Teams Ready device for Lync Phone Edition (LPE)


The models of Lync Phone Edition (LPE) devices that are affected by this change are:

  • Polycom: CX500, CX600, CX3000
  • HP: 4110 and 4120
  • Mitel/Aastra: 6721ip and 6725ip

Why is this important?

Older TLS versions (1.0 and 1.1) are known to have vulnerabilities used by hackers. Security regulated markets (for example credit card processing) force services to only utilize modern TLS implementations. While Microsoft has stated that there are no known vulnerabilities in their own implementations of TLS 1.0 they recognize the potential for future vulnerabilities and making this change to more modern TLS. These newer regulations also encourage moving toward new security mechanisms – for example, Modern Authentication that Microsoft has implemented in recent years.  These newer security mechanisms are fully supported by AudioCodes phones.

Microsoft will enforce TLS 1.2 on the Office 365 Cloud on October 31, 2018. Affected phones can utilize different services within Office 365. As mentioned above, basic calling may be facilitated by Skype for Business Online so that is affected. Likewise, affected phones can utilize Exchange Online services for calendaring, voicemail services, Outlook contacts, call logs, and more. The fact that phones cannot access Exchange Online services will also impact on-premises/hybrid deployments using Exchange Online.

Will this affect my existing non-LPE devices?

All 3PIP (Microsoft 3rd Party Interoperability Partner) phones which are certified for Skype for Business Online will continue work after this Office 365 TLS 1.2 change and work with and be supported by Microsoft Teams. There will be no change to 3PIP phones connected to Skype for Business Server on-premises. They will be able to join Microsoft Teams scheduled meetings and place calls with the same user experience and features detailed above in the Microsoft blog.  LPE Phones will still be able to connect to Skype for Business Server on-premises as long as TLS 1.0 and 1.1 are supported in that deployment. Connectivity to Office 365 features like Exchange Online will not work after October 31, 2018.

Additionally, at Enterprise Connect in March 2018, Microsoft announced a new line of ‘native Teams’ phones that run a Microsoft Teams app directly on the phone itself. LPE phones will not work with Microsoft Teams. For more details check out the Microsoft Tech Community blog. The current Microsoft Office 365 roadmap shows this support coming in 3Q 2018.

How can AudioCodes help?  Are there trade-in/trade-up incentives?

Yes! AudioCodes is introducing a replacement program for Microsoft LPE Phones that will stop working with Microsoft Office 365 Services beginning on October 31, 2018 when only TLS 1.2 compliant devices will be supported. The offer can be found on the AudioCodes website at:  For every model of AudioCodes in this offer, we have a matching (or more advanced) set of features. On top of standard expected calling features, our AudioCodes phones have modern features like advanced boss-admin, sidecar options, resiliency options, superior centralized management and more.  A few charts detailing how AudioCodes phones compare – along with frequently asked questions – can be found on our LPE Upgrade Program FAQ page.


Direct Routing the future of hybrid voice with Microsoft Teams

Direct Routing the future of hybrid voice with Microsoft Teams

On May 15th, 2018 Microsoft announced Public Preview of Direct Routing for Microsoft Teams via this blog. You might ask, what is Direct Routing? Direct Routing is the future of hybrid voice with Microsoft Teams, allowing organizations to leverage on-premises voice infrastructure through Teams certified SBC’s (enter AudioCodes). You can find more information by viewing the Microsoft blog Here.

What does this all mean and what benefit do I get?

What exactly does this all mean for you? It depends on where you are in your UC/IC journey. For some, the journey might be moving from an existing PBX to Microsoft Teams calling directly. Others might already be using Skype for Business / Skype for Business Online and ready to make the move to Teams calling. Still, others might have sites around the globe that are not yet able to migrate phone numbers from the local Telco providers into Microsoft Calling Plans.

Organizations looking to migrate to Microsoft Teams calling can now utilize direct SBC connectivity into the Microsoft Teams environment. This allows customers to bring their own PSTN trunk into the Microsoft environment via a Teams Certified SBC. With the combination of Teams and an AudioCodes SBC, organizations will now be able to take full advantage of Microsoft’s Intelligent Communications vision by providing a complete Teams experience for their users.

Direct Routing the future of hybrid voice with Microsoft Teams

What about my environment today and tomorrow?

Customers that currently utilize AudioCodes infrastructure to connect to their existing PBX, Skype for Business on-premises, or Skype for Business Online with Phone System (previously Cloud PBX) are in a great position. In this scenario, you have the ability to leverage your existing infrastructure and repurpose/reconfigure/update it to connect to the Microsoft Teams environment. If that current infrastructure is not already in place or maybe it needs an upgrade, AudioCodes has a large portfolio of certified SBCs that supports from a few sessions all the way up to tens of thousands of current sessions.

The benefit of a complete, unified portfolio is that AudioCodes has a solution to fit your needs today and tomorrow, from physical devices to a full complement of highly scalable virtual instances. Furthermore, depending on the level of functionality required, the SBC portfolio can also provide advanced high availability (HA).

Things to consider with Direct Routing SBCs from AudioCodes

Now that we know of the wide range of options available in Direct Routing scenarios, what about diving into some specific use cases that make the AudioCodes SBC stand out?

  1. Ever wonder what you are going to do with those existing analog devices? How in the world do I plug that analog wire into the cloud? That will likely never happen, but AudioCodes has you covered. Time and time again, the conversation comes up on how to integrate these existing analog devices (think elevator, common area, warehouse and laboratory phones) in organizations both large and small. For these scenarios you can easily place an AudioCodes MediaPack (analog adapter) behind the SBC, providing the necessary connectivity to allow Teams users to communicate with the analog device (and vice versa). Analog in Teams – no problem.
  2. What about sites that cannot have an SBC connect to the open internet and thus directly into Teams? Perhaps these sites only have MPLS back to a centralized site to funnel all outbound traffic. This is most common in larger organizations where local internet is not the best fit for the organization. The SBC can serve dual purposes to handle this situation – a centralized hub that hosts the main infrastructure (aka SBC) along with a spoke at a branch site with a local PSTN breakout. That local PSTN break out could be required due to local regulations or because of a cost-effective contract with a provider. Either way, the AudioCodes solution stack can make this type of scenario possible.
  3. Do you have a local regulation that requires routing of calls based on the location of a user? Specifically, when dialing emergency numbers (911, etc.) do you need to present to call to the PSAP in a specific fashion (aka ELIN)? That is a driving factor to leverage the SBCs ability to utilize the IP address subnets within a network and where the user generated the call to make logical and dynamic routing decisions. With SBCs in the environment, especially connecting to on-premises trunks, AudioCodes has the ability to utilize the SBC routing logic to make intelligent decisions based on the IP address of a particular user. This functionality is critical in emergency (aka 911) environments, especially when it pertains to larger campuses. A person making an emergency request may be pinpointed to a specific floor and room, allowing first responders to granularly identify their location.

What Next?

Now is the time for organizations who are looking to test Direct Routing with Microsoft Teams to contact your local AudioCodes representative or get in touch with AudioCodes via our website. Working with Microsoft for over 12 years, this is just another exciting step in the evolution of Enterprise Voice. AudioCodes is keen to work with you to architect the best path to the Teams future while keeping an eye on existing capabilities. If you already have SBC licenses in your environment, AudioCodes will be able to help determine the best way to connect to the Teams backend. For organizations that are not yet leveraging AudioCodes infrastructure, reach out today to get started with AudioCodes and Direct Routing in Microsoft Teams.

Watch over everything from a single pane of glass

A Network Management Idea Whose Time Has Come

Watch over everything from a single pane of glass

A few weeks ago, when my wife and I celebrated our 30th wedding anniversary, she bought me one of those (very) expensive, high-end watches. But even though my wife has excellent taste, and did indeed choose a beautiful timepiece, I’ve got to admit that I’m very far from being a watch fanatic. To be honest, I haven’t worn a watch on my wrist for over 10 years. Why would I need to? If I want to know the time, all I need to do is have a quick peek at my mobile phone. Even better, I can also see the date, my emails and my WhatsApp messages — and I can even get an up-to-date weather forecast for anywhere in the world. It’s all there. So much information available at a single glance.

What if there was something similar in the telecommunications industry that could make managing networks almost as simple as having a quick look at a single pane of glass? After all, VoIP management landscapes generally comprise three main layers of management tools that you need to learn and keep up with.

Let’s have a look at each of these layers.

In the top layer, sitting above everything, are the service providers’ network management systems (NMS). Typically vendor-agnostic, these applications provide a picture of the aggregated status of the entire service provider network. The service provider NMS aggregates the multi-vendor EMS indications into a central view and gives general network level insight.

The second layer consists of multi-vendor VoIP management solutions. These applications monitor the voice quality of all the elements in the network and provide a root cause analysis based on the voice and data layers combined.

The third layer is made up of vendor-specific management tools and expert systems that cover device and element management, service monitoring, analytics, security and advanced centralized VoIP routing.

For monitoring the devices’ status, an element management system (EMS) is going to be your application of choice. When you need to perform a root cause analysis on a VoIP issue, another application will be required. The same goes for analytics — you’ll need a third application for that. It’s a bit like having to walk around all day with three different watches on your wrist — one to tell you the time, one to tell you the date and one to tell you what day it is.

And talking of time, it’s clear that the time has come for a network management solution that gathers all these disparate parts together under one roof. A full lifecycle management suite for VoIP deployments that provides monitoring, management and operation of all the products in the network — all in a single pane of glass.

AudioCodes’ One Voice Operations Center (OVOC) is that solution. OVOC shows all the devices associated with a specific user and the user service experience in a single window, without having to jump from application to application. From this one solution, you can do everything that previously demanded several different applications, including:

  • New device detection and configuration
  • Accurate inventory population
  • Automation and mass operation support
  • A central, correlated alarm dashboard
  • Group-based configuration and update management
  • Change documentation and device configuration backup and restore.

A Network Management Idea Whose Time Has Come

And if all that wasn’t enough, you also get service alarms, trends and statistical analysis, reporting, user experience monitoring, root cause analysis and issue correction. OVOC brings it all together in a single pane of glass, exactly the way a smartphone does.

Although I don’t really like the watch my wife bought me, I feel compelled to wear it. I genuinely want to remain alive to be able to celebrate my 31st wedding anniversary. However, now and again something strange happens. Sometimes, when my wife and I are winding down with a glass of wine and a movie in the evening, my watch will suddenly pick up a reflection from the television screen. Instinctively, I tap on it as I would my phone to see if I’ve got any messages. Old habits always die hard, don’t they? With a quizzical look on her face, my wife asks me if all is OK with the watch and reminds me that it has a lifetime warranty.

Our application note, The OVOC Journey from Detection to Correction, explains in detail how OVOC seamlessly fuses VoIP network device management and quality of experience monitoring into a single, intuitive web-based application.

To learn more, click this button.

Get It Now

SBC Routing Tables Made Easy

SBC Routing Tables Made Easy

Taking the pain out of configuring service provider SBC routing tables

Session Border Controllers (SBCs) are a vital part of any VoIP network. Deployed, as their name suggests, at the border between an enterprise and a service provider, SBCs provide connectivity, security, quality assurance, regulatory compliance and media services. Not only that, SBCs are also adopting more and more network roles with the rapid growth of unified communications.

So it’s clear that SBCs are here to stay. But if you’ve ever configured a service provider SBC, the chances are you know exactly how complex the routing tables can get when each service provider SBC is a key element of the link to literally thousands of customers.

In fact, it wouldn’t be a stretch to say that configuring the routing table is generally thought of as being the most complicated part of incorporating and using an SBC in a network.

Obstacles Ahead?

Let’s have a look at some of the challenges that present themselves.

Because of the sheer number of customers that service provider SBCs are responsible for, you should take several important points into consideration when you configure routing tables.

Firstly, a service provider SBC must be able to easily distinguish between different customers while routing INVITES from the service provider server. It must also pass details about the customer to the service provider server while sending an INVITE from the SBC to the server.

Secondly, you need to determine how to eliminate the need for per customer message manipulations, customer service records and routing rules.

Thirdly, you’ve got to be able to configure call admission control for each customer.

And lastly, you want the ability to add additional customers without touching the common configuration settings.

Finding the Right Way

We at AudioCodes make it our mission with everything we do to cut right through to the heart of the matter. Our aim is always to make complex technology as easy to understand and as simple to use as possible. So, in the case of our SBCs, one of the things we asked ourselves was how we could make routing table configuration as painless as possible.

Our answer was to take apart and completely rethink the traditional SBC routing configuration model. We developed the concept of routing tags to simplify and reduce the number of route rules that need to be defined.

In essence, this involves dividing the routing process itself into two separate actions by adding a new route tagging stage. This is preceded by the classification stage and followed by the routing table, as per the traditional model. This means that routing on AudioCodes SBCs is actually executed over three steps instead of two, as shown below.

SBC Call Routing Architecture

SBC Call Routing Architecture

This configuration procedure is GUI-based, with no scripts needed. As a result, the routing tables are compact and easy to read, delivering total routing flexibility.

We’ll Get You There

This approach ensures maximum flexibility and can easily be adjusted to new methods or different nuances, such as different flavors of TGRP. Also, different data exchange methods can be used at the same time on the same device, with the ability to translate between them. The required configuration for each customer is minimal, there is no configuration redundancy, and configuration is non-bleeding. Finally, our SBCs can use external databases for routing, and they also allow both routing and advanced message manipulations.

OK, we admit it. We can’t (at least, not yet) give you a magic map or a handy GPS unit to figure out your SBC routing tables for you. But we think we’ve put our SBCs together in such a way that you can avoid most of the routing headaches. Why don’t you join us for the journey?

To learn more about making SBC routing easy, click the button.

Talk to us

Cast a spell over your SBCs

We’re Off to See the (SBC) Wizard

Try the magic wand that makes SBC configuration easy

In the Wizard of Oz, Dorothy and her companions found themselves trapped in a strange and unfamiliar land where nothing was as it seemed and everything was vastly more complicated than it needed to be. They embarked on a long search for everyday things that most of us usually take for granted, before finding out at the end of the movie that they had them all along but just didn’t know it.

SBC configuration is complex and time-consuming

If you’ve ever had the pleasure of installing SBCs for your customers, you’ll know that each deployment is different and that each SBC has thousands of possible parameters that need to be configured. The complexity of configuring these SBCs not only takes up a huge chunk of time – you also need well-trained (and therefore highly paid) people to do it.

What if there was another way of configuring SBCs that could cut through all the complexity? A splash of color in the middle of the monochrome monotony of network configuration. Well, now there is.

A simple solution to end complex configuration processes

At AudioCodes, our “Oz moment” was realizing that 80% of all SBC installations only use about 20% of the possible configuration parameters. We also understood that any differences between two installations containing the same PBX and SIP trunk service types tended to be very minor indeed. These two factors showed us where to look for an effective solution.

The AudioCodes Mediant SBC Configuration Wizard was designed with one thing in mind – to make the whole SBC configuration process quick and easy.

Cast a spell over your SBCs

As you’d expect, using the SBC Configuration Wizard is simplicity itself. You start by selecting the required IP-PBX model and SIP trunk service. After that, the Wizard walks you through a handful of straightforward and intuitive configuration screens.

Our templates make everything easy

The SBC Configuration Wizard works with a set of interoperability templates for different IP-PBX models and SIP trunk services. The AudioCodes template database currently contains over 35 IP-PBX models and over 95 SIP trunk services. Brand new and updated templates are routinely created by us and are then stored in the AudioCodes cloud. Whenever you open the Wizard, these templates are automatically available for you to use right away.

Once you’ve finished filling in the Wizard screens, you’ll see a summary of all the configuration details. If you’re happy with everything you’ve done so far, you can go ahead and create a configuration file. You can then send this file directly to the SBC, or you can save it for later if you haven’t yet installed the SBC on site. And that’s it.

Ready to go in less than five minutes

In many cases, the SBC will be fully operational at this point. In other cases, although you will be able to route calls through the SBC, you might also need to configure a few additional parameters on the device’s web GUI.

The AudioCodes SBC Configuration Wizard is available on the SBC Web GUI and as a standalone Windows application. The SBC Web GUI is ideal for on-site configuration, whereas the Windows application can be used to configure an SBC ahead of time before its actual installation.

The SBC Configuration Wizard has been used by our customers on thousands of installations, and is a tried and tested way of significantly reducing the length of time it takes to configure AudioCodes Mediant Session Border Controllers (SBCs). You can usually expect to have the first calls going through the SBC in less than five minutes.

In addition, the SBC Configuration Wizard can be used to configure AudioCodes media gateways and Multi-Service Business Routers (MSBRs).

Cast a spell over your SBCs

If you’re deploying AudioCodes Mediant Session Border Controllers (SBCs) in a customer’s network, you owe it to yourself to make configuration simple. Try the AudioCodes SBC Configuration Wizard now and pull back the curtain of complexity. You’ll be glad you did.

Put the Wizard’s magic in your hands today

Get it Now

Unified Communications: Technologies that Paved the Way for Cloud Communications Dominance

A Brief History of UCaaS

Guest post by Mark Dacanay of RingCentral

It was just a decade ago when only small and medium scale businesses saw cloud communications as a viable option for a business communications solution. Enterprises mostly ignored the emerging technology because they already had on-premises PBX phone systems and traditional telecoms that they had already been using for too long to take notice of a new alternative.

Technologies that Paved the Way for Cloud Communications Dominance

Technologies that Paved the Way for Cloud Communications Dominance

Fast forward to 2018 and cloud communications is poised to dominate the market through cloud-hosted unified communications solutions. On-premises PBX systems are on their way to being obsolete, while traditional telecoms are struggling to keep up with an always connected generation. In fact, the global unified communications and collaboration market is predicted to top $35 billion by 2019.

It seems like cloud-hosted unified communications is here to stay and is set to dominate the business communications industry in the near future.

But before we look more into the future, it is important to look back to the past. How did we end up here? How did cloud communications, specifically unified communications as a service (UCaaS), come to dominate?

To give you an insight, here are the technologies that paved the way for cloud communications dominance:

Development of VoIP

It was around 2000 to 2005 when companies started using IP networks to transmit voice data. The technology was called Voice over Internet Protocol or VoIP. Adoption was not that fast. In the early 2000s, very few calls were transmitted through IP based lines and companies still preferred the traditional PSTN. However, as internet connections became more stable, more and more companies saw the benefits of using VoIP. By 2008, 80 percent of all new corporate lines being installed were VoIP lines. Now, VoIP is used by most unified communications providers as its primary method of transmitting calls or voice data.

Virtualization of infrastructure

The 90s were all about hosting software on your own PCs, so it is not surprising that most businesses at the time also hosted their business apps on their own servers, within their own infrastructure. Intranet services or local web connections that could only be accessed within the premises of the company was a big thing back then. Aside from the familiarity with on-premises systems and infrastructure, cloud technology was still in its infancy and there were still various security concerns that needed addressing. After all, data is stored by a third-party provider and it is transmitted over the public internet.

It was not until Salesforce launched in 1999 that businesses were able to use an actual enterprise app delivered over the ‘net. Salesforce, like today’s cloud services, hosted their suite in a virtual server and delivered the service via the internet, which was accessed via their website. Since then, various cloud services have popped up including Amazon Web Services in 2002. Thus, the virtualization trend has begun. Organizations started delivering services (SaaS, PaaS, IaaS) via the cloud through different deployment models, namely private cloud (solely for one organization), public cloud (open for public use), and hybrid cloud (a combination of public and private). Security has also been addressed with most providers employing security measures like heavy encryption on all facets of data transmission.

Circumstances also aligned for the emergence of the virtualization of infrastructure. This includes the improvement of high-speed internet and the support of leading tech giants like Google and Microsoft. When these giants embraced virtualization technology, it also caused a domino effect within the industry as a whole.

Moving PBX from on-premises to the cloud

Private Branch Exchange or PBX has been around since the 40s. In the beginning, PBXs were simple systems managed by the local phone company itself. Calls were routed from the Central Office (CO) to a business customer. It was very simplistic back then but it paved the way for on-premises systems where companies invest in their own PBX infrastructure to route incoming calls within the company. As mentioned above, the virtualization of infrastructures presented an opportunity for PBX to be deployed through the cloud. Through the Software as a Service model (SaaS), cloud PBX started making noise around 2005 to 2010 as an alternative to on-premises PBX for small and medium companies who could not afford to invest in their own PBX infrastructure. But what started as an alternative to on-premises PBX soon became a viable business phone system for companies of all sizes because of its mobility, flexibility, and scalability, not to mention the numerous advanced features like auto-attendant, answering rules, caller ID, call screening, and call forwarding. As an actual business phone system, the cloud PBX has become the backbone of what we would call unified communications solutions nowadays.

Evolution of team messaging to team collaboration apps

Instant messaging has been around for a while with personal messengers like Yahoo Messenger but the technology did not take off with businesses right away. It was around 2010 when team messaging tools really became popular with companies with tools like Microsoft Lync and later apps like Jabber. Now, team messaging apps are more than just for chats. Apps like Slack, Glip, and HipChat are now full-on team collaboration apps with video chat capabilities as well.

Feasibility of stable audio and video conference

In the past, audio conference calls were a premium service only offered by traditional telecom companies. But with the rise of VoIP, the application of transmitting voice data over IP networks has also made audio conferencing more cost-friendly. In 2005, Lifesize Communication displayed the first video conferencing system at the Interop tradeshow with video showing 30 frames per second, with a 1280 by 720 resolution. By 2010, video conferencing has become a necessity for most enterprises and multiple video conference providers like GoToMeeting and Blue Jeans have popped up in the market.

The arrival of true Unified Communications as a Service

In the last couple of years, the main focus of the industry leaders in cloud communications is to combine these different communication channels into one streamlined service.

With a system that meets most, if not all, the business communication needs of a company and removing the need to rely on separate providers for each application, it is no wonder why cloud communications, UCaaS in particular, is set for domination in the future.

About the Author

Mark Dacanay is a Digital Marketing Professional who has been working with a B2B company offering cloud-based services for more than 5 years. He is obsessed with anything about the cloud – the technology, not the fluffy stuff in the sky. You can reach him through Twitter and LinkedIn .

AudioCodes Huddle Room Solution | Don’t let distance stop your people talking feature

The AudioCodes Huddle Room Solution

Don’t let distance stop your people talking

Last week, I went on a whistle stop tour of Europe to meet some AudioCodes customers. It was, as usual, a pretty hectic schedule. On my last day before flying home, I was sitting outside a coffee shop sipping a nice short espresso, waiting to join a conference call with a long-standing customer, John. It was, indeed, a perfect way to round off my trip.

The AudioCodes Huddle Room Solution | Don’t let distance stop your people talking

Ironically, this conference call had been arranged because John had expressed an interest in the AudioCodes Huddle Room Solution – a room system specially designed for getting the most out of Skype for Business meetings. I say ironically, because practically every conference call-related myth, stereotype and cliché reared its head during this meeting. But it turned out to be the best marketing opportunity for our solution that I could have wished for.

After several long minutes had passed, I was admitted to the meeting, with John apologizing profusely for the delay. Evidently, he had been struggling to initiate the meeting.

This proved to be a great starting point for our conversation. I began by explaining to John that simplicity is the key with the AudioCodes Huddle Room Solution, and that initiating or joining a conference call is very easy and straightforward. You just press one of two buttons on the console’s head unit screen – MEET NOW to start an ad hoc meeting, and CALENDAR to review your daily agenda and select the meeting you want to join.

I began by outlining some of the unique features of the Huddle Room Solution. John wanted his IT manager, Anni, to join the meeting. Anni was working offsite for the day, so John had to search for the correct PIN code for this specific conference call and send it to her before she could finally log in from her mobile phone. Eventually, she was with us. This seemed like a good moment to point out that the AudioCodes Huddle Room Solution lets you add a participant to any call quickly and easily with just a few clicks. And all participants can see who else is participating and who the meeting organizer is.

While I was explaining how simple it is to deliver meeting information and PIN codes directly via the head unit, our call was interrupted by the sound of a plane passing overhead at John’s location. When we resumed the call, I told them that the Huddle Room Solution neatly avoids such disturbances by allowing you to mute any or all participants for any reason, just as you can with the Skype for Business client.

In fact, everything that you’re familiar with in Skype for Business – and plenty more besides – can be done from the Huddle Room Solution’s control interface. For example, if a confidential topic comes up during a meeting you can go private simply by picking up the handset.

Anni said that the thing she looks most closely at with any new technology purchases – apart from quality and reliability, of course – is easy and effective troubleshooting. I explained that we at AudioCodes always aim to provide comprehensive holistic solutions, and the Huddle Room Solution is no exception to this. Beyond giving you amazing sound quality, we take it even further by empowering your IT team with our dedicated management tool.

This powerful yet simple tool makes managing the Huddle Room Solution simplicity itself. You can relax in the knowledge that your huddle room will always be available for use – with the most up to date software and voice quality optimization – whenever you need it. Even better, any problems can be dealt with remotely by your IT people.

With only a few hours left before my flight, and with John sounding very enthused by our conversation, I arranged to have some samples sent to him so he could see – and hear – for himself what the Huddle Room Solution can do.

A week after they received the samples, I got a call from Anni. It was great news. She and John were so impressed by the Huddle Room Solution’s superior acoustics and ease-of-use that they decided to order several units.

I thought back to that pre-flight espresso, and how much easier my al fresco conference call with John would have been with the Huddle Room Solution already in place – because no matter where you are, it really does turn any space into a meeting space.

To download our application note,
Collaboration in Today’s World Made Clear and Simple, Wherever You Are,
click the button below:

Get it now

We at AudioCodes always aim to provide comprehensive holistic solutions, and the Huddle Room Solution is no exception to this. Beyond giving you amazing sound quality, we take it even further by empowering your IT team with our dedicated management tool.