Lift Connectivity 2026: Emergency Voice, 4G, Monitoring and Elevator IoT
The Robustel EV8100 Industrial VoIP Gateway gives lift OEMs and service providers a practical way to migrate an analogue emergency phone to cellular or IP voice while keeping gateway management separate from the lift controller. That distinction matters: emergency voice, equipment telemetry and fleet operations may share a cabinet, but they do not share the same safety role or approval path.
For a building manager, the project often begins as a PSTN replacement. For the lift company, it quickly becomes a question about the lift car, monitoring centre, mobile coverage, backup power, controller interfaces and service ownership. A sound 2026 strategy deals with those dependencies before choosing a SIM or mounting a gateway.
Treat Lift Connectivity as Three Services
Emergency voice is the path from the alarm device in the lift car to a staffed answering point. It must carry intelligible two-way speech and the site or car identity expected by the monitoring centre. It is not simply “internet access in the machine room”.
Operational telemetry is different. Door cycles, alarm contacts, controller status or maintenance data may help a service team prioritise visits, but every signal must have an agreed source, meaning and owner. A serial or CAN port on a gateway is an integration opportunity, not proof that an arbitrary lift controller is compatible.
Fleet operations form the third service. They cover gateway reachability, configuration, software maintenance, SIM policy and investigation of communications faults across many buildings. These functions can reduce avoidable site visits without turning the gateway into the lift maintenance system.
| Service layer | Primary question | Typical owner | Acceptance evidence |
|---|---|---|---|
| Emergency voice | Can a passenger reach the correct monitoring centre? | Lift service provider and monitoring provider | witnessed calls from each car and failure-state tests |
| Lift telemetry | Which approved points are available and what do they mean? | Lift OEM/integrator | signed point list and controller-specific validation |
| Gateway fleet operations | Can communications health be observed and recovered? | Service operations/IT | inventory, alarms, access controls and replacement procedure |
Keeping these rows separate prevents a common procurement mistake: buying a broadly capable gateway and assuming every connected service has therefore been commissioned.
Design the Emergency Call Path First
Start at the alarm button and trace every dependency to the monitoring centre. Record the analogue phone interface, gateway, antenna, mobile service or SIP provider, destination number or URI, identity presented to the operator and the local power arrangement. If a building network is involved, include its switches, firewall, internet service and after-hours support owner.
A direct cellular voice path can reduce dependence on the building LAN. A SIP/VoIP path may align with a monitoring centre or communications platform already built around IP voice. Neither is automatically more reliable. The relevant question is which failure domains the building can test, power and support.
Robustel’s PSTN lift emergency-phone replacement Application Example is useful architecture evidence for this separation. It describes both 4G/VoLTE and SIP/VoIP routes; it is not proof that a particular carrier, monitoring centre or site will accept either route without commissioning.
Survey the Lift, Not the Street
Mobile coverage at the building entrance says little about the signal available beside a lift control panel. Reinforced concrete, steel shafts, basements, electrical plant and closed cabinet doors can all change the result. Survey the intended antenna position on the intended operators, then repeat under representative building conditions.
The test should record registration stability and call behaviour, not only a signal icon. Place and receive the calls required by the operating procedure, confirm the correct identity reaches the monitoring centre and test the weakest credible operating state. If an external antenna is needed, its route, connector security and future access become part of the installation design.
Dual SIM can provide another selectable mobile service path, but it is not the same as two independent systems. The same antenna location, power supply and gateway remain common dependencies. Failover timing and voice behaviour need a witnessed test with the actual SIMs and service configuration.
Decide What Continues When Building Power Fails
Lift emergency communications need a defined power-loss design. The Robustel EV8100 Industrial VoIP Gateway has a holder for two compatible flat-top 18650 lithium batteries; the batteries are not included by default. Battery selection, installation, ageing, inspection and replacement therefore belong in the project plan rather than in a generic hardware assumption.
The product documentation also specifies different temperature limits with and without batteries, including a narrower charging range. That matters in machine rooms and cabinets exposed to seasonal heat. A battery autonomy test conducted on a bench at room temperature is not sufficient evidence for every installed location.
List every load that must remain available: the gateway, lift alarm device, any interface equipment and any building-network components used by a SIP path. Then disconnect the normal supply and place a real call at the end of the required hold-up period. A calculation is useful for sizing; a witnessed discharge and recovery test proves the assembled path.
Add Elevator IoT Without Blurring Control Authority
The Robustel EV8100 Industrial VoIP Gateway documents RS-232, RS-485, CAN and digital inputs as well as Ethernet. Those interfaces can support approved telemetry designs in which the lift OEM exposes defined information. They do not authorise direct connection to every controller, nor do they make remote control appropriate.
Begin with a point register. For each point, name its controller source, engineering meaning, update behaviour, loss-of-data state, destination and operational response. Read-only data is often the safer first phase because the team can prove value without introducing an uncontrolled command path.
Robustel’s IoT-enabled smart elevators Application Example shows how voice and monitoring can coexist around one communications platform. Treat it as a solution pattern. The actual controller protocol, available points and remote workflow remain an OEM-approved integration project.
How the Robustel EV8100 Industrial VoIP Gateway Supports a Segregated Lift Connectivity Strategy
The Robustel EV8100 Industrial VoIP Gateway provides one FXS interface for an analogue device, supports VoIP and VoLTE, and offers dual SIM cellular connectivity. For ANZ deployments, the official model table lists EV8100-A-4L-A34AU and EV8100-B-4L-A34AU variants with RCM. The Wi-Fi and Bluetooth capability belongs to the B variant; it should not be transferred to every order code.
Two 10/100 Ethernet ports can be configured as one WAN plus one LAN or two LAN ports. SIP support includes RFC 3261 over UDP, SIPs and SRTP. Those are product capabilities; compatibility with a chosen SIP service, dial plan and monitoring platform must still be demonstrated end to end.
Robustel RCMS platform provides a managed view of the gateway fleet. Used well, it lets operations teams distinguish a communications-device issue from a broader lift fault, manage configuration and prepare recovery without driving to every site. It does not replace routine emergency-call testing or the monitoring centre’s own records.
The Robustel EV8100 Quick Pitch video is a concise product orientation for project teams. Follow it with the exact ANZ order code, carrier, antenna, voice route and site acceptance schedule; a family overview is not a commissioning record.
Allocate Ownership Before the First Retrofit
Many lift connectivity failures are ownership failures. The lift contractor assumes IT manages the SIP service; IT assumes the monitoring centre owns the dial plan; the building manager assumes the SIM is included indefinitely. A short responsibility schedule is more valuable than another architecture drawing if it closes those gaps.
Name who orders and renews SIMs, approves antenna locations, owns SIP credentials, receives device alarms, performs periodic calls and replaces batteries. Also name who can change gateway configuration and who holds the recovery copy. For strata property, the body corporate or appointed facilities manager should understand which obligations remain with the asset owner even when service work is contracted.
The Australian Government’s guidance on migration of lift phone services reinforces the practical point that lift phone services are safety-critical and that owners and managers retain responsibilities. It should be read with the applicable state, building, contractual and standards requirements for the site.
Migrate an Estate in Controlled Waves
Start with representative buildings rather than the easiest buildings. Include a basement machine room, a multi-car bank, a site using an external monitoring centre and a building where the local LAN would be difficult to support. These pilots expose operational differences that a laboratory cannot.
For each pilot, retain a signed record of coverage, call identity, speech quality, power-loss behaviour, SIM change, configuration recovery and alarm handling. Use the evidence to create a repeatable installation pack, but preserve site-specific fields so the standard does not hide local dependencies.
Scale only when the support desk can see the new fleet and the field team can replace a failed unit without improvising credentials. The migration is complete when the old service is safely retired, documentation is updated and the ongoing test schedule has an owner—not when the new gateway first registers.
Häufig gestellte Fragen
Q1. How do lift emergency phones work after PSTN lines are disconnected?
The analogue lift phone can connect to a gateway that carries the call over cellular voice or SIP/VoIP. The full route, caller or site identity, monitoring-centre acceptance, power-loss behaviour and periodic testing still need to be commissioned.
Q2. Does every lift need a dedicated phone line?
The required architecture depends on the applicable rules, lift arrangement and monitoring service. Avoid assuming that sharing infrastructure is acceptable merely because it is technically possible; have the responsible lift and compliance parties approve the design.
Q3. Can a lift use 4G for emergency calls?
Yes, when the gateway, carrier service, antenna position, monitoring destination and backup-power arrangement are suitable and the complete call path passes the required tests. Coverage should be measured at the installed location.
Q4. What is elevator IoT monitoring?
It is the approved collection and use of lift operating data for functions such as condition visibility, maintenance planning or alarms. It is separate from the emergency voice service and does not imply unrestricted controller access.
Q5. When is the Robustel EV8100 Industrial VoIP Gateway a good fit for lift connectivity?
It is a good fit when a project needs an FXS connection for a legacy analogue device, 4G/VoLTE or SIP/VoIP options, ANZ variants, industrial interfaces and managed gateway operations. Site coverage, controller integration and monitoring-centre compatibility must still be verified.
Schlussfolgerung
The Robustel EV8100 Industrial VoIP Gateway fits a lift connectivity strategy that keeps emergency voice, approved telemetry and gateway fleet management distinct while giving them a common industrial communications platform. That makes it particularly relevant to portfolios moving away from PSTN without wanting an improvised consumer adapter in each lift environment.
Its capability does not remove the project boundaries. The monitoring centre must accept the call route and identity, the lift OEM must approve controller data, the site must support the antenna and power design, and the responsible parties must continue testing the emergency path. Dual SIM, RCMS and a battery holder strengthen an engineered system; they do not turn an untested installation into a dependable one.
The best next step is a representative-building pilot with a written responsibility map and witnessed failure tests. Once the team can prove call delivery, power-loss behaviour, telemetry boundaries and unit replacement, it has evidence for an estate standard rather than a specification assembled from brochures.
Explore More Articles About Robustel Lift Connectivity
Über den Autor
Robert Liao | Technical Support Engineer
Robert is an IoT Technical Support Engineer at Robustel, specializing in industrial networking and edge connectivity. A certified Networking Engineer, Robert focuses on the deployment and troubleshooting of large-scale IIoT infrastructures. His work centers on architecting reliable, scalable system performance for complex industrial applications, bridging the gap between field hardware and cloud-side data management.