999/112 Call Answer and Queue Management

Overview#

Answer every 999 or 112 emergency call within mandated KPI ring-time, manage hold, transfer and conference workflows at the call-taker position, and link every session automatically to a single canonical incident record without any rekeying.

The call answer and queue management module is the operational front door of the PSAP. It covers the full call-taker workflow at the position: inbound delivery over both modern NG112/ESInet IP paths and legacy trunk presentation, ring-time enforcement with supervisor-visible KPI counters, one-touch hold and transfer controls, three-way conference, supervisor barge-in and whisper coaching, dual-channel session recording of both call audio and the call-taker screen, and automatic queue overflow to standby positions when primary staff are saturated. The queue model is designed for ambulance command-and-control reality: surge events must not wait for a free position, and every KPI breach must be visible to the supervisor before it becomes a clinical risk.

Every answered call is bound to a canonical incident record, so the call surface is never an island. The same incident spine is shared with CAD dispatch, AVL, EIDO context augmentation and the post-incident review surface.

Key Features#

• KPI-Bound Ring-Time Enforcement: Each call-taker position displays a live ring-time counter. The supervisor view escalates its colour state before the service-level threshold is reached, giving clinical governance leads advance warning rather than a retrospective breach report.

• Dual-Path Ingress: The position handles both modern ESInet IP delivery and legacy trunk presentation transparently, without the call-taker needing to know which path was used.

• Hold, Blind Transfer, Attended Transfer and Conference: Standard SIP call-control actions are exposed as one-touch controls at the active-call panel. Call state transitions, ringing, active, on hold, transferred, conferenced and ended, are tracked and audited throughout.

• Supervisor Barge-In and Whisper: A duty supervisor can join an active call silently to coach the call-taker, audibly to provide direct support, or fully to take over, at any point without dropping or alerting the caller.

• Dual-Channel Session Recording: Both the call audio and the call-taker screen are captured as a synchronised recording, producing a complete replay record for clinical governance, post-incident review and regulatory disclosure.

• Automatic Queue Overflow: When all primary positions are saturated, queued calls are routed to designated standby positions before a public ring-out can occur. The overflow event is logged against the call session for quality and audit purposes.

• Incident-Linked Call Sessions: Every answered call is automatically bound to a canonical incident record. A call cannot exist without an incident anchor, eliminating the risk of a disconnected call record that never reaches dispatch.

• Edge-Optimised Signalling: Call signalling and session orchestration are handled at the network edge, keeping the position console responsive under surge load even when the originating control room is geographically distant from the platform.

Use Cases#

Routine 999 and 112 Ambulance Call Answer#

A call-taker answers within KPI, captures the chief complaint using the integrated protocol card, and the call is automatically bound to a new canonical incident ready for CAD dispatch.

Mass Casualty Surge#

Inbound call volume exceeds primary position capacity. Queue overflow activates standby positions, ring-time KPI is preserved, and the supervisor view shows real-time queue depth and overflow status for every active call.

Supervisor-Assisted Difficult Call#

A duty supervisor whispers coaching to a call-taker handling a clinically complex caller, then joins audibly when escalation is needed. There is no disruption on the caller side and the full session is recorded.

Cross-Service Transfer#

A 999 call originally handled by ambulance command-and-control is conferenced with fire control, then transferred. The complete session recording and all call-control events remain linked to the same incident record.

Post-Incident Clinical Review#

A clinical governance lead replays the synchronised audio and screen recording of a call that preceded an adverse outcome. The call session is traceable through to the dispatch decisions and resource assignments made against the same incident.

Integration#

• Unified Incident Spine: The call answer module is one ingress channel of the platform's shared incident record. Every answered call carries an enforced reference to a canonical incident, so CAD dispatch, AVL and post-incident review surfaces all work against the same identifier.

• CAD Dispatch and AVL: Once an incident is created from a call, resource assignment in the CAD and vehicle tracking in the AVL surface use the same incident identifier, preventing any drift between the call that created the incident and the resources tasked to it.

• EIDO Context Augmentation: Incidents created from calls are immediately eligible for enrichment from nearby responder positions, maritime and aviation assets through the EIDO augmentation module.

• Call-Taker Console: The call-taker interface exposes queue depth, overflow state and per-call ring-time in a dedicated queue panel alongside the active-call controls, giving a single-screen operational picture at the position.

• Clinical and Regulatory Review: Dual-channel session recordings are addressable from the post-incident review surface using the same incident identifier, so audio, screen capture and dispatch decisions can be reconciled end-to-end.

• REST and WebSocket APIs: Queue state, call-session events and KPI counters are available to supervisory dashboards and external quality-assurance systems over authenticated REST and real-time WebSocket channels using standard JWT bearer tokens.

Open Standards#

• NENA-STA-010.3 (NENA i3): The core Next Generation 9-1-1 architecture standard covering ESInet routing and the BCF, ESRP, ECRF and LVF functional elements that the platform's call ingress path implements.

• NENA-STA-012: The NENA standard governing PSAP session recording architecture, which defines the recording metadata and session structures used for dual-channel call capture.

• ETSI TS 103 479: The European NG-eCall and NG112 architecture standard defining the modern emergency call delivery model used alongside legacy trunk presentation.

• IETF RFC 3261 (SIP): The Session Initiation Protocol, used for inbound call delivery, hold, transfer and conference control at the position.

• IETF RFC 7865 (SIPREC metadata): The SIP-based session recording metadata protocol, used to carry recording session descriptors and participant information to the session recording server.

• IETF RFC 7866 (SIPREC protocol): The session recording protocol defining the SIP-based mechanism for establishing and managing dual-channel recording sessions.

• IETF RFC 7852: Additional Data Related to an Emergency Call, defines the structured data blocks carrying caller location, subscriber information and service provider details delivered with inbound calls.

• IETF RFC 5222 (LoST): The Location-to-Service Translation protocol, used to map incident geographic coordinates to the responsible PSAP service URN during call routing.

• IETF RFC 4103 (RTT): Real-Time Text over SIP, supporting text-based emergency communication at the position for callers who cannot use voice.

• IETF RFC 2198 (RTP Redundancy): RTP payload redundancy encoding used to improve resilience of real-time text media streams over lossy paths.

• ETSI TS 102 634: eCall in-vehicle system to PSAP messaging, relevant to voice-supplemented eCall sessions ingested alongside standard PSAP calls.

• TLS 1.3 (RFC 8446): Mandatory transport security for all call signalling, media control and recording traffic between the session border controller, the platform and the recording infrastructure.

• W3C WCAG 2.2: Accessibility baseline for the call-taker console and supervisor view, ensuring positions remain usable across the full range of operator vision, motor and cognitive needs.

Security and Compliance#

All call signalling and media control between the session border controller and the platform uses mutual TLS with certificate validation. Recording sessions are access-controlled and tenant-scoped; a user in one tenant cannot address the recordings of another. Every call session event, KPI breach and recording issuance is written to an immutable audit log. Dual-channel recordings are retained in accordance with the applicable national emergency services regulatory framework and are accessible only through authorised clinical governance and legal disclosure workflows.

Last Reviewed: 2026-05-05 / Last Updated: 2026-05-05