UPES-ECS — Call Flows¶
Every call type on UPES-ECS, as sequence and flow diagrams with short narration. This is the runtime companion to 02-System-Architecture.md (the static build) and the operational ERT SOP. Diagrams are Mermaid with an ASCII fallback for the primary flow.
Golden rules that shape every flow below. 111 is human-first — no AI, internet, or cellular in its path. Unsure → escalate and keep the caller on the line. Only 111 and 199 are recorded end-to-end. Emergency controls (paging, conference, escalation) are role-restricted by dialplan context.
Disaster-ready additions. The campus learns one number: 111.
101(local-first AI) and102(offline coach) are internal routes the system invokes — a caller is never told to hang up and redial. When no human answers, the caller is coached immediately and in parallel with the system still trying to reach a responder — never left in silence. Every fallback path works with zero internet and zero AI service (offline TTS coach); the richer local-first AI (101) only upgrades this when the local AI stack is available.
0. Number → route map¶
Every dialable number and what it does. Authoritative source: Numbering Plan.
| Dialed | Name | Route / behaviour | Recorded? | Who may dial |
|---|---|---|---|---|
| 111 | Emergency Hotline (primary) | Record + incident ID → ert_emergency_queue (press 1 any time → first-aid) → on no-answer: background responder alert in parallel with offline panic-coach → retry / voicemail → Missed Incident |
✅ whole call | anyone |
| 102 | Offline panic-coach | Deterministic first-aid guidance (CPR / bleeding / choking / fire / lockdown / recovery / trapped), zero internet, zero AI service. The automatic fallback beneath 111; also a direct-dial for testing | ✅ (as 111) | auto-fallback · dial = test |
| 101 | AI triage (local-first, planned) | Conversational local-first AI (on-device Ollama/llama.cpp + Whisper + Piper — no cloud, no Gemini) that rides a 111 call — gives a spoken pre-brief to the ERT, escalates urgent cases to humans, and falls back to the 102 coach when the AI is unavailable. It is a capability the system invokes, never a number a caller dials | (as 111 on handoff) | auto · rides 111 |
| 199 | Drill / Test | Simulates 111 flow, isolated, DRILL-ONLY, no real dispatch |
✅ marked drill | any authenticated user |
| 198 | Echo test | Plays caller's own audio back (mic/speaker/network check) | ❌ | anyone |
| 196 | AI test (later) | Exercises AI pipeline only | ❌ | test roles |
| 700 | All-campus paging | Live broadcast to every zone — PIN + ERT Lead | ❌ (attempt logged) | ERT Lead only |
| 701–705 | Zone paging | Academic / Hostels / Security-gates / Medical-ERT / Admin-ops | ❌ (attempt logged) | ERT Lead / zone-authorized |
| 9000 | Main Incident Command | ConfBridge, recorded when active, PIN | ✅ when active | ERT + responder roles |
| 9001–9004 | Side coordination rooms | Security / Medical / Warden / Ops bridges, PIN | ❌ by default | role-scoped |
*45 / *46 |
Pause / resume in queue | Self-service queue toggle | — | ERT members |
| SAP ID | Person-to-person | Direct call between users; normal, not recorded | ❌ | per context |
| 4101 / 4110–4113 / 4120 | ERT Lead / Operators / Control | Dispatch/escalation targets; Operators + Control answer the queue | — | internal |
| 4200 / 4300 / 4400 / 4500 / 4600 | Medical / Security / Warden / Ops / IT | Dispatch targets (ctx_responder) — not queue answerers |
— | internal |
| 4700s | Fixed devices | Speakers / gate phones (ctx_fixed_device) |
— | fixed |
1. 111 — happy path¶
Caller dials 111; the call is recorded and given an incident ID before it rings anyone, so nothing is ever lost. The queue ring-alls every available ERT Operator position; the first to answer owns the incident, classifies it, and dispatches.
sequenceDiagram
autonumber
participant C as Caller (SAP ID)
participant A as Asterisk/FreePBX
participant R as MixMonitor + incident_id.sh
participant Q as ert_emergency_queue
participant O as ERT Operator position (4110–4112/4120)
participant T as Dispatch target (4200/4300/…)
C->>A: dial 111
A->>R: start recording · assign ERT-YYYYMMDD-NNNN
A->>C: answer + brief prompt
A->>Q: enter queue (ring-all available, 20s)
Q->>O: ring all available positions
O-->>Q: first position answers
Note over Q,O: escalation timer stops on answer
O->>C: "UPES Emergency Response… what & where?"
O->>O: capture 6 mandatory facts · classify
O->>T: dispatch (see §4)
O->>A: write incident notes · final status
A->>R: recording linked to incident ID
ASCII fallback (primary flow)
Caller ─dial 111─► Asterisk ─► [record + incident ID assigned FIRST]
│
▼
ert_emergency_queue (ring-all available ERT, 20s)
│ first position answers → timer stops
▼
ERT Operator: opening line → 6 facts → classify
│
▼
dispatch (target 4200/4300/…) → log → recording linked
- Recording covers the whole call, not just the bridged segment (MixMonitor).
- "Healthy" queue = ≥ 2 available positions (Drill SOP §4).
- Six mandatory facts and the opening line: ERT SOP Part A.
2. 111 — no responder → coach in parallel with reaching a human (disaster-ready)¶
Design principle (grounded in Emergency Medical Dispatch practice): a distressed caller must never sit in silence and must never be told to hang up and dial another number. The old serial ring-out (queue → Lead 20s → backup 20s → then voicemail) could leave a caller ~45–60s with no guidance before the one window that matters — so it was replaced. Now, the moment the queue times out, the system does two things at once:
- Alerts the ERT Lead + backup in the background (non-blocking Asterisk call-files,
alert_responders.sh) — their phones ring with a spoken alert and a "press 1 to join the emergency queue" option. This never holds the caller. - Immediately begins coaching the caller through the offline panic-coach
(
ctx_ai_helpline) — a deterministic first-aid decision tree (CPR / bleeding / choking / fire / lockdown / recovery / trapped), and logs a Missed Emergency Incident at once (severity critical, never auto-closed) so a human calls back regardless.
Meanwhile the caller can press 1 at any time during the queue to jump straight to
first-aid without waiting the queue out (fast-path, ctx_111_fastpath). Inside the coach,
9 = retry a responder (re-queues and bridges whoever has since become free) and
8 = leave a message → emergency voicemail. Nothing is ever a dead end, and every path
works with no internet and no AI service.
sequenceDiagram
autonumber
participant C as Caller
participant Q as ert_emergency_queue
participant K as Panic-coach (ctx_ai_helpline)
participant R as Lead 4101 + backup (background call-files)
participant M as missed_incident.sh / voicemail
C->>Q: in queue (press 1 any time → first-aid)
Q--xC: 20s, no responder
par Alert humans (non-blocking)
Q->>R: ring Lead + backup, "press 1 to join queue"
and Coach the caller now
Q->>K: begin first-aid guidance
K->>M: log Missed Emergency Incident (critical)
end
Note over K: 9 = retry a responder (re-queue) · 8 = leave a message
K-->>Q: caller presses 9 → re-queue → bridge a freed responder
K->>M: caller presses 8 → emergency voicemail
flowchart LR
Q["Queue 20s<br/>(press 1 → first-aid)"] -->|answered| DONE["Human handles"]
Q -->|no answer| P{"In parallel"}
P --> A["Background alert:<br/>Lead + backup ring<br/>press 1 to join queue"]
P --> K["Offline panic-coach<br/>+ log Missed Incident"]
K -->|"9 retry"| Q
K -->|"8 message"| V["Emergency voicemail"]
A -.->|"responder joins"| Q
- The coach + prompts:
../config/extensions_aihelpline.conf,../scripts/gen-coach-prompts.sh(offline TTS). - Background responder alert:
../scripts/alert_responders.sh. - Review workflow (listen → identify → call back → dispatch/close): ERT SOP Part F.
- EMD grounding (stay-on-line pre-arrival instructions; no redial loops): see Journal/Feature-Roadmap.md and the SOP 19 fallback matrix.
3. 199 — drill / test (isolated, DRILL-ONLY)¶
199 exercises the same shape as 111 so the mechanism is proven, but it is walled
off from real dispatch. Every artifact is stamped DRILL-ONLY so a drill can never
be mistaken for a real event.
sequenceDiagram
autonumber
participant C as Any authenticated user
participant A as Asterisk
participant Q as ert_emergency_queue (drill path)
participant O as ERT Operator (drill)
C->>A: dial 199
A->>A: label call DRILL-ONLY · start recording (marked drill)
A->>Q: simulate queue (ring-all, 20s)
Q->>O: ring position(s)
O-->>C: answer — practices flow
Note over O,C: NO real dispatch · NO real paging<br/>escalation/paging/conf only if ERT Lead enables drill-mode
O->>A: drill log written (DRILL-ONLY)
- Any authenticated user may self-test with 199; whether it exercises escalation/paging/conference is ERT-Lead-controlled drill mode (Drill SOP §1).
- Guardrails (never casually use 111, never surprise-page, never leave a simulated miss unreviewed): Drill SOP §7.
4. Dispatch — warm transfer & three-way bridge¶
The default is dispatch-without-transfer (keep the caller, separately call the team). Two other modes exist; blind transfer is discouraged because it drops ownership. The Operator stays Incident Owner until a handoff is confirmed.
4a. Warm transfer — responder must speak to the caller directly¶
sequenceDiagram
autonumber
participant C as Caller
participant O as ERT Operator (owner)
participant T as Responder target (e.g. Medical 4200)
O->>C: brief hold
O->>T: call target · brief the situation
T-->>O: "yes, I'll take it"
O->>C: reconnect + hand over
O->>T: transfer (ownership passes only on confirm)
Note over O: if T does NOT confirm → Operator keeps the caller
4b. Three-way bridge — serious / unclear / vague location¶
sequenceDiagram
autonumber
participant C as Caller
participant O as ERT Operator (stays on)
participant T as Responder target
O->>T: dial target into the call
T-->>O: joins
O->>C: three-way — responder questions caller directly
Note over C,T: Operator remains on the line & owns the incident<br/>recording continues across the whole call
| Mode | When | Ownership |
|---|---|---|
| Dispatch w/o transfer (default) | Help can be sent without caller talking to the team | Operator keeps it |
| Warm transfer | Responder must talk to the caller | Passes on confirm only |
| Three-way bridge | Serious / unclear / location vague | Operator stays & owns |
| ~~Blind transfer~~ | — | Discouraged (drops ownership) |
Full dispatch decision tree and quick-guide: ERT SOP Part C.
5. Silent-call protocol¶
A 111 that connects but is silent, whispering, or sounds like distress is treated as a real critical emergency — never a wrong number. The call already carries the caller's SAP ID (and location, if from a fixed device).
flowchart TD
S["111 connects · caller silent / whispering / distress"] --> H["DO NOT hang up<br/>listen to background"]
H --> P["Prompt: 'If you can hear me but can't speak, press any key'"]
P -->|DTMF keypress| K["Confirmed live silent emergency"]
P -->|no key, still open| K
K --> ID["Use SAP ID (identity) + registered/known location"]
ID --> D["Dispatch Security to known location<br/>discreet callback only if safe"]
D --> LOG["Log: silent emergency · severity critical · keep recording"]
- One number by design: someone hiding from a threat only has to remember 111 — there is deliberately no separate silent line to choose under pressure.
- Full protocol: ERT SOP Part I.
6. Paging a zone (700 with PIN)¶
Paging is a live one-way broadcast to fixed/shared devices. It is role-restricted; all-campus 700 requires a PIN and ERT Lead approval. Every attempt — allowed and denied — is logged.
sequenceDiagram
autonumber
participant O as Dialer (ERT Lead / authorized)
participant A as Asterisk (context check)
participant P as app_page
participant Z as Zone speakers (4700s)
O->>A: dial 700 (or 701–705)
A->>A: context allows paging code?
alt not authorized
A-->>O: denied
A->>A: log Emergency Paging Attempt (DENIED)
else authorized
A->>O: prompt PIN (700 = all-campus)
O->>A: PIN
A->>P: open page to zone
P->>Z: live audio: "Attention. This is UPES Emergency Response…"
A->>A: log Emergency Paging Attempt (OK)
end
- Zones: 700 all-campus, 701 academic, 702 hostels, 703 security gates, 704 medical/ERT, 705 admin/ops (Numbering Plan §4).
- Students/general staff are blocked from all paging codes; drill pages are prefixed "Drill, drill, drill." with prior notice.
- Message template and "use with care" rules: ERT SOP Part D.
7. Conference 9000 activation¶
9000 is the Main Incident Command Room — opened only for multi-team incidents or when the ERT Lead needs live coordination. It is recorded when active and PIN-gated.
sequenceDiagram
autonumber
participant O as ERT Operator / Lead
participant A as Asterisk (context + PIN)
participant B as app_confbridge 9000
participant R as Responders (Security/Medical/Warden/Ops)
O->>A: dial 9000
A->>A: role check + PIN
A->>B: create/join room · start recording (active incident)
O->>R: pull in relevant teams (they dial 9000)
R->>B: join (each join/leave logged)
Note over B: linked to Incident ID · limit 20 (side rooms 10)
- Side rooms 9001–9004 (Security / Medical / Warden / Ops) are not recorded by default.
- "Do not open 9000 for every call": ERT SOP Part E. Surge posture (broadcast first, pull coordination into 9000): ERT SOP Part J.
8. Student-to-student (normal call, not recorded)¶
Person-to-person calls by SAP ID are ordinary internal calls. They are not recorded
and get no incident ID — recording/logging is reserved for 111/199. Reachability is
governed by context (ctx_student / ctx_staff).
sequenceDiagram
autonumber
participant A as Caller (SAP ID)
participant PBX as Asterisk (ctx_student/ctx_staff)
participant B as Callee (SAP ID)
A->>PBX: dial callee SAP ID
PBX->>PBX: context permits this destination?
PBX->>B: ring
B-->>A: talk (no recording · no incident)
- Privacy by design: student calls stay private; only emergency traffic is recorded (Architecture §7).
9. 101 — AI assistant (future, always falls back to 111)¶
101 is a later phase and never sits in the 111 path. The AI triages, but on any urgency, uncertainty, or failure it escalates or falls back to 111 — the human-first line. 196 is its isolated test line.
flowchart TD
D["Caller dials 101 (later)"] --> AI["AI Assistant triages<br/>(isolated pipeline)"]
AI -->|urgent / unclear| E["Escalate to 111"]
AI -->|any AI/network failure| F["Fall back to 111"]
AI -->|clearly non-urgent info| INFO["Answer / guide · log"]
E --> H["111 human-first flow (see §1)"]
F --> H
sequenceDiagram
autonumber
participant C as Caller
participant AI as 101 AI Assistant (future)
participant H as 111 human-first path
C->>AI: dial 101
AI->>AI: triage
alt urgent / unclear / failure
AI->>H: hand off to 111 (recorded human flow)
else non-urgent
AI->>C: assist · log
end
Note over AI,H: 111 never depends on AI; AI never blocks 111
- Do not alias 101 to 111 — 101 is reserved for the AI (Numbering Plan §1).
- Design principle: 111 is human-first and AI always falls back to it (Architecture §7).
Cross-references¶
- Static architecture behind these flows → 02-System-Architecture.md
- Where recordings/incidents/logs live → 06-Numbering-and-Data-Map.md
- Network paths these calls traverse → 04-Network-and-Deployment.md
- Operate the flows → ERT SOP · Drill SOP