Keryx Core
The call-handling engine at the centre of the emergency room.
Keryx Core receives every emergency call your centre is responsible for — from a rotary landline or a video-capable smartphone — and presents it to a call taker as one clean, location-aware event. Everything else in Keryx builds on it.
What it does
Emergency communication centres are living through a slow migration. Legacy selective routers still deliver a large share of traffic, while IP-native calls carrying text, video, and precise location arrive over next-generation networks. Most centres end up running two workflows side by side, and the seams show at the worst possible moment.
Keryx Core closes that gap. It terminates traditional telephony and IP emergency traffic in a single platform, normalises the caller, media, and location data into one record, and hands that record to the call taker — and to every downstream Keryx module — through one consistent interface. The room sees one queue, one screen, and one source of truth, whichever network the call travelled on.
Capabilities
Next-generation call handling
Designed around the NENA i3 architecture so calls arriving over an ESInet are answered, held, transferred, and conferenced with their full data payload intact.
Voice, text, and video in one queue
Real-time text and video sessions sit alongside voice calls in the same queue, with the same priority rules, so a caller who cannot speak is never routed to a second-class workflow.
Legacy and IP traffic, unified
Calls from selective routers and calls from IP networks land in the same interface. Call takers never need to know which path a call took to reach them.
Location you can act on
Caller location arrives as structured data — from carrier records or device-provided coordinates — and is plotted, validated, and attached to the call before the first ring finishes.
Policy-driven routing and overflow
Route by geography, skill, language, time of day, or load. When a centre is saturated or offline, overflow rules move calls to a partner agency automatically, with context attached.
An operator console built for pressure
Large targets, keyboard-first controls, and a layout that keeps the caller, the map, and the action buttons within a single glance. Nothing is more than one keystroke away.
Standards and interoperability
Built on the open specifications the emergency services community has already agreed on, so it connects to what you run today and what your network is migrating toward.
- NENA i3
- The functional architecture Keryx Core is designed around for next-generation emergency call handling.
- ESInet
- Interoperates with Emergency Services IP networks as the transport for NG911 and NG112 traffic.
- SIP
- Session signalling for IP-native emergency calls, transfers, and conferences.
- Real-time text
- Character-by-character text conversations carried in the same session as the call.
- PIDF-LO
- Structured caller location delivered with the call and rendered directly on the map.
- HELD
- Location retrieval from network location servers when the device does not supply it.
Why centres choose it
— Stays up when everything else is busy
Core is built to run across multiple sites with no single point of failure. A hardware fault, a network cut, or a regional outage reroutes traffic without a call taker noticing.
— One screen, not three
Call takers stop alt-tabbing between a phone system, a mapping tool, and a records screen. Core presents the caller, their location, and the next action together.
— The foundation, not the ceiling
Because Core owns the call record, adding dispatch, messaging, AI transcription, or wearable alerts means switching on another Keryx module — not integrating a new vendor.
Part of the Public Safety suite
See Keryx Core handle a live call.
We will walk your team through a call from first ring to hand-off, on your own scenarios. Tell us about your centre and we will set it up.