Implementing Aura Part 1
There has been a lot of news in the UC/SIP market around Avaya Aura since their (Avaya’s) official launch early last year. With the launch of Aura/SM, then shortly there after, Avaya’s purchase of Nortel Enterprise division, Avaya key messages of “Fit for Purpose” and “Wrap & Embrace” began to take hold within customer mind sets.
Avaya is changing the landscape of the traditional PBX market with Avaya Aura. From the PBX and distributed communications market of today, to a Session based architecture with core routing, a PBX access layer with multi-vendor support of tomorrow. All while providing an endless pool of applications and features to end users across the enterprise, all without having to upgrade in the traditional distributed model of today.
That really is quite a promise Avaya…
But how familiar is Session Manager to the market? “Who is deploying it”? and more importantly is it really integrating as promised? and if so how successful?”
We have heard these questions and many more about Avaya’s Aura from all of our customers and the voice market here in Canada. (for more info see What Exactly is Avaya Aura?)
Combat is going to try and answer a few of these questions and many others in a series of posts that we hope will help highlight Avaya Aura and its capabilities, features, functions and interoperability during our installation here at Combat Networks.
Combat Networks strongly believes in practicing our preachings, and in this case Combat will be implementing Avaya Aura – Nationally throughout our organization.
Combat is looking to achieve the features and benefits that Avaya preaches to the market of what Aura and Session Manager can bring to unified communications, costs savings and interoperability with our existing Nortel system.
Over the past few years Combat Networks has been growing steadily offering our voice and data services across Canada to enterprise Nortel and Avaya customers. With our most recent announcement of our Toronto office, Combat is facing communication concerns.
Our growth nationally comes with communication and expansion issues and questions that we see our customers face on a daily basis – e.g.:
- Opening a new office, what do I need to support x-users with voice mail?
- What size of system/PBX do I need for my new office?
- How do I Connect my new office to HQ?
- How do I connect Calgary regional with my HQ?
- How will SIP save me money?
- SIP vs. PRI?
- how to set organizational standardization on extensions?
- Running 4.5 in Montreal and 5.0 in Calgary how do I upgrade?
It’s funny how often we meet new customers, and how often we can all forget that we – Combat – have the same organizational challenges as they do when it comes to telephony and data considerations. And really, that is the intent of this series of articles, to share Combat Networks’ – migration/integration of Avaya Aura within our organization, nationally – right across Canada.
I hope that our demonstration, our integration, our commitment to Avaya and its benefits are demonstrated to you in these series of posts. During this upgrade please feel free to contact us and share your thoughts and comments with us and the community as we begin sharing the process of our testing, trialing and ultimately our implementation of Avaya Aura here at Combat.
Join Greg Curry and Myself and the Combat team as we move forward with Avaya Aura,