White Paper

Your Users Moved to the Cloud. Why Is Your SBC Still in the PBX Era?

jonathan.harris@auraalliance.com (Jonathan Harris) — Tue, 22 Sep 2026 12:25:23 GMT

Secure Voice for Defense & Government | Aura

jonathan.harris@auraalliance.com (Jonathan Harris) — Tue, 08 Sep 2026 23:00:00 GMT

When communications support operations, command, critical services or public safety, the priorities are different: security, resilience, control and the ability to continue operating when conditions are far from normal.

That is why Aura and Ribbon provide a particularly strong combination for organizations across the UK and United States looking to modernize secure communications without compromising the systems and resilience they depend on.

What makes communications different in defense and government?

Commercial organizations can often design around the assumption that connectivity and cloud services will be available.

Mission-critical organizations cannot always make that assumption.

Networks may need to operate through cyberattack, connectivity loss, infrastructure failure or degraded operating conditions. They may also need to integrate decades of existing telephony, secure networks, analogue devices and specialist systems while progressively introducing platforms such as Microsoft Teams.

The answer is rarely to replace everything with cloud communications.

It is to create an architecture that can use modern technology while retaining control and survivability where the mission requires it.

Ribbon has built much of its defense portfolio around exactly this principle, supporting secure SIP communications, survivable architectures, legacy migration and resilient networking. Aura designs and deploys that portfolio into working architectures for mission-critical customers.

Why is Ribbon particularly strong in US defense?

Few technology environments impose communications requirements as demanding as the US Department of Defense.

Ribbon has an established portfolio of products that have completed testing through the Defense Information Systems Agency’s Joint Interoperability Test Command — JITC — and are listed on the DoDIN Approved Products List.

In August 2025, Ribbon expanded that portfolio further when its PSX Policy Engine, RAMP management platform and Ribbon Analytics were added to the DISA Approved Products List, joining existing platforms including SBC SWe, SBC 5400, SBC 7000, the G5 Media Gateway and Ribbon Application Server.

This matters because JITC testing goes well beyond normal enterprise interoperability. DISA evaluates products against requirements for areas including security, interoperability and reliability before they can be approved for use within DoD networks.

Ribbon was also selected in 2024 as the technology provider for DISA’s Soft Switch Backbone modernization program, supporting secure and resilient voice communications across US Department of Defense branches and agencies.

For organizations evaluating technology for high-security environments, that is significant evidence of real-world pedigree.

What security credentials should an SBC bring?

Security should never be reduced to a badge, but certifications provide useful independent evidence.

Across the Ribbon portfolio Aura deploys, key certifications include:

DISA JITC-certified solutions and DoDIN Approved Products List entries
FIPS-compliant and FIPS 140-2 validated SBC platforms, depending on product and software release
Microsoft Teams certification, including Ribbon's position within Teams environments designed for DoD deployment
CMMC Level 2 certification for Ribbon Communications Federal
ISO/IEC 27001:2022 information-security certification at the corporate level
ISO 22301:2019 business-continuity certification at the corporate level

Specific certification and cryptographic-validation status should always be confirmed against the exact product and software version being proposed. For example, NIST currently lists a FIPS 140-2 validation for the Ribbon SBC 5400 and defines the precise approved configuration.

The important outcome is a communications platform designed around security and assurance from the outset, rather than security being added after deployment.

How do Aura-deployed SBCs protect mission-critical voice?

A Session Border Controller (SBC) sits at one of the most important boundaries in an IP voice environment.

It controls communication between networks and can provide a security enforcement point for SIP signaling and media.

The SBC platforms Aura deploys include capabilities designed to protect communications against threats such as denial-of-service attacks, eavesdropping and unauthorized access, while supporting encryption, policy enforcement and interoperability between different communications environments.

That becomes particularly valuable in defense and government, where organizations may need to connect:

Aura’s implementation of Ribbon’s standards-based SIP helps organizations connect these environments without forcing all communications onto a single proprietary platform.

Can secure organizations move to Microsoft Teams without losing local resilience?

Yes, and this is one of the most important parts of a modern secure communications strategy.

Cloud collaboration creates enormous benefits, but critical locations may still require the ability to communicate if cloud or WAN connectivity becomes unavailable.

Aura designs architectures using Ribbon’s survivability technology that combine Microsoft Teams with local survivability and existing communications infrastructure, allowing organizations to modernize while retaining local communications capabilities where required.

For a normal office, this might be valuable. For a military base, command location, government facility or critical operational site, it can be fundamental.

The objective is therefore not necessarily cloud-only.

It is cloud where appropriate, local resilience where necessary.

What about the UK defense and government market?

The terminology and accreditation framework differs from the US, so US DoD approvals should not be presented as UK MOD certifications.

They do, however, provide strong evidence of the level of security, interoperability and resilience engineered into the platforms Aura deploys across defense environments internationally.

For UK government, defense and national-security projects, the architecture must be designed around the specific security classification, deployment model, data handling requirements and customer accreditation process.

That can mean very different architectures. Some environments may use Microsoft cloud services. Others may require completely private infrastructure. Some may need geographically restricted management and support.

And highly secure environments may require solutions to remain entirely on-premises, with no dependency on public-cloud services.

This flexibility is one of the reasons Aura builds its UK secure communications architectures around Ribbon technology.

Modernization does not have to mean surrendering control.

Where does Aura add value?

Secure technology is only one part of a secure communications environment.

How that technology is designed, deployed, integrated, supported and changed is equally important.

Aura is a Ribbon Super Partner with deep experience across Ribbon SBCs, enterprise voice, Microsoft Teams and complex hybrid communications environments. Aura provides design, professional services, integration and managed support across the Ribbon lifecycle.

Our approach is particularly suited to organizations that cannot simply switch off existing infrastructure and start again.

Aura One

Through Aura One, we can bring strategy, migration, integration, managed services and continuous optimization into a single transformation framework.

That means helping organizations determine:

What needs to remain isolated or on-premises?
What can safely move to modern IP or cloud platforms?
Where is local survivability required?
How should legacy PBX and analogue services be protected?
How should SBCs and gateways be resiliently designed?
How should Microsoft Teams interact with the secure voice environment?

And, critically, how can the organization modernize without introducing unnecessary operational risk?

Why does global capability matter to defense?

Secure government and defense organizations rarely operate from one office.

Users may be distributed across bases, government facilities, command locations and international deployments.

Aura combines specialist communications engineering with a global delivery capability. Aura currently supports engineering, deployment and managed services across more than 170 countries, enabling organizations to use a consistent partner while still providing local support where it is needed.

For UK and US organizations with international operations, that can reduce another major source of risk: relying on a different communications provider at every location.

One architecture.

One operating model.

One accountable partner.

Security without standing still

Secure communications cannot remain static.

Threats evolve. Software changes. Networks modernize. Users adopt new ways of working. AI and automation introduce both opportunities and new security considerations.

The challenge for military and government organizations is therefore not simply to protect today’s network. It is to modernize without weakening the characteristics that made the network trusted in the first place.

Aura brings the architecture, integration, telecoms expertise, global delivery and managed services required to turn Ribbon’s technology into an operational communications environment. That technology carries extensive defense pedigree, including JITC-tested and DoDIN-approved solutions, FIPS capabilities and resilient voice architectures deployed across mission-critical government environments.

Together, that creates a compelling proposition for organizations across the UK and United States that require more than enterprise voice.

They require communications they can depend on when they matter most.

Secure. Resilient. Mission ready.

For defense and government, communications modernization should not be a choice between innovation and security. The right architecture can deliver both.

Protect what matters. Modernize what makes sense. Maintain control. Build resilience into every layer. That is the value of bringing Aura and Ribbon together for mission-critical communications.

Supporting the Armed Forces Community

For Aura, supporting defense and military organizations goes beyond technology. We’re proud to support military charities such as Help for Heroes, which provides practical, physical, financial and emotional support to members of the Armed Forces community.

As we grow our work across defense, government and other highly secure environments, we’re committed to giving back to the people behind the mission — those who serve, and those who have served.

For us, that means combining our expertise in mission-critical communications with a wider commitment to the people behind the mission.

Supporting those who serve – and those who have served – should be part of the responsibility that comes with working in this sector.

Ready to modernize secure communications without compromising control?

Talk to Aura about designing a resilient, defense-grade voice architecture built around Ribbon technology.

Teams Phone Migration: Keep Your Analogue Services - Aura

joel.heasman@auraalliance.com (Joel Heasman) — Thu, 20 Aug 2026 23:00:00 GMT

Introduction

How to retire the legacy PBX without losing local calling, analogue devices, paging, door entry or the infrastructure your sites still depend on

For many organisations, moving users to Microsoft Teams Phone is the easy part. The real complexity often sits behind the scenes. Analogue phones. But also lift and emergency devices, fax machines, door entry systems, paging amplifiers, factory phones, reception devices, existing two-wire cabling, krone frames, and local PSTN circuits. And, perhaps most importantly, the requirement for people at critical locations to continue making and receiving calls if connectivity to Microsoft 365 becomes unavailable.

These are often the reasons an organisation ends up maintaining an expensive legacy PBX long after the majority of its users have migrated to Microsoft Teams.

The PBX may have hundreds of unused extensions, consume rack space, require specialist support and represent another platform that needs patching, maintaining and renewing. Yet it remains because five analogue devices still need dial tone, a warehouse needs paging or a site cannot accept losing local telephony during a WAN outage.

It does not have to be this way.

With the right combination of Microsoft Teams Phone, Survivable Branch Appliance technology, Ribbon Session Border Controllers, analogue gateways, Algo endpoints and local engineering, organisations can build a Microsoft-first voice architecture without ignoring the physical and operational realities of their sites.

This is exactly where Aura’s Integrate to Migrate approach comes in.

The last 10% of a Teams migration can be the hardest part

Real enterprise environments rarely look that simple.

A site survey may uncover:

Analogue extensions connected through decades-old two-wire cabling
Krone blocks and 1308 telephone cable distributing services around the building
Lift, help point, alarm or emergency devices
Fax machines and modems
Door entry and intercom systems
Warehouse, manufacturing or external phones
Overhead paging systems
Existing analogue or digital PSTN circuits
Local call routing requirements
A requirement to retain telephony if the site’s WAN or Microsoft 365 connectivity is unavailable

Historically, the easiest response was often: leave the PBX there.

That solves the immediate problem, but it leaves the customer operating two voice environments indefinitely. Licensing, hardware maintenance, power, rack space, support contracts and specialist knowledge remain. More importantly, the organisation never quite completes its migration.

A better approach is to understand why the PBX still exists and replace those individual functions with technology designed for a modern Teams environment.

What is a Microsoft Teams Survivable Branch Appliance?

One of the most important tools for organisations with critical sites is the Microsoft Teams Survivable Branch Appliance, or SBA.

Microsoft developed SBA functionality for Direct Routing environments where a site may temporarily lose connectivity to Microsoft 365 while the local network and connection to the site’s Session Border Controller remain available.

When properly designed and configured, Teams clients at the affected branch can automatically enter appliance mode and continue to make and receive PSTN calls through the local SBC. When connectivity to Microsoft is restored, users automatically return to normal Teams operation.

That changes the conversation around cloud voice.

Previously, organisations could look at an on-premises PBX and a cloud calling platform and ask:

“What happens to the site if the cloud disappears?”

An SBA allows us to design a much more resilient answer.

What can Teams users do during an outage?

Microsoft currently supports a range of calling functions in SBA mode, including:

Making and receiving PSTN calls
Hold and resume
Blind transfer
Selected call forwarding
Local VoIP calling between users registered behind the same SBA
PSTN fallback for certain calls
Selected Auto Attendant and Call Queue redirection scenarios

The objective is not to reproduce every Microsoft Teams cloud service locally. It is to preserve the critical voice functionality required to keep a location operational while normal cloud connectivity is restored.

That distinction is important.

Survivability should be designed around the business functions that genuinely need to survive, rather than attempting to recreate the entire Microsoft cloud inside every branch.

Where Ribbon fits into the solution

Aura works closely with Ribbon to provide the local edge infrastructure required for these more complex environments.

Ribbon’s Microsoft-certified SBC portfolio supports Microsoft Teams Direct Routing and Microsoft SBA, allowing the SBC and survivability architecture to be positioned locally where required. Ribbon supports SBA capabilities across its SBC Edge portfolio, including hardware and virtual deployment options.

But survivability is only part of the story.

Ribbon’s hardware-based edge solutions can also provide traditional interfaces such as FXS, FXO, BRI and T1/E1, allowing modern SIP and Teams environments to interoperate with devices and services that were never designed for Microsoft Teams.

This means the edge can become the bridge between:

Microsoft Teams Phone > SIP > Ribbon > existing analogue or traditional telephony infrastructure

Instead of maintaining an entire PBX to support a handful of devices, we can provide the specific interfaces that those devices actually require.

Do analogue devices need to be replaced when moving to Teams?

Not necessarily. This is one of the biggest misconceptions we see during Teams migrations.

An analogue telephone, fax machine, door entry unit or other device does not necessarily care whether the organisation’s core communications platform is Microsoft Teams, Avaya or a traditional PBX.

It needs an appropriate analogue interface and dial tone.

With an FXS interface or suitable analogue gateway, we can convert between SIP and the analogue connection required by the endpoint.

That means an organisation could have:

Microsoft Teams Phone > Ribbon SBC / analogue gateway > existing two-wire cabling > analogue device

For a larger site, analogue interfaces can be centralised around the communications room.
For a smaller requirement, a compact edge gateway or ATA can often be placed close to the device.
The architecture should be determined by the site rather than forcing every site into the same design.

What about the existing Krone blocks and two-wire cabling?

This is where telecommunications experience becomes just as important as Microsoft expertise.

Many enterprise buildings still contain extensive traditional voice cabling.

You may have 1308 cable leaving the communications room, Krone frames distributing extensions between floors, intermediate distribution points and two-wire connections that eventually appear at a wall socket hundreds of metres away.

Moving to Microsoft Teams does not automatically mean all of this cabling has to be removed.

Where the cabling is serviceable and appropriate for the application, Aura can assess whether it can be reused.

Our engineers can:

Trace and identify existing analogue circuits
Locate endpoints and cable routes
Tone and test pairs
Identify services on Krone blocks
Re-terminate circuits
Patch existing building cabling into new gateways
Install new analogue or SIP gateways
Rack and stack Ribbon and associated equipment
Install network connectivity
Replace or extend cabling where required
Label and document connections
Test inbound and outbound calls
Support cutover and decommissioning

This is an important difference between delivering a Teams licence and delivering a complete communications migration.

Sometimes the most important part of a Microsoft Teams project involves a screwdriver, cable tester and Krone tool.

Paging does not have to keep your PBX alive either

Paging is another common reason organisations retain legacy telephony.

Manufacturing plants, warehouses, hospitals, schools, transport environments and large offices may have significant investment in overhead speakers and amplifiers.

Replacing the entire system can be unnecessary.

Using technology from Algo, existing analogue paging infrastructure can be integrated into Microsoft Teams using IP paging adapters. An Algo device can provide the bridge between Teams and an existing paging amplifier, allowing the organisation to retain speakers and other infrastructure while modernising the communications platform behind it.

For new installations, organisations can move further towards IP using Algo speakers, horns, visual alerting and other IP endpoints.

Algo’s supported endpoints can integrate with Microsoft Teams through the Teams SIP Gateway, providing native options for paging, alerting and hands-free visitor communications.

Again, the objective is choice.

Keep what makes sense. Replace what needs replacing. Modernise without creating unnecessary disruption.

Door entry and intercoms can become part of the Teams environment

The same principle applies to door entry. A legacy PBX may currently provide the extension behind a reception intercom or door phone. Removing the PBX does not mean losing that functionality.

Algo provides IP doorphones, intercoms and door controllers that can integrate into a modern SIP and Microsoft Teams environment, enabling calls from an entrance or intercom point to be presented to the appropriate Teams user or workflow.

The result is a more joined-up communications architecture covering not only knowledge workers at laptops, but also the physical environment around them.

A Teams Phone architecture designed around the whole site

A complete solution might therefore look something like this:

↓ Microsoft Teams Phone
↓ Aura Connect / Direct Routing
↓ Ribbon Session Border Controller + Microsoft SBA at critical locations
↓ Local PSTN or SIP connectivity for survivability where required
↓ FXS / analogue gateways for legacy endpoints
↓ Existing Krone, 1308 and two-wire infrastructure where suitable
↓ Fax, lift phones, emergency phones, analogue handsets and other devices

Alongside this:

Microsoft Teams > Teams SIP Gateway > Algo > paging, alerting, intercom and door entry

The exact architecture changes by location. A headquarters may require a Ribbon SBC, SBA, significant analogue density and resilient local connectivity. A warehouse might require a small analogue gateway and Algo paging integration. A small branch may need nothing more than cloud Teams Phone.

That is why we believe enterprise Teams migrations should be designed site by site, but managed as one global programme.

Global migration requires local hands

Architecture is only half the challenge, somebody still has to get into the communications room.

For multinational organisations, that can quickly become a major problem. A Teams migration covering 50, 100 or 500 locations may require people locally to survey equipment, trace cables, install gateways, rack equipment, patch circuits and support cutovers.

Coordinating a different local telecoms company in every country brings the complexity straight back.

Aura Global provides local engineering, deployment and support capabilities across 173 countries, giving organisations one partner through which to coordinate both the cloud transformation and the physical work required at each location.

We can combine central programme management and architecture with local activities such as:

Site surveys
Telecoms room audits
Cabling identification
Krone and cross-connect work
Device installation
Rack and stack
SBC and gateway installation
Paging and door-entry deployment
Circuit testing
Migration assistance
Cutover support
Equipment removal and decommissioning

That matters because communications transformation rarely stops at the Ethernet port.

Microsoft-first does not have to mean Microsoft-only

At Aura, our strategy is Microsoft-first. But Microsoft-first does not mean Microsoft-only.

Most enterprise customers have years or decades of communications infrastructure already embedded within their organisation.

Some of it should be replaced.
Some of it should be integrated.
Some of it should continue operating until there is a commercial or operational reason to change it.

→ Our job is not to force everything into the cloud regardless of the consequences.

Our Integrate to Migrate approach is built around connecting Microsoft Teams with the systems, devices and infrastructure that businesses still depend on, allowing customers to modernise at the pace that makes sense for them.

Integrate today. Migrate when you need to.

Can you finally remove the legacy PBX?

In many environments, yes. If the only reasons for retaining a legacy PBX are:

Local survivability

Analogue extensions

Local PSTN access

Paging

Door entry

Lift or emergency devices

Legacy cabling

then it is worth challenging whether an entire PBX is still the right way to provide those services.

Together, that provides an architecture designed around 100% of the communications requirement, not simply the easiest 90% to migrate to Teams.

A note on critical and life-safety devices

Analogue does not always mean simple. Lift phones, fire systems, alarms, emergency help points and other regulated devices may have specific requirements relating to power, signalling, line monitoring, emergency location or local regulations.

They should therefore be assessed individually rather than automatically connected to an analogue adapter.

Microsoft also documents specific limitations that apply when Teams is operating in SBA mode, including considerations around emergency location information and emergency call routing policies.

A proper migration should identify these services during discovery and determine the right technology, connectivity, power and resilience strategy for each one.

That is another reason the discovery phase is so important.

FAQ

Don’t migrate Teams. Migrate communications.

Moving to Microsoft Teams Phone should not mean solving the easy parts and leaving the difficult parts running on an ageing PBX for another decade. The goal should be bigger.

Understand every device. Every circuit. Every critical workflow. Every survivability requirement. Every paging zone. Every door phone. Every cable that still has a reason to exist.

Then design the right destination architecture around them.

At Aura, we bring together Microsoft Teams Phone, Aura Connect, Ribbon, Algo, legacy voice expertise and local engineering across 173 countries to help organisations modernise the complete communications environment.

One partner. One architecture. One accountable outcome.

Integrate to Migrate means moving forward without leaving the difficult parts behind.

Ready to remove the PBX without losing the services your sites depend on?

Talk to Aura about an Integrate to Migrate assessment covering Teams Phone, survivability, analogue devices, paging, door entry and local site infrastructure.

Why GCC High is a priority for regulated industries

jonathan.harris@auraalliance.com (Jonathan Harris) — Sun, 10 May 2026 23:00:00 GMT

For organizations operating in regulated industries, security and compliance are no longer separate conversations from collaboration and communications. They are deeply connected.

As Microsoft Teams, AI, and cloud-based collaboration become central to day-to-day operations, more organizations across the Defense Industrial Base (DIB) are reassessing whether their current Microsoft environment is secure enough for the contracts, data, and compliance obligations they now face.

Interest in Microsoft GCC High is expanding well beyond traditional defense contractors. For many organizations supporting government projects, handling sensitive data, or preparing for evolving CMMC requirements, it is increasingly becoming part of long-term modernization planning.

Why the Microsoft environment matters more now than ever

Microsoft Teams is no longer just a collaboration tool. It now sits at the center of day-to-day operations for many regulated organizations – connecting meetings, messaging, document sharing, workflows, voice, external collaboration, and increasingly AI-powered productivity tools.

That shift matters because sensitive operational data is no longer spread across disconnected systems. It is increasingly being accessed, shared, and managed inside one Microsoft environment.

As a result, organizations are starting to look differently at security and compliance. The focus is moving beyond endpoint protection and access policies toward a broader question:

Is the underlying Microsoft environment aligned with the sensitivity of the data and contracts the organization supports?

That question becomes even more important for organizations working within the defense supply chain, handling Controlled Unclassified Information (CUI), or preparing for evolving CMMC requirements.

GCC High is no longer just a defense conversation

Historically, GCC High was associated with large defense primes and major federal contractors. Today, that is changing.

More subcontractors, suppliers, manufacturers, engineering firms, and service providers across the Defense Industrial Base are now being pulled into the same compliance conversation because of the data they access, the contracts they support, or the customers they work with.

These organizations are increasingly facing pressure around:

Protecting Controlled Unclassified Information (CUI)
Demonstrating stronger cybersecurity controls
Preparing for CMMC assessments
Modernizing infrastructure securely
Supporting hybrid work without increasing compliance risk

For many IT leaders, the concern is no longer simply whether the current environment is secure today. It is whether the environment will continue supporting future contractual, operational, and compliance requirements.

What is Microsoft GCC High?

Microsoft GCC High (Government Community Cloud High) is a dedicated Microsoft 365 government cloud environment designed specifically for organizations handling sensitive government data and controlled workloads.

Unlike commercial Microsoft 365 environments, GCC High operates inside a segregated U.S. sovereign cloud infrastructure with stricter security, compliance, and access controls. This supports compliance with frameworks and regulations such as CMMC, DFARS, ITAR, FedRAMP High, and NIST 800-171.

It is built primarily for:

Defense contractors
Aerospace organizations
Defense Industrial Base (DIB) suppliers
Federal agencies
Organizations handling Controlled Unclassified Information (CUI)
Businesses managing ITAR-regulated data

The environment provides a significantly higher level of security and sovereignty than standard commercial Microsoft environments, helping organizations reduce compliance risk while securely modernizing collaboration and communications.

Why secure voice is becoming part of the strategy

Voice is where many regulated environments still look fragmented.

Organizations may have standardized collaboration inside Microsoft Teams, while telephony continues operating across legacy PBXs, local carriers, and disconnected voice platforms built over many years.

The issue is not just aging infrastructure. It is the lack of consistency that comes with it – different governance models, separate security controls, limited visibility, and communications operating outside the wider Microsoft environment.

As Teams becomes more deeply embedded into daily operations, those gaps become harder to ignore.

This is driving greater interest in Teams Phone for GCC High, particularly among organizations looking to simplify communications governance while reducing dependence on siloed infrastructure.

The migration challenge organizations are underestimating

Many organizations treat GCC High as something they can address later if compliance requirements increase. The reality is that migration becomes harder as Microsoft environments mature.

Once Teams, voice, workflows, automation, and AI initiatives are deeply integrated into day-to-day operations, moving environments can impact far more than IT infrastructure alone.

In some cases, organizations may need to redesign tenants, rebuild security and identity policies, migrate collaboration environments, and modernize communications infrastructure simultaneously.

The longer organizations wait, the more difficult migration becomes.

How Aura can help

Successfully deploying GCC High requires more than licensing. Organizations need expertise across Microsoft government environments, communications infrastructure, compliance requirements, and operational transformation.

As a Microsoft-first communications partner, Aura helps regulated organizations simplify that complexity through:

GCC High strategy and readiness
Microsoft Teams Phone for GCC High
Secure voice transformation
Direct Routing and Operator Connect
Migration and coexistence planning
Compliance-aligned communications architecture
Ongoing operational support

Aura is also TX-RAMP certified, strengthening our ability to support organizations operating in highly regulated and security-sensitive environments.

For organizations modernizing inside Microsoft, we help bring communications, collaboration, security, and compliance together inside one connected strategy.

GCC vs. GCC High: Which is right for your business?

jonathan.harris@auraalliance.com (Jonathan Harris) — Tue, 21 Jan 2025 10:45:00 GMT

Old Systems, New Tricks: How to Modernise Legacy Applications

tony.parish@auraalliance.com (Tony Parish) — Sun, 29 Dec 2024 15:45:00 GMT

Choosing the best Contact Center for your business

jack.condron@auraalliance.com (Jack Condron) — Mon, 02 Dec 2024 21:15:00 GMT

Keep your tech talking with a Managed IT Service

tony.parish@auraalliance.com (Tony Parish) — Wed, 13 Nov 2024 08:45:00 GMT

The ins and outs of E911 and how to comply

jack.condron@auraalliance.com (Jack Condron) — Wed, 16 Oct 2024 22:00:00 GMT

The Benefits of Global SIP Trunking for Multinational Corporations

tony.parish@auraalliance.com (Tony Parish) — Fri, 05 Jul 2024 14:45:00 GMT