00:00Integrations
Fits beside the systems you already run
Rescuora reads a copy of the audio and writes only what a person confirms. Here is how it connects.
- In
- Call audio, radio audio, caller location
- Out
- Confirmed CAD fields, events, reports
- Identity
- SAML or OIDC single sign-on
00:04Connections
Five systems Rescuora connects to
Phone system and NG911
A SIP/RTP media fork of each call, plus caller location where your system provides it.
CAD
Confirmed fields pushed through your CAD's interface; we build connectors with pilot centers.
Radio
Optional audio from radio channels for Fieldora and Sonara.
Recorder and QA
Transcripts and tags for your existing quality-review process.
Identity
Single sign-on with your directory, with roles for each job.
00:09NVIDIA stack
What runs on the appliance
| Component | Used for | Product |
|---|---|---|
| Riva | Streaming recognition, translation, speech synthesis | Lingora, Fieldora |
| Maxine audio | Noise reduction on poor lines | Lingora |
| NeMo and Guardrails | Training models; keeping suggestions inside protocol | Sonara, Protora, Simora |
| TensorRT, TensorRT-LLM, Triton, NIM | Fast, concurrent serving | All |
| Jetson, IGX, Holoscan, DeepStream | Edge devices and sensor pipelines | Fieldora |
| Cosmos, Omniverse | Synthetic scenarios and the floor twin | Simora |
00:15API
Read what Rescuora produced, on the appliance
{
"call": "4127",
"fields": [
{ "name": "location", "value": "Rua das Flores 128, apt 3", "confirmed_by": "ct-07" },
{ "name": "incident_type", "value": "unresponsive", "confirmed_by": null }
]
}ExampleIllustrative request and response. The API is in design.
The API and event stream are served on the appliance, inside your network. Unconfirmed fields carry a null confirmer so your systems can ignore them.
Write access is limited to confirmation from the Rescuora console; other systems read only.
00:22Data formats
What Rescuora reads and writes
| Format | Direction | Used for | Status |
|---|---|---|---|
| SIP / RTP (G.711, Opus) | In | Call audio media fork | In design |
| PIDF-LO | In | Caller location from NG911 systems | In design |
| NENA EIDO (JSON) | Out | Incident data to CAD and other agencies | In design |
| OASIS CAP 1.2 | Out | Alerts to other systems | Planned |
| JSON Lines events | Out | Captions, tags, suggestions, confirmations | In design |
| WebVTT | Out | Transcripts for QA and recorders | Planned |
Dispatch
Send us your CAD interface specification
We will tell you how a connector would work and what a pilot needs from your IT team.