Powered by HPE networking infrastructure Campus Emergency Communication System

One number. Every emergency.

A LAN-first campus emergency system built on Asterisk. The whole campus dials a single number to reach a trained response team — with no internet, no cloud, and no SIM.

In an emergency, dial
111
44
Languages supported
111
Number to remember
None
Internet dependency
100%
Data kept on-site
Enterprise infrastructure

Powered by HPE networking

The backbone of UPES-ECS is enterprise networking infrastructure from HPE — engineered for high availability, low latency, and complete local network control, with no dependence on the internet or cellular networks.

HPE Juniper SRX300 / 320
The guarded edge

Firewall, DHCP, and local time source in one branch gateway. It enforces the LAN-only boundary, so emergency traffic never leaves campus.

8× GbE · zones · NAT · DHCP · NTP
HPE Juniper EX2300-C-12P
The voice fabric

Fanless PoE switches power and connect every phone, access point, and server. They carry the voice network, give 111 priority with quality-of-service, and can pinpoint a caller by switch port.

12× PoE+ · 124 W · 10G uplinks · Virtual Chassis
HPE Juniper Mist AP32
Campus-wide reach

Wi-Fi 6 access points carry the softphones that dial 111 — reaching every corner of campus, entirely on the local network.

Wi-Fi 6 · 4×4:4 · BLE + scanning radio
111softphones Mist AP32Wi-Fi 6 ×2 EX2300-C ×2Virtual Chassis · PoE · QoS SRX300edge · firewall PBX + Operations Console Internet*

HPE Juniper Networking hardware — presented at HPE's Bangalore University Networking Day.

HPE × UPES

Showcased with Team HPE

In July 2026, UPES-ECS was presented alongside HPE's enterprise networking team — first at HPE's campus in Bengaluru, then live at UPES.

HPE Networking University Day

15 July 2026 · HPE Mahadevapura Campus, Bengaluru — a first-hand look at enterprise networking and data-center infrastructure at scale.

Team HPE visits UPES

20 July 2026 · UPES — UPES-ECS demonstrated live on its HPE- and Juniper-powered networking backbone, end to end.

Capabilities

Built for the worst day

Nineteen features, distilled into what matters when seconds count.

How it works

A call's journey

From a caller in distress to the right responder — every path stays on the campus network.

111Caller dials 111 over Wi-Fi AsteriskAsterisk call core Responder queue4110 · 4111 · 4101 102Offline coach Operations console LED wallboards answered no answer
See it in action

Watch UPES-ECS in action

A short walkthrough — from a caller dialing 111 to the response team answering on the live operations console.

Video shot & edited by @harshdeepsinghin — with huge thanks.

Resilience

When networks fail, we don't.

No internet. No cellular. No cloud. UPES-ECS runs entirely on the campus network, so the one number that matters keeps working when everything else goes down.

High availability
Redundant, self-healing network paths keep the hotline reachable.
Low latency
Local switching connects every emergency call in an instant.
Local control
Every packet stays on campus, fully under your control.
Speaks everyone's language

One promise, 44 languages

Every prompt, the console, and the wallboards localize to the caller's language — fully offline.

Beyond the campus

One architecture, many missions

The same HPE-powered design scales past a single campus — to universities, disaster-response sites, and any critical-communication zone where reliability is essential.

Universities
Disaster response
Critical zones
Documentation

Read the full story

Architecture, runbooks, feature specs, and deployment guides — all in one place.