Moving enterprise telephony to Microsoft Teams Phone often starts with a simple objective: remove the PBX, retire expensive legacy telephone lines and consolidate communications into the cloud.
Then someone asks: “What happens to the elevator phones?”
For organisations with offices across the United States, the answer can be considerably more complicated than expected.
An elevator emergency phone is not simply another analogue device. It is part of a life-safety communications system, and the requirements governing it can depend on the state, city, age of the elevator, type of building, code edition adopted locally and the requirements of the relevant Authority Having Jurisdiction (AHJ).
That means replacing a traditional POTS line with an ATA, VoIP gateway or spare analogue port without first understanding the local requirements can create a compliance problem, even if the telephone appears to work.
Technically, it may be possible to make an analogue elevator phone place a call through an ATA or gateway.
That does not automatically make it an appropriate or compliant elevator emergency communications solution.
This is an important distinction during a Microsoft Teams migration.
Elevator communication requirements in the US commonly draw on standards including ASME A17.1/CSA B44, the International Building Code and accessibility requirements. The precise edition and any amendments that apply can differ between jurisdictions.
For example:
When replacing a traditional phone line, it is tempting to think:
Elevator > ATA > SIP > Teams/cloud = Problem Solved
But an elevator emergency system may need much more than dial tone.
Depending on the applicable code and installation, considerations can include:
The International Code Council’s guidance for newer IBC requirements, for example, references ASME A17.1/CSA B44 and requirements enabling authorised personnel to verify that someone is in the elevator, determine whether they are trapped and communicate the progress of assistance.
The question therefore isn’t simply: “Can we get this phone to make a call?”
It is: “Will the complete emergency communication service operate as required when somebody is actually trapped in the elevator?”
This issue frequently appears because the elevator phone has been almost invisible to IT.
It may be connected to:
A legacy PBX analogue extension
A copper POTS line
An old building telephone circuit
A dedicated emergency line
An analogue port nobody knew still existed
Everything else may be ready for Microsoft Teams Phone, but disconnecting that service could leave the elevator without compliant emergency communications.
The result? A PBX or expensive legacy line remains in service purely because nobody is confident about what to do with the elevator.
That is exactly the type of problem Aura’s Integrate to Migrate approach is designed to solve.
The elevator does not need to become a Teams endpoint just because the rest of the organisation is moving to Microsoft Teams.
In many situations, the cleaner solution is to separate life-safety communications from normal enterprise calling and provide a purpose-designed connection for the elevator.
Aura can help determine:
What is installed > What local requirements apply > What connectivity is appropriate > What needs changing > How it will be installed and supported.
Depending on the site and the requirements of the local AHJ, that could include moving an existing elevator telephone away from an ageing POTS or PBX connection and onto a purpose-built cellular solution.
Aura’s North American elevator solution, for example, provides analogue RJ-11 connectivity, DTMF support and battery backup, with carrier selection based on local cellular coverage.
Our existing approach also combines the connectivity with installation and 24/7 monitoring services rather than treating the emergency line simply as another telecom circuit.
Crucially, the appropriate solution should be validated against the requirements applying at that specific location rather than assuming one design works everywhere.
For a large enterprise, one elevator may sound insignificant. Multiply it across 50, 100 or 500 buildings and it can become a serious migration dependency.
You may have elevators in California, Illinois, Texas, New York and dozens of other jurisdictions, alongside warehouses, offices and manufacturing locations. Aura can manage this as part of the wider migration.
We can help identify analogue and life-safety services during discovery, determine which services should migrate into the Teams environment and which should be separated, coordinate the appropriate solution, and provide local engineering for physical installation and cutover.
With engineering capability across 173 countries, Aura can also support the onsite work that cloud migration programmes often overlook, tracing circuits, locating legacy cabling, installing equipment, testing services and helping retire the infrastructure that is no longer required.
The result is not simply a Microsoft Teams deployment. It is a path to actually turning the old platform off.
The final stages of a Microsoft Teams Phone migration often expose services that have been hidden for years. Elevator phones are a perfect example.
Instead, identify the requirement, understand the local code, provide the right emergency communications solution and remove the dependency properly. That’s what we call Integrate to Migrate. Aura can help you address the difficult analogue and life-safety requirements alongside Microsoft Teams Phone, giving you a practical route to complete the migration rather than stopping at the easy 90%.
Talk to Aura before you disconnect the existing lines. Let Aura help determine what needs to stay, what can change and how to remove the legacy dependency safely.