A Major Northeast U.S. Health System Consolidates Avaya Aura Across Hospitals and Clinics

Like many multi-hospital systems that grew by affiliation, the customer inherited multiple Avaya Aura islands. Hospitals and clinic clusters ran local H.323 cores with overlapping four-digit extension plans, inconsistent 46xxsettings files, mixed firmware generations, and limited central visibility. Telecom and network teams could not treat “the phone system” as one estate. 

The business needed to: 

• Convert H.323 extensions from four digits to five- or seven-digit numbering without visiting every desk.
• Migrate devices from local Aura systems onto a consolidated Avaya Aura core, moving the estate toward SIP while H.323 devices were still in production.
• Centrally vend firmware and settings, reboot or reset devices remotely, and keep inventory accurate across hospitals and clinics. 
• Do the work with a lean staff, remote professional services, and no multi-week truck-roll campaign across rural sites.
• Preserve clinical uptime — conversion failures had to be logged and remediated, not left as silent misdials in patient-care areas.

Native Avaya tools and spreadsheets could not orchestrate group-based conversion, record the new extension, then drive the subsequent core-site migration with a controlled reboot. That gap is what Endpoint Manager R6 was deployed to close. 

INEMSOFT Endpoint Manager R6 was deployed as an on-premises management platform on customer-supplied VMware infrastructure. The initial production design supported up to 7,000 managed devices, with additional servers available to scale and with a recommended high-availability pattern of one instance per data center. 

Standard implementation covered project planning, an IPT workbook for the customer’s Avaya Aura environments, a second-day operating model, remote install of the Endpoint Manager instance, database configuration for an initial device/group/core set, remote training, and cutover support. Avaya Application Enablement Services (AES) with SMS links to Communication Manager were required so H.323 devices could be managed in place. 

Enhanced Design services compressed the time from OVA install to a production-ready operating model. That work organized device hierarchies around network architecture, device models, firmware trains, business units, and locations; configured LDAP authorization; redesigned 46xxsettings onboarding maps; bound policies and profiles to model, subnet, group, location, and business unit; linked up to five Avaya Aura serving sites (CM / SMGR / SM / AES); bulk-loaded the device estate; and tested firmware up/down and settings changes on representative models before cutover. 

Key Results

• Single management plane Firmware, settings, inventory, reboot/reset, and grouping for up to 7,000 devices — expandable with additional servers. 
• Renumber without desk visits 4-digit H.323 extensions converted to 5- or 7-digit plans while the phone stayed logged in; no manual re-login for a successful conversion. 
• Core consolidation path After conversion, devices could be migrated from local Aura islands to the system core, with a controlled reboot carrying the new registration data. 
• Exception handling Failed or complex conversions were logged instead of disappearing into the network. Clinical sites were not left guessing which phones still had the old number. 
• Repeatable onboarding Maps and profiles aligned 46xxsettings to model, subnet, group, location, and business unit so new devices could be brought online without rebuilding settings by hand. 
• Rural-safe delivery model Implementation, training, and cutover were performed remotely with the customer’s on-site teams — essential across a statewide hospital and clinic footprint.