Call handling
With BitVoice, and without it
bitdispatcher takes the caller's location from any standards-compliant call-handling system. With BitVoice, BioDream's open-source phone system and 911 call handling, it uses every hook BitVoice offers a CAD. BitVoice is never required.
bitdispatcher takes caller location from any standards-compliant call-handling system: ALI spill over TCP or serial, NENA i3 PIDF-LO, and EIDO incidents (NENA-STA-024).
With BitVoice it also uses BitVoice's live event stream (calls ringing before answer, rebids, caller photos), sends EIDO both ways, texts the caller, sends a video link and shows live video, takes radio emergencies, acknowledges them both ways and shows unit positions from the radio system. The full list is in docs/BITVOICE.md. BitVoice is never required.
The standards at each boundary
| From | What | Standard |
|---|---|---|
| Any call-handling system | The caller's number, class of service and location | ALI spill over TCP or serial |
| Any NG911 system | The caller's location, with its uncertainty | NENA i3 PIDF-LO |
| Any NG911 system | The incident as the call-taker saw it, both ways | EIDO (NENA-STA-024) |
| BitVoice | Calls ringing before answer, rebids, caller photos and video, texting the caller | BitVoice's event stream and API |
| BitVoice's radio console | Emergency buttons, acknowledgement both ways, unit positions, last heard | BitVoice's radio webhook |
| The state's switch | NCIC inquiries, logged with purpose and reason | The state's message formats (a training simulator built in) |
The full list of BitVoice's hooks and how each is used: docs/BITVOICE.md.
The demonstration runs on a simulated BitVoice
Every 911 call, ALI record and radio event in the demo comes from the BitVoice simulator, and is marked SIMULATED.